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

Two ways to run the handoff — and why one keeps losing demos

Every team runs one of two handoff models, and the whole point of this Reboot is to make the choice explicit instead of accidental.

Option A — the informal handoff. The AE finishes Discovery, grabs the SE in a hallway or Slack thread, says "big deal, they want to see the reporting piece Thursday," and forwards a call recording. The SE reconstructs context from a 45-minute transcript, guesses at the pain, and builds a demo that shows the product's power. It is fast to schedule and feels frictionless. It is also where most demos quietly die: the SE never learns the compelling event, the buyer hears a feature tour instead of their own problem solved, and the deal stalls in "evaluation" for a quarter.

Option B — the gated handoff. The AE writes a one-page Discovery Doc, the SE turns it into a Demo Plan, both sign a pre-brief, and attendees are verified before anything hits the calendar. It costs roughly 25–30 minutes of upfront work per opportunity. In return, the SE walks in knowing the pain in the buyer's words, the three quotes to echo, the single screen that delivers payoff, and exactly what not to show.

The Reboot exists because Option A is the default everywhere and nobody chose it — it just happens under scheduling pressure. Peter Cohan calls the unprepared demo a "harbor tour": a tour of the boat instead of a path to the buyer's destination. The training's job is to make Option B the muscle-memory default across the sales org, so the handoff stops being a favor and becomes a standard.

How to decide which handoff a given deal gets

Not every opportunity needs the full gate, and pretending it does is how teams abandon the process in week two. The decision rule is about deal complexity and stakeholder risk, not deal size alone.

Route a deal to the full gate when any of these are true: more than one buyer persona attends the demo, an economic buyer's budget sign-off is required, a competitor is actively in the evaluation, or the Discovery surfaced a date-bound compelling event. Route to a lightweight handoff — a short written summary and a two-minute verbal sync — only when it is a single-stakeholder, single-persona, low-ACV deal where the SE has demoed to that exact profile many times.

The failure mode to avoid is treating the gate as bureaucracy that "slows down hot deals." The hottest deals — multi-stakeholder, competitive, economic-buyer-present — are precisely the ones the gate protects. A 15-minute alignment call is cheap insurance against a 90-minute Friday-night rebuild and a burned first impression you cannot get back.

Teach reps to run this decision in under 30 seconds. The point is not to gate everything; it is to never let a complex deal slip through as if it were a simple one.

The four gates, line by line

The core artifact of the Reboot is a single template that turns a Discovery call into an approved Demo Plan. Reps fill it in live during the 15-minute template block for a real, demo-requested-but-unscheduled opportunity they bring to the session.

Part A — Discovery (AE owns). Ten fields, each of which is a red gate if blank: compelling event (date-bound yes/no), the business problem in the buyer's own words, measurable pain expressed in dollars or hours per week with evidence, a current-state process map (step 1 → 2 → 3 → 4), decision criteria split into must-have versus nice-to-have, the decision process (who decides, who approves, who blocks), a budget signal with its source, the competitive set (incumbents, alternatives, and do-nothing), a champion test (have they introduced you to power, shared an internal doc, or defended you?), and the single Critical Business Issue the demo must move.

Part B — Demo Plan (SE owns, AE approves). The demo goal written as one sentence — "Show [capability] solves [pain] for [persona] so they will [next step] by [date]" — followed by an audience list (name, title, stake, what they see), a 3-to-5-beat story arc, the "do-it" moment (the single screen that delivers payoff), three verbatim Discovery callbacks, an off-limits list of features you will not show, one proof point tying a logo, metric, and quote to the Critical Business Issue, and a specific dated next-step ask.

The four gates that must all be green before booking: Discovery Doc complete with MEDDPICC scored at least 7 of 9; the SE/AE 15-minute alignment call held and logged; the anti-feature-dump pre-brief signed by both AE and SE; attendees verified by name, title, and stake.

Cohan drives Part B item four — show the destination first, the screen the buyer will live with after they buy, then back into the capabilities that produce it. Robert Falcone drives the 3-to-5-beat arc: a demo is a story, not twenty-five features. John Care drives the current-state map and the single Critical Business Issue. Force Management's MEDDPICC discipline is what the 7-of-9 gate enforces.

