CHURN IS DEAD
Your CSMs Are Selling You Snake Oil
9 min read · Strategy
Your CSMs Are Selling You Snake Oil
Sarah walked into the executive meeting with a thick folder of "customer insights." Twenty-three pages of verbatim customer quotes, sentiment analysis charts, and carefully crafted summaries of the "voice of customer" her CS team had captured over the quarter.
The CEO leaned forward. "This is exactly what we need. What are customers really telling us?"
Sarah opened to page one: "Customers want better integrations, faster support response times, and more training materials. They're frustrated with the onboarding process and need more customization options."
Sound familiar? It should. Because that's the exact same "insight" every CS team has been delivering to leadership for the past five years.
Here's the uncomfortable truth: Your CSMs aren't delivering customer insights. They're selling you snake oil.
The Great Voice of Customer Scam
Customer Success has positioned itself as the definitive source of customer intelligence. CSMs are supposedly your direct line to customer needs, market shifts, and product gaps. Leadership treats every CSM update as gospel because "they talk to customers every day."
But here's what's actually happening: Your CSMs are professional excuse-makers who've confused customer complaints with customer insights.
The difference is critical. A complaint is reactive noise: "Your platform is slow." An insight is predictive intelligence: "Customers who experience load times over 3 seconds during month two of onboarding have 60% higher churn rates because they haven't reached their first success milestone."
Most CSMs deliver the former while claiming it's the latter.
The Snake Oil Symptoms:
• Your "voice of customer" reports read like support ticket summaries
• Every customer insight sounds like a feature request
• CSMs can't quantify the business impact of what they're hearing
• The same "insights" appear quarter after quarter with no resolution
• Customer intelligence changes based on which CSM delivers it
The Five Lies CSMs Tell About Customer Intelligence
Lie #1: "I Know What Customers Need Because I Talk to Them Daily"
Talking to customers doesn't equal understanding customers. Your CSMs are having the wrong conversations.
They're reactive listeners, not investigative interviewers. When a customer says "we need better reporting," most CSMs dutifully note it as an insight. A real investigator asks: "What decision are you trying to make that current reports don't support? What happens when you can't make that decision quickly?"
The difference between collecting complaints and extracting insights is the depth of inquiry.
Lie #2: "Our Customers Are All Saying the Same Thing"
No, they're not. Your CSMs are pattern-matching surface-level complaints into false patterns.
When three customers mention "better integrations," CSMs report it as validation. But customer A wants integrations to automate manual processes, customer B wants integrations to reduce data silos, and customer C wants integrations to enable self-service. These are three different problems disguised as the same request.
Surface-level pattern matching creates the illusion of customer consensus where none exists.
Lie #3: "I'm the Voice of the Customer in This Organization"
Your CSMs aren't neutral conduits of customer voice. They're interpreters with their own biases, limitations, and blind spots.
Every CSM filters customer feedback through their own lens of what's "fixable" or "reasonable." They unconsciously suppress feedback that makes their job harder or amplify feedback that validates their existing priorities.
The voice of the customer shouldn't have an accent. When it does, you're hearing the CSM's interpretation, not the customer's reality.
Lie #4: "These Insights Will Drive Product Strategy"
Most CSM insights are strategically useless because they lack business context.
"Customers want more customization options" isn't product strategy input. "High-value customers in regulated industries are 3x more likely to expand if they can customize compliance workflows, and this represents 40% of our total ARR" is product strategy input.
Without quantified business impact, customer insights are just opinions.
Lie #5: "We're Customer-Centric Because We Listen to Customers"
Listening isn't the same as being customer-centric. Customer-centricity means making decisions based on what drives customer outcomes, not what customers say they want.
Customers told Netflix they wanted more DVDs by mail. Netflix built streaming instead. Customers tell your CSMs they want more features. Customer-centric companies might build better workflows instead.
True customer intelligence predicts behavior, not just preferences.
The Voice of Customer Reality Framework
Real customer intelligence follows a different pattern. It's investigative, quantified, and predictive. Here's how to transform your CS team from snake oil salespeople into intelligence analysts:
Component 1: Context Collection Before Conclusion
Stop letting CSMs report what customers say. Start requiring them to report why customers say it.
Every piece of customer feedback should include:
• The business situation that prompted the feedback
• The impact of the current state on customer operations
• The quantified cost of the problem to the customer
• Alternative solutions the customer has considered
Component 2: Pattern Analysis Over Pattern Matching
Replace surface-level complaint categorization with root cause analysis.
Instead of: "Five customers want better reporting"
Require: "Five customers can't make real-time inventory decisions because current reports have 24-hour delays, costing them an average of $50K monthly in stockout losses"
Component 3: Business Impact Quantification
Every customer insight must connect to business metrics.
CSMs should report:
• Revenue impact of addressing vs. ignoring the feedback
• Percentage of ARR affected by the underlying issue
• Correlation between the problem and customer health metrics
• Competitive advantage implications
Component 4: Predictive Intelligence Over Reactive Reporting
Shift CSMs from reporting what happened to predicting what will happen.
Traditional reporting: "Customer satisfaction decreased this quarter"
Predictive intelligence: "Customers showing these three early warning signals have 80% probability of churning within 90 days"
Component 5: Action-Oriented Recommendations
Customer insights without clear next steps are just interesting stories.
Every intelligence report should include:
• Specific recommended actions
• Resource requirements for implementation
• Expected timeline and success metrics
• Risks of inaction
Implementing the Framework
Start by auditing your current "voice of customer" process. Most CS teams will fail spectacularly at components 1, 3, and 4. That's not a criticism, it's a baseline.
Next, retrain your CSMs on investigative interviewing techniques. They need to learn how to ask follow-up questions, probe for business context, and quantify impact.
Finally, change your reporting structure. Stop accepting complaint summaries as customer insights. Require business impact quantification and predictive recommendations.
This isn't about making CSMs work harder. It's about making them work differently. The goal is fewer, higher-quality insights that actually drive business decisions.
Stop buying snake oil from your own team. Real customer intelligence requires discipline, training, and systematic process changes. Your CSMs can deliver genuine insights, but only if you stop accepting complaints disguised as strategy.
The companies that figure this out first will have a massive competitive advantage. The companies that don't will keep getting the same recycled "insights" quarter after quarter while their competition pulls ahead.
Kuber
P.S. If your last "voice of customer" report mentioned better integrations, faster support, or more training materials, you're definitely buying snake oil. Time for a reality check.
By Kuber Sethi · All issues · Subscribe