Template

Sales proposal deck

A sales proposal deck contains three things, in this order: the offer, the evidence, the price. In practice that is sixteen slides — the buyer's problem in the words they used, what it is costing them now, your recommendation and what it includes, proof it has worked for someone comparable, then the price, the exclusions, the timeline and one specific next step. Everything else that ends up in these decks — company history, team photographs, a values slide — belongs in an appendix or nowhere. The test for any slide is whether cutting it would make the buyer less likely to sign; if the answer is no, it is padding, and you are asking a busy person to pay for it with their attention.

16 slides

The slide order

  1. 01
    Cover

    This document is a proposal for this named company, prepared on this date, by these people.

    Avoid: Using your standard pitch cover, so the first thing the buyer sees is a slide that was not made for them.

  2. 02
    Their situation

    Here is where you are today, described the way you described it to us.

    Avoid: Translating what they said into your category language, which reads as a template and tells them you were not listening.

  3. 03
    What it costs today

    The current situation costs you this much money, time or risk per month.

    Avoid: Leaving the cost qualitative. "Inefficient" has no budget attached to it; nine days of finance time a month does.

  4. 04
    The brief, restated

    This is what you asked us to solve, and this proposal covers exactly that.

    Avoid: Quietly widening the brief here to justify a bigger number. The buyer notices, and it costs you the benefit of the doubt on every later slide.

  5. 05
    Recommendation

    We recommend this one thing, in one sentence, and the rest of the deck defends it.

    Avoid: Presenting three equally weighted approaches. An unmarked menu hands your job back to the buyer.

  6. 06
    How it works

    This is the mechanism that turns your problem into the outcome we just promised.

    Avoid: An architecture diagram drawn for your engineers. The reader needs the causal chain, not the component list.

  7. 07
    What you get

    These are the concrete deliverables, with quantities and dates attached.

    Avoid: Verbs without nouns. "Ongoing optimisation" is not a deliverable and cannot be checked off.

  8. 08
    The product itself

    This is what it looks like in use, shown rather than described.

    Avoid: A blurred screenshot scaled up from a sales email. If the product slide looks cheap, so does the product.

  9. 09
    Results elsewhere

    A comparable customer got this measurable result in this amount of time.

    Avoid: A percentage with no baseline. "Up 40%" from an unnamed starting point is read as marketing and discounted entirely.

  10. 10
    The reference

    A named person at a named company will say this about working with us.

    Avoid: An anonymous quote from "a Fortune 500 client". Unattributable praise is worth less than no praise.

  11. 11
    Who else uses it

    Companies that look like yours have already made this decision.

    Avoid: A logo wall of everyone you have ever invoiced. Fifteen irrelevant logos are weaker than four peers.

  12. 12
    Price

    The cost is this number, over this term, and this is the variable that moves it.

    Avoid: Burying it, deferring it, or splitting it across two slides so no single figure can be quoted back to you.

  13. 13
    What is not included

    These specific things sit outside this price, and here is what they would cost.

    Avoid: Skipping this slide to keep the mood positive. Every exclusion you omit becomes an argument during delivery.

  14. 14
    Timeline and owners

    Work starts here, lands here, and these named people on both sides own each stage.

    Avoid: A timeline with no obligations on their side. It hides the fact that your dates depend on their access and their data.

  15. 15
    Terms and risk

    Here is the contract term, the notice period, the security position and what happens to your data at the end.

    Avoid: Leaving this for procurement to ask about later. Late questions become late deals.

  16. 16
    The decision

    This is the exact next action, with a named person and a date.

    Avoid: Ending on a thank-you slide. Gratitude is not an ask, and a proposal that ends on nothing gets answered with nothing.

A sales proposal deck is not a shorter pitch deck. A pitch argues that your company should exist; a proposal argues that this buyer signs this scope at this price this quarter. The second is harder, because the reader already knows you and is hunting for reasons to say no.

Why does the proposal open with their problem and not your company?

Because the first ninety seconds decide whether the rest is read as an argument or skimmed as a brochure. If slide 2 is your founding story and your office map, you have told the buyer this document existed before the discovery call. Everybody recognises a template, and they stop reading for meaning and start scrolling for the number.

Open with their situation instead, in the words they used — not paraphrased into your category language, the actual sentence from the call. If the operations director said the team spends the first week of every month reconciling invoices by hand, that sentence goes on slide 2 verbatim. It proves you listened, and it fixes the problem definition to one you can solve. A buyer who accepts your statement of the problem has accepted most of your answer.

  • Quote them, do not summarise them. A direct quotation from discovery is the cheapest credibility available to you.
  • Put a number on the problem before you put one on the price. A figure they can check makes the later figure arguable rather than arbitrary.
  • Name who inside their organisation is affected. A problem with no owner has no budget behind it.
  • Stop at three problems. Seven reads as a survey, and a proposal solving everything sells nothing.

Where should pricing go in a proposal deck?

On a slide of its own, after the evidence and before the timeline. In a sixteen-slide proposal that is slide 12. Not the appendix, and not a line offering to discuss commercials.

