Sales decks
Why a deck that reads well when emailed is a document pretending to be a deck, and why the real decay here is forking rather than aging.
The operational shape
- Trigger
- Positioning changes, a launch, or a deal shape recurring often enough to standardize
- Reads
- Positioning and the registers, from decisions. Cleared proof. How the product works, from product.
- Cadence
- Maintained, revised on change rather than on a schedule
- Gate
- Approve before publish
A sales deck is a conversation aid. If it reads well when emailed with no explanation, it is a document pretending to be a deck — and it will feel flat in the room, because everything it needed to say is already on the slides.
The reverse failure is just as common: a deck built entirely for the conversation gets forwarded to someone who was not there, and lands as a series of unexplained assertions. Both problems are real, and the fix is to build the first thing and write a separate leave-behind for the second.
The operational shape
Trigger. Positioning changes, a launch, or a deal shape standardizing.
Reads. Positioning and the registers, from decisions. Cleared proof. How the product works, from product.
Cadence. Maintained, revised on change.
Gate. Approve before publish.
What good looks like
Every slide is talked to. A slide that exists to be present rather than discussed is a slide the presenter skips, and skipping teaches the room that some of this does not matter.
It leads with one register and holds it. A deck that opens on the promise and then argues the diagnosis in the middle asks the room to re-orient halfway through, and rooms do not re-orient — they disengage.
The proof slide is specific and cleared. This is where numbers get invented under pressure, and where a slide outlives the number it quoted by two years.
It has a version that survives being sent. Written deliberately, not by adding speaker notes.
It admits the limits. The same discipline as a product page, and the same payoff — a limit raised by the seller is a discussion, and one discovered by the buyer is an objection.
When it goes stale
The real decay here is not aging, it is forking, and no other capability has this problem in the same way.
A deck gets copied. A rep needs a version for a specific call, duplicates it, edits two slides, and that copy becomes their deck. Six months later there are nine decks, three of them contain a claim the company has stopped making, and nobody can say which one a given prospect saw.
The other three triggers are ordinary. Positioning moved and the argument is now the old one. A number expired. The product changed and a screenshot shows something that no longer exists.
The structural fix is a single maintained source with instantiation rather than duplication — the same pattern as every other asset in this category, and the one most often abandoned here because duplication feels faster in the moment.
What it feeds
- Proposals and one-pagers — the same argument, arranged to be read alone
- Meeting prep — which slides matter for this account
- Learnings — which slides get skipped, which is the deck telling you what to cut
Frequently asked
- Should there be one deck or several?
- One maintained deck, plus a leave-behind. Several decks means several versions of the argument, and the version a prospect saw becomes impossible to know.
- How many slides?
- However many the conversation needs, which is fewer than most decks have. The constraint that matters is that a slide earns its place by being talked to, not by existing.
- What about the version that gets emailed afterward?
- Make it deliberately. A deck built for a conversation is thin without the talking, and a deck built to be read is dead in the room. Build the first and write a leave-behind for the second.