Plan the reading order
Supply the audience, decision, source material and required coverage. Review the outline before generating. For a QBR, keep results, variance, risks and next decisions distinct instead of mixing them into a status collage.
A sales deck has a different job from a pitch deck: not to explain, but to persuade a buyer to act. The sequence that converts leads with their pain, not your product: audience problem → offer → proof → differentiation → outcomes → call to action. Here's what each slide does — and why real proof, not invented ROI, is what closes.
Open an actual exported deck, then compare its outline, source constraints and slide choices with the job you need to finish.
A 12-slide buyer conversation about protecting customer data, built only from two FTC guides: why customer information is worth protecting, the guides’ five principles and ten lessons, and practical first steps. It describes no provider and no product, so its proof is the FTC’s own guidance.
A client-facing deck for a conversation between a security services provider and the owner of a small business that holds customer information. Open on the owner's situation, then the proof, then the next step. The proof is what the supplied FTC guides say; do not describe, praise or price any provider, product, customer or result, and name no company. Every statement must come from the supplied guides; where they give no figure or finding, do not supply one and use no placeholders. Workflow: Sales and marketing. 12 slides requested. Documents supplied as text (FTC, "Start with Security: A Guide for Business (FTC)", https://www.ftc.gov/system/files/documents/plain-language/pdf0205-startwithsecurity.pdf; FTC, "Protecting Personal Information: A Guide for Business (FTC)", https://www.ftc.gov/system/files/documents/plain-language/pdf-0136_proteting-personal-information.pdf).
A separate reviewer agent read the deck’s 78 claims, slides and speaker notes, against the two FTC guides: 73 are supported, 5 loosen or go a little beyond the guides’ wording, and none is missing from them or contradicts them. 37 of the 78 are advice the deck gives, and 36 of those are supported. It is not a person’s review.
Supply the audience, decision, source material and required coverage. Review the outline before generating. For a QBR, keep results, variance, risks and next decisions distinct instead of mixing them into a status collage.
Edit structured slide fields, preview field alternatives or review a whole-slide rewrite. Ask Lumen can propose wider changes; inspect and select the changes before applying them to the saved deck.
Check charts, speaker notes, images and contrast in presentation view and the downloaded file. A new-period deck is a separate draft with changed values and sources to review.
Choose a creation mode and workflow profile, supply source material and review the planned coverage. Slide fields have layout-specific budgets. Field assistance offers alternatives with rationale and word counts; whole-slide refinement shows field-level changes. Ask Lumen can propose wider structural edits, which require a reviewed preview before application.
Paste spreadsheet rows, choose header handling and preview replacement chart data. Where offered, select Business metrics explicitly and inspect their source receipt. Review changes in values and sources before accepting a next-period draft. Theme controls cover brand colors, type, logo placement, background and contrast choices; a custom theme still needs visual review.
Inspect full-screen and audience views, speaker notes, next-slide preview, navigation and timer. Check PDF and PowerPoint separately. Supported elements can become native editable shapes or charts; complex visuals can use a flattened fallback. Speaker notes and per-slide handoff choices should be inspected in the actual file.
PowerPoint export is hybrid: supported content may remain editable while complex visuals can be flattened. Conversion between a responsive story and slides requires a preview; it is not lossless.
Why “their problem” goes first: the highest-converting B2B decks follow the strategic-narrative approach popularized by Andy Raskin — open on the shift in the buyer’s world and what’s at stake, not on your company or features. The deck earns attention before it asks for anything.
The mistake that kills sales decks is opening with your company and your features. A buyer doesn't care yet — they care about their problem. So a converting sales deck starts where the buyer is (their pain), earns the right to be heard (proof), explains why you over the alternatives (differentiation), shows what they'll get (outcomes), and tells them exactly what to do next (the CTA).
Persuasive, but disciplined: concrete benefits, an explicit ask, and proof that's real — because the moment a prospect catches an invented customer or an inflated ROI figure, the deck is dead.
Open on the buyer's pain in their words. Show you understand the problem better than they expected — that's what earns the next slide.
Your solution, framed as the answer to that pain — not a feature tour. One clear value proposition.
The credibility slide: real customers, metrics, testimonials, case results. This is where a sales deck is won or lost, so use proof you can stand behind.
Why you over the alternatives the buyer is also considering. Be specific and fair — a comparison that's obviously slanted reads as weakness.
What changes for them after they buy — concrete results, tied to the problem you opened with.
One explicit next step — a trial, a pilot, a meeting. A deck without a clear ask leaves the buyer to decide what happens next, which usually means nothing does.
A sales deck lives or dies on the proof slide, which is exactly why it's the most tempting place to exaggerate — a customer you're "about to close," an ROI number that's aspirational. Don't. A prospect who catches one inflated claim re-reads the whole deck as marketing.
Lumen's sales workflow keeps supplied proof, source settings, generation-time provenance, and citations close to the deck. It does not automatically verify every customer, quote, or ROI figure, so the reviewer must compare sales-critical claims with the approved source before delivery.
The three get used interchangeably and they are not the same document. Getting the label right saves you from writing the wrong deck well.
A pitch deck is for investors. Its job is to argue that the company is worth backing, which is why the running order is problem, market, product, traction, business model, team and the ask — and why the numbers on it get diligence. If that is what you are building, the sequence on this page is the wrong one; use how to structure a pitch deck instead.
A sales deck is for a buyer. Its job is to move one specific account toward a decision, so it opens on their problem and closes on a next step. Same slide count, different centre of gravity: an investor is buying the company, a customer is buying an outcome.
An elevator pitch is neither — it is the two-sentence version you say before either deck opens. It is still worth writing down, because it is the test of whether the offer slide holds up: if the value proposition cannot survive being said out loud in twenty seconds, it will not survive slide three either.
Then there is the fourth thing people mean by “deck”: the slide deck you leave behind. A live sales deck and a leave-behind are different artefacts — one is spoken over, the other is read alone. If a prospect will forward it internally, the proof and outcome slides have to carry the argument without you in the room.
Updated