Hiding the price is the most common mistake in this document and an expensive one. The buyer skips ahead regardless; everyone who has ever read a proposal looks for the number first. All that withholding achieves is that they find it while irritated, out of order, without the evidence you spent eleven slides assembling. Worse, a proposal with no price cannot be forwarded — and it will be, because the person you presented to is rarely the one who approves it.

If the number is not in the deck, the deck cannot circulate without you. That is not restraint. It is a bottleneck you built yourself.

Show it as a small table: the fee, the term, what is included, then one sentence naming the variable that moves it — seats, sites, volume. Offer three options at most and mark one as recommended. Put every discount beside its condition, because a discount with no condition tells the buyer the first price was invented.

Should you send the deck before the call?

No. Send a one-page summary before and the deck after. Read at speed in an inbox by someone hunting for the price, a proposal sets the meeting up to start from its worst reading. Sending afterwards costs nothing: the follow-up email is the version that gets forwarded anyway.

What is the difference between the deck you present and the deck you leave behind?

The same slides carrying different amounts of text. Pretending there is no difference produces the document everybody hates: too dense to read on screen, too thin to be useful a week later. In the room the slide is the headline and you are the body copy. The leave-behind has to survive a finance director who never met you.

  • Presented: one claim per slide, a heading of six to ten words, the chart arguing.
  • Leave-behind: the same slides plus a caption under each chart saying what it shows and where the data came from.
  • Leave-behind: assumptions come out of the appendix. They are the first thing anyone forwarding your proposal gets asked about.
  • Both: an identical price slide. Two versions of one number is how deals die.

Build one deck and export the reading version. Slideable's PDF export is vector quality, so slide 9's chart stays sharp when the CFO prints it, and a share link re-publishes without the URL changing — fix a typo and nobody has to work out which link is current.

How do you get a proposal past procurement?

Procurement is not your buyer. They are not judging whether the recommendation is right; they are checking that it is comparable, defensible and low-risk to sign. They kill deals late, by attrition, over things your champion never mentioned. Answer them in the deck, not across three weeks of email.

  • State the term, the notice period and what happens to their data at the end — all three, on one slide.
  • Give the price a unit. Procurement benchmarks, and a total with no unit gets compared against something you did not pick.
  • Name who has already reviewed your security position; a wall of comparable customers works better than a certificate list.
  • Say what is out of scope. The exclusions slide is not defensive; it is what makes the inclusions believable.
  • Put a named person and a date on the next step. "Signed by 14 March, Priya countersigns" beats looking forward to hearing from you.

What should you build it in?

Slideable ships this proposal as a 16-slide template, one of 94 layout archetypes, with the widgets it needs: device mockups, pull quotes, logo walls, QR codes. Its eight chart types are edited in place, in the deck's brand palette, with no spreadsheet step — the results chart is the slide people quietly drop when building it costs forty minutes. Every slot carries a character budget the box was drawn for, so the leave-behind cannot creep into eight-point type. It runs in the browser with no account, and an MCP server exposes 14 tools, so an agent in Claude, Claude Code, Cursor or Codex can draft and review the argument with you.

Common questions

How long should a sales proposal deck be?
Sixteen slides is the working length for a considered B2B proposal: eight on the offer, three on evidence, five on price, scope and terms. Below about ten slides you have not shown enough evidence for a buyer to defend the decision internally, and above about twenty you are relying on an appendix nobody opens. Length is not the real constraint anyway — one claim per slide is, and a deck that obeys that rule tends to land near sixteen.
Should the price be in the proposal deck or a separate document?
In the deck, on its own slide, roughly three quarters of the way through and after the evidence. A proposal without a price cannot be forwarded to the person who actually approves it, and that person is rarely the one you presented to. Keep the separate document for the contract and the detailed rate card; the deck needs the headline number, the term and the one variable that changes it.
What is the difference between a pitch deck and a sales proposal deck?
A pitch deck argues that a company or an idea is worth backing, and it is aimed at investors or at a first meeting. A sales proposal deck argues that one specific buyer should sign one specific scope at one specific price, and it is aimed at someone who already knows who you are. The proposal therefore opens with the buyer, not with you, and it must contain commercial detail — price, exclusions, timeline, terms — that a pitch deck never carries.
What should the last slide of a proposal say?
The exact next action, with a named person and a date on it: a signature by a given day, a pilot start, an introduction to their security team. A thank-you slide ends the document on nothing and invites a reply that also says nothing. If you cannot name the next action, the proposal is not finished, because you do not yet know what you are asking for.
Do you send the proposal deck before or after the meeting?
After. Sent in advance, a proposal is read at speed in an inbox by someone searching for the price, and the meeting then begins from their worst reading of it. Send a one-page summary beforehand so they can prepare, present the deck live, then send the PDF as the follow-up — that PDF is the version that gets forwarded internally, so it is the one worth writing captions and assumptions into.

Other deck types

Build the deck instead of describing it.

Runs in the browser. No account needed.

Start now