← Hub
Pulse ← Library ⚡ Hire a Fractional CRO
Pulse Reviews and Analysis

How do you coach a rep to give a demo that closes?

Kory WhiteCurated by Kory White · Fractional CRO, CRO Syndicate
👍 Yup or 👎 Nope — vote this up its category:
📅 Published · 9 min read
How do you coach a rep to give a demo that closes?

Direct Answer

You coach a rep to give a closing demo by stopping them from demoing features and forcing them to demo discovered pain. The core move is the tell-show-tell structure from demo2win by Peter Cohan: tell the buyer what you're about to show and why it matters to *them*, show it in 90 seconds against the exact problem they named in discovery, then tell them what just changed for their business.

As the manager, you don't fix the demo for the rep — you watch a recorded demo (in Gong or Chorus), diagnose whether the gap is skill, will, knowledge, or a broken discovery hand-off, then run a focused coaching conversation and role-play loop. The closing happens *during* the demo through trial closes, not in a separate "next steps" slide at the end.

This guide gives you the verbatim scripts, the diagnosis tree, and the weekly cadence to make it stick.

How do you coach a rep to give a demo that closes?

Why This Happens — Diagnose Before You Coach

A demo that doesn't close is a symptom, not a root cause. Before you coach, find out *why* the rep's demo is flat. There are four real causes, and each one needs a different response. Coaching the wrong cause wastes everyone's time.

flowchart TD A[Rep's demo isn't closing] --> B{Did discovery surface<br/>2+ named, quantified pains?} B -->|No| C[System / hand-off problem<br/>Fix discovery first] B -->|Yes| D{Does the rep tie each<br/>feature to a named pain?} D -->|No| E{Can they do it when<br/>you walk through it live?} E -->|Yes| F[Will issue<br/>Coach ownership and prep] E -->|No| G[Skill issue<br/>Coach tell-show-tell + trial closes] D -->|Yes| H{Do they run trial<br/>closes during the demo?} H -->|No| G H -->|Yes| I{Do they know the product<br/>deeply enough to go off-script?} I -->|No| J[Knowledge gap<br/>Send to enablement / SE shadowing] I -->|Yes| K[Likely fit / comp / territory<br/>Not a demo problem]

Run this tree before your 1:1. If the answer is the bottom-right box, more demo coaching won't help — you may be looking at a fit, comp, or territory issue that needs a different conversation, not another role-play.

The Coaching Conversation

Use the GROW model (Goal, Reality, Options, Will) so the rep diagnoses their own demo instead of being lectured. Pull up the recording first. Never coach from memory — coach from the tape. Here are the verbatim scripts.

Goal — set the frame:

"I pulled the Acme demo from Tuesday. Before we watch it, what was your goal for that call — what did you want the buyer to do next?"

If they say "show them the product," that's your first finding. Reframe it: *"The goal of a demo is to get a commitment, not to inform. Let's watch with that lens."*

Reality — let the tape do the work:

"At 4:12 you opened the reporting dashboard. What pain from discovery were you connecting that to?"

Stay quiet. Most reps will admit they were demoing because the feature is cool, not because the buyer named that pain. Then:

"In discovery, Dana told you their CRO can't get a clean forecast in under three days. Where in the demo did you show *that* getting solved?"

Options — get them to generate the fix:

"If you ran this again, how would you open the dashboard so Dana feels it's about her forecast problem, not our feature?"

Coach them toward tell-show-tell: *"Dana, you said the forecast takes three days and you still don't trust it (tell). Here's the same forecast in one view, refreshed live (show). That's three days back every week and a number you can take to the board (tell)."*

Then add the trial close they skipped:

"Right after you show it, you ask: *'Dana, if your team had this on Monday, how would that change your week?'* — that's a trial close. You're testing temperature before you ask for the deal."

Will — lock the commitment:

"What's the one thing you'll change on the Beacon demo Thursday? Send me the recording and I'll watch the first ten minutes."

Notice you never gave the answer outright — you used their own deal to surface it. Reps own what they discover; they forget what they're told.

The Coaching Plan / Cadence

One conversation doesn't build a skill. Run a tight weekly loop and a 30/60/90 arc.

flowchart LR A[Observe<br/>watch recorded demo] --> B[Diagnose<br/>skill/will/knowledge/system] B --> C[Coach<br/>GROW + tell-show-tell script] C --> D[Practice<br/>role-play open + trial close] D --> E[Apply<br/>rep runs live demo] E --> F[Measure<br/>demo-to-next-step rate] F --> A

