How do you coach a rep whose demos are technically strong but boring?

What a boring demo actually is, and why RevOps should care

A demo that reviewers call "boring" is almost never a knowledge failure. The reps who draw this feedback usually know the product better than anyone else on the floor — they can explain the data model, the permission hierarchy, the API rate limits, and the three edge cases where the integration silently fails. That fluency is exactly the trap. Deep product knowledge creates a feature-dump reflex: the rep equates thoroughness with value, treats coverage as respect for the buyer's time, and delivers the demo as a download rather than a discovery-driven conversation. The buyer sits through forty minutes of competent narration and leaves with nothing they can repeat to their boss.

The specific failure mode has a shape you can name. The rep opens with an agenda slide and a company overview. They share their screen within the first three minutes. They navigate the product in the order the product is built rather than the order the buyer's pain occurs. Every screen gets roughly equal airtime because every screen is roughly equally interesting to the rep. There is no tension, no moment where the buyer feels the cost of the status quo, and no point where the rep stops and hands the conversation back. The rep talks for eighty to ninety percent of the call. The buyer's only contributions are "makes sense" and "got it." At the end, the rep asks whether there are any questions, gets none, and books a follow-up that quietly never happens.

This matters to RevOps and not only to the frontline manager, because a boring demo is a measurable leak in a stage you already instrument. Demo-to-next-step conversion is a stage transition sitting in your CRM. If one rep's demos convert to a mutual action plan at half the rate of the team median while their discovery-to-demo rate looks normal, you have isolated a coachable defect to a single stage with a single owner. That is a far cleaner intervention than a broad "win rates are down" conversation. It is also a forecast-accuracy problem: a rep who runs technically impressive but engagement-free demos tends to carry deals that feel healthy on activity metrics — meetings booked, demos delivered, notes logged — while producing none of the multi-threading and stakeholder pull that actually predicts a close. Those deals inflate the pipeline and then slip.

There is a second-order effect worth naming. Boring demos concentrate in specific hiring profiles: reps promoted from support or implementation, sales engineers moved into a closing seat, founders' first technical hires, and anyone selling a product whose differentiation is genuinely architectural. If your last two hiring classes leaned technical, this is not one rep's problem — it is a cohort-wide enablement gap that will show up as a demo-stage conversion dip about one full sales cycle after those reps ramp. Watch for the pattern before you diagnose the individual.

The distinction that matters most in the diagnosis is between four different root causes, because the fix for each is completely different and applying the wrong one wastes a quarter. A skill gap means the rep cannot structure a narrative, does not know how to create tension, does not ask engaging questions, and defaults to a linear click-tour. This is the most common cause and it is highly coachable. A will or mindset gap means the rep believes the product sells itself, or considers showmanship beneath a serious technical professional. Also coachable, but you must move the belief before any drill will stick. A buyer-knowledge gap means the rep over-indexes on technical depth because they never ran real discovery and therefore have nothing to anchor a story to — fix discovery upstream and the demo improves on its own, with no demo coaching at all. A system or casting problem means the demo environment is broken, there is no script library, or the rep is genuinely miscast and belongs on a sales-engineering track. Coaching does not fix a casting error, and pretending otherwise burns six months and a good employee.

The step-by-step coaching process

Start with evidence, not opinion. Pull one recorded demo from your conversation-intelligence tool before you schedule anything. Watch the first five minutes yourself and write down three timestamps: when the rep first shared their screen, when the buyer last spoke unprompted, and the longest uninterrupted monologue. Those three numbers become the entire spine of the coaching conversation, and they do the confronting so you do not have to.

Run the 1:1 on the GROW structure — Goal, Reality, Options, Will. Do not open with "your demos are boring." That sentence produces defense in every rep who has ever heard it, and defense is the state in which no learning happens. Open with the outcome you both want and let them define it.

For the Goal step, ask what a perfect demo produces. Something like: "I want to spend this 1:1 on demos, because I think it's the highest-leverage thing for your win rate this quarter. When a demo goes perfectly, what does the buyer actually do differently by the end?" You are steering toward outcomes — they get excited, they pull in colleagues, they ask about next steps — rather than toward coverage. Reps who answer "they understand the product" have just told you their mental model, and that model is the thing you are about to change.

