Every SaaS business has a quiet drain. Customers leave, plans shrink, cards fail, and revenue slips out like water through a small crack. That leak is churn. When I want a clear view of it, I start with saas churn rate and track it inside Baremetrics.
In this guide, I break down the formulas I use, the difference between customer and revenue churn, and the mistakes that can twist the numbers. I also show how Baremetrics turns a messy spreadsheet job into a dashboard I can read in minutes.
The churn formulas I trust
Churn is simply the share of customers or recurring revenue I lose in a set period. I picture it as a bucket with a slow leak. New sales pour in, but churn decides how much water stays.
When I calculate saas churn rate, I start with one rule: I never mix people with dollars. Customer churn measures lost accounts. Revenue churn measures lost recurring revenue. A business can lose very few customers and still lose a lot of money if one large account leaves.
I keep the main formulas in one place.
| Metric | Formula | What it tells me |
|---|---|---|
| Customer churn | Lost customers / customers at start of period x 100 | How fast accounts leave |
| Revenue churn | Lost MRR / MRR at start of period x 100 | How much recurring revenue disappears |
| Gross revenue churn | (Cancelled MRR + downgraded MRR) / starting MRR x 100 | The raw revenue leak |
| Net revenue churn | (Cancelled MRR + downgraded MRR – expansion MRR) / starting MRR x 100 | Whether expansion offsets loss |
The key is consistency. I use the starting base for the period, not the ending base, and I keep new sales out of churn. If I want a second check on the math, I like Chargebee’s churn rate formulas and examples and Hubifi’s customer and revenue churn guide.
A quick example with real numbers
Say I start April with 200 customers and lose 10. My customer churn rate is 10 / 200 x 100, which equals 5%.
Now say I start the month with $20,000 in MRR. During April, I lose $1,200 from cancellations and $300 from downgrades. My gross revenue churn is $1,500 / $20,000, which equals 7.5%. If existing customers also expand by $400, my net revenue churn becomes ($1,500 – $400) / $20,000, which equals 5.5%.
Net revenue churn tells me how well expansion cushions the blow. Gross revenue churn shows the raw leak. I track both, because one can look healthy while the other tells a harder truth.
How Baremetrics makes the math easier
From current public information, Baremetrics gives me a quick way to watch churn without living in spreadsheets. It tracks MRR movement, customer churn, and revenue churn in one place. Its subscription analytics also tie churn to upgrades, downgrades, failed payments, and reactivations.
What I like most is the context. If MRR dips, I compare periods and see whether one big loss or many small cancellations caused it. Baremetrics also offers cohort analysis, so I can group users by signup date and see which cohorts stay longest. That helps when a new onboarding flow improves one group but not another.
The platform also surfaces cancellation insights and customer profiles. So, when churn rises, I don’t have to guess. I can inspect who left, what plan they had, and whether a failed card caused the loss. Baremetrics also offers Recover, which focuses on dunning and can reduce involuntary churn.
This is the simple review loop I use:
- Connect billing data and view churn monthly.
- Check customer churn, gross revenue churn, and net revenue churn side by side.
- Review cohorts and cancellation reasons for the same period.
- Watch failed payments, because accidental churn can look like true churn.
Baremetrics also sends regular reports, including daily, weekly, and monthly summaries. That helps me catch changes before they harden into a trend. After the numbers point to a problem, I often read Baremetrics’ guide on ways to reduce SaaS churn rate for practical next steps.
Monthly vs annual churn, and the traps that skew it
I track churn monthly first, because monthly data gives me faster signals. If churn jumps in May, I can inspect pricing, onboarding, support, or billing right away. Annual churn matters too, especially when contracts renew once a year. Still, I don’t treat annual churn as monthly churn times 12. The better view is compounded, and the story can change a lot over a year.
For example, a 5% monthly customer churn rate does not mean 60% annual churn. A rough compounded view is 1 minus 0.95 to the 12th power, which is far worse than many teams expect. That’s why monthly churn can feel small while the yearly loss feels brutal.
The biggest mistakes are simple:
- Using ending customers instead of starting customers in the denominator
- Comparing customer churn to revenue churn as if they mean the same thing
- Hiding downgrades inside net revenue churn and never checking gross churn
- Counting failed payments as normal cancellations
- Ignoring contract length when looking at annual plans
I never compare a customer count metric to a revenue metric. They answer different questions.
When I need a reality check on retention patterns, I find KISSmetrics useful for diagnosing churn and retention problems. The lesson stays the same, the number matters, but the reason behind the number matters more.
The bottom line on saas churn rate
Churn is the leak that tells me whether growth is real or rented. Once I separate customer churn from revenue churn, and gross from net, the picture gets much clearer. Baremetrics helps me watch those numbers in one place, then trace them back to cohorts, cancellations, and failed payments. If I were starting today, I’d track monthly churn first, because small leaks are easiest to fix before they become a flood.
