How to Calculate Agency MRR Churn
How to calculate MRR churn for a GoHighLevel SaaS Mode agency, with the formula, a worked example, and common measurement mistakes.
Updated September 14, 2026
Logo churn (accounts lost) and MRR churn (revenue lost) tell different stories, and a GoHighLevel agency that only tracks one is missing half the picture. This guide walks through the actual MRR churn formula, a worked example, and the mistakes that most commonly distort the number.
What is the formula for MRR churn?
MRR churn rate = (MRR lost to cancellations and downgrades during the period) / (Starting MRR for the period) × 100. It measures the percentage of recurring revenue lost from your existing sub-account base, independent of any new revenue added during the same period.
This is a gross number — it doesn’t net out expansion revenue from upgrades. That’s intentional: mixing expansion into the churn number hides how much revenue you’re actually losing behind how much you’re gaining, which makes a shrinking base look healthier than it is.
How do I calculate it with a worked example?
Take an agency with $50,000 in starting MRR across all SaaS Mode sub-accounts. During the month, 6 accounts cancel (totaling $1,800 in lost MRR) and 3 accounts downgrade plans (losing another $600). Total MRR churned is $2,400, so MRR churn rate = $2,400 / $50,000 × 100 = 4.8%.
Compare that to logo churn for the same period: if those 6 cancellations came out of 250 total active accounts, logo churn is 6/250 = 2.4% — exactly half the MRR churn rate. That gap usually means the accounts that left were paying more than average, which is worth knowing on its own.
Why can logo churn and MRR churn diverge?
They diverge because not every sub-account is worth the same amount — losing one enterprise-tier account can move MRR churn significantly while barely touching logo churn, and losing several small starter-tier accounts can do the opposite. Tracking only one metric can hide which segment is actually driving revenue risk.
If MRR churn is consistently higher than logo churn, your highest-value accounts are churning disproportionately — a different problem than a high volume of small accounts leaving, and one that usually calls for a different fix (account management for top clients, not broader onboarding improvements).
Should downgrades count as churn?
Yes — a sub-account that stays but drops from a premium plan to a basic one is losing you the same MRR as a partial cancellation, even though it shows up as “retained” in a simple logo-churn count. Excluding downgrades from your MRR churn calculation overstates how healthy your revenue actually is.
This is part of why net revenue retention (NRR) is often a more complete metric than churn alone — it nets churn and downgrades against expansion from upgrades, showing the full direction of your existing revenue base rather than just the losses.
What counts as “starting MRR” when sub-accounts change mid-month?
Use MRR as of the first day of the measurement period as your denominator, and don’t adjust it for accounts added mid-period — new accounts belong in next month’s starting MRR, not this month’s churn calculation. Mixing periods is the single most common mistake that makes a churn number impossible to trust or compare month over month.
Keep the period boundary consistent every month (calendar month is simplest) and apply the same rule every time, even when it’s inconvenient — a churn number that’s calculated differently each month isn’t actually trackable over time.
Turning the number into action
A single month’s MRR churn is noisy — a rolling 3-month average smooths out one bad month without hiding a real trend. Calculating it monthly only matters if you also track why it’s moving, which means tying it back to the underlying behavior: login activity, workflow adoption, and usage-based spend per sub-account, the same signals covered in GoHighLevel agency churn benchmarks.
For the retention process built around catching these signals early, see the GoHighLevel SaaS Mode retention playbook. GoCSM’s Revenue Intelligence tier tracks MRR and usage-based spend per sub-account automatically, so this calculation doesn’t require exporting billing data by hand every month.