60-Min Sales Training: Running a Killer Demo

The two ways to run the hour, and why the choice matters

Every sales manager building this session lands on the same fork: teach the framework, or drill the reps. Both are defensible. They produce different reps, and picking the wrong one for your team's current state is why most demo trainings evaporate by Thursday.

Option A — the framework-heavy hour. Roughly 35 minutes of teaching and script walkthrough, 15 minutes of demonstration by the manager or a top rep, 10 minutes of Q&A and action items. Reps leave with a shared vocabulary: the macro arc (Problem → Solution → ROI → Next-Step), the micro loop (Tell-Show-Tell inside every feature), and printed verbatim scripts. Nobody performs. Nobody gets corrected. The hour feels smooth and everyone rates it highly on the post-session survey.

This is the right shape when the team has no common language. If three reps open with a company slide, two open with "so tell me what you're hoping to see today," and one opens by sharing screen at second nine, you do not have a coaching problem — you have a definition problem. Drilling reps on a framework they cannot name produces confused repetition. Teach first.

Option B — the reps-heavy hour. Ten minutes of framework refresh, 35-40 minutes of role-play in rotating pairs, 10 minutes of debrief and rubric review. Every rep performs at least twice, out loud, in front of a peer, with a manager floating and correcting in real time. It is uncomfortable. Attendance dips. The post-session survey scores lower and the behavior change is far larger.

This is the right shape when the team can already recite the arc but does not execute it under pressure. The classic tell: reps describe the framework accurately in a 1:1 and then, on a recorded call, open the demo with a feature tour anyway. Knowledge is not the gap. Retrieval under buyer pressure is the gap, and only reps close that.

The hybrid most teams actually need. In practice the durable version is 5 setup / 15 teach / 15 scripts / 15 role-play / 5 pitfalls and drill. It leans reps-heavy while preserving enough teaching that a new hire in week two is not lost. The critical constraint is not the split — it is that role-play never gets cut when the hour runs long. Managers cut the drill because it is the awkward part. That is exactly backwards: teaching is the part that survives being rescheduled, and drilling is the part that only happens if you protect it.

There is a third option worth naming and rejecting: the recorded-call teardown hour. You pull one rep's call and dissect it as a group. It is high-signal and it scales badly. One rep gets coached, nine watch, and the one who gets coached is publicly corrected in a way that quietly reduces volunteers next time. Use teardowns in 1:1s. Use the group hour for reps.

The same fork appears in adjacent training topics — renewal conversations, discovery calls, objection handling, executive-briefing prep. The decision rule transfers cleanly: teach when the vocabulary is missing, drill when the vocabulary exists but the behavior does not. Onboarding cohorts are almost always teach-first. Teams two quarters into a flat conversion rate are almost always drill-first, no matter how much the manager wants to re-explain the deck.

How to decide between them

Run the diagnostic before you build the agenda, not after. It takes four minutes and it is the difference between a training that moves a number and one that fills a calendar slot.

Step one — the sticky-note count. Open the session by asking every rep to pull their last five demos in your call-recording tool and count how many ended with a held calendar invite on the next step. Not "they said they'd circle back." Not "I'm sending materials." A held invite with a date. Write the number on a sticky, hold it up.

The distribution tells you which hour to run. If the room is mostly zeros and ones, and reps also cannot describe what should have happened, that is a teaching gap. If the room is mostly ones and twos but every rep can articulate exactly what they should have said, that is an execution gap — drill.

Step two — the vocabulary check. Ask one rep at random to name the four acts of a demo and the three beats inside a feature. If they can do it cold, you have vocabulary. If they hesitate or invent something, you do not.

Step three — the recording spot-check. Before the session, pull one demo per rep and note the timestamp of the first screen share. Reps sharing screen before the two-minute mark are skipping the problem replay entirely. That is a structural miss, not a polish miss, and it argues for teaching the arc before drilling anything.

