60-Min Sales Training: Running a Killer Demo

1. Setup (5 min)

Setup (5 min)

Open the meeting at exactly :00. Share screen with this single line on slide 1: *"By Friday, every demo we run ends in a held calendar invite or a written no."* No other agenda slide.

Manager script (verbatim, 60 seconds):

> "Pull up your last five demos in Gong. How many ended with a held next step on the calendar? Not a 'we'll circle back,' not a 'let me loop in finance' — a held invite. Write the number on a sticky. Hold it up."

You will see numbers between 0 and 2 out of 5. That is the entire reason for this meeting. Pavilion's 2027 Pulse data puts the median demo-to-next-step held rate at 38% across mid-market SaaS — most teams sit below it because reps treat the demo as a feature tour, not a forcing function.

Warm-up (2 min): Each rep says, in one sentence, the single moment in their last demo where they felt the buyer's energy drop. No diagnosis yet — just the moment. This primes them for the Recovery section.

The promise you make now, out loud: *"We will not leave this room until each of you has run a 90-second demo opener using the new framework, and you know what to do when the buyer goes quiet."*

2. Framework Teach (15 min)

Framework Teach (15 min)

The demo has one job: convert a curious prospect into a buyer who books the next meeting before they leave the call. To do that, every demo runs on two nested structures — the macro arc and the micro loop.

The Macro Arc: Problem -> Solution -> ROI -> Next-Step

This is the shape of the whole 30-45 minute demo. Four acts, hard transitions, in this order:

1. Problem (8-10 min) — Replay the buyer's pain in their own words from discovery. No product yet.
2. Solution (15-20 min) — Walk three to five capabilities, each tied to a problem they named.
3. ROI (5-7 min) — Live math, on screen, with their inputs.
4. Next-Step (3-5 min) — Held calendar invite or a written no. No exit without one.

April Dunford's Sales Pitch work (2023, still the standard read in 2027) reinforces this: the demo is not a feature parade, it is a narrative that resolves a defined problem. Skip the problem replay and your buyer drifts inside six minutes.

The Micro Loop: Tell-Show-Tell

Inside every single feature you show — *every one* — you run a three-beat loop:

• Tell: "Here is the problem this solves and why it matters to you."
• Show: Click the thing. Live product. Not slides.
• Tell: "So what just happened, and what does it mean for your Tuesday-morning workflow?"

Skip the closing Tell and the buyer remembers the click but not the meaning. That is the single biggest reason reps lose attention at minute 22.

The non-negotiable rule: No feature gets shown that does not map to a problem the buyer surfaced in discovery. If a rep wants to show something cool, they cut it.

3. Verbatim Scripts (15 min)

Verbatim Scripts (15 min)

Hand these out printed. Reps will read them in role-play in the next block.

Script A: The Problem Replay (opening 90 seconds)

> "Before I share my screen, I want to make sure I heard you right last week. You told me three things were broken. First — your CS team is spending roughly 11 hours a week reconciling renewal data between HubSpot and your billing system. Second — your CRO can't see net revenue retention by segment without your ops lead pulling a manual report every Monday. And third — you've lost two enterprise renewals this year because the team didn't catch a usage drop until the QBR. Did I get that right, or do you want to add or correct anything?"

The buyer either confirms or adjusts. Either way, they are now invested. You have not opened the product yet.

Script B: The Tell-Show-Tell Loop (single feature)

> Tell: "You said your CS team loses 11 hours a week to reconciliation. I'm going to show you the renewal health view next. The reason that view matters to you specifically is that it pulls from HubSpot and your billing system on a 15-minute sync, so the manual reconciliation work goes away." > > Show: *[Share screen. Click into the renewal health dashboard. Filter by their actual segment if you populated the sandbox.]* > > Tell: "So what just happened — you saw every at-risk renewal flagged automatically, with the usage drop highlighted in red. For your team, that means Sarah on CS stops doing the Monday reconciliation entirely, and your CRO sees NRR by segment without pinging ops. The 11 hours a week comes back to the team."

Script C: The Live ROI Math (5 minutes in)

> "Let's do the math on the table together. You said 11 hours a week of reconciliation work. Your CS ops lead is fully loaded at — call it $95K. That's roughly $46 an hour. 11 hours a week, 48 working weeks, is $24,288 a year just on reconciliation. Our annual price for the team you described is $38,400. So the reconciliation savings alone covers 63 percent of the cost. We have not even counted the two enterprise renewals you mentioned. Does that math line up with how you'd model it internally?"