For Reality, play the clip and use the numbers. "Watch these three minutes with me. How much of that was you talking versus them? In your last five demos, when did a buyer last interrupt you because they were excited?" Then stop talking. The silence is doing work. Most reps arrive at the diagnosis themselves within about thirty seconds, and a self-reached diagnosis survives contact with the next live call in a way an imposed one does not.

For Options, force story-first thinking before you offer any technique. "If you couldn't show a single screen for the first five minutes, how would you make them care? What's the one customer story that maps to what they told us in discovery?" Only after they have tried to answer do you introduce the structural move: tee up every screen with the pain it kills before clicking anything. "You told me renewals slip through the cracks — watch what happens here." Click. Then stop and ask how their team would use it before moving on.

For Will, get a specific commitment attached to a specific call and a specific review date. "Pick the next demo on your calendar. What's the one thing you'll do differently, and how will I know you did it? I'll watch the recording Friday." Naming the call and the review date is what converts the conversation into behavior change. Vague encouragement changes nothing and both of you know it.

Then sequence the skill over ninety days rather than trying to fix everything at once. Days zero through thirty are story-before-screen and nothing else: every demo opens with a customer story tied to stated pain, and every screen is teed up by pain before the click. Score the weekly recording on that dimension only. Days thirty-one through sixty add interaction: deliberate pause-and-ask checkpoints after each major capability, plus one tension move that surfaces the cost of not solving the problem. Days sixty-one through ninety add command and choreography — multi-stakeholder demos, reading the room, adapting live, and teaching the buyer something they did not know walking in.

Between sessions, build reps rather than lecture. The no-screen pitch has the rep deliver the product's value for ninety seconds with the laptop closed; if they cannot make you care without a screen, the live demo never will. The tee-up drill gives them five features and requires a specific pain statement before each one, scored for specificity to a real named account. The pause-and-ask role-play has you play a buyer who goes quiet, forcing the rep to build in questions and react to shifts in your attention. Steal-the-best has the rep watch the top closer's recorded demo and write down three moves to copy — peer proof lands with technical reps in a way manager opinion never does.

Timelines, effort, and what the numbers typically look like

Budget the manager time honestly, because under-budgeting is why most of these plans die in week three. A serious ninety-day demo-coaching plan costs roughly one hour per week per rep: about twenty to thirty minutes reviewing the recording on your own before the 1:1, twenty to thirty minutes in the coaching conversation itself, and ten to fifteen minutes of role-play or drill. Across a team of six, that is six hours a week if you are coaching everyone, which is unsustainable. Coach one or two reps intensively at a time and put the rest on a lighter monthly cadence. A manager who spreads coaching evenly across six reps changes nobody's behavior.

Expect the changes to land in a staggered order, and set expectations with the rep accordingly. Structural changes — the story-first open, the pain tee-up before each click — usually appear in the second or third demo after the conversation, because they are scripted and the rep can prepare them the night before. Interaction changes take longer, typically four to eight weeks, because pausing mid-flow contradicts a reflex that fires under pressure. Command-level adaptation, where the rep abandons the planned path because the room went a different direction, is a sixty-to-ninety-day skill at minimum and some reps never fully get there. Anyone promising a fixed timeline beyond that is guessing.

On leading indicators, the honest framing is directional rather than absolute. Talk-to-listen ratio is the cleanest available proxy for engagement, and published research from conversation-intelligence vendors has consistently found that top performers listen more than losers do. Do not fixate on a specific target number — the right ratio varies by product complexity, deal size, and where you are in the cycle. What matters is the trend for this rep against their own baseline and against your team's own top-quartile performers on similar deals. Establish the baseline from five to ten of their recent recordings before you start coaching, then track the same metric monthly.

