Skip to content

Frameworks Customer Experience, churn

Blueprint Equity Build Team22 Oct 20263-minute read

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 customer went.

For
CX leaders, CSMs and RevOps
Scope
6 primary and 17 secondary buckets
Used for
Churn reviews, save plans and QBRs
Owner
CSM for signals, department for fixes
Prepared by
Blueprint Equity Build Team
Reviewed by
Not yet reviewed
Issue
A, 22 Oct 2026
Status
Published
Pencil drawing of six identical pails on one ground line, with a dimension line marking six equal spans

Every churn event has two owners

Proactive: the CSM

Flag the risk before the cancellation call.

Across all six buckets, including the accounts that simply go quiet.

Reactive: the owning department

Fix the cause so it doesn’t recur.

Each bucket has a named department that owns the systemic fix.

If the cancellation is the first signal, treat it as a process gap, not a customer failure.

Give every churn event one primary bucket

If several causes exist, record the primary driver and tag the rest as secondary reasons. If two buckets look equally responsible, pick the one nearest the root cause and note the ambiguity.

Bucket, and what it meansWhat the CSM watches forWho fixes it, and how
Product gapA required capability is missing.
Log feature requests and quantify ARR at risk.Product. Audit the capability; decide to build, partner or deprecate.
Value gapThe capability exists, but the customer isn’t realizing value.
Track adoption against the purchased use case; run ROI check-ins at 30, 90 and 180 days.CX. Refresh adoption playbooks, ROI tools and pricing.
Experience gapThe product works, but support, reliability or service make it hard to work with.
Monitor ticket volume, severity and NPS weekly.Support and Product. Fix the top three process failures.
External gapA change outside our control, such as a budget cut, an acquisition or a shutdown, drove the loss.
Monitor funding, layoffs and leadership changes.Sales. Sharpen ICP and risk profiling.
Implementation gapOnboarding stalled or failed, so the customer never reached first value.
Escalate slipped first-value milestones the same week.CX and Services. Fix the onboarding playbook.
Sales gapThe customer bought something that can’t be delivered, or was a poor fit.
Surface mis-sold accounts in the first 60 days and route them back to Sales.Sales management. Improve ICP qualification and selling practice.

Tag the rest from a closed list

Optional, non-exclusive tags for portfolio-level pattern-finding. The list is closed; new values are added monthly, not on the fly.

Product and capability 6

  • Feature missing
  • Integration missing
  • Lost integration
  • Security or compliance
  • Known tech issues
  • Stability

Value and commercial 4

  • Low adoption
  • Pricing
  • No business case
  • Budget cut

Experience and relationship 4

  • Relationship
  • Too many support tickets
  • Failed implementation
  • Overpromised

External 3

  • RIF
  • Closing down
  • ICP

Record the competitor as a destination.

“Lost to a competitor” explains nothing about why they left. The destination is a required field, kept separate from the bucket that explains why the customer left.

Lost to[bucket];Required. One of the six buckets.went to[destination].Required. One of the five below.

  • Competitor
  • In-house build
  • Spreadsheets
  • Manual
  • Unknown

What the CSM does, and when

WhenRitualWhat happens
Weekly, MondayHealth scanReview usage, tickets, NPS and last executive touch. Flag accounts trending red on two or more signals.
Weekly, WednesdayExternal scanTrack funding, layoffs, news and leadership moves; log external risk as soon as it appears.
MonthlyBucket reviewTag each at-risk account to a bucket; bring the top three to the cross-functional save meeting.
MonthlyLoop to ownersReport bucket-level churn and saves to each owning department.

Roll it out in six steps

  1. Add the six buckets and the destination field to the CRM churn form as required fields.
  2. Add the secondary reasons as a closed multi-select.
  3. Assign a named owner in each department to each bucket.
  4. Build a dashboard of churned ARR by bucket and month, and show it first in every CX review.
  5. Run a coaching-style postmortem on any churn where risk wasn’t flagged at least 30 days out.
  6. Standardize loss recording as “lost to [bucket]; went to [destination].” The same wording as the competitor rule.

Put it to work

Work through this with the Build Team All frameworks

A22 Oct 2026. Moved to Blueprint Equity Design System v4.

More frameworks

  • 01

    The bottom-up expansion forecast

    Your CX function is a machine that opens expansion pipeline. Stop forecasting expansion as a percentage of your base. Build the named-channel machine that produces it.

    Read framework
  • 02

    The CSM equation

    Whether you need CSMs, and what they should do all day, is not a philosophy debate. It is three numbers: customer base, reachability and ACV.

    Read framework
  • 03

    The 4-week onboarding plan

    A plug-and-play onboarding system for early-stage founders. Replace every instance of [Company Name] with yours, assign owners, and hand it off. Built to be customized, not followed blindly.

    Read framework