How is churn rate calculated?
Churn rate measures loss over time. You pick a period, count what you had at the start, count what you lost by the end, and divide the second number by the first. Multiply by one hundred to express it as a percentage of the starting base.
The unit you count changes the meaning of the metric. Customer churn (also called logo churn) counts accounts that canceled. User churn counts individual people who stopped using the product, which is closer to monthly active users going quiet. Revenue churn counts recurring revenue lost through cancellations and downgrades. A business can have low customer churn and high revenue churn at the same time if its largest accounts are the ones leaving.
Two details trip up most teams. First, new customers added during the period should not be in the denominator, because they had no chance to churn yet. Second, gross revenue churn ignores expansion, while net revenue churn subtracts upgrades from the loss. Net revenue churn can be negative when existing customers grow faster than others leave.
Why does churn rate matter for a SaaS business?
Subscription revenue depends on customers staying. Every account that leaves has to be replaced before the business can grow at all. A high churn rate turns the sales and marketing budget into a treadmill: new logos arrive, old ones leave, and the total barely moves.
Churn also compounds. A small monthly loss repeated for a year removes a large slice of the customer base, so a metric that looks harmless on a monthly dashboard can be severe on an annual view. This is why investors and boards ask for churn early and often.
Beyond the money, churn is the clearest signal that the product is not delivering the value people expected. It is a lagging indicator, though. By the time a customer cancels, the decision was usually made weeks earlier when they stopped logging in, stopped reading updates, or gave a low score on a Net Promoter Score survey. Reading churn alongside user engagement gives you time to act.
Examples of churn rate in practice
A project management tool with monthly plans. The team counts paying workspaces at the start of each month and the workspaces that canceled before month end. Because plans renew monthly, they report monthly customer churn and watch it week by week.
A B2B analytics platform with annual contracts. Cancellations only happen at renewal, so monthly churn is nearly meaningless. The team tracks annual logo churn and, separately, net revenue churn so that seat expansion in large accounts is visible.
A mobile app with a free tier. There are no cancellations to count. The team defines a churned user as anyone with no session in thirty days and reports user churn against the active base, which links the metric directly to user retention cohorts.
A marketplace with seasonal demand. Customers pause during the off season and return later. The team separates pauses from cancellations so seasonal dips do not read as permanent loss.
How to reduce churn rate
Churn drops when customers reach value quickly and keep finding new value. The practical work sits in onboarding, communication, and feedback. The seven ways to reduce SaaS churn guide goes deeper on each of these.
- Fix activation first. Customers who never reach the core value moment churn early. Measure user activation and remove the steps that stall it.
- Announce what you ship. Users cannot value features they never noticed. A visible changelog and in-app updates raise feature adoption, which is the main lever on retention you control.
- Watch for silence. A drop in logins, opened digests, or widget views is the earliest churn signal you have. Route those accounts to customer success while there is still time.
- Close the feedback loop. Collect requests, tell people when they ship, and show the roadmap. A working customer feedback loop turns frustrated users into invested ones.
- Learn from every cancellation. Ask why in the cancellation flow, tag the reasons, and review them monthly. Pricing, missing features, and poor onboarding need different fixes.
- Segment the number. Churn by plan, company size, and acquisition channel tells you where the problem lives. A blended rate hides it.
Churn rate vs. retention rate and other common mistakes
Retention rate and churn rate are two views of the same event. Retention counts who stayed; churn counts who left. For a single cohort over a single period they add up to the whole starting base, so you rarely need both on one chart. The user retention rate guide covers when each view is more useful.
Common mistakes include:
- Mixing periods. Comparing monthly churn from one product line to annual churn from another produces nonsense.
- Counting new customers in the base. Signups during the period inflate the denominator and make churn look lower than it is.
- Treating downgrades as retention. A customer who moves from the top plan to the cheapest one is retained by logo count but is revenue churn in every way that matters.
- Ignoring involuntary churn. Failed payments and expired cards are churn with a fix that has nothing to do with product quality.
- Reporting a single blended number. A healthy enterprise segment can mask a self-serve segment that is bleeding. Use user segmentation before drawing conclusions.
How AnnounceKit handles churn rate
AnnounceKit works on the causes of churn rather than the metric itself. A changelog page on your own domain and more than ten in-app widget display modes keep users aware of what shipped, so features get adopted instead of forgotten. Segmentation lets you show the right update to the right plan or role, and email digests plus Slack reach the people who are not logging in.
NPS surveys surface unhappy accounts before they cancel. Feature requests with voting and Jira sync give users a voice and give product teams a prioritized list. AI post generation and an official MCP server for AI agents cut the time between shipping and telling customers. Pricing is flat per project from $79 per month, with a 15-day free trial.