If they push back on numbers, change the inputs live. Do not argue. Lower the hourly rate, lower the hours. The math still works. Show them you are not afraid of their pen.

Script D: The Next-Step Forcing Question (final 3 minutes)

> "Based on what you've seen, what would have to be true for you to move forward with us in the next 30 days? And if the answer is 'nothing major,' I'd like to put a 30-minute call on the calendar right now with you and your CRO to walk her through the renewal-health view. I have Thursday at 2 or Friday at 10. Which works?"

If they hedge: "Totally fair — what's the specific blocker?" Then silence. Five seconds. The next words out of the buyer's mouth are the truth.

Script E: The Recovery (when buyer disengages)

> "I want to pause for a second. I'm noticing we've been on this view for a few minutes and I'd rather make sure this is actually relevant. How does what I'm showing compare to how you'd handle this today? And — honestly — is there a different question on your mind I haven't gotten to yet?"

Pattern interrupt. Hand the conversation back. CrankWheel's 2026 buyer-attention research flagged that 91% of sellers cite virtual attention as the hardest part of the cycle — the only fix is the explicit pause.

4. Role-Plays (15 min)

Role-Plays (15 min)

Pair reps. 5 minutes per round, 3 rounds. Rotate pairs each round. One rep is seller, one is buyer. Manager floats, observes, scores on the rubric below.

Role-Play 1: The Problem Replay Cold Open

Buyer brief: You are a VP of CS at a 180-person Series C SaaS company. You named three pains in discovery: manual renewal reconciliation, no segment-level NRR visibility, two lost enterprise renewals. You are friendly but you've seen 40 demos this year.

Seller task: Open the demo with Script A. Do not share screen for the first 90 seconds. Confirm the three problems.

Coaching note: If the seller starts with "Thanks for taking the time" niceties beyond 15 seconds, the observer calls it. Get to the problem replay inside 30 seconds.

Role-Play 2: The Tell-Show-Tell Single Feature

Buyer brief: Same persona. The seller is now 12 minutes into the demo and is about to show one feature.

Seller task: Run a full Tell-Show-Tell on a feature of their choice from your product. Must include the closing Tell — the "so what does this mean for your Tuesday morning" beat.

Coaching note: 80% of reps will skip the closing Tell. That's the entire point of the drill — catch the skip.

Role-Play 3: Recovery From Disengagement

Buyer brief: You are 22 minutes into a demo. You stopped nodding eight minutes ago. Your camera is on but you're clearly looking at email. When asked a direct question, you give a one-word answer.

Seller task: Run Script E (Recovery). Pattern-interrupt. Re-engage. Then forcing-question them toward the next step before time runs out.

Coaching note: If the seller keeps demoing through the silence, stop the drill at 90 seconds and reset. The single most common mistake is plowing forward when the buyer has already left the room mentally.

Observer Rubric (one sticky per pair)

Score 1-5 on each:

• Discovery replay accuracy — Did the seller name the buyer's actual pains in the buyer's actual words?
• Tell-Show-Tell completeness — Did every feature have a closing Tell tied to a workflow?
• ROI math live and adjustable — Did the seller change inputs without flinching?
• Recovery handled — Did the seller pause and hand the conversation back, or plow on?
• Next-step forced — Did the demo end with a calendar invite attempt or a written no?

5. Common Pitfalls (5 min)

Common Pitfalls (5 min)

Walk these out loud. Two minutes total. Reps will recognize themselves.

• The Feature Parade. Reps show 14 features because they're proud of the product. Buyer remembers two. Fix: cap at five features, each mapped to a named pain.
• The Skipped Closing Tell. Reps Tell, Show, and then move on. Buyer saw the click but does not know the meaning. Fix: end every feature with "so what this means for you on Tuesday morning is..."
• The ROI Hedge. Reps say "ROI depends on your situation" and refuse to do the math. Buyer translates that as "you don't believe your own pricing." Fix: do the math live, adjust inputs on the fly.
• The Disengagement Plow. Buyer's camera goes dark, rep keeps demoing for nine more minutes. Fix: at the first sign of drift, use Script E. Pause is a feature, not a bug.
• The Soft Close. Rep ends with "I'll send you some materials" or "let me know what you think." That is the leak point. Fix: Script D, calendar invite or written no.
• The Missing Problem Replay. Rep dives into product at minute 1. Buyer never re-anchors to their own pain. Fix: 90 seconds of Script A before any screen share.

