What are the concrete steps to run a demo coaching session with a rep before their first live demo in 2027

A concrete scenario that frames the problem

Picture a mid-market SaaS team in early 2027. A rep named Dana has been on the floor for four months, has run discovery calls and a handful of technical Q&A sessions, and next Tuesday at 10:00 a.m. she runs her first live product demo with a real buying committee — a VP of Operations, an IT manager, and a procurement analyst. The deal is worth roughly $48,000 in annual contract value. Her manager, a RevOps-aligned enablement lead, has exactly one working week to get her ready.

This is the situation the coaching session exists to solve. It is not a training class. It is not a ride-along. It is a rehearsal with a scorecard, and it happens before the live call, not after. The distinction matters because most teams default to "shadowing" — the rep watches a senior AE demo, then does it herself with no dry run. That pattern produces avoidable failure: the rep narrates features in the order the UI presents them, forgets the discovery notes she collected two weeks earlier, and freezes when the IT manager asks about SSO and data residency.

The coaching session is the intervention. It compresses the learning loop from "one bad live demo and a lost deal" into "one bad rehearsal and a corrected live demo." For a 2027 buying environment where committees are larger, evaluation cycles are longer, and buyers arrive having already read your documentation and your competitor's, the rehearsal is the cheapest risk reduction available. A single lost mid-market deal typically costs more than twenty hours of coaching time, so the math is not close.

The scenario also sets the constraint that makes the steps concrete: you have one week, one rep, one live demo, and limited calendar availability across a sales manager, an SE, and possibly a peer rep. Every step below is designed to fit inside that envelope.

How the mechanism actually works

The coaching session works because it separates three things that normally blur together in a live demo: content recall, narrative sequencing, and adaptive response. A rep who has never rehearsed is doing all three simultaneously in front of a buyer, which is why first demos feel frantic. The rehearsal isolates each one, gives feedback on each one, and then recombines them under time pressure.

The mechanism has four moving parts:

1. Cold run. The rep presents the demo as if it were live, with no interruptions and no help. This surfaces the true baseline — what she actually remembers and how she actually sequences.
2. Rubric scoring. The coach scores against pre-written criteria rather than giving vibes. Scores become the agenda for the debrief.
3. Targeted drill. The coach stops the tape at the two or three lowest-scoring moments and has the rep re-deliver just those segments, sometimes three or four times, until the language is clean.
4. Timed re-run. A shortened second pass 48 hours before the live call confirms the fixes stuck and rebuilds confidence under mild pressure.

The critical design choice is that the coach does not demo during the session. The moment the coach takes the keyboard, the rep becomes an observer again and the rehearsal value collapses. The coach's job is to ask, score, stop, and re-run — never to perform.

Notice the loop back from the re-run. A failed re-run does not mean cancel the live demo — it means shrink it. A 25-minute demo that lands beats a 45-minute demo that wanders, and the coaching session is where that scope decision gets made while there is still time.

The second mechanism worth naming is recording. A rep watching her own recording notices things no debrief can convey: filler words, mouse wandering, talking over the buyer's imagined question, reading bullet points aloud. Self-review within 24 hours of the coaching session roughly doubles retention of the feedback, because the rep connects the coach's note to a specific moment she can see.

Real numbers, ranges, and benchmarks

Coaching sessions vary widely in length and structure, but a few ranges hold up across teams. These are practitioner conventions rather than published study results, so treat them as starting defaults to tune, not as universal law.

Timing. Book the session 5–7 business days before the live demo. Closer than 48 hours and there is no room for a re-run; further than 10 days and the rep forgets the feedback before the live call. The re-run lands 24–48 hours out — close enough to be fresh, far enough to fix something.

Duration. 60 minutes for a rep with prior demo exposure, 90 minutes for a true first-timer. Split it roughly 25 minutes cold run, 35 minutes debrief and drill, 20 minutes re-deliver of the two weakest segments, 10 minutes logistics. Going past 90 minutes produces diminishing returns; attention and honesty both drop.

Demo length target. For a mid-market committee demo in 2027, 25–30 minutes of presentation plus 15–20 minutes of discussion is a common shape. First-time reps routinely over-run by 40–60 percent, which is why the rehearsal must be timed with a visible clock.

Rubric size. Five to seven dimensions, each scored 1–5. Fewer than five and you miss something important; more than seven and the debrief becomes a lecture. A workable set: discovery handoff, narrative arc, product proof, objection handling, interaction and questions, close and next step, and pacing.

Score thresholds. A common green-light rule is no dimension below 3 and an average of 3.5 or higher. A dimension at 2 or below triggers a targeted drill. Two or more dimensions at 2 or below usually means the demo scope is too broad for a first live run — cut a segment rather than coach harder.

