CHURN IS DEAD
CS Teams Don't Have a Churn Problem. They Have a Courage Problem.
6 min read · Strategy
Archive note: This issue predates the evidence ledger introduced in August 2026. Treat uncited benchmarks and examples as editorial analysis, not independently verified findings.
Customer Success has a dirty secret: We've become really good at predicting churn and terrible at preventing it.
The industry spent the last decade building increasingly sophisticated health scores, risk alerts, and predictive models. We can tell you with 87% accuracy which customers will churn in the next 90 days. We just can't do anything meaningful about it.
Why? Because somewhere between "customer-centric" and "proactive engagement," CS teams lost the ability to have difficult conversations. We optimized for customer comfort instead of customer outcomes. We became professional excuse-makers who measure success by how rarely customers complain, not by how often they achieve their goals.
The result: CS teams that sound like therapists in renewal meetings and wonder why their "partnership" conversations end with one-year contracts and seat reductions.
With AI eliminating 70-80% of support tasks and CFOs demanding CS justify their existence, teams that can't move beyond reactive churn prevention to proactive value creation are being cut first. Block eliminated 4,000 positions as AI systems absorbed Tier 1 work. Salesforce quietly reduced support from 9,000 to 5,000 people while claiming "redeployment."
The teams that survive this wave aren't the ones with the best health scores. They're the ones with the courage to tell customers hard truths.
The Comfort Optimization Trap
CS teams measure the wrong thing: customer satisfaction instead of customer progress.
We celebrate CSMs who "manage difficult conversations well" instead of CSMs who eliminate the need for difficult conversations by addressing problems before they metastasize. We promote people who can explain away low usage rather than people who can drive high usage.
The enterprise reality: Your customer isn't paying you $200K annually to make them feel good about their poor adoption. They're paying you to ensure they get $2M in value. Those are different jobs.
But CS teams have convinced themselves that being "customer-centric" means never making customers uncomfortable. So we create elaborate justification frameworks for why their ROI calculation is wrong, why their usage patterns are actually fine, and why their concerns about renewal aren't valid.
Meanwhile, their actual business metrics deteriorate. Their executive sponsor gets fired. Their budget gets cut. And they blame the economy.
Why Customer Success Became Customer Comfort
Three forces conspired to turn strategic advisors into professional excuse-makers:
The Support Team Mindset Migration: When companies moved support teams into CS, they imported the support team's core operating principle: resolve the immediate concern with minimal escalation. Support optimizes for case closure. CS adopted this optimization for conversation closure.
The Vendor-Customer Power Dynamic Myth: CS leaders teach CSMs that customers "hold all the power" in renewal conversations. This creates a negotiating stance where CS argues from weakness. You can't drive transformation from a position of assumed inferiority.
The Expansion Revenue Without Expansion Authority Problem: CS got assigned expansion targets but not expansion capability. So instead of building systems to drive value that naturally expands, they learned to make excuses for why expansion isn't happening.
The result: CS teams that approach every customer conversation like they're asking for a favor instead of delivering a service the customer bought.
The Courage Ladder Framework
Strategic CS requires four levels of conversational courage. Most teams never climb past Level 1.
Level 1: Truth-Telling
Share usage reality vs. stated goals without softening the message.
*Comfort CS*: "Your adoption has been a bit slower than we initially projected, but that's totally normal in the first quarter."
*Courage CS*: "Your team logged in 12 times last month. Your success plan assumed 200+ logins. At this pace, you'll miss your Q1 efficiency target by 60%."
Level 2: Gap-Naming
Identify the specific difference between current state and success without offering immediate solutions.
*Comfort CS*: "There are some opportunities to optimize your workflow."
*Courage CS*: "Your approval process adds 8 days to every transaction. Your goal was 2-day cycle times. Either we redesign the approval workflow or we reset the success criteria."
Level 3: Investment-Challenging
Question whether their current approach matches their stated ambition.
*Comfort CS*: "What additional resources might help accelerate adoption?"
*Courage CS*: "You want to save $500K annually but you've assigned one part-time person to this implementation. Companies that hit these targets assign 2-3 full-time people in month one. What are you actually optimizing for?"
Level 4: Future-Forcing
Make them choose between change and consequences without managing their emotional response.
*Comfort CS*: "We want to make sure you get maximum value from the platform."
*Courage CS*: "Based on current usage patterns, you'll spend $200K this year and save approximately $30K. Your CFO will not approve renewal. We can change the usage pattern or we can document the business case for why this approach failed. Which conversation do you want to have in Q4?"
What Courage Looks Like In Practice
Courageous CS doesn't mean being harsh. It means being useful.
In onboarding calls: Instead of asking "How's the rollout going?" ask "Show me your usage dashboard. Walk me through why these three departments haven't logged in."
In QBRs: Instead of presenting health scores, present gap analysis. "Here's where you said you'd be in Q1. Here's where you actually are. Here's what has to change in Q2."
In renewal discussions: Instead of defending pricing, defend value. "Renewal isn't a discussion about cost. It's a decision about commitment. Are you committed to achieving the outcomes we designed this program around?"
In expansion conversations: Instead of pitching features, present math. "Your current configuration supports 50 transactions daily. You're processing 140. We can upgrade your capacity or we can document why the system is failing your growth."
The pattern: Replace comfort with clarity. Replace explanation with expectation. Replace justification with facts.
The Cost of Comfort
Every comfortable lie you tell a customer costs you strategic credibility.
When you explain away poor adoption, you signal that poor adoption is acceptable. When you justify missed milestones, you communicate that milestones are optional. When you offer to "customize the success metrics," you announce that success is negotiable.
Customers don't respect advisors who optimize for their comfort. They respect advisors who optimize for their results.
The enterprise pattern: Executive sponsors prefer CS partners who tell them what they need to hear over CS partners who tell them what they want to hear. The CFO who questions renewal decisions doesn't want to hear about "implementation challenges." She wants to hear about business impact.
Comfort optimizes for today's conversation. Courage optimizes for next quarter's outcome.
Building Conversational Courage
Most CS teams need structured practice in uncomfortable conversations.
The Monthly Truth Audit: Review your last 10 customer calls. Count how many times you shared negative data without immediate solutions. If the ratio is below 30%, you're optimizing for comfort.
The Executive Sponsor Test: Before every customer interaction, ask: "Would I say this to their CEO?" If not, you're not operating at the right level.
The Renewal Reality Check: In every conversation, answer: "Based on today's discussion, are they more likely or less likely to renew at current spend?" If you can't answer, you're not asking the right questions.
The Future State Forcing Function: End every meeting with a specific commitment or a specific concern. "You'll complete user training by Friday, or we'll need to discuss timeline adjustments." No meeting ends with "Let's check in next week."
Courage is a muscle. The more you exercise it, the stronger it gets.
The CS teams that survive the AI wave aren't the ones with the most sophisticated health scores. They're the ones willing to have the conversations that health scores can't automate.
Customers don't need another vendor who makes them feel better about their problems. They need advisors who help them solve their problems.
The choice: Comfortable conversations that lead to churn, or courageous conversations that lead to outcomes.
Your next customer call is your next opportunity to choose.
By Kuber Sethi · All issues · Subscribe