Step four — the honest calendar check. How many hours of manager time can you commit to follow-up this week? A reps-heavy hour creates homework — recorded demos to review, rewritten openers to give feedback on. If you cannot fund the follow-up, the drill's effect decays fast. In that case run the teaching hour and schedule the drill hour for the following Monday when your calendar is clearer. Half a drill with no follow-through is worse than an honest teaching session.

One more decision input people skip: deal complexity. A two-call transactional cycle with a $12K ACV can absorb a sloppier demo because the buyer's risk is low. A six-figure enterprise cycle with a security review and three stakeholders cannot — a bad demo there burns the only shot you get at the economic buyer. Weight toward drilling when the average deal size is large and the demo count per rep per week is small, because each rep gets fewer live reps to learn from naturally.

Concrete numbers behind each option

Managers ask for a number to justify the hour. Here is how to build one from your own data rather than borrowing a vendor benchmark that may not describe your motion.

The baseline you must measure first. Held next-step rate: demos that ended with a dated calendar invite, divided by total demos, over a trailing four weeks. Most teams that have never trained this land somewhere between 20% and 40%. Pull it per rep, not just as a team average — the team average hides the fact that one strong rep is usually carrying it.

The teaching hour's economics. Ten reps × 1 hour = 10 hours of selling time, plus roughly 2 hours of manager prep to build the agenda and print scripts. Twelve hours total, one time. The realistic ceiling on a pure teaching hour is a shared vocabulary and a modest lift on the most mechanical behavior — reps stop opening with the company slide, reps stop showing eleven features. Expect the effect to show up in demo structure within a week and in conversion within a quarter, if at all, without follow-up drilling.

The reps-heavy hour's economics. Same 10 hours of selling time, plus 2 hours of prep, plus the real cost: 3-5 hours of manager time that week reviewing one recorded demo per rep and giving written feedback. Call it 17 hours. The payback math is straightforward once you know your numbers. If a rep runs 5 demos a week at a 30% held next-step rate, that is 1.5 progressed opportunities. Moving to 50% is 2.5 — one additional live opportunity per rep per week. Across ten reps that is ten additional progressed opportunities weekly. Multiply by your demo-to-close rate and your average contract value to get the revenue figure. Do that math with your actual numbers on a whiteboard during the session; reps engage differently when the number is theirs.

The feature-count number. Cap demos at five features, each mapped to a pain the buyer named in discovery. This is the single most testable rule in the session because it is countable after the fact. Pull a recorded demo, count distinct features shown, count how many trace to a discovery note. Reps who show eleven features typically map three. The correction is not "show fewer things" — it is "cut anything you cannot trace to a sentence the buyer said."

The timing budget inside the demo itself. For a 45-minute demo: 8-10 minutes of problem replay, 15-20 minutes of solution blocks, 5-7 minutes of live ROI math, 3-5 minutes of next-step. For a 30-minute demo, compress proportionally but never below 5 minutes of problem replay and never below 3 minutes of next-step. The next-step block is the one reps sacrifice when they run long, which is why the demo that felt great produced nothing.

The ROI math you teach reps to run live. The pattern matters more than any specific figure. Take a quantity the buyer stated — hours per week spent on a manual process. Multiply by a fully loaded hourly rate the buyer confirms. Multiply by working weeks per year. Compare to your annual price. Then say the honest thing: "Does that math line up with how you'd model it internally?" If the buyer pushes back on an input, change it live and re-run. A rep who lowers their own assumption in front of the buyer and still lands a defensible number is far more credible than one who defends the original figure.

The rubric numbers. Five criteria, scored 1-5 by the observing peer: discovery replay accuracy, Tell-Show-Tell completeness, ROI run live and adjusted, recovery handled when the buyer disengaged, next-step forced. A 20 or above is competent. Below 15 on any single criterion is that rep's assignment for the week. Track it across sessions — the criterion that stays lowest team-wide is your next training topic, which conveniently removes the "what should we train on next" debate.

One adjacent number worth watching. Demo no-show and reschedule rate. A rep whose demos convert well but who runs three per week instead of six has a pipeline problem, not a demo problem. Training the hour will not fix that, and mistaking one for the other wastes a quarter.

