How do you coach reps to stop doing feature-dump demos?

The two coaching paths: skill-building vs. structural fix

There are really only two levers that stop feature-dump demos, and most managers pull the wrong one first. The first lever is individual skill-and-confidence coaching — you work directly with the rep to change how they run discovery, how they select which capabilities to show, and how they confirm relevance mid-demo. The second lever is a structural fix — you change the demo script, the sandbox environment, the deck, or the comp plan that is quietly instructing every rep on the team to show everything.

Skill-and-confidence coaching is the right lever when the problem is isolated to one or two reps while the rest of the team demos tightly. You will see the tell in call recordings: the rep who feature-dumps has a longer talk-ratio, fewer discovery questions, and a habit of clicking through screens in a fixed order regardless of what the buyer said. This rep usually falls into one of two buckets — a skill gap, where they genuinely do not know how to connect a capability to a stated pain, or a will gap, where features function as a security blanket because qualifying questions feel confrontational. Both respond well to 1:1 coaching, role-play, and a demo scorecard, and both typically show measurable change inside four to six weeks of consistent review.

The structural fix is the right lever when feature-dumping is a team-wide pattern. If every rep on the team runs the same 35-screen guided tour, the problem is not eight individual reps making the same mistake independently — it is the sales motion itself. A demo deck built as a linear product tour trains every new hire to feature-dump from day one, no matter how strong their discovery skills are. In this case, no amount of 1:1 coaching fixes the root cause; you are coaching reps to fight the tool they were handed. The fix is rebuilding the demo script around a modular, persona-gated structure — three or four core screens per buyer persona, with the rest available only if the buyer asks — and retraining the whole team on the new script simultaneously.

Most RevOps orgs actually need both levers running in parallel, just weighted differently depending on what the data shows. If two reps out of ten are dumping and eight are not, spend 90% of your energy on individual coaching. If eight out of ten are dumping, spend 90% of your energy on the demo script and sandbox, because individual coaching against a broken system is coaching reps to defy their own enablement materials — a losing, exhausting fight that burns trust in the coaching itself. The practical move is to pull four weeks of demo recordings across the full team before you commit to either path, because guessing wrong here costs a full quarter of misdirected effort.

How to decide which path fits your rep

The decision tree below is the fastest way to route a specific rep to the right intervention instead of defaulting to generic demo coaching that does not address the actual cause. Walk it in order — do not skip to role-play before you have confirmed the rep even ran real discovery.

Use this tree on every rep who shows up in your feature-dump list before you plan a single coaching session. A rep routed to the skill or will path gets the 25-minute GROW conversation described below. A rep routed to the knowledge path gets a working session to build the persona map, not a confrontation about behavior. A rep routed to the system path should not be coached at all until the deck itself changes — coaching a symptom while the cause stays live just teaches the rep that your feedback is inconsistent with what the company hands them.

The numbers that separate a fixed rep from a repeat offender

Vague coaching produces vague results, so anchor the whole effort to numbers you can pull weekly from call intelligence tools like Gong, Chorus, or Clari. Here is what "fixed" looks like in measurable terms, and what "still dumping" looks like.

Talk-ratio before the screen-share opens. A rep running real discovery talks 40-50% of the pre-demo conversation and lets the buyer talk the rest. A feature-dumper talks 65-75% and treats discovery as a formality before the "real" part of the call. Track this number specifically in the five minutes before the screen is shared — it is the single best leading indicator you have.

Features shown per demo. Reps who feature-dump typically show 12-20 discrete capabilities in a standard 30-minute demo. Reps who have internalized tell-show-tell show 4-7. The drop is not because they know less product — it is because they stopped narrating a tour and started answering specific questions.

Feature-to-pain attachment rate. Score each shown feature as either tied to a pain the buyer stated out loud, or not. A feature-dumping rep runs 20-30% attachment — most of what they show was never asked for. A coached rep runs 80%+ within six to eight weeks of consistent review.

Demo-to-next-step conversion. This is the outcome metric that justifies the whole exercise. Feature-dump demos convert to a committed next step (a follow-up call with the right stakeholder, a technical validation, a pilot) at roughly half the rate of focused demos in most B2B SaaS pipelines. If you track nothing else, track this one, because it is the number that ties directly to pipeline velocity and gives you a business case for the time spent coaching.

Self-flag rate. Once a rep starts catching their own feature-dumps in the recording before you point them out, that is the strongest signal the skill has moved from coached to internalized. Early in the cadence this number is near zero; by week eight it should be climbing past 50% of instances caught by the rep first.

Time to visible change. Expect the discovery recap and reduced screen count to show up within three to four weeks of twice-weekly call reviews. Full internalization — where the rep runs tell-show-tell without prompting across a full quarter of deals — typically takes eight to twelve weeks. Reps who show no movement in feature-to-pain attachment after a full quarter of structured coaching are signaling a will or fit problem that more role-play will not solve.

Implementation details and sequencing

Building this into a repeatable program means sequencing the diagnosis, the coaching conversation, the drills, and the measurement in the right order — skipping steps is the most common way managers burn a quarter without changing behavior.

Start with a diagnostic pull, not a conversation. Before you say a word to the rep, pull three to five of their recent demo recordings and score talk-ratio, feature count, and feature-to-pain attachment. Walking into a 1:1 with data instead of an impression changes the entire tone of the conversation — you are showing the rep a pattern, not accusing them of a mistake.

