The Discovery-to-Demo Handoff Reboot — 60-Min Training

Section 1 — Open & Frame the Gated Handoff (5 min)

State the rule out loud: "No demo gets on the calendar until the discovery doc is written, the demo plan is approved, and every attendee is named." Peter Cohan, in *Great Demo!*, calls the unprepared demo a "harbor tour" — a tour of the boat instead of a path to the buyer's destination. The fix is procedural, not motivational.

• Name the cost of a bad handoff: burned SE hours, a buyer who feels misread, a deal stuck in "evaluation" forever.
• Set the stance: AEs own discovery quality, SEs own demo design, both own the handoff artifact.
• Pre-work: every AE brings one demo-requested but not yet scheduled opportunity to run through the templates live.

The rule for the next 12 weeks: if the four gates below are not green, the demo does not get booked.

---

Section 2 — The Discovery Doc → Demo Plan Template (15 min)

Walk it line by line. Reps fill it in for their live opportunity as you teach.

DISCOVERY DOC → DEMO PLAN — [Account] — [Date] — AE: ___ SE: ___

PART A: DISCOVERY (AE owns)

1. Compelling event: ____________________ (date-bound? Y/N)
2. Business problem: ____________________ (in buyer's words)
3. Measurable pain: $______ or ___ hrs/week, evidence: _______
4. Today's process: Step 1 → 2 → 3 → 4 (current-state map)
5. Decision criteria: Must-have: ___ Nice-to-have: ___
6. Decision process: Who decides? Who approves? Who blocks?
7. Budget signal: $______ range, source: ______
8. Competition: Incumbents / Alternatives / Do-nothing
9. Champion test: Have they intro'd to power, shared an

internal doc, or defended us? Y/N

1. Critical Business Issue the demo must move: ______________

PART B: DEMO PLAN (SE owns, AE approves)

1. Demo goal: "Show [capability] solves [pain] for [persona]

so they will [next step] by [date]."

1. Audience list: Name | Title | Stake | What they see
2. Story arc (3-5): Illustration → Capability → Proof
3. The "do-it" moment: The single screen that delivers payoff
4. Discovery callbacks: Three verbatim buyer quotes
5. Off-limits topics: Features we will NOT show (and why)
6. Proof point: Logo + metric + quote tied to the CBI
7. Next-step ask: Specific, dated, calendared in the demo

GATES (all four GREEN before demo is booked) [ ] Discovery doc complete, MEDDPICC scored >= 7/9 [ ] SE/AE 15-min alignment call held and logged [ ] Anti-feature-dump pre-brief signed by AE + SE [ ] Attendees verified (name + title + stake)

Cohan drives Part B item 4 — the "do-it" moment: show the destination first (the screen the buyer will live with after they buy), then back into the capabilities that produce it. Falcone drives item 3: a demo is a story in 3-5 beats, not 25. Care drives Part A items 4 and 10: current-state map plus one Critical Business Issue the demo must move.

---

Section 3 — The 15-Minute SE/AE Alignment Call (10 min)

A fixed-format meeting that happens after discovery is documented and before the demo is scheduled. Force Management's MEDDPICC lives here.

• Min 0-3 — Walk-through. AE reads Part A out loud, line by line. Empty line = red gate.
• Min 3-8 — SE challenges. Four questions: *"What proof moves the economic buyer? What objection will the technical buyer raise? What will the competitor show that we cannot? What single screen turns this demo on?"*
• Min 8-12 — Co-author Part B. SE drafts the demo plan; AE confirms it ties back to the buyer's words.
• Min 12-15 — Gate check. Both initial the doc. Red gate = demo delayed, not de-scoped.

The Pavilion SE community publishes this cadence as a norm, not a favor. A 15-minute call avoids a 90-minute rebuild Friday night.

---

Section 4 — The Anti-Feature-Dump Pre-Brief (10 min)

Most demos die from feature spray — the SE shows everything to prove the product is "powerful." The buyer reads it as *"you did not listen."* Falcone calls it the biggest sin in B2B SaaS demos.

A one-page checklist, signed by AE and SE the morning of the demo:

• Story arc, 3-5 beats only. Sixth beat appears, something gets cut. Cap the list before walking in.
• The "do-it" first. Open with the screen the buyer will use after they buy — not the data model.
• Three discovery callbacks, verbatim. SE prints three buyer quotes and reads them at the right beat. The room hears its own language.
• Off-limits list. Two or three tempting-but-irrelevant features both sign not to show.
• Time budget. 45 minutes = 25 demo + 15 dialogue + 5 next-step. Anything else is a presentation.
• Single next-step ask. Exact words at minute 40: *"Based on what you saw, the next step is X by Y date — does that work?"*

Care frames the pre-brief as the SE's rehearsal contract: AE confirms what will be said, SE confirms what will not be shown, demo becomes a performance, not a pitch.

---

Section 5 — Attendee Verification & Live Practice (15 min)

The gate most teams skip — and the one that quietly kills the most deals.

Attendee verification — 5 min. Before the demo is booked, the AE confirms in writing:

• Every name, title, and stake — *who they are, what they need to see, what they will say "yes" or "no" to.*
• The economic buyer is on the invite or has a follow-up touchpoint dated within 5 business days. Neither = "feedback session," not a deal-advancing demo, and the forecast is downgraded.
• Stranger on the invite the morning of? AE runs a 10-minute pre-demo call to learn what they care about, or the demo is politely rescheduled. Unknown attendees are unmanaged risk.

Live practice — 10 min. Pairs (AE + SE) take the live opportunity they brought, run the 5-minute alignment call, then read the demo plan out loud for 5. Facilitator audits one pair in front of the room against the four gates. Goal: feel the rhythm so Monday is muscle memory.

---

Section 6 — Sign, Schedule, Close (5 min)

End with three concrete acts:

• Sign the gate. Every AE and SE signs: *"For the next 12 weeks, no demo I run gets booked until all four gates are green."* Manager countersigns.
• Schedule the cadence. AE/SE alignment call is a recurring 15-min slot inside the deal — AE schedules, SE leads. Ops reports gate-compliance weekly.
• State the Monday move. Not "improve discovery" but *"send Part A for [Account] to [SE] before 10 AM Monday."*

Cohan's reminder: "Demos are not where you sell — they are where the buyer sees themselves succeeding." Gate the handoff, earn that moment. Skip it, and the demo is where the deal dies.

---

Related on PULSE

• [The Inbound Lead Handoff Reboot — 60-Min Training](/knowledge/st227)
• [The SDR-to-AE Handoff Reboot — 60-Min Training](/knowledge/st187)
• [The Sales-to-CS Handoff Reboot — 60-Min Training](/knowledge/st188)
• [Top 10 sales enablement drills for PLG handoff reps](/knowledge/st0644)
• [Top 10 sales training workshops for PLG handoff teams](/knowledge/st0643)
• [60-Min Sales Training: AE-to-CSM Handoff That Doesnt Suck](/knowledge/st0477)

Common Handoff Anti-Patterns and How to Fix Them

Even with a formal gated handoff process, teams often fall into predictable traps that undermine the training. The most common anti-pattern is the "discovery dump" — the AE sends the SE a 15-page call transcript and expects them to extract the relevant nuggets. This wastes 20–30 minutes of SE prep time and guarantees a demo that feels generic. Fix: enforce a one-page Discovery Summary template with exactly four fields — *Primary Pain*, *Decision Criteria*, *Key Stakeholders*, *Must-Have vs. Nice-to-Have*. If it doesn't fit on one page, the discovery wasn't focused enough.

Another frequent failure is the "ghost stakeholder" — the AE books a demo with a champion who claims to have authority but actually needs three other approvers who never attend. This leads to a demo where you're pitching to someone who can't buy. The fix is a stakeholder verification call 48 hours before any demo: the AE confirms each attendee by name, title, and decision-making role. If the buyer hesitates or says "I'll loop them in later," the demo gets postponed until all relevant parties are confirmed. This single rule typically cuts no-show and low-stake demo rates by 30–50% within two weeks.

A third anti-pattern is the "demo-as-discovery" crutch — the SE uses the demo to ask basic qualifying questions because the AE didn't dig deep enough. This destroys credibility and extends sales cycles. The training should include a "Discovery Depth Check" exercise: before any handoff, the AE must answer five questions (e.g., "What happens if this problem isn't solved in 90 days?" "What budget has been allocated?" "Who else has tried to solve this and failed?"). If more than two answers are vague or missing, the handoff is blocked.

Building the Pre-Brief Ritual in 10 Minutes

The pre-brief is the single highest-leverage 10-minute block in the entire handoff process, yet most teams skip it or treat it as a casual chat. A structured pre-brief follows a strict agenda that takes exactly 10 minutes when timed properly:

• Minutes 0–2: Attendee verification — AE reads each attendee name, title, and stated stake. SE confirms they understand each person's role and likely questions.
• Minutes 2–5: Demo flow alignment — SE shows the drafted demo plan (3–5 slides/steps maximum). AE confirms it matches the discovery summary and flags any political landmines (e.g., "Don't mention pricing unless the CFO asks directly").
• Minutes 5–7: Objection pre-brief — AE shares the top 2–3 objections that came up during discovery. SE prepares a 30-second response for each, tied to a specific demo slide or feature.
• Minutes 7–9: "What not to show" — SE lists any features or capabilities that would confuse, overwhelm, or distract from the primary pain. AE agrees or pushes back if the buyer specifically asked about them.
• Minutes 9–10: Next-step commitment — Both agree on the desired outcome (e.g., "We want them to agree to a technical validation call with their IT team") and who will say what during the close.

Train this ritual by role-playing it three times during the 60-minute session: once with a clean handoff, once with a discovery gap (AE can't answer a key question), and once with a stakeholder conflict (champion vs. gatekeeper). Teams that adopt this ritual report 40–60% fewer "demo redo" requests and a measurable increase in post-demo next-step conversion rates.

Monday Morning Commitments That Stick

The training is worthless without a concrete Monday-morning action plan. Each rep must leave with three written commitments:

1. "I will implement the one-page Discovery Summary template for every new opportunity this week." — No exceptions. If the AE can't fill it out after the first call, they schedule a second discovery call before any handoff. The SE commits to rejecting any handoff that doesn't include this summary.

1. "I will schedule a 15-minute pre-brief for every demo this week, using the 10-minute agenda." — This means blocking time on both calendars at least 24 hours before the demo. If the AE refuses or "forgets," the SE has permission to escalate to the sales manager. The training should include a shared calendar template with pre-brief blocks pre-populated.

1. "I will verify every attendee by name, title, and stake before any demo." — The AE sends a confirmation email 48 hours before the demo that explicitly asks: "Please confirm your name, title, and role in this decision. Who else from your team will be joining and what is their stake?" If the response is incomplete or evasive, the demo is postponed.

The manager's role is to review these commitments in the Monday morning standup and track compliance for the first two weeks. After 14 days, the gated handoff becomes muscle memory — and the 60-minute training becomes the foundation of a repeatable, predictable demo pipeline.

FAQ

What exactly is a "gated handoff" and why is it necessary? A gated handoff means no demo is scheduled until a written Discovery Doc and Demo Plan exist, an AE/SE alignment call has occurred, and every attendee is verified by name, title, and stake. This prevents the common failure where discovery is incomplete and the handoff is just a quick conversation, leading to demos that miss the mark.

How long does the training take and what's the format? The training runs 60 minutes and is split into six blocks: 5, 15, 10, 10, 15, and 5 minutes. It's designed as an interactive session where teams walk away with one template, one gate, and a Monday-morning commitment from each rep.

What sources or methodologies is this training based on? It draws from Peter Cohan's *Great Demo!*, John Care's *Mastering Technical Sales*, Robert Falcone's *Just F*ing Demo!*, Force Management's discovery-gated discipline, and norms from the Pavilion SE community. These are established frameworks in sales and demo effectiveness.

Will this work for any team size or sales model? It's designed for teams that do discovery-led demos, typically in B2B tech. The principles apply whether you have a few reps or dozens, but the specific gate steps (like the 15-minute alignment call) may need slight adjustments for very small or very large teams.

What if our AEs and SEs resist adding more steps before a demo? The training addresses this by showing how skipping these steps leads to wasted demo time and lost deals. The gate is framed as a time-saver, not a blocker, and each rep commits to trying it on one deal the following Monday.

Do we need any special tools or templates to start? No special tools are required. The training provides a simple Discovery Doc → Demo Plan template that can be used in any document or CRM. The key is the process, not the software.

Sources

1. Peter Cohan, *Great Demo! How to Create and Execute Stunning Software Demonstrations* (Second Story Press, 2nd ed. 2005) — "do-it" first method and harbor-tour anti-pattern.
2. John Care, *Mastering Technical Sales: The Sales Engineer's Handbook* (Artech House, 4th ed. 2022) — SE/AE handoff discipline and current-state mapping.
3. Robert Falcone, *Just F\*ing Demo! Tactics for Leading Kickass Product Demos* (2018) — 3-5 beat story arc and anti-feature-dump principles.
4. Force Management, *Command of the Message* and MEDDPICC playbooks — discovery-gated demo and economic-buyer access discipline.
5. Pavilion Sales Engineering community of practice — pre-brief norms and AE/SE alignment-call cadence.
6. Greg Holmes / 2nd Derivative, *Demo2Win!* workshop materials — demo planning frameworks aligned with Cohan's method.
7. Chris Orlob, Gong research on demo win rates — call analytics on opening with outcomes, not features.
8. Jacco van der Kooij, *Blueprints for a SaaS Sales Organization* (Winning by Design, 3rd ed. 2018) — gated handoff stages in SPICED.