The metrics worth instrumenting, roughly in order of how early they move: buyer talk time on demo calls, number of unprompted buyer questions per demo, number of distinct attendees on the demo, demo-to-next-step conversion, new contacts added to the opportunity within seven days of the demo, stage-progression rate post-demo, and finally win rate. The first three move within weeks. Win rate is a lagging confirmation that arrives one full sales cycle later — for most B2B teams that is a quarter or two, which is precisely why you cannot coach to it. If the early indicators climb and the number has not yet turned, the coaching is working and you should hold the course rather than change the plan.

Tooling cost is a real line item and worth stating plainly rather than guessing at. Conversation-intelligence platforms are typically sold per-seat on annual contracts and land in the meaningful-software-spend category rather than the credit-card category, so pricing depends entirely on your negotiated terms. If you do not have one of these tools, the coaching still works — it just costs more manager time, because you attend live calls or watch raw meeting recordings and hand-score them. Do not let the absence of tooling become the reason for skipping the coaching. A scorecard on a shared doc and one attended call a week beats a tool nobody opens.

There is a real trade-off in how aggressively you push. Reps who are technically strong often have the highest product credibility on the team, and stripping their demos down to fewer screens can feel to them like being asked to dumb it down. Handled badly, that lands as a demotion and you lose engagement. The reframe that works: depth on the right screen for this specific buyer beats coverage of everything, and the technical credibility is what makes the one deep dive land. You are not asking for less expertise. You are asking for the expertise to be spent where it converts.

Where teams get this wrong

The single most common failure is coaching the deal instead of the skill. A manager sits down with the rep, fixes the upcoming demo for the specific account, the demo goes better, and everyone feels good. Nothing transferred. The next demo, for a different account, reverts. The fix is to name the repeatable behavior explicitly, write it down, and review the next demo specifically for evidence that the behavior appeared without your involvement. If it only shows up when you help prepare, you have not coached anything — you have been doing the rep's prep work.

The second failure is confronting with opinion. "Your demos are boring" is unfalsifiable, personal, and impossible to act on. It also implies a judgment about the rep rather than about a behavior. Recordings and talk-ratio numbers convert the same message into something the rep can examine without defending their identity. This is not softness — it is the difference between a message that produces change and one that produces a quiet resume update.

Third: changing everything at once. A rep handed a list of eight demo improvements applies none of them, because under live-call pressure the trained reflex wins over the eight competing new intentions. One skill per thirty-day cycle. It feels slow and it is the only thing that works.

Fourth: skipping the follow-through review. If you set a review date in the 1:1 and then do not watch the recording, you have taught the rep — far more effectively than any words in the meeting — that the coaching was optional. This is the most common way good coaching plans die. Put the review on your calendar in the same meeting where you set it.

Fifth: coaching every rep identically. A technical rep responds to proof, data, and peer modeling; hand them a top closer's recording and a scorecard and let them reverse-engineer it. A green AE with no product depth needs structure, scripts, and repetition. Running the technical rep's playbook on the green AE produces a rep who can talk about narrative theory and still cannot demo. Running the green AE's playbook on the technical rep produces open resentment.

Sixth: rescuing in live calls. Jumping in to save a demo that is going flat robs the rep of the actual repetition and signals to the buyer that the rep is not the owner. Sit on your hands, take notes, and debrief afterward. The exception is a genuinely at-risk strategic deal, and even then, be explicit afterward about why you broke the rule so the rep does not read it as a pattern.

Seventh, and this is the RevOps-specific one: instrumenting the wrong stage. Teams frequently see a demo-conversion problem and coach the demo when the actual defect is upstream. If discovery is thin, the rep genuinely has nothing to anchor a story to and every demo becomes a generic feature tour by necessity. Before running a ninety-day demo plan, check whether the rep's discovery calls surface a quantified business problem, a named stakeholder set, and a stated timeline. If they do not, the demo is a symptom and you are about to spend a quarter treating it.

Eighth: ignoring the demo environment itself. A rep working from a demo instance full of "Test Account 47" and lorem-ipsum data cannot tell a credible story no matter how well they are coached. Sandbox hygiene, industry-specific demo data, and a small library of pre-built scenarios are a systems investment that raises the ceiling for every rep at once. This is squarely RevOps territory and is frequently cheaper than a quarter of individual coaching.

