The Six Buckets of Churn
A shared classification for why customers leave. Six primary buckets, each with a CSM on the proactive side and an owning department on the reactive side, plus a separate field for where the account went. It gives churn reviews a consistent language and routes each root cause to an accountable owner.
Two Accountabilities for Every Churn Event
What this is forEach churn event carries two accountabilities. The CSM holds the proactive one: watching for early signals and flagging risk ahead of the cancellation call, regardless of which bucket the root cause falls into. Even an account that goes quiet is a signal a CSM can act on before shutdown. The department on the right holds the reactive one: the process or product change that reduces the next occurrence of the same bucket.
The CSM is expected to flag churn risk before the cancellation call. When the first signal is the cancellation itself, treat it as a process gap to close, not a customer failure. Proactive accountability sits with the CSM across all six buckets; the reactive fix sits with the owning department.
The Six Primary Buckets
Read each row as a scale. The CSM sits on the left of every bucket; the owning department sits on the right and differs by bucket, because that is where the reactive fix lives. Assign one primary bucket per churn event — the buckets are the reporting spine and are treated as mutually exclusive at the primary level. When more than one cause is present, record the primary driver here and capture the rest as secondary reasons (Section 03). If two buckets look equally responsible, choose the one nearest the root cause and note the ambiguity in the account record.
Log feature requests as they come in. Quantify ARR at risk per gap. Bring a ranked list to product review ahead of renewal, rather than a ticket filed after the cancellation.
Product Gap
The product cannot do what the customer needs. Use when a required capability is missing or incapable — not when the capability exists but is unused (that is Value Gap).
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
The product can do the job, but the customer is not realizing enough value from it. Use when adoption or ROI is the issue — not when a capability is missing (Product Gap) or the product is unreliable (Experience Gap).
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. Churn in this bucket usually follows a pattern of issues rather than one bad day, so track the trend per account and escalate when it worsens.
Experience Gap
The product does the job, but support, reliability, or service delivery makes it hard to work with. Use for stability and service issues — not for a missing capability (Product Gap).
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. Much external risk is visible in advance, so log it early and open the conversation before the customer raises it.
External Gap
A change outside our control drove the loss — budget cut, acquisition, shutdown, or a shift in the customer's business. Use only when the cause sits outside the product and our delivery; if we sold into a poor-fit account, that is Sales Gap.
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 that week rather than waiting for renewal. A stalled start tends to weigh on the account for the rest of the contract term.
Implementation Gap
Onboarding stalled, mis-fired, or never fully completed, so the customer never reached first value. Use when the product was fit for purpose but rollout failed — not when the wrong thing was sold (Sales Gap).
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 does not, raise it that week and route it back to Sales, rather than absorbing the reset and carrying the cost to renewal.
Sales Gap
The customer bought something we cannot deliver, or bought for the wrong reason or as a poor fit. Use when the mismatch traces to how the deal was sold or qualified — not to a rollout that went wrong (Implementation Gap).
Review ICP qualification, discovery rigor, and training. Coach reps to sell to the customer's outcome, and feed both wins and saves back into 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 broadly for pattern-finding rather than narrowly for a single event. The goal is the portfolio-level signal: if six of the last ten losses carry a Pricing tag, that is worth investigating even when only two were primarily pricing-driven.
Record the Competitor as a Destination
When a customer leaves for a competitor, record the competitor as the destination and classify the underlying reason in one of the six buckets separately. "They went to [X]" is the destination; a bucket is the reason they left. Capturing both fields preserves the analysis — the destination tells you where accounts go, and the bucket tells you why.
Where did they go?
Log this on every churn, including moves back to spreadsheets, paper, or no tool at all. Non-software destinations are often the most diagnostic, since they usually indicate the value was never established.
Why it mattersLogging "competitor" as the reason hides the actual gap and leaves no owning department accountable for a fix. Separating the reason (bucket) from the destination (competitor field) keeps both fields available for analysis and points each root cause at an owner.
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. This scan surfaces External-bucket risk; log it as soon as it appears rather than at renewal.
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, and Support each own a bucket-level number alongside 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 gets a postmortem — run it as a coaching review, not a blame session.
- Record losses as "lost to [bucket]; went to [destination]" rather than "lost to [competitor]." Standardize the phrasing so reporting stays consistent across the team.