On this article

Churn Rate Explained: What It Is and How to Reduce It

What churn rate is, how to calculate it, why it quietly caps growth, and the practical levers to reduce it before users leave.
This is some text inside of a div block.

Churn Rate Explained: What It Is and How to Reduce It

You can pour users into the top of your funnel forever and still not grow — if they leak out the bottom just as fast. That leak is churn, and it's the metric that quietly decides whether all your acquisition and activation work actually compounds or just treads water. The good news: churn is measurable, diagnosable, and — with the right focus — very reducible.

The short version: Churn rate is the percentage of customers (or users, or revenue) you lose over a given period. You calculate it by dividing the number who left during the period by the number you started with. It matters because churn caps growth — every lost customer is one you have to re-acquire just to stand still — and because small differences in churn compound enormously over time. To reduce it, find where and why users leave using cohort and retention analysis, get more users to real value early (activation), and intervene before at-risk users go quiet rather than after.

What is churn rate?

Churn rate measures how many customers or users stop using your product over a set period — the mirror image of retention. If retention is who stays, churn is who leaves. It's usually expressed as a percentage over a window (monthly or annual), and it's one of the clearest health signals a subscription or product business has: high churn means you're losing the customers you worked to win.

A quick but important distinction: customer churn (how many accounts leave) and revenue churn (how much revenue leaves) can tell different stories. If you lose lots of small accounts but keep your big ones, customer churn looks scary while revenue churn stays fine — and vice versa. Serious teams track both.

How to calculate churn rate

The basic formula is simple:

Churn rate = (customers lost during the period ÷ customers at the start of the period) × 100

For example, if you began the month with 1,000 customers and 50 left, your monthly churn rate is 5%. Revenue churn works the same way, using recurring revenue lost instead of customer count.

Two things to keep consistent so the number stays meaningful: the window (monthly and annual churn are very different figures — don't compare them directly), and how you handle customers who joined during the period (most teams measure against the starting cohort to keep it clean).

What's a good churn rate?

Be skeptical of any universal benchmark — a "good" churn rate depends heavily on your business model, price point, and customer type. Consumer apps typically see much higher churn than enterprise software; a self-serve tool churns differently than an annual contract. A number that's healthy in one context is alarming in another.

So rather than chase someone else's benchmark, watch your own churn trend over time and segment it. The most useful comparison isn't you-versus-the-industry; it's this month versus last, and your healthy segments versus your leaky ones.

Why churn rate matters so much

Churn punches above its weight for two reasons:

  • It caps growth. Every churned customer is one you have to re-acquire just to stay flat. When churn is high, acquisition becomes a treadmill — you run faster and stay in place. Reducing churn is often cheaper and higher-leverage than buying more traffic.
  • It compounds. Small churn differences create huge long-term gaps. A product retaining 95% of customers each month keeps far, far more of them a year out than one retaining 90% — the gap widens every month. This is the flip side of your retention curve, and it's why a point or two of churn is worth real effort.

How to reduce churn rate

Churn is a symptom; reducing it means treating the causes. Five levers, roughly in order of leverage:

  1. Find where and why users leave. Use cohort analysis to see when churn spikes (early? after month three?) and segment to see who churns most. You can't fix churn you haven't located — early churn and late churn have completely different causes.
  2. Fix early churn with activation. A huge share of churn is really failed onboarding — users who never reached value in the first place. Improving your activation rate is often the single biggest lever on churn, because a user who never got value was always going to leave.
  3. Catch at-risk users before they go quiet. Declining usage usually precedes cancellation. Identify the behavioral signals of a disengaging user (fewer logins, dropped key actions) and intervene while they're still reachable — not after they've cancelled.
  4. Close the value gap for the right reasons. Talk to churned users. If they're leaving over a missing feature, a pricing mismatch, or a recurring frustration, that's a roadmap — and a few systemic causes usually explain most of the churn.
  5. Reduce involuntary churn. A meaningful slice of churn isn't a decision at all — it's failed payments and expired cards. Dunning emails and card-update prompts recover customers who never meant to leave.

How to measure churn in Amplitude

In practice, you'd track churn as the inverse of retention: build a retention or cohort analysis to see how many users from each starting cohort are still active over time, and watch where the curve drops off. Layering in behavioral cohorts — users who did (or didn't) hit your activation event — quickly reveals which behaviors protect against churn, which tells you exactly what to nudge users toward.

Get the data behind your churn right

You can only reduce churn you can see clearly — and that depends on clean event tracking, a solid definition of an "active" user, and reliable cohorts. If that foundation isn't in place, our Data Foundation engagement gets your tracking set up so churn (and the retention behind it) reflects reality.

Book a call with our team →

Frequently asked questions

What is a good churn rate?
There's no universal benchmark — it depends heavily on your business model, price, and customer type, with consumer products typically churning far more than enterprise software. The most useful measure is your own churn trend over time and across segments, not a comparison to an industry average.

What's the difference between customer churn and revenue churn?
Customer churn measures how many accounts leave; revenue churn measures how much recurring revenue leaves. They can diverge — losing many small accounts while keeping large ones looks bad on customer churn but fine on revenue churn — so it's worth tracking both.

How is churn rate related to retention rate?
They're two sides of the same coin: retention is who stays, churn is who leaves, and for a given period they're complements. If your monthly retention is 95%, your monthly churn is roughly 5%. Reducing churn and improving retention are the same goal viewed from opposite ends.

What causes customer churn?
Common causes include poor onboarding (users who never reached value), a gap between expectations and the product, declining engagement over time, pricing mismatches, and involuntary churn from failed payments. Cohort analysis and talking to churned users usually reveal a few systemic causes behind most of it.

How do you reduce churn rate?
Locate where and why users leave with cohort analysis, improve early activation so users reach value, identify and intervene with at-risk users before they disengage, address the systemic reasons churned users cite, and reduce involuntary churn with payment-recovery flows.

Related articles

Guide
5min

How to Turn Experiment Results Into New Hypotheses

Every finished test—win, loss, or flat—should spawn new ideas. How to make experiment results compound into your next hypotheses.
Quick Tip
5min

Guardrail Metrics Explained: What They Are and How to Catch Cannibalization

Guardrail metrics protect what you're not trying to move. How they work, common examples, and why they're your best cannibalization check.
Guide
5min

How to Add Product Analytics to a Desktop App (No SDK Required)

Desktop apps and other no-SDK cases can still send events to Amplitude—server-side, from a warehouse like Snowflake via the HTTP API.

Get in touch!

Adasight is your go-to partner for growth, specializing in analytics for product, and marketing strategy. We provide companies with top-class frameworks to thrive.

Gregor Spielmann adasight marketing analytics