Deciding what to do: skill, will, discovery, or casting

Route the diagnosis before you commit a quarter. The sequence below is deliberate — each question rules out a cheaper or more upstream cause before you land on the expensive individual-coaching path.

Read the branches practically. If you land on discovery, do not run demo drills — run discovery coaching for thirty days and re-measure the demo without touching it. In a meaningful share of cases the demo problem resolves on its own, because the rep now has three specific pains to anchor screens to and the narrative writes itself.

If you land on will, the sequence matters. Skill drills applied to a rep who thinks engagement is theater produce compliance without conviction, which reads worse on a call than the original monologue. Move the belief first, and move it with evidence rather than argument: have them watch two recordings of the same product demoed by different reps to similar buyers, one that converted and one that did not, and ask them to account for the difference. Let them build the case themselves.

If you land on system, escalate it out of the 1:1. One rep cannot fix a demo environment. This is where RevOps earns its keep — build the scenario library, seed the sandbox with realistic industry data, standardize the three or four demo paths that map to your main segments, and every rep's ceiling rises without a single coaching hour.

If you land on casting, have the honest conversation early rather than late. A rep who consistently prefers technical depth, dislikes persuasion, and does their best work in the supporting seat is often an outstanding sales engineer and a mediocre closer. Moving them is not a demotion in a well-designed org, and it is far kinder at month three than at month twelve after a missed number and a performance plan. Be direct, frame it as fit rather than failure, and be specific about what you have observed.

One more decision worth framing: individual coaching versus enablement programming. If a single rep shows this pattern, coach the rep. If three or more do, stop coaching individually and build the asset — a demo scorecard everyone self-scores against, a library of recorded reference demos by segment, and a standing thirty-minute weekly session where the team reviews one recording together. Group review has a compounding advantage over 1:1: reps calibrate against each other, the strong performers surface moves you would not have thought to teach, and the norm shifts faster than any individual plan moves it.

Adjacent patterns this coaching also fixes

The demo is where this shows up most visibly, but the underlying capability — running a two-way, pain-anchored conversation instead of delivering information — leaks into several neighboring motions, and coaching it once tends to improve all of them.

Discovery calls are the obvious neighbor. A rep who monologues in demos usually monologues in discovery too, just less noticeably, because discovery has fewer screens to hide behind. Watch for the tell: the rep asks a question, the buyer gives a two-sentence answer, and the rep moves immediately to the next question on the list instead of following up. That is the same behavior — treating the call as a script to complete rather than a conversation to steer. If you coach the demo without checking discovery, you will fix the visible half.

Technical validation and security review calls are the downstream neighbor. Technically strong reps often run these themselves and run them the same way, walking the buyer's technical evaluator through an exhaustive architecture overview when the evaluator has three specific concerns and no interest in the other forty minutes. The same fix applies: ask what they need to be confident, address that, stop. The rep's instinct to be complete is actively costing them time in a stage where speed matters.

Executive readouts and mutual-action-plan reviews are where the cost is highest. An economic buyer joining for twenty minutes will not sit through a capability tour, and a rep whose only mode is comprehensive coverage will use those twenty minutes badly. This is why the days sixty-one through ninety multi-stakeholder work matters — it is not a nice-to-have finishing skill, it is the stage where deals are won and where the boring-demo habit does the most damage.

Renewal and expansion conversations inherit the pattern too. A customer-success or account-management motion run by someone with the same instinct becomes a quarterly feature-release recap instead of a conversation about what has changed in the customer's business. If your post-sale team is staffed from the same technical talent pool, expect the same coaching need and the same fix.

Finally, internal communication. Reps who present rather than converse tend to run deal reviews the same way — a thorough narration of everything that has happened on the account, with no clear ask and no point of tension. This is worth naming because it gives you a low-stakes practice surface: coach the deal-review to be three sentences of situation, one specific risk, and one specific ask, and you are drilling exactly the same muscle in a setting where nothing is at stake if it goes badly.

Related questions

