Reference
Churn Definition
Learn the governed definition of churn, including logo churn, revenue churn, loss-event timing, edge-case treatment, and ClariLayer Drift Risk.
Metric 4 of 16
Retention
Churn
Churn measures the loss of customers, subscriptions, or recurring revenue from a defined starting population over a defined period, with the exact answer depending on whether the governed variant is logo churn, revenue churn, or another approved loss view.
Governed formula
lost logos or lost recurring revenue from the starting population / starting population
- Logo churn and revenue churn answer different questions and should keep separate labels.
- State whether downgrades, pauses, non-payment, reactivations, and product migrations count as churn, contraction, or neither.
Logo Churn
Counts customers from the starting population that are no longer active by the end of the period.
Useful for customer-base health, but it ignores the size of each lost account.
Gross Revenue Churn
Counts recurring revenue lost from churn and contraction before expansion offsets.
Useful for downside pressure, but it needs a clear boundary between full churn and contraction.
Net Revenue Churn
Offsets lost recurring revenue with expansion or recovery inside the same governed population.
Useful for net movement reviews, but it can hide loss patterns if expansion is not shown separately.
Decisions to lock
Is the governed metric counting logos, subscriptions, seats, or recurring revenue?
The grain determines whether a lost small account and a lost large account carry the same weight.
When does churn occur: cancellation request, contract end, service stop, billing stop, or data inactivity?
Different operational systems mark churn at different times, creating period misalignment.
How are pauses, downgrades, reactivations, non-payment, and product migrations classified?
Churn can be inflated or understated when edge cases move between churn, contraction, and retained states.
Validation questions
- Can each churned logo or revenue amount be tied back to a member of the starting population?
- Do cancellation, billing, and customer-success states agree on the churn date or expose a governed precedence rule?
- Are downgrades, pauses, non-payment, and reactivations reported as explicit exceptions instead of being hidden in churn?
Common drift traps
- A customer marked canceled in CRM still has an active billing subscription, so logo churn and revenue churn diverge without explanation.
- Downgrades are counted as full churn in one dashboard and contraction in another because the movement taxonomy is not governed.
- Reactivated accounts are removed from churn retroactively, changing historical retention without a visible version change.
Source-system boundary
Loss-event spine
Billing platform, Contracts, CRM, Customer success platform, Product analytics, Data warehouse
The governed definition should state the starting population, loss event, reactivation rule, and whether the metric is logo-based or revenue-based.
Context-layer proof
ClariLayer's context layer should keep churn tied to an approved grain, starting population, loss event, and edge-case taxonomy so teams can tell whether they are discussing logo loss, recurring revenue loss, or contraction.
- Governed signals
- metric grain, starting population, loss event, edge-case taxonomy
- Review cadence
- Review after cancellation-flow, billing-state, renewal-process, or customer-success-process changes.
ClariLayer Drift Risk
Churn is high risk because the same word is used for logo loss, revenue loss, contraction, non-payment, and inactivity unless the governed grain is attached.
Ambiguity
5/5The label churn does not reveal whether the metric counts logos, revenue, subscriptions, seats, or product activity.
Source-system dependency
5/5The metric can draw from CRM cancellations, billing status, contract end dates, success records, and product activity.
Time-window sensitivity
5/5Cancellation request date, service end date, billing stop date, and reactivation timing can move churn between periods.
Governance need
5/5Churn drives retention, forecast, customer-success, and finance decisions, so edge-case treatment needs approved ownership.
AI-agent risk
An AI agent can answer churn questions with the wrong grain if it does not know whether the user needs logo churn, revenue churn, contraction, or a retention-cohort movement view.