Talk ratio. Aim for the rep speaking 60–70 percent of the time during the presentation portion and under 50 percent during discussion. First-timers often sit at 85–90 percent, which reads as a monologue and suppresses the buyer's questions.

Question handling. Expect 8–15 questions in a 45-minute committee demo. A rep who answers in under 30 seconds per question keeps momentum; a rep who delivers a three-minute answer per question runs out of time and never reaches the close.

Rehearsal count. Two full passes plus one targeted drill is the practical ceiling for a single week. Three or more full runs tends to produce a memorized script that breaks the moment a buyer goes off-script.

Cost framing. If a fully loaded AE hour costs the business somewhere in the low hundreds of dollars and a mid-market deal carries five figures of ACV, a 90-minute coaching session plus prep is a rounding error against a single at-risk deal. That ratio is the argument to make when a manager says there is no time.

Adoption reality. Teams that formalize pre-demo coaching typically report that a meaningful share of first demos would have gone better with a rehearsal — but the honest framing is that the value shows up as fewer unforced errors, not as a dramatic win-rate jump on its own. Coaching is one input among discovery quality, lead source, and pricing.

Trade-offs and alternatives

Pre-demo coaching is not free, and it is not always the right tool. The honest trade-offs:

Time versus coverage. A 90-minute session with one rep is 90 minutes the manager is not spending with the other seven reps on the team. If you coach every first demo at that depth, a ten-rep team with high turnover can consume a full day of management time per week. The usual resolution is tiering: full 90-minute coaching for first-ever demos and for deals above a value threshold, a 30-minute rubric review for routine demos, and self-recorded review for experienced reps entering a new product line.

Standardization versus authenticity. A tight rubric produces consistent demos, which buyers and SEs appreciate, but it can sand off the rep's natural voice. The fix is to score structure and substance, not script. Never require exact wording; require that the discovery handoff, the proof, and the close all appear.

Rehearsal versus spontaneity. Over-rehearsed reps can sound canned and struggle when a buyer redirects. This is why the drill should include at least one deliberate curveball — the coach interrupts mid-segment with a hostile question, or asks the rep to skip to a later section and then come back.

Coaching versus shadowing. Shadowing a senior rep is cheaper and requires no rubric, but it teaches by osmosis and gives no feedback on the learner's own delivery. Shadowing works well as a supplement in the week before the coaching session, not as a replacement.

In-house versus peer coaching. A peer rep who recently ran the same demo can coach credibly and costs no manager time, but peers tend to be generous and to skip the uncomfortable notes. A manager or enablement lead brings authority and honesty. Many teams use a peer for the cold run and a manager for the scored debrief.

The decision tree matters because the most common failure mode in demo coaching is over-applying it. A blanket policy that every demo gets a 90-minute rehearsal burns management capacity and breeds resentment. Tier by experience and deal value, and revisit the tiers quarterly.

Common pitfalls and how to avoid them

Pitfall 1: The coach demos. The single most damaging mistake. The moment the coach grabs the keyboard to "just show how it's done," the rep stops rehearsing and starts watching. Avoid it by agreeing the rule out loud at the start: the coach does not touch the product during the cold run.

Pitfall 2: No rubric, just reactions. Feedback like "that felt a bit long" is unusable. A written rubric with five to seven scored dimensions turns vague impressions into a prioritized fix list. Write the rubric before the session, not during it.

Pitfall 3: Coaching the whole demo at once. Twenty notes delivered in sequence overwhelm the rep and none of them stick. Cap the debrief at three fixes. If the cold run reveals twelve problems, pick the three that would cost the most in the live call and park the rest for the next cycle.

Pitfall 4: Skipping the re-run. Teams often do the session, feel good, and never verify. Without a timed re-run 24–48 hours before the live call, you have no evidence the fixes held. The re-run is the cheapest part of the process and the most commonly dropped.

Pitfall 5: Rehearsing against a friendly audience. If the coach nods along and asks soft questions, the rep is unprepared for a skeptical IT manager. Build at least two hard questions into the cold run: a pricing challenge, a security or integration question, and a "why not just keep doing it in spreadsheets" objection.

Pitfall 6: Ignoring the discovery handoff. Many first demos fail not because the product story is weak but because the rep never restates what the buyer said in discovery. The rubric must include a dimension for tying the demo back to the buyer's stated pain, in the buyer's own words, in the first two minutes.

Pitfall 7: No recording. Without a recording, the rep cannot self-review and the coach cannot show a specific moment. Recording also creates a library that shortens future coaching — a new rep can watch three recorded demos before her own session.

