How do you coach a rep who always defaults to a feature dump instead of benefits
Kory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a Call
Direct Answer
You coach a rep out of a feature dump by shifting their mental model from "what does it do" to "what does it do *for you*." The root cause is rarely laziness — it’s usually a knowledge gap about the buyer’s world or a skill gap in translating technical specs into tangible outcomes. Your job is to install a repeatable framework (like FAB — Feature, Advantage, Benefit) and then drill it relentlessly through call shadowing, role-play, and post-call debriefs where you literally stop them mid-sentence and ask, *"What benefit does that feature give the customer?"* Over time, you replace the dump reflex with a diagnostic reflex — the rep learns to ask questions first, then match a benefit to what they just heard. This guide gives you the exact scripts, drills, and feedback loops to break the habit in 30 days.
Why They Dump — Diagnose the Root Cause
Before you prescribe a fix, figure out *why* the rep defaults to features. Most reps don't dump because they love specs — they dump because they're nervous, unprepared, or don't know how to ask discovery questions. There are three common root causes:
- Knowledge Gap: The rep doesn't understand the buyer's industry, role, or pain points. They can't connect a feature to a benefit because they don't know what the buyer cares about. If this is the case, your coaching starts with buyer persona research and industry context sessions.
- Skill Gap: The rep knows the buyer but has never been trained to translate features. They might have a technical background or were taught to "spec-sheet sell." Here, you need a structured framework like FAB (Feature, Advantage, Benefit) or SPIN (Situation, Problem, Implication, Need-payoff) to give them a new verbal muscle.
- Anxiety Gap: The rep is afraid of silence. They fill dead air with features because they think talking = selling. This is a confidence issue — they need to learn to ask a question and *shut up*. Role-play with deliberate silence is your tool.
A quick diagnostic: listen to three of their calls. Count how many open-ended questions they ask versus how many feature statements they make. If the ratio is 1:10 or worse, you have a clear diagnosis.
The FAB Framework — Your Core Tool
The FAB framework is the simplest, most teachable model for turning features into benefits. Here's how it works:
- Feature: A factual statement about the product. *"This CRM has automated email sequencing."*
- Advantage: What the feature does. *"It lets you send a series of follow-ups without manual work."*
- Benefit: What the advantage *means* to the buyer. *"So you can stay top-of-mind with every prospect without spending hours clicking send."*
The magic is in the benefit statement. It must be personalized to the buyer's specific situation. Coach your rep to always ask themselves: *"So what? Why does this matter to *this* person, right now?"* Drill this with a simple exercise: take your product's top 10 features and have the rep write a benefit for three different buyer personas (e.g., a CFO, a VP of Sales, and an IT Director). The benefit for the CFO might be cost savings; for the VP of Sales, time saved; for IT, security compliance.
Drills That Rewire the Habit
You cannot talk a rep out of a habit — you have to drill it out. Here are three high-impact exercises:
- The "So What" Game: For 10 minutes, the rep reads a feature aloud. You respond with "So what?" They must answer with a benefit. If they give another feature, you say "So what?" again. Repeat until they land on a genuine buyer outcome. This builds the translation reflex.
- The Question-Only Call: In a safe role-play, the rep is *forbidden* from stating any feature. They can only ask questions. The goal is to uncover the buyer's pain so deeply that when they *do* offer a benefit, it lands perfectly. This breaks the talk-first, listen-later pattern.
- The Post-Call Rewrite: After a real call (recorded), the rep transcribes every feature they mentioned. Next to each, they write the benefit they should have given. Then they practice saying those benefit statements aloud. This creates a feedback loop they can use independently.
Run one of these drills in every 1:1 for two weeks. Track their feature-to-benefit ratio — aim for 80% benefit statements by week three.
Real-Time Coaching on Live Calls
The fastest way to kill the feature dump habit is to intervene in the moment. But you have to do it without embarrassing the rep or losing the deal. Use these techniques:
- The Pre-Call Pause: Before a call, ask the rep, *"What's the one benefit you want the buyer to walk away remembering?"* This sets a north star and reduces the chance they'll ramble.
- The Mid-Call Nudge: If you're listening live (via a tool like Gong or Chorus), send a Slack message or text with a single word: *"Benefit."* This is a low-friction cue that the rep can act on without breaking flow.
- The Post-Call Debrief: After the call, don't say "You dumped too many features." Instead, ask: *"If you could redo one part, where would you have asked a question instead of listing a feature?"* Let them self-diagnose. Then reinforce with the FAB framework.
The key is timing — intervene early enough to prevent the dump, but late enough that the rep feels ownership of the fix.
How to Give Feedback That Sticks
Feedback on a feature dump can feel like a personal attack if the rep is proud of their product knowledge. Use the SBI model (Situation, Behavior, Impact) to depersonalize it:
- Situation: *"On yesterday's call with Acme Corp, when the CFO asked about pricing..."*
- Behavior: *"...you listed three features of the premium plan before asking what budget they had in mind."*
- Impact: *"That made it hard to tailor the pitch to their actual needs, and the call ended without a clear next step."*
Then immediately pivot to a forward-looking question: *"Next time, what could you ask instead of listing features?"* This keeps the conversation solution-oriented rather than punitive.
Also, catch them doing it right. When the rep delivers a clean benefit statement on a call, stop and acknowledge it: *"That was perfect — you turned a spec into a reason to buy. Do you notice the difference in how the buyer responded?"* Positive reinforcement builds the new habit faster than criticism.
Measuring Progress — The Feature-to-Benefit Ratio
You need a quantitative way to know if the coaching is working. Track the Feature-to-Benefit Ratio (FBR) on recorded calls. Here's how:
- Listen to a 5-minute segment of a call.
- Count the number of feature statements (e.g., "It has AI-powered scoring").
- Count the number of benefit statements (e.g., "So you'll spend less time on leads that won't close").
- Divide benefits by features. A ratio of 1:1 is average; 3:1 is excellent.
Track this weekly. If the ratio isn't improving after three weeks of drills, revisit the root cause diagnosis — you may have misidentified the gap. For example, if the rep knows the FAB framework but still dumps, the issue might be anxiety or entrenched habit, requiring more intensive role-play.
Share the trendline with the rep. Seeing their own improvement (or lack thereof) is often the most powerful motivator.
Kory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallThe "So What?" Drill: A Simple Intervention for Every Call
The fastest way to rewire a feature-dumping rep is to introduce a single, repeatable question they must ask themselves after every feature they mention: "So what?" This drill forces the rep to pause and articulate the benefit before moving on.
Start by role-playing a mock call. Every time the rep lists a feature (e.g., "Our platform has real-time analytics"), stop them and say, "So what?" The rep must then complete the sentence: "So what that means for you is..." This creates a mental bridge between the technical spec and the customer's outcome. For example, "Our platform has real-time analytics. So what that means for you is you can spot a drop in lead quality within minutes, not days, and adjust your campaign before you waste budget."
Make this a daily warm-up exercise for two weeks. Have the rep take three features from your product and write out the "So what?" for each one, tailored to three different buyer personas (e.g., a CFO, a VP of Sales, and an Operations Manager). This builds the habit of contextualizing benefits rather than reciting specs. During live calls, use a subtle signal—like tapping your pen or a code word like "pivot"—to remind the rep to ask themselves "So what?" if they start to drift into a dump.
To reinforce it, record a short segment of a call where the rep did this well. Play it back in a team meeting and ask, "What made that benefit land?" This positive reinforcement is more effective than criticizing the dump. Over time, the "So what?" becomes an internal reflex, and the rep learns to lead with the customer's gain, not the product's features.
The "Customer Story First" Rewrite Exercise
Feature dumps often happen because the rep is product-centric: they start with what they know best (the product) rather than what the buyer cares about (their problem). A powerful coaching tactic is to force the rep to rewrite their pitch from the customer's perspective—starting with a story of a similar customer who achieved a specific outcome.
Give the rep a blank document and ask them to write a 90-second opening for a discovery call using this structure: "A customer in your industry was struggling with [problem]. They tried [old approach], but it wasn't working. After working with us, they were able to [outcome]. Let me ask you—does that sound familiar?" This flips the script from "Here's what we do" to "Here's what someone like you achieved."
Then, have the rep map each feature they would have dumped to a line in that story. For example, instead of saying "Our tool has automated workflows," they now say, "That customer saved 10 hours a week because we automated their follow-ups." The feature is still there, but it's embedded in a narrative about the customer's success.
Repeat this exercise weekly, using a different customer case study each time. The goal is to build a mental library of "benefit stories" the rep can draw on spontaneously. During a live call, if the rep feels the urge to dump, they can pivot to a story: "That reminds me of another company that faced the same issue..." This is far more engaging than a feature list and positions the rep as a problem-solver, not a product presenter.
The "Two-Question Rule" for Discovery Calls
The root cause of many feature dumps is that the rep hasn't done enough discovery—they talk too early because they don't know what the buyer needs. A simple rule to enforce is: before you can mention any feature, you must ask and answer two discovery questions about the buyer's current situation.
During role-play or call shadowing, coach the rep to slow down. Every time they want to talk about a feature, they must first ask a question like:
- "How are you handling [process] today?"
- "What's the biggest frustration with your current approach?"
Only after the buyer answers can the rep say, "That's interesting—one reason our customers switch is because [benefit tied to that frustration]." This ensures the benefit is always a response to something the buyer said, not a pre-rehearsed script.
To make it stick, create a cheat sheet with five universal discovery questions the rep can memorize. During post-call debriefs, review the transcript and count how many features were preceded by a discovery question. If the ratio is low, that's the coaching point. Over time, the rep learns that their job isn't to talk about the product—it's to uncover a problem and then offer a solution that fits. The feature dump disappears because it's no longer the default move; it's a strategic response to a specific need.
FAQ
What if the rep argues that features are what the buyer wants? That's a sign they haven't been trained to listen. Ask them to replay a call and identify where the buyer actually *asked* for a feature vs. where the rep assumed. Usually, the buyer asks about outcomes, and the rep translates that into a feature list.
How long does it take to break the feature dump habit? With daily drilling and live coaching, most reps show measurable improvement in 2-3 weeks. Full rewiring of the habit takes 4-6 weeks of consistent reinforcement.
Should I ban the word "feature" entirely? No — features are important for credibility. The goal isn't to eliminate features, but to always pair them with a benefit. Teach the rep to say "We have X, which means Y for you."
What if the rep is a former engineer or product person? This is common. Their identity is tied to technical knowledge. Reframe the coaching: "Your deep product knowledge is an asset — now let's learn how to translate it into the buyer's language." Use analogies and customer stories to bridge the gap.
Can this be fixed with call recording software alone? Tools like Gong or Chorus can flag feature-heavy calls, but they can't teach the rep *how* to change. You still need human coaching — the drills and feedback loops — to rewire the behavior.
What do I do if the rep resists coaching on this? Resistance often comes from fear of looking less knowledgeable. Acknowledge their expertise, then set a clear expectation: "I'm not asking you to know less about the product. I'm asking you to know more about the buyer. Let's try it for two weeks and see if your close rate improves."
Sources
- Sales Hacker — Articles on FAB framework and benefit selling
- Gong Labs — Research on call analytics and feature-to-benefit ratios
- Chorus.ai (now ZoomInfo) — Best practices for call coaching and feedback
- RAIN Group — Training on consultative selling and buyer-centric communication
- HubSpot Sales Blog — Guides on moving from features to benefits
- The Sales Enablement Society — Community resources on coaching frameworks
- Forbes — Articles on sales coaching and habit change
- Harvard Business Review — Research on feedback models like SBI
Related on PULSE
- Explore more in the PULSE library.