Build a Sales Deck Around the Customer's Decision, Not Your Company History
Build a Sales Deck Around the Customer’s Decision, Not Your Company History
A sales deck has one job: to leave the buyer able to make a decision you have earned. Not to admire your trajectory, not to be impressed by your team, not to feel that a partnership is somehow the natural next chapter. The buyer of a repair-appointment scheduler does not need your founding year. They need to know whether Thursday morning will keep falling apart the way it did last week, what would have to be true for it to stop, and what it costs to find out.
Slide order is not a packaging decision. It is a claim about what matters, and about the order in which the buyer should think. Send the buyer through eight slides of company development before reaching their own problem, and you have told them plainly that the problem is an afterthought you worked up to. Here is what a deck looks like when the sequence belongs to the buyer instead.
1. Start at the buyer's actual starting point
Before a single slide, you need three things: a task this buyer does, a difficulty inside that task, and what the difficulty costs. Confirmed context, not atmosphere. Anything you cannot confirm yet is a question to bring, not a wound to open.
Take the current workaround seriously. Fourteen technicians and three people answering the phone is a configuration in which a shared calendar and a stream of text messages is a cheap system that everyone already understands, and it may still be working fine. A deck that makes the workaround look foolish insults the person who built it, and that person is usually in the room. If the workaround has held up and you are selling something else — headroom, or fewer quiet failures, or the ability to add two vans without adding a coordinator — say that. Both arguments are respectable. Passing the second off as the first is not.
Keep three kinds of statement visibly separate: what the buyer told you, what you infer from it, and what you are illustrating for the sake of argument. A deck that blends them cannot be checked by the person reading it, which is the only person whose checking matters.
Now the example. Everything that follows is invented — an invented vendor, an invented buyer, an invented episode — and it exists to show the shape of an argument, not to report one.
The vendor sells Slotline, a scheduling tool. The buyer is Northgate Appliance Repair, fourteen technicians and three people on the phones. On Monday, Rosa books a caller for Thursday at 10:00. She checks the shared calendar; Dev's Thursday morning column looks clear. On Wednesday afternoon, Dev looks at his own week and sees that a warranty job in the south zone runs until 10:30, and the Thursday address is twenty-five minutes away on the north side. He texts Rosa. Rosa calls the customer back. The appointment moves to 1:00 p.m.; the customer had arranged to be home in the morning.
Nothing in that account is a catastrophe. That is the point. A timeline deck would open with the year Slotline was founded and build toward this handoff at slide nine. The handoff is the subject. Open there. The founding date can appear later, briefly, in the one place where it does work: if the team has run dispatch for a fleet of thirty vans, that fact answers a route-realism question a skeptical operations manager is already asking. One slide. Not the spine.
2. Explain the relevant change before touring the product
The buyer is asking a narrower question than most decks answer. Not "what does this thing do?" but "what would be different on Monday, and where does the difference stop?" Those have different answers, and only one of them helps.
So locate the offering inside the work. Slotline enters between Rosa learning what the customer needs and Rosa offering a time. What changes: the search. Instead of reading a calendar and borrowing a memory of who is usually where, Rosa sees a set of slots that already account for committed work and the drive between stops. What stays outside: which parts are in which van, whether a technician holds the certification for a particular brand, the customer notification, billing, and whether a technician takes the job at all. That last one needs care, because the deck will later show a technician accepting a slot. The tool narrows the candidates and records which one he accepts; it does not oblige him to take the work. A technician who can't make the drive, or wants a job reassigned or escalated, settles that with dispatch the way he does now. That boundary is not a confession. It is the map the buyer needs in order to know which question they are answering.
A product tour answers a capability question. The buyer is deciding about a change, and a capability list is not a change. This is the useful part of the practitioner guidance in Pete Kazanjy's Founding Sales, whose chapter on sales materials ties presentation material back to the customer-facing narrative rather than treating the deck as a catalogue (checked 8 September 2026). It is advice from early B2B selling, not a slide formula and not evidence about conversion. Take the rationale — connect the explanation to the buyer's story — and build the sequence yourself.
3. Demonstrate one claim at the scale of its evidence
Pick a single workflow, and pick the one that makes the contribution visible in the buyer's own terms. For Northgate, that is the Thursday handoff. Then say what kind of thing the audience is watching.
The grades are worth keeping straight, because each one supports a different sentence:
- "It can do this here." A prepared demonstration, configured for this scenario, running on sample data. It shows selected behaviour under chosen conditions. It does not show reliability, savings, or what happens at any other customer.
- "It did this for you." A supervised run on this buyer's own records, with their conditions and their exceptions.
- "It does this for organizations like you." Reference accounts whose situation resembles theirs in the ways that matter.
The statement you want to make determines the grade you need. A demo cannot carry an outcome claim, no matter how smooth the demo is.
The invented demonstration for Northgate is prepared, configured with fictional sample data for a fictional north-side address, and shows three candidate slots on Rosa's screen, one of which the fictional technician accepts from a phone. It demonstrates slot filtering and acceptance on data the vendor chose. It does not demonstrate what happens when the field app fails to sync, and the deck should not let the walkthrough imply otherwise. A polished demonstration is a strong way of showing and a weak way of proving. Reliability and savings live somewhere else, in records that belong to the buyer.
4. Give adoption effort and limits a place in the argument
A deck the buyer cannot use to judge plausibility is a brochure. Three things have to be on the surface for it to become something else.
The customer's work. The clerks learn a new search. Technicians confirm the candidate slot rather than being handed a time, though declining or escalating the assignment still runs through dispatch. Somebody owns the availability data, and if it drifts, the slots drift. Even a small change has a name attached to it, and the buyer will want to know whose.
The supplier's work. Configuration, integration, support, the first weeks. Say whose hours these are and roughly how many.
The unresolved dependencies. For Northgate there is one that decides everything else: the technicians already use a field-service app. Does Slotline read the schedule from it, or do technicians maintain a second calendar? If it is a second calendar, the gain may not survive a busy Wednesday, and no amount of demo polish changes that. This is not a footnote. It is one of the two or three facts the decision rests on.
Placement matters as much as content. A limitation standing next to the claim it bounds reads as a team that knows its own product. The same limitation on slide twenty-six, after the price has been implied, reads as a catch. Neither is dishonest; only one is usable.
The main deck does not need to be an implementation plan. It does need enough for the buyer to judge whether the change is plausible inside their organization. Detail belongs in an appendix. Essential qualifications belong in the room. Ask of every deferred slide: if this vanished, could the buyer still reach a defensible verdict? If not, it was never detail.
5. End with the decision this evidence can support
The closing ask should match the uncertainty the deck has actually resolved. Get that backwards and the rest of the work is wasted.
For the invented Northgate argument, fit is genuinely open. Nobody has counted how often a booked slot turns out to be infeasible, and the integration question has no answer yet. So the right step is not a signature and not "let's explore a partnership." It is a ninety-minute workflow review with Rosa, Dev and the operations manager, walking back through four weeks of appointments to count the mismatches and to test whether technicians would keep a second calendar current. Output: proceed to a paid pilot, or stop.
That step has a purpose, named participants, a duration and an aftermath. It also has somewhere to land besides yes.
Where the prerequisites are already established — integration confirmed, the mismatch common, technicians willing — an identified purchase decision is a fair thing to ask for. The point is not to keep deferring. The point is that the ask should be the next thing this evidence can actually support. A closing that cannot come back no is not a decision. It is a hope wearing a decision's clothes.
Here is a test for a draft deck, and it takes about two minutes. Read the slide titles in order as if they were sentences. If they read as a company's history — founded, funded, growing, and here is the product — you have written about yourself, and the buyer has been given a reason to be patient rather than a reason to evaluate. If they read as the buyer's decision — the problem, the change, the demonstration, the work, the limits, the next step — you have produced something a person can use on their own time.
Then ask the harder version: which of these slides would the buyer need in order to say no honestly? If the deck contains no route to a clear no, it is asking for belief. Belief in the company's story is not a substitute for the buyer's own evaluation, and it never closes anything the evaluation would not have closed on its own.
Frequently asked questions
Why should a sales deck not open with company history?
Slide order is a claim about what matters and the order in which the buyer should think. Leading with founding year, funding and growth tells the buyer their problem is an afterthought. Company facts can appear later only where they do work for the buyer's decision, such as answering a route-realism question.
What should the opening of a sales deck establish?
A task the buyer does, a difficulty inside that task, and what the difficulty costs: confirmed context, not atmosphere. Take the current workaround seriously rather than making it look foolish. Keep separate what the buyer told you, what you infer, and what you are illustrating for the sake of argument.
How do the three evidence grades differ?
'It can do this here' is a prepared demo on sample data under chosen conditions; it does not show reliability, savings or other customers. 'It did this for you' is a supervised run on the buyer's records. 'It does this for organizations like you' is reference accounts. The statement you want determines the grade, and a demo cannot carry an outcome claim.
Where do adoption effort and limits belong in the argument?
Next to the claim they bound. Surface the customer's work, the supplier's work, and unresolved dependencies such as whether the tool reads from an existing field-service app or requires a second calendar. A limitation beside its claim reads as a team that knows its product; the same limitation late reads as a catch.
What closing ask is appropriate for a sales deck?
One the evidence can support. In the invented Northgate case, fit is open, so the next step is a ninety-minute workflow review with named participants, a purpose, duration and aftermath, ending in proceed to a paid pilot or stop. If prerequisites are already established, an identified purchase decision is fair. A closing that cannot come back no is a hope, not a decision.