TL;DR
- The six churn archetypes are: value-not-realised, wrong-fit customers, competitor-switch, budget-cut, champion-left, and feature-gap.
- Each has a distinct signal in product usage data that fires weeks before the cancellation event in your dashboard.
- By the time churn fires in your analytics, the decision was made 30–60 days earlier. Most teams are reading the outcome, not the leading indicator.
- The wrong intervention for the right churn type produces no result — and sometimes accelerates the decision to leave by making the interaction feel off-point.
Why the churn event fires too late
Churn analysis typically starts at the cancellation event. A user cancels, the event fires, it lands in the churned cohort, and someone pulls up the dashboard to understand what happened. The problem is that by this point, the question is historical — the decision to leave was made weeks ago.
The decision to cancel a SaaS subscription typically happens weeks before the cancellation event fires. It looks like a gradual disengagement in the usage data: login frequency drops, specific features go unused, session length shortens. Sometimes there is a specific trigger — a competitor comparison, a budget cut email, a champion leaving the company. But the trigger lands on top of a user who was already mentally out the door.
This means that a retention program anchored on the cancellation event is too late for most accounts it is trying to save. Early warning signals — leading indicators that predict churn before the cancellation decision solidifies — are the only signals that leave enough time to change the outcome. And those signals are different for each churn archetype.
The typical gap between when a customer decides to churn and when the cancellation event fires in your analytics. Most churn dashboards read the outcome. Early warning systems read the decision as it forms.
The six archetypes
Value-not-realised
The user signed up, explored the product, and left before ever reaching the activation event — the moment that marks genuine adoption. They did not get value because the onboarding never delivered them to it. This is not failure to convince; it is failure to guide.
Wrong-ICP (wrong ideal customer profile fit)
The customer was never a good fit. They came through a channel that does not qualify for ICP (ideal customer profile) alignment, passed a sales process that did not surface the mismatch, and churned as soon as the reality of the product became apparent. This is a sales and qualification problem, not a retention problem.
Competitor-switch
A better-fitting alternative emerged or was discovered. The user evaluated it — sometimes prompted by a competitor ad, sometimes by a peer recommendation — and chose to switch. This churn type is the one most teams over-index on, often because it is the most visible in exit surveys. It is also the one where the intervention is most frequently misdirected.
Budget-cut
The product delivered value. The customer had no complaint about the product. The cancellation was a budget decision — a cost reduction exercise, a founder pulling back on tools spending, a procurement audit. This is externally caused churn, and the intervention set is entirely different from product-driven churn types.
Champion-left
The primary user — the person who drove adoption, trained their team, and owned the relationship with the product — left the company. Their successor inherited an account but not the context, the muscle memory, or the internal advocacy. Without a champion, the product is at risk from the moment the login stops.
Feature-gap
The product does not do the specific thing the customer needed. The gap may have been known at purchase and accepted as "close enough" — or it may have emerged as the customer's use case evolved. Either way, the customer has been working around the missing functionality, and at some point the workaround cost exceeds the product's value.
How to identify which type you have
The six archetypes are not mutually exclusive — a churned account can exhibit signals from multiple types simultaneously. Budget-cut churn often coincides with champion-left. Feature-gap churn often precedes a competitor-switch. The goal is not to assign a single label to every churned account; it is to identify the primary driver at the cohort level so the intervention targets the right problem.
The diagnostic framework has three layers:
| Layer | Data source | What it surfaces |
|---|---|---|
| Product usage | Event stream, session data, feature adoption | Activation status, feature breadth, login patterns, export activity |
| Account data | CRM, billing, support tickets | Sales cycle length, deal source, support ticket themes, payment history |
| Timing | Churn date vs. calendar, vs. product releases, vs. company news | Budget cycle correlation, champion departure correlation, feature launch correlation |
When these three layers are combined and segmented by churn timing, the dominant archetype for each cohort becomes visible. A cohort where 60% of churned accounts had zero activation event completions is a value-not-realised cohort. A cohort where churn clusters in Q1 and the champion-left signal is present in 40% of accounts is a combined budget-cut and champion-left problem — two separate intervention tracks.
Building the early warning system
An early warning dashboard does not track cancellations. It tracks the leading indicators — the behavioural signals that precede each archetype — and surfaces accounts that are showing them before the decision calcifies.
Each archetype has a corresponding early warning signal that fires weeks before the churn event:
- Value-not-realised: user reaches day 7 without completing the activation event
- Wrong-ICP: feature breadth score below threshold at 14 days
- Competitor-switch: integrations page + data export within the same week
- Budget-cut: payment failure or downgrade at renewal, or Q1/Q4 timing
- Champion-left: primary user login gap exceeding 7 days with no secondary user activity
- Feature-gap: same feature request category appearing in two or more support tickets from the same account
None of these signals require a data warehouse or a machine learning model. They require a tracking plan that captures the right events, a tool that can query the event stream, and a dashboard that makes the signals visible to the person whose job is to act on them.
Churn Analysis & Prevention
In the Churn Analysis & Prevention cohort, you build the early warning dashboard for your own product — against your real data. You leave with the signals defined, the dashboard built, and the intervention playbook mapped to each archetype you actually have.
Frequently asked questions
Why does the churn event in my dashboard fire too late to act on?
The decision to cancel is typically made 30 to 60 days before the churn event fires in your analytics. By the time a cancellation registers, the user has already mentally disengaged, often stopped logging in, and frequently already evaluated alternatives. Early warning signals — login frequency drops, feature adoption reversals, support ticket patterns — fire weeks before the churn event and are the only signals that leave time to intervene.
What is value-not-realised churn?
Value-not-realised churn occurs when a user cancels before ever completing the activation event that marks genuine product adoption. They signed up, explored, never hit the moment where the product became worth keeping, and left. The signal is churn that clusters before the activation event in your funnel. The intervention is onboarding redesign or in-app guide triggers — not a win-back campaign.
What is champion-left churn?
Champion-left churn occurs when the primary user or buyer who drove adoption at an account leaves the company. Their successor has no relationship with the product and no history of its value. The signal is a primary user login stopping, followed by the account going dark. The intervention is multi-stakeholder onboarding and account-level adoption records that do not depend on a single champion.
How is budget-cut churn different from other types?
Budget-cut churn is externally caused — the product did not fail the customer. External signals include churn clustering in Q1 or Q4 (renewal budget periods), accounts where the champion was downgraded or title-changed before leaving, and macroeconomic headwinds in the customer's industry. The intervention is not product improvement — it is pricing flexibility, pause options, and downsell paths that reduce the pressure to cancel entirely.
About the Author
Jake McMahon writes about analytics architecture, product instrumentation, and the decisions B2B SaaS teams make when building their data foundations. ProductQuant helps teams design what to instrument, set it up correctly the first time, and connect analytics to decisions that affect revenue.
Know which type of churn you have before you build a retention program.
The Churn Analysis & Prevention cohort walks through the diagnostic framework against your own product data and builds the early warning dashboard you will actually use.