Concrete numbers behind each option

The reason the gated handoff wins is measurable, and the training should put real ranges in front of reps rather than platitudes.

Time cost. The gated path adds roughly 25–30 minutes of structured work per opportunity: about 10–15 minutes for the AE to write Part A, 5 minutes for the SE to draft Part B, a fixed 15-minute alignment call, and a 10-minute pre-brief the morning of. The informal path adds close to zero upfront — but routinely costs the SE 20–30 minutes of transcript-mining prep that produces a generic demo anyway, plus the far larger cost of a lost or stalled deal.

The alignment call is 15 minutes, timeboxed hard: roughly 0–3 minutes for the AE to read Part A aloud line by line (any empty line is a red gate), 3–8 minutes for the SE to challenge with four questions — what proof moves the economic buyer, what objection the technical buyer raises, what the competitor will show that you cannot, and what single screen turns this demo on — then 8–12 minutes to co-author Part B and 12–15 minutes to gate-check and initial.

Attendee verification cuts risk sharply. Confirming every attendee by name, title, and stake — and requiring the economic buyer on the invite or a follow-up dated within 5 business days — is the gate most teams skip and the one that quietly kills the most deals. A stakeholder-confirmation email sent 48 hours out, plus postponing when attendees are unconfirmed, typically cuts no-show and low-stake demo rates by 30–50% within two weeks. A stranger who appears on the invite the morning of gets a 10-minute pre-demo call to learn what they care about, or the demo is politely rescheduled.

Demo hygiene has its own budget. A 45-minute demo splits into roughly 25 minutes of demo, 15 minutes of dialogue, and 5 minutes for the next-step ask. Story arc is capped at 3–5 beats; the moment a sixth beat appears, something gets cut before you walk in. Teams that adopt the structured pre-brief ritual report 40–60% fewer "demo redo" requests and a measurable lift in post-demo next-step conversion. These are the numbers to write on the whiteboard so the gate reads as a time-saver, not a blocker.

Implementation and sequencing — the six blocks and the Monday move

The Reboot runs 60 minutes in six timed blocks: 5 / 15 / 10 / 10 / 15 / 5.

Block 1 (5 min) — Open and frame. 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. Name the cost of a bad handoff — burned SE hours, a buyer who feels misread, a deal stuck forever. Set the stance: AEs own Discovery quality, SEs own demo design, both own the handoff artifact. Every AE arrives with one demo-requested-but-unscheduled opportunity to run live.

Block 2 (15 min) — The template. Walk the Discovery Doc → Demo Plan line by line while reps fill it in for their live deal. This is where the sales team learns the artifact by using it, not by reading it.

Block 3 (10 min) — The alignment call. Demonstrate the fixed 15-minute format, then have pairs practice the walk-through, challenge, co-author, and gate-check rhythm.

Block 4 (10 min) — The pre-brief. Teach the one-page checklist signed by AE and SE the morning of the demo, and role-play it three times: once clean, once with a Discovery gap where the AE cannot answer a key question, and once with a stakeholder conflict of champion versus gatekeeper.

Block 5 (15 min) — Verification and live practice. Five minutes on attendee verification, ten minutes of pairs running their real opportunity end to end while the facilitator audits one pair in front of the room against the four gates.

Block 6 (5 min) — Sign, schedule, close. Every AE and SE signs a 12-week commitment: no demo I run gets booked until all four gates are green, manager countersigns. The alignment call becomes a recurring 15-minute slot inside each deal. And each rep leaves with three written Monday-morning commitments: implement the one-page Discovery Summary on every new opportunity, schedule a pre-brief 24 hours before every demo, and send a name/title/stake confirmation email 48 hours out.

The manager's role is to review the three commitments in Monday standup and track compliance for the first two weeks. After 14 days the gate stops being a training artifact and becomes how the team simply works — a repeatable, predictable demo pipeline instead of a series of harbor tours.

Related questions

What is the single highest-leverage step if we only adopt one?

Attendee verification. Confirming every attendee by name, title, and stake — and refusing to book without the economic buyer present or a follow-up dated within 5 business days — prevents the "ghost stakeholder" demo where you pitch to someone who cannot buy. It alone cuts low-stake demos 30–50%.

