Guide · 8 min read

How to structure a sales deck that closes

A ten-part structure for a sales deck that moves a deal forward: the buyer's problem, the cost of waiting, proof, objections, pricing and next step.

Published 27 October 2026

A sales deck has one job: move the deal to its next stage. It is not a brochure, a company history or a tour of every feature you have built. When a deck fails, it is usually because it is organised around the seller instead of the buyer. The slides follow the order of your product, not the order of the buyer’s thinking.

The structure below fixes that. It has ten parts, and each one answers a question the buyer is already asking, whether or not they say it out loud. Use it as a starting point for any deck you present to a prospect, then adjust the depth of each part to the meeting in front of you.

Start before the first slide

The best structure in the world will not save a deck built for the wrong audience. Before you open a file, write down three things:

  • Who will be in the room. A head of finance, an operations lead and an end user care about different things. List their roles and what each one is measured on.
  • What a win looks like for them. Not for you. A lower cost per order, fewer manual steps, a launch that ships on time.
  • What you want to happen after the meeting. A second call with the technical team, a pilot, a signed order. Be specific.

If you can’t fill in all three, you need another discovery conversation more than you need a deck. Everything that follows depends on these answers.

The ten parts at a glance

Part The buyer’s question Typical slides
1. Their problem Do you understand my situation? 1 to 2
2. Your value in one line Why should I keep listening? 1
3. The cost of doing nothing Why change now? 1
4. The solution as a bridge How does this solve my problem? 2 to 4
5. Proof Why should I believe you? 1 to 3
6. Objections What could go wrong? 1 to 2
7. Pricing What will it cost, and is it fair? 1
8. The next step What do you want me to do? 1
9. Design for clarity (Not a slide; it applies to all of them)
10. The appendix Where is the detail if I want it? As needed

That is roughly ten to sixteen slides for a typical first presentation. If you want a deeper look at length for different kinds of meetings, see how long a sales deck should be.

Part 1: open with their problem

Your first content slide should describe the buyer’s world, not yours. Name the challenge they deal with every week in words they would use themselves. If your discovery call surfaced a phrase like “we re-key every order twice”, put that phrase on the slide.

It shows you listened, and it gives the buyer something to agree with early, which turns the meeting into a conversation rather than a pitch.

Leave your logo wall, founding story and office locations for later, or for the appendix. They answer a question nobody has asked yet.

Part 2: say what you deliver in one sentence

Once the problem is on the table, state the outcome you provide in a single sentence. A useful pattern is: we help [this kind of team] [achieve this result] without [the usual pain].

For example: “We help mid-sized distributors process orders the same day without adding headcount.” The sentence should be specific enough that a competitor couldn’t use it unchanged. If it could describe any company in your category, keep sharpening it.

Part 3: make the status quo expensive

Plenty of deals are lost not to a competitor but to “not now”. Your deck has to make waiting feel like a choice with a cost.

Show what the current problem costs in terms the buyer already tracks: hours spent, errors made, revenue delayed, customers lost. Use their numbers where you can, gathered during discovery, and label any estimate as an estimate. A simple slide that says “at your current volume, manual re-keying takes about 40 hours a month” is more persuasive than a dramatic industry chart, because the buyer can check it.

Part 4: present the solution as the bridge

Now, and only now, introduce what you sell. Frame it as the bridge between the problem in part 1 and the outcome in part 2.

The simplest way to do this is to map capabilities to problems. For each pain you named, show the one part of your product that addresses it. If a feature doesn’t connect to a problem on an earlier slide, it probably doesn’t belong in this deck. Keep it for the demo or the appendix.

A screenshot with one clear annotation does more than a slide listing eight features.

Part 5: prove it

Every claim in parts 2 to 4 needs support the buyer can check. Good evidence includes:

  • results from a pilot or trial, with the method described;
  • before-and-after numbers for a comparable situation, clearly labelled;
  • a short walk-through of how the product handles the buyer’s actual scenario;
  • references the buyer can speak to directly, if you have them.

Avoid adjectives standing in for evidence. “Fast”, “powerful” and “seamless” ask the buyer to trust you. A specific, checkable fact lets them decide for themselves.

Part 6: handle objections early

By this point, the buyer has doubts. Common ones are price, the risk of switching, the effort to implement and whether your company will be around in three years. Raising them yourself, before the buyer does, is a sign of confidence.

A single slide that names the two or three objections you hear most, each with a short, honest answer, often defuses them before they harden. There’s more on building these slides in how to handle objections on a slide.

Part 7: make pricing clear

If pricing belongs in this meeting, show it plainly. One slide, a small number of options, and the assumptions behind each one. For example, a deck for an Indian mid-market buyer might show two plans in ₹ per user per month, with what is included in each and the minimum term.

A buyer who can’t explain your pricing to their finance team will struggle to get the deal approved.

If pricing depends on scoping, say so, and explain what you need to produce a quote. That becomes a natural next step.

Part 8: end with one next step

The final slide should ask for one specific action. Not “questions?” and not a menu of five options. Choose the step you wrote down before you started: a technical review on a named date, a two-week pilot with agreed success measures, a signature on the order form.

Write it as a short plan if that helps: what happens, who is involved, and when. Then stop talking and let the buyer respond.

Part 9: design for clarity

Design is not a separate step at the end. It runs through every slide:

  • One idea per slide. If a slide makes two points, split it.
  • Headlines that say the point. “Manual re-keying costs 40 hours a month” works better than “Current process”.
  • Generous space and consistent type. A crowded slide reads as a complicated product.
  • Charts with one message. Highlight the bar or line that matters and mute the rest.

A good test is to read only the slide headlines in order. If they tell the whole story on their own, the deck is well structured.

Part 10: use the appendix

Detail that some buyers need, and others don’t, belongs after the closing slide: security information, integration diagrams, implementation timelines, the full feature list, your company background. The main deck stays focused and you still look prepared.

Adjusting the structure to the meeting

The ten parts stay the same, but their weight changes with the stage of the deal.

  • First meeting: spend most of the time on parts 1 to 3. Keep the solution brief and the next step modest, such as a follow-up demo.
  • Demo or deep dive: keep parts 1 to 3 to a quick recap and give parts 4 and 5 the most room.
  • Final presentation to a buying group: cover all ten parts, with more weight on proof, objections and pricing, because new stakeholders may be seeing your story for the first time.
  • A deck that will be sent rather than presented: write fuller headlines and add short notes, since you won’t be there to explain each slide.

Keep a master deck and adapt a copy for each meeting. Rewrite the problem slides in each prospect’s own words.

Delivery matters as much as structure. Rehearse the move from proof to pricing out loud, and see this walk-through of sales presentations that close deals for more on the delivery side.

A one-page outline to start from

Copy this into your notes before you build the next deck:

  1. Audience: who is attending, and what is each person measured on?
  2. Problem: the challenge, in the buyer’s own words.
  3. Value line: we help [who] [achieve what] without [which pain].
  4. Cost of waiting: what the status quo costs, in the buyer’s numbers.
  5. Solution: one capability for each problem named.
  6. Proof: the evidence that supports each claim.
  7. Objections: the two or three you expect, with honest answers.
  8. Pricing: options, assumptions and what’s included.
  9. Next step: one action, with a date and owner.
  10. Appendix: the detail to keep in reserve.

Fill in the outline first and the slides become much easier to write. It is also exactly what you can hand to SalesDeck to draft a structured, on-brand sales deck from your notes. For the decks your team makes outside the sales cycle, such as all-hands updates, training sessions or internal reviews, Presentations.AI is a good fit for the rest of your team’s decks.

All guides and articles