Churn

Pipeline

The rate at which customers cancel or stop paying, measured as a percentage of revenue or accounts lost over a period.

What is Churn?

Churn is the rate at which customers cancel their subscription or do not renew their contract within a given period. It is measured as a percentage of customers or revenue lost in a period divided by the total at the start of that period. Revenue churn, also called MRR churn, is typically more meaningful than customer count churn because it reflects the commercial impact rather than headcount, and large and small customers count equally in count-based churn metrics.

Churn is the single most important efficiency metric for subscription businesses because of its compounding effect. At 5% monthly churn, a company that does not acquire a single new customer loses over 50% of its customer base in 12 months. The inverse is also true: reducing churn from 5% to 2% monthly has a larger impact on long-term revenue than doubling the new customer acquisition rate while keeping churn constant.

Churn has two main categories: voluntary churn, where customers actively choose to cancel, and involuntary churn, where customers lapse due to payment failures or administrative issues. Voluntary churn indicates product, value, or relationship problems. Involuntary churn is a recoverable mechanical problem that can be addressed with payment retry logic and dunning sequences. Separating the two produces more actionable diagnostics.

The primary drivers of voluntary churn are: not achieving the expected outcome from the product, poor onboarding that prevents customers from reaching activation, competitive alternatives that better satisfy evolving needs, and changes in customer circumstances such as budget cuts or company restructuring. Exit interviews and churn surveys are the most direct source of data for diagnosing which driver is most significant in your specific customer base.

In a B2B pipeline model, this is only useful if it changes resourcing or prioritization. A clean definition helps the team decide where to push harder, where to cut waste, and which funnel step deserves attention next. It usually becomes more useful when it is defined alongside LTV, Expansion revenue, and Net revenue retention.

Churn — example

A SaaS company has 2% monthly logo churn, which seems low until they calculate annualised revenue impact. 2% monthly churn means roughly 22% annual customer loss. At an average ACV of £12K, and 200 customers, they are churning £528K in ARR annually — equivalent to their entire new customer acquisition for the year. A dedicated customer success programme targeting customers showing low product usage signals reduces monthly churn to 1.1% within two quarters, adding the equivalent of 100 retained customers' ARR to the business.

A B2B company cleans up how it uses Churn after noticing that leadership likes the headline number but cannot explain what operationally caused it to move. They rebuild the logic so the term maps back to specific pipeline actions and owners. They also make sure it connects cleanly to LTV and Expansion revenue so the definition is not trapped inside one team.

Frequently asked questions

When does a B2B team need to define Churn more carefully?

Churn becomes important when it starts affecting decisions, handoffs, or measurement. If different teams use the term differently, or if the concept changes how leads, deals, campaigns, or workflows move, it deserves a clear definition. The main reason to formalize it is to improve operating quality, not to make the glossary longer.

How can a team tell whether Churn is working well?

Strong Churn is clear enough that two smart people would apply it the same way under pressure. It should make the workflow easier to run, not harder to explain. In practice, that usually means cleaner inputs, fewer edge-case debates, and better downstream consistency.

What usually goes wrong with Churn?

The most common mistake is using Churn as loose language instead of as an operating rule. Once different teams start interpreting it differently, reporting gets noisy and handoffs weaken. The fix is usually a simpler definition, clearer ownership, and a few worked examples.

What is the best way to review Churn on a regular basis?

Review Churn wherever it affects real execution. That may be in CRM audits, dashboard reviews, campaign analysis, or manager callouts during weekly meetings. The key is to tie the term to one decision or action so the team knows why it is being reviewed.

What is the most important companion idea to review with Churn?

If you want Churn to hold up in the real world, review it with LTV. Most glossary terms become far more useful when they are linked to the adjacent process that creates or validates them. That is usually where the practical leverage sits.