This guide is for account executives, solution consultants, and pre-sales leads who present to buying committees of several people and see the same deck reused from first call to final defense. If you sell a single product to one decision maker in one meeting, a short demo will do more for you than anything below.
A sales deck is a slide presentation that walks a buyer from a change in their world to a decision about your solution, with the proof they need to defend that decision internally. In a complex B2B sale, there is no single deck: there are at least three, one for the first meeting, one for the tailored proposal, and one for the orals or RFP defense. Each has a different audience, a different job, and a different slide order. Most published guides treat them as one file, which is why decks go stale after the first call.
Key takeaways
- A sales deck in a complex B2B deal comes in three forms: a first-meeting deck, a tailored proposal deck, and an orals or RFP defense deck.
- Andy Raskin's analysis of the Zuora deck sets a five-part narrative: a change in the world, winners and losers, a promised land, features as gifts, and evidence.
- Guy Kawasaki's 10/20/30 rule (ten slides, twenty minutes, thirty-point font) was written in 2005 by a venture capitalist listening to founder pitches.
- In US federal procurement, FAR 15.102 lets an agency require part of a proposal as an oral presentation, with time limits and media rules set in the solicitation.
- A proposal deck tailored for a buying committee changes the problem slide and the proof slide for each role, while the narrative spine stays the same.
What is a sales deck, and how is it different from a pitch deck?
The first sells a solution to a buyer, while a pitch deck sells a company to an investor. The two share a format, but the audience, the question, and the proof are different. Confusing them is the root of many weak decks.
An investor asks whether the company will grow. A buyer asks whether this solution will fix a problem they own, at a risk they can accept, faster than the alternatives. A pitch deck built for fundraising therefore leads with market size, traction, and team. A buyer-facing deck leads with the buyer's situation and ends with a decision the buyer can take.
The confusion is visible in the advice itself. Many guides on slide count quote a rule designed for investor meetings, as the section on slide count below shows. The format looks the same, so the rules travel across contexts without anyone checking where they came from.
Which deck does a complex deal need at each stage?
A complex deal needs a different deck at each stage because the audience grows and the question changes. At the first meeting you talk to one or two people about a problem. At the proposal stage you write for a committee that will read the deck without you. At the orals stage you defend a submitted offer against scoring criteria.
The guides that rank for this topic list deck types (intro deck, demo deck, case study deck, pricing deck), but they sort them by content, not by deal stage. That is the gap. A deck sorted by content tells you what to put in. A deck sorted by stage tells you who reads it and what decision it has to unlock.
The first-meeting deck should be short because the meeting is for listening. A practitioner on Reddit put the problem plainly in a thread titled "Ditch the pitch? Should sales presentations still be a thing?": "the deck we are supposed to use for first calls is 30 slides." The fix is not fewer slides for their own sake. It is a deck that leaves room for the questions a discovery call is meant to answer.
How should a sales deck be structured?
A solid sales deck structure follows a narrative: a change in the buyer's world, the stakes of that change, a target state, how your solution gets them there, and the evidence that it works. This spine comes from Andy Raskin's analysis of the Zuora deck, the first result in our search for this keyword. Dock and Pitch, two of the three competitor guides we reviewed, both point back to it.
In "The Greatest Sales Deck I've Ever Seen", Raskin breaks the Zuora narrative into five elements. He advises against opening with your product, your investors, or your clients. Instead, "name the undeniable shift in the world that creates both (a) big stakes and (b) huge urgency for your prospect." He adds that the promised land "is a new future state, not your product or service."
For a complex B2B deal, we adapt that spine into the following slide order. It works for a proposal deck of ten to fifteen slides.
- The change: one slide naming the shift that affects the buyer's market or operations, in their words.
- Winners and losers: what happens to organizations that adapt and to those that do not.
- The buyer's situation: what you learned in discovery, quoted back with their figures and constraints.
- The target state: concrete criteria for success, agreed with the buyer before you show the solution.
- The approach: how your solution closes the gap, framed as answers to obstacles, not a feature list.
- Value by stakeholder: one slide or one row per role in the buying committee (see the stakeholder section below).
- Proof: a customer result from a similar context, attributed to a named customer.
- Plan and risks: the implementation steps, the owners on both sides, and the risks you have already identified.
- Commercials: the price structure and what it includes, if this stage of the deal calls for it.
- Next decision: one specific step, with a date and an owner, not a generic "questions?" slide.
The plan slide is where many decks stop being presentations and start being commitments. If you already run a mutual action plan with the buyer, the plan slide should be a snapshot of it, not a second version that drifts away from it.
How many slides should a sales deck have?
There is no fixed number: ten to fifteen slides suits a proposal deck, and fewer suits a first meeting. The sources that rank for this question disagree, and the disagreement comes from where their rule was born.
Dock's list of examples recommends Guy Kawasaki's 10/20/30 rule as a slide-count standard. Vibe's guide suggests ten to eleven slides, and twelve to fifteen for complex deals. The original rule has a specific context. Kawasaki published it in 2005 and opens with "As a venture capitalist, I have to listen to hundreds of entrepreneurs pitch their companies." His ten slides include business model, team, and projections, which are investor topics. He does say the rule applies to "making a sale", but the slide list he gives is a fundraising list.
Our position: keep the twenty-minute discipline and the large font, and drop the fixed count. A proposal deck read by a committee without you in the room needs more context per slide than a pitch delivered live. A Reddit thread on slides versus no slides in SaaS selling shows the other side of the trade-off: "I use slides only if absolutely necessary. I focus on story telling and keeping it conversational." Both views hold, at different stages of the same deal.
Sales deck examples worth studying
The sales deck examples below are public and widely referenced, and each one teaches a single transferable lesson. We chose them for what they show about complex deals, not for design.
- Zuora: the reference for narrative structure. As analyzed by Raskin, the deck names a shift (the "subscription economy"), documents winners and losers among large companies, and only then introduces the product. Lesson: earn the right to talk about yourself.
- Sastrify: according to Pitch's review of public decks, the deck breaks down benefits for the three teams in its typical purchasing process: Finance, Procurement, and IT. Lesson: write one value slide per buying role.
- ChartMogul: the same review presents it as a pre-read or leave-behind deck that a convinced contact can forward to a colleague. Lesson: design the proposal deck to be read without you.
- Asana: Dock's teardown of 24 B2B decks highlights a differentiation slide that plots tools on "power" and "ease of use", plus a logo wall and sourced statistics. Lesson: show your position against alternatives on criteria the buyer already uses.
- LinkedIn Sales Navigator: the same teardown notes a single "new buying reality" slide that condenses third-party research, then asks how the viewer is adapting. Lesson: turn research into a question for the buyer, not a statement about you.
Notice what these decks share. None of them leads with the product. Notice also what they lack: they are mostly marketing-built master decks, and none shows how a rep adapted them for a specific account. That adaptation is where complex deals are won or lost.
How do you tailor a sales deck for each stakeholder in a buying committee?
Keep the narrative spine and rewrite two slides per role: the problem slide and the proof slide. The change in the world and the target state stay the same for everyone, because the committee has to agree on them. What changes is what each member is accountable for and what evidence they need.
Start from a stakeholder map of the account, not from the org chart. The map tells you who decides, who influences, and who can block. Then build one row per role, as in the matrix below. Dock's guide does recommend separate decks for "technical vs. operational buyers", but it stops at segments and never goes down to the roles inside one account.
The champion row matters most, because the champion presents your deck when you are not there. A sales champion who lacks material retells your story from memory, and the economic buyer hears a weaker version of it. Give the champion a version with speaker notes and a one-slide summary.
The constraint is time. Rebuilding five slides per role, per account, from CRM notes, call recordings, and past proposals is what makes reps fall back on the master deck. Cobl, the AI sales agent for teams selling complex solutions, starts from the live context of the opportunity and your Shared Drive to produce a deck for that specific account and committee, exported to editable PowerPoint. See how Cobl builds a tailored deck from your deal context.
What changes in an orals or RFP defense deck?
An orals deck follows the buyer's evaluation criteria, not your narrative. The panel scores what you say against a grid, so the slide order should mirror that grid. Creativity in structure costs points here.
US federal procurement makes the rules explicit. Under FAR 15.102, "oral presentations by offerors as requested by the Government may substitute for, or augment, written information." The solicitation may describe the evaluation factors, the qualifications of the people presenting, limits on "the use of written material or other media", and "the time permitted for each oral presentation." The same section states that information intended as material contract terms "shall be put in writing."
Private-sector buyers rarely publish rules this precise, but the logic carries over. Three practices follow from it:
- Mirror the criteria: one section per evaluation factor, in the order the buyer listed them, with the factor name as the slide title.
- Present the named team: the people who will deliver the work should present their part, since panels often assess the team itself.
- Stay inside the written offer: anything you promise orally that is not in the submission creates risk for both sides, so align the deck with the final proposal line by line.
An orals deck is the last step of a response that started much earlier. For the written part, our guide on how to respond to an RFP, with examples covers the compliance work the deck will later defend.
Can AI build a deck you can actually present?
AI can produce a first version of a tailored deck quickly, if it has the deal context. Without that context, it produces a generic deck that looks finished and says nothing specific about the account. The input matters more than the tool.
A general-purpose assistant starts from a prompt, so the rep has to paste in discovery notes, the stakeholder map, pricing, and references every time. Cobl keeps that context per opportunity and draws on approved company knowledge, which removes the reconstruction step. Ato reports a 15% increase in its conversion rate with Cobl. Results like this are customer-reported and depend on the team and the deal mix.
AI-produced deal documents still need a human review before they reach a buyer: pricing, scope, legal terms, and compliance claims must be checked by the people accountable for them. Treat the output as review-ready work, then put your judgment on the slides that carry commitments.
Build the deck for the decision, not the meeting
A sales deck in a complex deal is three decks: one to open the conversation, one to equip the committee, and one to defend the offer. The narrative spine from the Zuora example holds across all three. What changes is the audience, and with it the problem slide, the proof slide, and the order imposed by the buyer.
The fastest improvement for most teams is the proposal deck, tailored per stakeholder and built to be read without the rep in the room. Pick a live opportunity, take the matrix above, and rebuild the two slides per role that your current deck leaves generic.
Move a live deal forward with a deck built from your actual deal context. You can try Cobl for free for 15 days, at app.cobl.ai.