Implementation details and sequencing

The hour only works if the week around it is designed. Here is the sequence that holds.

The Friday before. Pull the baseline. Held next-step rate per rep, first-screen-share timestamp per rep, feature count on one demo per rep. Print the scripts — physical paper, not a shared doc. Reps read from paper in role-play without alt-tabbing to Slack.

Setup, minutes 0-5. Open at exactly :00. One slide, one line: "By Friday, every demo we run ends in a held calendar invite or a written no." Run the sticky-note count. Then a two-minute warm-up where each rep names, in one sentence, the single moment in their last demo where they felt the buyer's energy drop. No diagnosis, just the moment. This primes the recovery drill and it surfaces the room's real pattern faster than any survey.

Framework teach, minutes 5-20. Two structures, nothing else. The macro arc is the shape of the whole call: replay the buyer's pain in their own words before touching the product; walk three to five capabilities each tied to a named problem; do the ROI math live on screen with their inputs; force the next step. The micro loop lives inside every feature — Tell why this matters to them, Show the live product, Tell what just happened and what it means for their Tuesday morning. Reps skip the closing Tell roughly four times out of five. That omission is why buyers remember the click and not the meaning, and it is the most common reason attention collapses around minute twenty.

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

Scripts, minutes 20-35. Five scripts, read aloud, one rep per script so the room hears the cadence rather than reading silently.

*The problem replay* — before sharing screen, restate the three things the buyer said were broken, in their words, with their numbers, then ask "did I get that right, or do you want to add or correct anything?" The buyer confirms or adjusts. Either way they are now invested, and the product has not appeared yet.

*The Tell-Show-Tell loop* — one feature, all three beats, ending with a named person on the buyer's team whose Tuesday changes.

*The live ROI math* — the pattern above, run out loud, ending with the invitation to challenge the inputs.

*The next-step forcing question* — "Based on what you've seen, what would have to be true for you to move forward in the next 30 days?" Then, if the answer is nothing major, propose two specific times. If they hedge, ask "what's the specific blocker?" and stay silent for five seconds. The next words are usually the truth.

*The recovery* — "I want to pause. We've been on this view a few minutes and I'd rather make sure it's relevant. How does this compare to how you'd handle it today? And is there a different question on your mind I haven't gotten to?" Handing the conversation back is the only reliable fix for a buyer who has mentally left. Plowing forward never recovers it.

Role-plays, minutes 35-50. Three rounds, five minutes each, rotating pairs. Round one: the problem replay cold open, no screen share allowed for the first 90 seconds. Round two: a single feature run as full Tell-Show-Tell, with the observer specifically watching for the closing Tell. Round three: recovery — the buyer stopped nodding eight minutes ago, gives one-word answers, is visibly reading email. The seller must pattern-interrupt and then force a next step before the clock runs out. If the seller keeps demoing through the silence, stop the drill at 90 seconds and reset. That plow-through is the behavior you are here to kill.

Buyer briefs should be written and identical across pairs so scores compare. A useful default: VP of Customer Success at a 180-person company, three named pains, friendly, has sat through dozens of demos this year and is hard to impress.

Pitfalls and drill, minutes 50-60. Name the six failure modes out loud — the feature parade, the skipped closing Tell, the ROI hedge, the disengagement plow, the soft close ("I'll send some materials"), and the missing problem replay. Reps recognize themselves; that recognition is the point. Then assign the week: review your last three demos and cut every unmapped feature, rewrite your opener and send it to the manager by Tuesday EOD, run at least three demos on the new structure and record them, end every one with the forcing question.

End at :60 exactly. No overtime. It is the same clock discipline the demo itself requires, and reps notice whether the manager keeps it.

Sequencing across a quarter. One hour does not build a demo motion. A reasonable cadence is demo structure in week one, objection handling inside the demo in week three, executive-stakeholder demos in week five, and renewal or expansion conversations in week seven — each hour reusing the same rubric so scores are comparable. Reps tolerate repetition of format far better than they tolerate a new framework every month.