How is this different from just doing better Discovery?

Better Discovery still fails if it never reaches the SE intact. The Reboot's contribution is the gate and the artifact: a written doc that transfers context, an alignment call that stress-tests it, and a signed pre-brief. It fixes the handoff, not just the Discovery call.

What if AEs and SEs resist the extra steps?

Frame the gate as a time-saver, not a blocker. A 15-minute alignment call avoids a 90-minute Friday rebuild and a burned first impression. Ask each rep to try it on exactly one deal the following Monday; the win rate difference sells the process better than any mandate.

Does this work for PLG or self-serve motions?

The gate is built for discovery-led, human-run demos in B2B. In PLG, the same principles apply at the sales-assist moment when a product-qualified account requests a guided demo — you still verify stakeholders and cap the story arc — but the full alignment call may compress for single-persona deals.

How do we measure whether the Reboot worked?

Track four things before and after: demo-to-next-step conversion, "demo redo" request rate, low-stake or no-show demo rate, and average days from demo to committed next step. A working Reboot moves all four within the first 30 days.

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, a pre-brief is signed, and every attendee is verified by name, title, and stake. It prevents the common failure where Discovery is incomplete and the handoff is a quick hallway chat, producing demos that miss the mark.

How long does the Training take and what is the format? The Training runs 60 minutes across six blocks — 5, 15, 10, 10, 15, and 5 minutes. It is interactive: reps bring a real opportunity, fill in the template live, drill the alignment call and pre-brief, and leave with one template, one gate, and a written Monday-morning commitment each.

What sources or methodologies is the Reboot based on? It draws on Peter Cohan's *Great Demo!*, John Care's *Mastering Technical Sales*, Robert Falcone's *Just F\*ing Demo!*, Force Management's MEDDPICC and discovery-gated discipline, and pre-brief norms from the Pavilion sales-engineering community. These are established, widely used demo and technical-sales frameworks.

Will this work for any team size or sales model? It is designed for discovery-led B2B demos and applies whether you have a few reps or dozens. Very small teams may compress the 15-minute alignment call for single-persona deals; very large teams may add an ops-run weekly gate-compliance report. The decision rule scales the gate to deal complexity.

What if our reps say the extra steps slow down hot deals? The hottest deals — multi-stakeholder, competitive, economic-buyer-present — are exactly the ones the gate protects. Show the numbers: 25–30 minutes upfront versus a stalled quarter or a lost deal. Have each rep try the gate on one deal Monday; the result converts skeptics faster than a mandate.

Do we need special tools or templates to start? No. The Discovery Doc → Demo Plan template works in any document or CRM field, and the pre-brief is a one-page checklist. The Reboot is a process, not software — the only requirements are the written artifact, the timeboxed call, and manager follow-through for the first 14 days.

Sources

1. Peter Cohan, *Great Demo! How to Create and Execute Stunning Software Demonstrations* — the "do-it" first method and the harbor-tour anti-pattern. https://www.greatdemo.com/
2. John Care, *Mastering Technical Sales: The Sales Engineer's Handbook* (Artech House) — SE/AE handoff discipline and current-state mapping. https://us.artechhouse.com/
3. Robert Falcone, *Just F\*ing Demo! Tactics for Leading Kickass Product Demos* — the 3-to-5-beat story arc and anti-feature-dump principle. https://www.justfingdemo.com/
4. Force Management — Command of the Message and MEDDPICC playbooks on discovery-gated demos and economic-buyer access. https://www.forcemanagement.com/
5. Pavilion — sales and go-to-market community of practice, sales-engineering norms and alignment-call cadence. https://www.joinpavilion.com/
6. Gong — call-analytics research on demo win rates and opening with outcomes rather than features. https://www.gong.io/resources/
7. Winning by Design — Jacco van der Kooij, *Blueprints for a SaaS Sales Organization* and the SPICED framework for gated handoff stages. https://winningbydesign.com/
8. HubSpot Sales Blog — practical guidance on discovery calls, demo structure, and stakeholder qualification. https://blog.hubspot.com/sales

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 Doesn't Suck](/knowledge/st0477)