Run the coaching conversation itself as a 25-minute 1:1 built on the GROW model — Goal, Reality, Options, Will. Open by playing 90 seconds of the rep's own recording where they stacked three or four features with nothing tying them to a stated pain, then ask what they notice. Move to Reality by asking how many of the shown screens mapped to something the buyer actually said. Move to Options by teaching tell-show-tell out loud and asking the rep which three screens they would keep if they could only show three. Close on Will by getting one specific, checkable commitment — "I'll do a 60-second discovery recap before I share my screen" — and write it down, because that sentence is what you inspect the following week.

Layer in drills across the next several sessions rather than front-loading everything into the first meeting. The three-screen drill — hand the rep a live opportunity and require they justify each of exactly three screens against a discovery quote — kills the tour reflex faster than any lecture. Pain-first role-play, where you interrupt as a skeptical buyer after the second feature and force the rep to reconnect to a stated pain, builds the muscle for handling real-time pushback. The mute-the-product drill, where the rep delivers the value story with the screen-share off, proves whether they are using the product to sell or to fill silence.

Sequence the cadence itself as a 30/60/90 arc rather than an indefinite weekly habit. Days 1-30: two call reviews per week, focused on diagnosis and building the persona-to-capability map together. Days 31-60: shift from reviewing past demos to rehearsing upcoming ones, introduce the scorecard, and expect the rep to start self-flagging. Days 61-90: drop to one review per week and watch the leading-indicator numbers above; if the behavior holds for three consecutive weeks, fade the cadence and move the rep into peer coaching so the skill keeps reinforcing without consuming your calendar indefinitely.

Any RevOps leader running this at scale should build the diagnostic pull into the normal call-intelligence workflow — Gong, Chorus, or Clari scoring rules can flag high talk-ratio, high feature-count demos automatically, so managers spend their coaching time on the conversation instead of manually scrubbing recordings looking for who is doing the most damage. Treat the automated flag as a starting point for the decision tree above, never as the final verdict — a flagged demo still needs a human to confirm whether the cause is skill, will, knowledge, or a broken system before you pick a fix.

Related questions

How do you coach a rep who's great at demos but can't close?

The demo usually is not the problem — check qualification of the economic buyer and multi-threading instead. A polished, well-attached demo to the wrong stakeholder still stalls; use MEDDIC or Command of the Message to find the real gap downstream of the screen-share.

How do you know if feature-dumping is a discovery problem or a demo problem?

Pull the pre-demo talk-ratio. Reps who ran real discovery rarely feature-dump because they already know the two screens that matter. Long, unfocused demos almost always trace back to a thin or skipped discovery call.

Should you fix the demo script before coaching individual reps?

Yes, if the majority of the team feature-dumps in the same pattern. Coaching reps against a deck built as a 40-screen tour teaches them to defy their own enablement materials, which wastes coaching time and damages trust.

How often should managers review demo recordings during an active coaching push?

Twice weekly for the first 30 days, tapering to once weekly through day 90. Less frequent review lets the old habit re-form between sessions; daily review usually outpaces what a rep can actually change week over week.

FAQ

How do I coach a rep who insists buyers want to see everything? Test the belief with their own data. Pull two of their recordings and show the drop-off point where buyers disengage after the second unrequested feature, then run the three-screen drill so they feel a tighter demo land and book a next step their old approach would likely have lost.

Is feature-dumping usually a discovery problem or a demo problem? Almost always discovery. A rep who deeply qualified the buyer's pain has no reason to show fifteen screens — they already know which two matter. If demos consistently run long and unfocused, audit the discovery call before touching the demo itself.

How long before this behavior actually changes? Plan on a 30/60/90 arc. Most reps show a tighter screen count and a discovery recap within three to four weeks of consistent twice-weekly reviews. Full internalization, where the rep runs tell-show-tell without you in the room, typically takes the back half of a quarter.

What if the rep demos tightly but still loses the deal? Then the issue has moved downstream, usually to qualification of the economic buyer or weak multi-threading after the demo. Use a framework like MEDDIC to check whether the deal has a real champion and confirmed metrics, and redirect your coaching there instead of the demo mechanics.

When does feature-dumping become a hiring problem instead of a coaching problem? If a rep still cannot connect a single capability to a buyer's stated words after a full quarter of structured GROW coaching, drills, and inspection, you likely have a will problem or a fit issue that coaching will not resolve — at that point it becomes a performance conversation, not another role-play session.

Should RevOps build automated flags for feature-dump demos instead of manual review? Yes, as a starting signal, not a verdict. Automated scoring on talk-ratio and feature count from tools like Gong or Chorus tells a manager where to look first, but a human still needs to route the flagged rep through the skill/will/knowledge/system decision tree before choosing a fix.

Sources

• Gong Labs
• Harvard Business Review — The Best Salespeople Do What the Best Coaches Do
• RAIN Group — Sales Coaching Techniques
• Winning by Design — Discovery and Demo Frameworks
• Performance Consultants — The GROW Model
• MEDDIC Academy
• Challenger Inc. Blog
• Clari Resources

Related on PULSE

• [How do you coach a rep to stop discounting to win deals?](/knowledge/cg0083)
• [How do you coach a rep who's great at demos but can't close?](/knowledge/cg0081)
• [How do you coach a rep whose demos are technically strong but boring?](/knowledge/cg0065)
• [How do you coach reps across multiple time zones?](/knowledge/cg0186)
• [How do you coach reps you never see in person?](/knowledge/cg0182)
• [How do you coach reps to handle silence and pauses on calls?](/knowledge/cg0180)