Demo deck vs leave-behind: two jobs, two densities

A live demo deck and a leave-behind look related and behave like strangers. The demo orients a conversation while the product does the proving. The leave-behind must stand alone for a champion who forwards it at eleven at night. Shipping your demo PDF as the follow-up is how deals stall with polite silence.

Hub: sales presentations. Method: Method. Examples: examples.

Spine: sales deck structure.

The density rule

Live density: one claim per slide, minimal body copy, titles that cue the click path, speaker notes for timing. Leave-behind density: complete claims, proof paragraphs, assumption tables, objection FAQ, commercial framing, and a CTA that works without you. If removing a sentence would make an async reader lost, that sentence belongs in the leave-behind even if it would clutter the live room.

Live demo spine: five to eight slides

Agenda and outcomes in one slide. Problem reminder in their words—thirty seconds, not a re-pitch. Three demo chapters mapped to three pains, each with a slide that names the job and the moment you will show. Proof slide with one peer metric. Mutual plan with owners and date. Everything else—security questionnaires, full feature matrices, second and third case studies—belongs in the leave-behind or appendix.

Leave-behind spine: complete enough to forward

Open with the shared problem and cost of status quo so a new reader who missed the call can catch up. Restate what was shown in the demo as outcomes, not click-by-click. Include one metric case, one risk reducer, implementation timeline with owners, commercial framing or pointer to proposal, FAQ for the top five objections, and a clear next step. The champion should be able to present this deck without you and without embarrassment.

Slide budget for the live room

Use meeting minutes to cap the live slide count. A twenty-five minute demo with an exec cannot carry fourteen slides and a product tour. Calculate the budget, then force the cut before you rehearse.

Worked example: returns automation demo

Live twin (seven slides): outcomes for the session; overtime cost reminder from discovery; demo chapter one inbound exception queue; demo chapter two NetSuite sync confirmation; demo chapter three supervisor dashboard; peer metric slide showing twenty-eight percent faster cycle at a similar retailer; mutual plan for Tuesday technical workshop. Leave-behind twin (fourteen slides): adds full cost table with assumptions, security posture, thirty-sixty-ninety implementation, packaging options summary, five-objection FAQ, and appendix pointer for architecture. After the call, the AE sends the leave-behind twin within two hours—not the seven-slide live PDF.

When to send what

• Before demo, Agenda and outcomes only; not the click path.
• During demo, Present-link live twin; product carries detail.
• After demo, Leave-behind twin within two hours while context is warm.
• Before proposal committee, Dense leave-behind twenty-four to forty-eight hours ahead.

Failure modes

• Demo PDF as follow-up, Sparse file dies in inbox. Fix: ship dense twin.
• Reading dense slides live, Room tunes out. Fix: cut to titles; talk the story.
• Pre-sending the click path, Room races ahead. Fix: agenda only before demo.
• Divergent twins, Live and LB disagree on price. Fix: shared outline version.
• Notes-dependent leave-behind, Reader cannot see notes. Fix: put claims on canvas.

Not for you if…

If your motion is a pure webinar recording with no live facilitation, build leave-behind density from the start. If legal forbids any leave-behind until NDA, use a present link with access control and still write complete claims—access control is not an excuse for sparse slides.

Gamma next step

Generate one outline from discovery tags in AI sales presentation or AI presentation maker. Duplicate the deck: cut the live twin to five to eight slides; densify the leave-behind with proof, risk, FAQ, and CTA. Name files Account_Demo_Live_vN and Account_Demo_LB_vN so versions stay paired.

Operating system: controls that keep AI drafts honest

Demo and leave-behind twins fail when teams ship one density for both jobs. Write the decision the meeting must produce before you open the generator. Assign an owner for every assumption on the slide. Schedule a title-only review with someone who was not in the source meeting. When those three controls exist, AI drafts accelerate the spine instead of decorating a vague brochure. When they do not, you get polished ambiguity that stalls in the room. Keep a one-page failure log of decks that missed their job—wrong density, missing cost or decision framing, soft close, unlabeled options, invented metrics—and coach the pattern, not the personality of the author.

Checklist before send for Demo deck vs leave-behind: two jobs, two densities: every headline uses audience language; every proof artifact has a commitment label; every number has a source; the last slide names owner and date when a decision is required; live and leave-behind twins share a version when both exist; and you can delete twenty percent of slides without losing the decision path. In Gamma, paste constraints first—audience, minutes, stakes, proof you already have, and the ask—then reject outline sections that invent facts.

Express path for late joiners

Not every stakeholder needs the full tour of Demo deck vs leave-behind: two jobs, two densities. Build a three-slide express path: the cost of inaction or the core tension, the wedge with one proof point, and the dated ask or decision. If the main deck cannot compress into that express path, the narrative is still a catalog. Train managers to request the express path in reviews; it surfaces structural rot faster than debating color palettes. Pair this with the public evaluation axes on Method when you compare tools.

Micro-example: what good looks like in numbers