Bridge Group's 2026 SaaS sales benchmark put the average demo-to-close conversion at 22% for teams that skip the structured Problem replay, versus 41% for teams that lead with it. Almost double. The replay is the single highest-leverage 90 seconds in the entire cycle.

6. Action Items + Drill (5 min)

Action Items + Drill (5 min)

Walk this out and end at :60 exactly. No overtime. Respect the clock — it's the same clock the demo runs on.

This week, every rep:

1. Reviews their last three demos in Gong before Wednesday. Flags every feature shown that did not map to a discovery pain. Cuts those from their default flow.
2. Re-writes their demo opener using Script A. Sends it to the manager by EOD Tuesday for one round of feedback.
3. Runs at least three demos using the new structure. Records every one. Scores themselves on the observer rubric.
4. Ends every demo with Script D. Calendar invite or written no. No "we'll circle back" allowed.

Accountability metric:

Held next-step rate. Out of every 5 demos this week, how many ended with a held calendar invite? Target by end of week: 3 of 5 (60%). Pavilion's 38% median is the floor. We're aiming above it.

Manager publishes the leaderboard Friday at 4 PM in the team channel. Top rep gets to pick the next training topic.

Related on PULSE

• [Top 10 templates for running effective morning sales huddles](/knowledge/st0761)
• [60-Min Sales Training: Running a Renewal Conversation](/knowledge/st0476)
• [Sales Demo Best Practices: Agenda and Script for a Peer-Led Training Workshop](/knowledge/st0788)
• [Top 10 demo role-play scenarios for sales teams](/knowledge/st0536)
• [Top 10 demo training drills for B2B sales reps](/knowledge/st0535)
• [60-Min Sales Training: Handling Demo Objections in Real Time](/knowledge/st0455)

FAQ

How long does the sales training take? The training is designed as a single 60-minute session, typically held on a Monday morning. It’s a focused, high-impact meeting, not a multi-day workshop.

What if my team has never used the Problem → Solution → ROI → Next-Step arc? That’s the core framework taught in the session. The training walks reps through each step with a “Tell-Show-Tell” method, so even beginners can apply it immediately after the hour.

How do we handle buyers who go silent or turn off their cameras? The training includes specific techniques to “recover the room,” such as asking a direct question or reframing the value. The goal is to re-engage the buyer within seconds, not let the demo stall.

What’s the single most important metric to track after this training? Every demo must end with either a calendar-held next step or a written “no.” The training eliminates vague “we’ll get back to you” outcomes, forcing clear decisions from prospects.

Can this training work for a team selling a complex, high-price product? Yes, the arc and Tell-Show-Tell structure scale to any deal size. The focus is on clarity and next steps, which is critical whether your average sale is a few thousand or six figures.

Is there any follow-up or ongoing coaching after the 60-minute session? The training is a standalone meeting, but the drill metric (clear next step or “no”) is meant to be tracked weekly. Many teams pair it with a short weekly check-in to reinforce the habit.

Sources

• Pavilion 2027 GTM Pulse Report — demo-to-next-step held rate benchmarks across mid-market SaaS.
• April Dunford, Sales Pitch (2023) — problem-narrative structure as the demo's spine.
• Chris Orlob, pclub.io "Win the Demo" course — verbatim demo opener scripts and next-step forcing questions.
• Bridge Group 2026 SaaS Inside Sales Benchmark — demo-to-close conversion by demo structure.
• Gong Labs research on demo conversation patterns — talk-to-listen ratios and engagement drop points.
• 30 Minutes to President's Club podcast (Nick Cegelski, Armand Farrokh) — demo and discovery tactics.
• Winning by Design — SaaS Sales Method blog, "How to Run a Great SaaS Sales Demo."
• CrankWheel 2026 Buyer Attention research — virtual-demo disengagement signals and re-engagement plays.
• Hyperbound 2026 Sales Simulator data — rep behavior retention curves after demo training.
• Demodesk blog — "Why Defining Next Steps During Your Demo Can Make or Break the Sale."