← All Posts

The Churn That Doesn't Show Up in Your Churn Rate

Your churn rate is lying to you.

Not because the math is wrong. Because it's measuring the wrong thing.

Churn rate counts the customers who leave. It doesn't count the revenue you lose from the customers who stay — and quietly downgrade at renewal because they never got enough value out of what they bought to justify renewing at the same level.

That's contraction. And for most CS organizations, it's a bigger revenue problem than churn. It just doesn't show up where they're looking.


The Right-Sizing Problem

Here's how it happens.

A customer buys your product at a certain level — let's say 50 seats, or a mid-tier plan, or a contract that includes a capability they intend to use. In the first 90 days, adoption is shallow. They're using maybe 30% of what they bought. Life gets busy. The deep-use-case rollout gets deprioritized. Nobody on your team pushes back because the customer isn't complaining and the health score is green.

At renewal, the customer looks at their usage data. They're paying for 50 seats and using 30. They're paying for a capability they haven't really deployed. They have a renewal conversation with their CS team, and the outcome is a "right-sized" contract that reflects their actual usage rather than their original intent.

Revenue dropped. NRR took a hit. And your churn rate didn't move.


Why This Is an LTV Problem, Not a Renewal Problem

The framing of contraction as a renewal problem is what causes CS teams to address it too late.

By the time a customer is right-sizing at renewal, the outcome was determined months earlier. The customer who is only using 30% of what they bought at month 11 was only using 30% at month 6. The signal was there. The intervention window was open. Nobody walked through it.

The renewal conversation is when the consequence becomes visible. The cause is in the adoption phase.

This is why LTV thinking is so much more powerful than churn thinking. When you're focused on LTV, you're asking: what happens to the total value of this customer relationship over time? What does the trajectory look like? Where is it accelerating and where is it flattening?

A customer with shallow adoption has a flattening LTV trajectory. Catch it at month 3 and you can change it. Catch it at month 11 and you're negotiating the contract down.


The Compounding Upside

Here's the flip side that most CS leaders miss.

Customers who achieve depth adoption — who are actually using the features and capabilities they paid for — don't just renew at the same level. They expand earlier than you expect. Often well before renewal.

Why? Because they've gotten enough value from the core use case that they're now thinking about the adjacent one. They're not questioning whether they should keep paying for what they have. They're asking what else they can do.

That's a completely different conversation. And it happens months before the renewal, not at it.

Getting adoption right doesn't just protect the renewal. It pulls the expansion timeline forward. It increases ACV. It makes the customer a reference and an advocate. It compounds across the entire lifetime of the relationship.

The difference between a customer who achieves depth adoption and one who doesn't isn't just retention. It's the entire LTV trajectory. It's the difference between a customer worth $50K over their lifetime and one worth $200K.

You have almost full control over which one they become.


What Gets in the Way

Most CS teams know this intuitively. They know that shallow adoption leads to contraction. They know that depth adoption leads to expansion. They know that catching the signal early is the difference between intervention and damage control.

What they don't have is a system that surfaces the signal at the right time, for every account, without requiring a CSM to manually review 80 accounts every week to find the ones that need attention.

That's not a people problem. It's a workflow problem. And it's a solvable one.

The right agentic workflow surfaces the accounts that are showing signs of shallow adoption before the trajectory is set — giving your CSMs the visibility to intervene when intervention actually matters.

Not at renewal. At adoption.

That's where LTV is won and lost. Not in the renewal conversation. In the 90 days before anyone is thinking about renewal.


Lincoln Murphy formally named and popularized Customer Success starting in 2010 and has spent 15 years connecting it to expansion revenue and commercial outcomes. Read The Premise.

Access the 5x LTV Case Study.

See how one CRM SaaS drove 5x LTV in 90 days. Full framework, milestone breakdown, and cohort analysis.

← Previous
The Reveal Is the Pitch
Next →
What Complexity Are You Forcing Onto Your Customer That You Could Eat?