How to Brief a Buyer Presentation for a Technical Sale

A buyer presentation is easier to commission when the brief names the commercial decision before it names the slide count. This guide is the client-side brief for that job. How Deep Tech Brand and Pitch Work Is Scoped covers the wider question of project scope and fees.

Name the reader, the stage and the decision

Every buyer presentation starts from three answers. Who receives it, when in the buying process, and what they have to decide. A buyer's organisation meets a supplier several times, and each meeting has a different reader. A sourcing team shortlists suppliers. A sustainability lead builds the internal business case. Technical and risk teams run diligence. Procurement, finance and legal approve the purchase. Those readers may need different sections, a forwarded memo or separate presentations. Scoping chooses the smallest suitable material for the first decision.

Then name the ask. It is the commitment this reader can give at this stage, such as a trial, a sample programme, a reservation of capacity or a place on a supplier list. From Pilot to Purchase shows how to size the smallest defensible commitment.

Take a materials company that meets a brand's sourcing team in six weeks. The reader is the head of sourcing. The stage is shortlisting suppliers for a trial. The decision is whether to add the company to the trial list, and the ask is a sample request with a named technical contact. The case the sustainability lead later takes to finance is a second presentation, with its own reader and its own ask.

Name one more reader, the colleague the presentation will be forwarded to. What Your Buyer Has to Defend After You Leave the Room covers what that person needs.

Build the intake from files and a kickoff

Read what already exists

Intake comes before any writing. We ask for everything a buyer has already seen and everything the team relies on when it answers questions.

Intake checklist

1. The current deck, and the last version sent to a buyer.
2. Proposals, offers and term sheets already in circulation.
3. Pilot reports, test data, certifications and methods.
4. The price basis and the commercial terms on offer.
5. Buyer emails and meeting notes the team is authorised to share internally, with personal and confidential details protected.
6. The objections the sales team hears, in the buyer's words.
7. Existing personas, case studies and website pages.
8. Brand guidelines, templates and source files.
9. The people who will sign off technical, commercial and legal claims.

We then read the current material in the order the buyer meets it and stop at the first unresolved question, unsupported claim or ask the reader cannot act on. The Belief Gap, the 2026 guide by Aaron C. Leaman, calls that point the First Break. Start With the Decision sets out the method. The same read checks the six gates, which are evidence, economics, incentives, authority, capacity and timing, and regulation. If the price fails against the buyer's current supplier, or the reader has no authority over the decision, the presentation waits and the scope changes. When Better Communication Is the Wrong Answer works through each gate.

Case strategy and the narrative read

Case strategy decides what the presentation argues. It fixes the opening problem in the buyer's terms, the product and application that lead, the evidence behind each claim, the comparison the buyer will make, the price basis shown and the single ask at the close. Some of those choices belong to the company. We write them into a short case note, and the team signs it off before any slide is written.

The narrative read tests the existing story against the reader. We look at where the technology appears relative to the buyer's problem, where the first number lands, which objections already have answers and what the last slide asks for.

A useful case note is short enough for the commercial, technical and design teams to approve before slide writing begins. It records the buyer problem, the first application or project, the comparison the buyer will make, the evidence that carries the claim, the commercial basis shown and the single ask. When the team cannot agree one of those lines, the brief has found work that comes before design.

Pair the document drop with a short kickoff. The data room shows what exists. The kickoff shows which files the team trusts, which offers are current, which buyer questions keep returning and which claims are still waiting for evidence. The two together are more useful than asking a founder to remember every relevant file in one meeting.

A company that arrives without personas can draw the same list of objections from its own meeting notes during intake.

The evidence check

Every claim in the presentation goes into a register before design starts. Each row records the claim, the slide it sits on, its source, its status and the person at the company who approves it. Record evidence maturity and permission as separate fields. These labels answer different questions.

Evidence status

• Measured or observed. State the test, date, conditions and limitations.
• Modelled or forecast. Name the assumptions and responsible owner.
• Contracted or documented. Identify the agreement or record and the obligation it actually creates.
• Missing or under review. Hold the claim, narrow it or state the open evidence requirement.

Sharing permission

• Public. Approved for the named public use.
• Under NDA. Permitted for a specified recipient and purpose under the relevant agreement.
• Internal. Not approved for external circulation.

A claim goes on a slide once its wording, evidence status, source and permitted use have been approved by the company’s responsible owner. A pending claim is narrowed to what the evidence supports, or held back, and we say what evidence would strengthen it. The company approves every technical, legal and commercial claim. Our check confirms that each claim matches its source. Independent verification of a project or product sits with specialists and is scoped separately. For pilot results, the four labels in From Pilot to Purchase separate what was observed from what is inferred.

Design, speech and review rounds

Scope the format with the setting. A presentation shown live needs a speech or speaker notes. One forwarded inside the buyer's company has to read on its own, so its slides carry full sentences and the source beside each figure. Many presentations need both, and the scope says so. Design covers the information design, charts redrawn from source data and checked against it, and the template, either the company's own or one built for the piece. The company receives the editable source files.

The scope fixes the review rounds and who takes part in each. A typical sequence has four checkpoints.

1. Case note. The team approves the argument, the reader and the ask.
2. Full draft text. One internal owner returns consolidated comments.
3. Designed draft. The team reviews the layout, the charts and the speech.
4. Factual approval. Named experts approve each claim on the final file.

The internal owner gathers comments and resolves conflicts between them within an agreed response window. Extra rounds and extra audience versions are scoped as additions.

From one presentation to a programme

The first presentation leaves reusable work behind, in the case note, the claim register and the design system. Later pieces are cut from the same case for other readers at other stages. Typical next pieces are the business case a sustainability lead takes to finance, a diligence presentation for technical and risk teams, an offtake or reservation offer for procurement, finance and legal, and one presentation for each project or product a buyer might shortlist. What Is an Offtake Agreement sets out how those commitments differ, and the commercial proposal holds the terms once a buyer agrees the next step.

The company sets the order. Three tests help.

• Where deals stop. Start at the stage where buyers most often go quiet.
• What has a date. Build first for the meeting already in the diary.
• What the others depend on. Build first the piece the others will cite, often the presentation on evidence and integrity.

Once buyers respond, record which questions changed, which evidence they asked for and which next document the account needs. That record decides whether the first presentation remains enough or becomes the core for a wider set of buyer materials.

The scope on one page

Fill this sheet in with your own team before you brief any studio.

One buyer presentation, scoped

• Reader. Name, role and function.
• Stage. Where they sit in the buying process.
• Decision. What they decide after reading it.
• Ask. The one commitment the close requests.
• Second reader. Who it will be forwarded to, and what they own.
• Setting and date. Live, forwarded or both, and the date of the meeting.
• Existing material. The intake list, with gaps marked.
• Claims and approvers. The register, and who signs each type of claim.
• Review rounds. The checkpoints, the owner and the response window.
• Outside the scope. Extra versions, independent verification, website changes.
• Next piece. The presentation that would follow, and the test for choosing it.

If the team cannot fill in the decision or the ask, start there, because the rest of the sheet depends on both. To set two studios' proposals for this work side by side, use the four-layer sheet in How to Compare Branding and Website Quotes.

One buyer presentation can be a first engagement with Brighter Future. Our Buyer & Commercial Cases work covers the case strategy, narrative, writing, design and speech, and can grow into a programme of pieces in the order you set. If a buyer decision has stalled and the cause is unclear, The Belief Diagnosis finds where it stopped.

Sources and further reading

• The Belief Gap, Aaron C. Leaman, version 1.1, Brighter Future, 2026