Concrete numbers beat adjectives for Demo deck vs leave-behind: two jobs, two densities. A thirty-five minute medium-stakes meeting usually supports eight to ten live narrative slides at roughly fifty seconds each, plus appendix. A sixty-minute high-stakes committee can support twelve to fourteen live slides if proof and risk earn the minutes. If your draft lands at twenty-two live slides for a thirty-minute call, you do not have a design problem—you have a prioritization problem. Cut until the title-only story still stands, then densify the async twin for readers who were not in the room.

Enablement: how managers review this deck type

Managers reviewing work about Demo deck vs leave-behind: two jobs, two densities should score binaries before aesthetics. Does the opening answer the job in under sixty words of titles? Is proof labeled for commitment level? Are tradeoffs or exclusions explicit? Is the close a decision with owners rather than a thank-you? Fail two binaries and the deck returns for rewrite. Celebrate cuts publicly so brevity becomes status. Record which failure modes repeat across authors—those become the next enablement clinic, not another template skin.

For AI-assisted drafts on Demo deck vs leave-behind: two jobs, two densities, require the human to paste source constraints in the prompt: discovery tags, scorecard rows, principles, or claim titles. Ban regenerate-until-pretty workflows. The model is a layout accelerator after the spine is locked. Teams that skip the lock spend twice as long arguing with slides that look finished and reason unfinished.

Channel rules: live, async, and export

Choose density from channel. Live facilitation of Demo deck vs leave-behind: two jobs, two densities wants sparse claim slides and optional speaker cues. Async readers want complete claims, definitions, and FAQ. Export when the buyer or board process requires a file they can markup; present from a link when you control the room and want the latest version. Always re-check hierarchy and table fidelity after PPTX export. A beautiful canvas that collapses in the packet is not done.

Version twins together. When scope, metrics, or recommendations change for Demo deck vs leave-behind: two jobs, two densities, bump the shared version and send a one-slide change log: what moved, why, and whether the ask changed. Silent revisions are how champions and executives get blindsided by their own follow-up threads.

Anti-patterns library for this motion

Watch for these anti-patterns whenever you ship Demo deck vs leave-behind: two jobs, two densities: homepage transplants that ignore audience language; chronology that buries the answer; equal-weight icon grids that flatten hierarchy; miracle metrics without inputs; soft closes that replace dated asks; and appendix tours that steal airtime from decisions. Each anti-pattern has a fix already named in the failure modes above—teach the fix in deal or design review, not in a style guide nobody opens.

When time is scarce, protect the ask and the proof. Cut secondary cases, decorative section dividers, and repeated logos before you cut the mutual plan or the decision log. Rooms that run out of time before the ask are process failures. Build cut options into speaker notes or facilitation plans so the close survives.

Putting it into Gamma this week

This week, pick one real meeting that needs Demo deck vs leave-behind: two jobs, two densities. Gather the minimum inputs—tags, metrics, decision options, or weak slides to rewrite. Generate outline-first in Gamma. Run a title-only read with a skeptic. Cut twenty percent. Produce the density twin if async readers matter. Send before the context goes cold. After the meeting, log what worked and which slide still failed so the next draft compounds instead of restarting from a blank brochure.

If you lead a team, convert this page into a one-page checklist owned by enablement or the chief of staff. Attach it to the calendar invite template for meetings that use Demo deck vs leave-behind: two jobs, two densities. Tools do not fix missing rituals. Rituals plus outline-first generation do.

Additional teaching detail for Demo deck vs leave-behind: two jobs, two densities: treat every slide title as a sentence the audience could text to a colleague. If the texted sentence is vague, rewrite the title before you touch layout. Ambiguous titles are the leading indicator of later meeting failure across sales, product, and design motions alike. Keep a running list of strong titles from winning decks and reuse the pattern—not the nouns—on the next draft.

Additional teaching detail for Demo deck vs leave-behind: two jobs, two densities: treat every slide title as a sentence the audience could text to a colleague. If the texted sentence is vague, rewrite the title before you touch layout. Ambiguous titles are the leading indicator of later meeting failure across sales, product, and design motions alike. Keep a running list of strong titles from winning decks and reuse the pattern—not the nouns—on the next draft.

Additional teaching detail for Demo deck vs leave-behind: two jobs, two densities: treat every slide title as a sentence the audience could text to a colleague. If the texted sentence is vague, rewrite the title before you touch layout. Ambiguous titles are the leading indicator of later meeting failure across sales, product, and design motions alike. Keep a running list of strong titles from winning decks and reuse the pattern—not the nouns—on the next draft.

Additional teaching detail for Demo deck vs leave-behind: two jobs, two densities: treat every slide title as a sentence the audience could text to a colleague. If the texted sentence is vague, rewrite the title before you touch layout. Ambiguous titles are the leading indicator of later meeting failure across sales, product, and design motions alike. Keep a running list of strong titles from winning decks and reuse the pattern—not the nouns—on the next draft.