The Six Buckets of Churn
A shared language for why customers leave. Six primary buckets, each with a CSM on the proactive side and an owning department on the reactive side. Because churn is never a surprise — and it's never someone else's problem.
The CSM Owns the Signal. The Department Owns the Fix.
Why this frameworkEvery churn event has two accountabilities. The CSM is proactively accountable for all churn — they should see it coming, regardless of root cause. Even "they shut down" is a signal the CSM should have flagged before shutdown day. The department on the right owns the reactive fix — the systemic change that prevents the next one.
No churn is a surprise. If the CSM learns about it on the cancellation call, the process failed — not the customer. Proactive accountability sits with CSM for every bucket, every time.
The Six Primary Buckets
Read each row as a scale. The CSM sits on the left of every bucket — always. The owning department sits on the right, different for each reason. That's where the systemic fix lives.
Log feature requests in real time. Quantify ARR at risk per gap. Bring a ranked list to product review — not a surprise ticket after cancellation.
Product Gap
The product can't do what the customer needs it to do.
Audit the specific capability. Is it in-flight, backlogged, or off-strategy? Decide build / partner / deprecate. Close the loop back to CSM.
Track adoption vs. purchased use case. Run ROI check-ins at 30/90/180. Escalate when usage drifts below the "sticky" threshold for the tier.
Value Gap
They have the product but aren't getting enough out of it.
Revisit the adoption playbook. Build or refresh ROI calculators. Test pricing strategies — right tier, right outcome, right proof.
Review ticket volume, severity, and NPS by account weekly. Customers don't churn on one bad day — they churn on a pattern. Spot the pattern.
Experience Gap
The product works, but dealing with us is painful.
Review stability metrics and ticket root causes. Fix the top-3 process failures. Close the loop on SLA, tone, and time-to-resolution.
Track funding events, RIFs, leadership changes, and news. External risk is visible if you're looking. Pre-empt the call, don't receive it.
External Gap
Something outside our control changed — budget, business, or the company itself.
Re-examine ICP signals: stage, funding runway, industry volatility. Stop selling into profiles where external risk trumps product fit.
Gate the handoff. If onboarding slips past the first-value milestone, escalate the same week — not at renewal. Bad implementations haunt you for 11 months.
Implementation Gap
Onboarding stalled, mis-fired, or never truly finished.
Review rollout steps, resourcing, and enablement. Tighten the handoff from Sales. Decide what can't be self-serve and staff for it.
In the kickoff, verify the expected outcome matches what was sold. When it doesn't, name it — don't quietly absorb the reset and then pay for it at renewal.
Sales Gap
The customer bought something we can't deliver, or bought for the wrong reason.
Review ICP qualification, discovery rigor, and training. Coach to outcome-sells, not feature-sells. Close the loop: wins and saves feed the playbook.
Secondary Reasons
Optional tags the CSM can add to any churn event for richer reporting. These do not have to map to a specific primary bucket — a single churn can carry multiple secondaries across buckets. Use them to look for patterns across the portfolio, not to justify a single event.
Product & Capability
Value & Commercial
Experience & Relationship
External
Tag aggressively, not precisely. You want the portfolio-level pattern — "six of our last ten losses tagged Pricing" is a signal, even if only two of them were primarily pricing-driven.
Competitor Is Never a Reason
If a customer leaves for a competitor, the competitor didn't cause the churn — one of the six buckets did. "They went to [X]" is the destination, not the reason. Capture it as its own field, always, and always in addition to a primary bucket.
Where did they go?
Log this on every churn — even when they're going back to spreadsheets, paper, or nothing at all. Non-software destinations are the most diagnostic: they tell you the value was never landed.
Why it matters"Competitor" as a reason hides the actual gap. It lets every department off the hook. Separating the reason (bucket) from the destination (competitor field) forces honest analysis and keeps the six-bucket framework intact.
The CSM Proactive Cadence
A weekly rhythm that makes "no churn is a surprise" operational. Short, predictable, and each step produces a signal.
Health scan
Usage, support tickets, NPS, last exec touch. Flag any account trending red on two+ signals.
External scan
Funding, RIFs, news, leadership moves. External bucket risk lives here — log it before the customer does.
Bucket review
Tag every at-risk account to one of six buckets. Bring the top three to the cross-functional save meeting.
Loop to owners
Report bucket-level churn and saves to each owning department. Product, Sales, Support all own a number — not just CX.
How to Roll This Out
- Add the six primary buckets and the destination field to your CRM churn form. Make both required — no save without them.
- Add secondary reasons as a multi-select. Keep the list closed — adding new values is a monthly decision, not a CSM-level one.
- Assign a department owner to each bucket in writing. Product, Sales, Support, CX, Sales Mgmt — names, not teams.
- Build one dashboard: churned ARR by bucket × month. This is the first slide of every CX review from now on.
- Any churn where the CSM didn't flag risk ≥30 days out becomes a postmortem — not a blame session, a coaching session.
- Never say "we lost them to [competitor]." Say "we lost them to [bucket]; they went to [destination]." Practice the phrasing until it's automatic.