Pitfall 8: Scheduling too late. A session booked the day before the live demo leaves no room for a re-run and turns the coaching into a cram. Protect the 5–7 day window on the calendar as a hard rule.

Pitfall 9: Treating it as a pass/fail gate. If the rep reads the session as an audition, she will perform safe and hide weaknesses. Frame it explicitly as a rehearsal where mistakes are the point, and where the only failure is not surfacing a problem before the buyer does.

Pitfall 10: Forgetting the close. First-timers routinely end the demo without a clear next step. The rubric should require an explicit ask — a technical deep dive, a scoped pilot, a proposal review — and the rehearsal should end with the rep practicing that ask out loud.

Related questions

How far in advance should the coaching session be scheduled?

Five to seven business days before the live demo. This leaves room for a 24–48 hour re-run and for the rep to self-review the recording. Sessions booked inside 48 hours become cramming and rarely change behavior.

Who should run the coaching session?

A sales manager, enablement lead, or experienced peer who knows the demo and the buyer profile. The coach must not take over the keyboard. For technically complex deals, include an SE so security, integration, and data questions get rehearsed too.

What should the rubric actually score?

Five to seven dimensions: discovery handoff, narrative arc, product proof, objection handling, interaction and questions, pacing, and close. Score each 1–5, require no dimension below 3, and cap the debrief at three fixes.

Does the rep need to rehearse the full demo every time?

No. One full cold run, a targeted drill on the weakest segments, and one shortened timed re-run is enough. Three or more full passes tends to produce a memorized script that breaks when a buyer goes off-script.

What if the re-run still shows problems?

Shrink the demo rather than coach harder. Cut a segment, simplify the narrative, and narrow the scope to the two or three capabilities that map directly to the buyer's stated pain. A tight 25-minute demo beats a wandering 45-minute one.

FAQ

How long should a pre-demo coaching session last? Sixty minutes for a rep with some demo exposure, 90 minutes for a true first-timer. Split it roughly into a 25-minute cold run, 35 minutes of debrief and drilling, 20 minutes re-delivering the weakest segments, and 10 minutes on logistics. Beyond 90 minutes, attention and honesty both fall off.

Should the coaching session be recorded? Yes. Recording lets the rep self-review within 24 hours, which roughly doubles retention of the feedback because she connects each note to a specific moment. It also builds a library that shortens coaching for future hires, who can watch recorded demos before their own session.

What is the single most important rule for the coach? Do not take the keyboard. The moment the coach demos, the rep becomes an observer and the rehearsal value collapses. The coach's role is to ask, score, stop the tape, and re-run — never to perform the demo herself.

How many fixes should come out of one session? Three at most. A cold run often surfaces a dozen issues, but a rep cannot absorb more than a few at a time. Pick the three that would cost the most in the live call, assign owners and dates, and park the rest for the next cycle.

What if there is no time for a coaching session before the live demo? Do a 30-minute version: a 15-minute cold run of just the opening and the close, a 10-minute debrief with two fixes, and a 5-minute re-deliver. It is far better than nothing, though it will not catch mid-demo problems. Protect the 5–7 day window whenever possible.

Does this work for a rep who has demoed before but is new to this product? Yes, with a lighter format. Skip the full cold run and instead have the rep self-record a 20-minute demo, then spend 30 minutes in review focused on product proof and objection handling. Experienced reps need calibration, not basic rehearsal.

Sources

• Gong, "Sales Demo Best Practices" — https://www.gong.io/blog/
• HubSpot, "How to Give a Product Demo" — https://blog.hubspot.com/sales/product-demo
• Salesforce, "Sales Enablement Resources" — https://www.salesforce.com/resources/
• Harvard Business Review, "The End of Solution Sales" — https://hbr.org/2012/07/the-end-of-solution-sales
• Gartner, "B2B Buying Journey" — https://www.gartner.com/en/sales/insights/b2b-buying-journey
• Forrester, "Sales Enablement Research" — https://www.forrester.com/research/
• LinkedIn Sales Solutions, "Sales Blog" — https://www.linkedin.com/business/sales/blog
• Corporate Visions, "Sales Messaging Research" — https://corporatevisions.com/blog/

Related on PULSE

• How to build a demo scorecard your reps will actually use
• Running discovery-to-demo handoffs without losing the buyer's words
• Onboarding a new AE in 2027: a 30-60-90 day demo readiness plan
• Objection handling drills that work under live pressure
• When to bring an SE into the demo — and when it hurts
• Measuring demo coaching impact without vanity metrics