The loop is weekly during ramp, then biweekly once the demo-to-next-step rate stabilizes. The discipline is reviewing the tape every cycle — that's where coaching gains compound.

CRO Syndicate — Need a fractional Chief Revenue Officer? CRO Syndicate connects you with vetted fractional and interim revenue leaders. Kory White, Fractional CRO · 25 yrs · $0 to $200M scaled.

👉 Quick Call with Kory White, Fractional CRO · See Kory on LinkedIn · CRO Syndicate

Drills & Role-Play

Build the skill in reps, not lectures.

What to Measure

Quota is a lagging indicator. Coach to leading indicators that prove the demo behavior is changing:

Track these per rep on a simple scorecard so the rep sees their own trend, not just yours.

Common Mistakes Managers Make

FAQ

How do I coach a rep who insists on demoing every feature? Show them the buyer talk-time on the recording. Feature tours are monologues; closing demos are conversations. Then run the "so what" gauntlet until they feel how exhausting a feature list is for the buyer, and replace it with two or three pains demoed deep via tell-show-tell.

What if the demo is bad because discovery was bad? Then you have a discovery problem masquerading as a demo problem — the most common misdiagnosis. Coach discovery first (MEDDIC or SPIN questioning) so the rep walks into the demo with two or three named, quantified pains. No demo skill survives empty discovery.

How many demos should I review per week per rep? One per rep during ramp or active coaching, reviewed deeply — not five reviewed shallowly. Use Gong or Chorus so you can review on your schedule and drop timestamped comments the rep can rewatch.

When is it not a coaching problem? When the diagnosis tree lands on knowledge (fix with enablement and SE shadowing), or on fit, comp, or territory. A rep who can demo beautifully in role-play but won't prep for live calls has a will or fit issue, and that's a different, honest conversation — sometimes a performance plan, not more coaching.

Should the rep or the SE drive the demo? The rep should own the narrative and the trial closes; the SE owns the technical depth. Coach the rep to direct the demo, not hand it off. If the SE runs the whole thing, the rep never builds the closing muscle.

How do I get a rep to run trial closes without sounding pushy? Reframe trial closes as temperature checks, not asks: *"How would this change your week?"* feels like curiosity. Drill it in role-play until it's reflexive, and have them count their own trial closes on the next recording.

Bottom Line

The one move: make the rep demo discovered pain, not features, using tell-show-tell with trial closes baked in — and coach it from the recording, not from memory. Diagnose skill vs. Will vs.

Knowledge vs. Broken discovery before you say a word, then run the weekly observe-diagnose-coach-practice-measure loop until the demo-to-next-step rate climbs. Coach the skill, never rescue the deal.

Sources

*Sales coaching for closing demos — how to coach a rep to give a demo that closes, sales manager demo coaching guide, tell-show-tell demo framework, trial-close coaching, and a rep demo coaching playbook for 2027.*

Keep reading
Was this helpful?  
Sources cited
sourcePulse RevOps cross-pillar reuse
⌬ Apply this in PULSE
Free CRM · Revenue IntelligenceAudit pipeline, score reps, ship the fix
Related in the library
More from the library
pulse-speeches · speechesA Toast for a Baby Showerrevops · current-events-2027Why are GTM teams adopting AI-powered deal rooms for committee consensus?revops · current-events-2027Which AI in the funnel applications are buying committees in 2027 most suspicious of?revops · current-events-2027Why are longer sales cycles in 2027 forcing B2B companies to adopt outcome-based pricing models?revops · current-events-2027Why are longer sales cycles in 2027 driving adoption of AI-based meeting summarization tools?revops · current-events-2027Why do 2027 AI-driven lead scoring models degrade 60% faster after a vendor consolidation event?revops · current-events-2027Are vendor consolidation efforts in 2027 failing because of unresolved data migration between legacy platforms?revops · current-events-2027What happens to pipeline coverage ratio when 2027 AI agents auto-remove stale deals 3x faster than humans?pulse-speeches · speechesA Wedding Speech for a Best Womanrevops · current-events-2027Why are 20% longer sales cycles in 2027 linked to AI hallucination audits during technical validation?revops · current-events-2027Which vendor consolidation trends are making API-first architectures a RevOps priority?revops · current-events-2027Why are buying committees in 2027 demanding AI-generated ROI breakdowns before first demos?pulse-speeches · speechesA Wedding Speech for a Vow Renewalpulse-speeches · speechesA Toast for a 70th Birthdayrevops · current-events-2027What 2027 data shows that AI in the funnel increases demo-to-proposal time by 30% instead of reducing it?