How do you coach a rep whose demos are engaging but who loses on technical depth?

The inverse problem, and usually easier. Pair them with a sales engineer for the technical portion, give them a five-question technical FAQ they must be able to answer cold, and coach them to say "I don't know, let me get you a precise answer" rather than improvising. Credibility loss comes from bluffing, not from gaps.

Should a sales engineer run the demo instead?

Often yes for complex products, but do not use it to dodge the coaching. Split the roles explicitly: the rep owns the narrative, the pain framing, and the next step; the SE owns depth and validation. If the rep hands the whole call to the SE, you have a casting question, not a staffing solution.

How many recorded demos should I review per rep per week?

One, reviewed properly, beats four skimmed. Twenty to thirty minutes of real analysis on a single call produces one specific coachable observation. Skimming four produces general impressions the rep cannot act on. Consistency matters more than volume — the same call every week at the same time.

Does this coaching work for remote or asynchronous demos?

Yes, with adjustments. Recorded async demos need tighter narrative discipline because there is no buyer to react to, so the story-arc coaching matters more and the pause-and-ask coaching matters less. Coach to a strict length limit and a single clear call to action instead.

How do I know when to stop coaching and start managing performance?

If the leading indicators have not moved after two full thirty-day cycles with consistent weekly review on your side, the plan is not working. At that point re-run the diagnosis honestly — most often you missed a will or casting issue at the start — and have the direct conversation rather than starting a third cycle.

FAQ

How do I tell a rep their demos are boring without crushing them?

Do not say it. Show a recording and ask how much of it was them talking. The data does the confronting and the rep keeps their dignity. Frame the entire conversation around raising win rate, not around fixing a personal flaw. Reps who feel judged defend; reps who feel coached experiment.

What if the rep insists the product is technical and demos have to be detailed?

Agree that depth matters, then reframe: depth on the right feature for this specific buyer beats coverage of everything. Have them watch a top performer demo the same technical product and count how few screens actually appeared. The count usually surprises them more than any argument you could make.

How long until the demos actually improve?

Structural changes — the story open, pain before each click — show up in the second or third demo because they can be prepared. Real interaction takes four to eight weeks. Command-level adaptation takes sixty to ninety days of weekly review. Track the leading indicators so you see progress before win rate confirms it.

Is this a coaching problem or a hiring mistake?

If the rep runs real discovery, can tell a pain-to-payoff story when prompted, and believes engagement matters, it is a coachable skill gap. If they consistently prefer technical depth and visibly dislike persuasion, they may be a stronger sales engineer. That is a casting conversation, and having it at month three is kinder than at month twelve.

Should I use conversation-intelligence tools for this?

They help substantially, because they turn a subjective "boring" into objective, timestamped coaching data — talk ratio, longest monologue, question counts. But the tool only diagnoses and measures. You still run the 1:1, the drills, and the follow-through review, and those are where the behavior actually changes.

What is the single highest-leverage change?

Tee up every screen with the pain it solves before clicking anything. "You said renewals slip through the cracks — watch this." That one move converts a feature tour into a value conversation faster than any other single change, and it is easy enough that a rep can apply it to their very next call.

Sources

• Gong Labs — Talk-to-listen ratio research
• MindTools — The GROW Model of Coaching and Mentoring
• RAIN Group — Sales Coaching Best Practices
• Harvard Business Review — The Secret to Developing the Perfect Sales Team
• Winning by Design — Revenue Architecture resources
• Sandler — Sales management and coaching blog
• Salesforce — What is sales coaching
• HubSpot — Sales demo best practices

Related on PULSE

• [How do you coach a rep who's great at demos but can't close?](/knowledge/cg0081)
• [How do you coach reps to stop doing feature-dump demos?](/knowledge/cg0062)
• [How do you coach a rep who gets ghosted after strong first calls?](/knowledge/cg0790)
• [How do you coach a rep who's slipping after a strong start?](/knowledge/cg0135)
• [How do you coach a rep with great results but low activity?](/knowledge/cg0164)
• [How do you coach a rep to write a strong breakup email?](/knowledge/cg0049)