What breaks this. Three things, reliably. A manager who cuts role-play to finish the teaching. A follow-up week where nobody reviews the recordings, which teaches reps the metric is theater. And a leaderboard that shames the bottom rep publicly — publish the team rate and coach the bottom privately, or you will get quiet gaming of what counts as a "held" invite.

Related questions

How is this different from a discovery-call training?

Discovery trains listening and question sequencing; the demo trains narrative and forcing a decision. The overlap is the problem replay — it is the handoff point where discovery notes become the demo's opening 90 seconds. Train discovery first if replays are inaccurate.

Should new hires attend or run their own version?

Attend, but do not role-play in round one. Have them observe and score the rubric, then role-play in rounds two and three. Scoring peers before performing accelerates their pattern recognition and removes the fear of going first.

What if we sell a product that demos badly live?

Then the ROI block and the problem replay carry more weight and the product walk shrinks. Show two capabilities instead of five, spend the recovered time on live math with the buyer's inputs, and use a recorded segment for anything fragile.

How often should this hour repeat?

Re-run the full hour quarterly and drill single beats — just the recovery, just the forcing question — for ten minutes in weekly huddles. Full sessions monthly cause fatigue; single-beat drills stay fresh because they are short and specific.

Does this work for partner or channel sellers?

The arc holds, but the problem replay is weaker because the partner rarely ran discovery. Compensate with a required pre-demo brief from the partner listing three buyer pains, and treat a missing brief as a reason to reschedule.

FAQ

How long does the sales training take?

A single 60-minute session, typically Monday morning. It is a focused meeting, not a multi-day workshop. The hour itself is only half the intervention — the recorded demos and manager review during the following week are what convert the session into behavior change.

What if my team has never used the Problem → Solution → ROI → Next-Step arc?

Run the framework-heavy version first: more teaching, more script walkthrough, one round of role-play instead of three. Then schedule the reps-heavy hour for the following Monday. Drilling a framework reps cannot name produces confident repetition of the wrong thing.

How do we handle buyers who go silent or turn off their cameras?

Pause explicitly and hand the conversation back — ask how what you are showing compares to how they handle it today, and whether there is a different question on their mind. The explicit pause is the only reliable recovery. Continuing to demo through the silence never works.

What is the single most important metric to track after this training?

Held next-step rate: the share of demos ending with a dated calendar invite or an explicit written no. It is countable, it is hard to game if you define "held" tightly, and it maps directly to pipeline movement rather than to how the demo felt.

Can this training work for a complex, high-price product?

Yes, and the case for drilling is stronger there. Large deals mean fewer demos per rep, so reps get less natural practice and each demo carries more risk. Expect a longer solution block, more stakeholders in the room, and a next-step that is often a security or technical review rather than a second demo.

Is there follow-up coaching after the 60-minute session?

There should be. The session assigns rewritten openers due Tuesday and three recorded demos by Thursday, with the manager reviewing one per rep. Without that review week, the hour decays quickly — reps read the absence of follow-up as evidence the metric does not matter.

Sources

• https://www.gong.io/resources/labs/ — Gong Labs research on demo and discovery conversation patterns
• https://www.aprildunford.com/sales-pitch — April Dunford on problem-narrative structure for sales pitches
• https://winningbydesign.com/resources/ — Winning by Design SaaS Sales Method resources
• https://www.saleshacker.com/ — Sales Hacker articles on demo structure and next-step discipline
• https://blog.hubspot.com/sales — HubSpot Sales Blog on product demos and closing next steps
• https://www.30mpc.com/ — 30 Minutes to President's Club, demo and discovery tactics
• https://hbr.org/topic/subject/sales — Harvard Business Review sales topic archive
• https://www.demodesk.com/blog — Demodesk blog on demo best practices and next steps
• https://www.salesforce.com/blog/ — Salesforce blog on sales enablement and coaching cadence

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)