Reduce SaaS churn with a five-step monthly review

What to take away

Bring the same three numbers

Every review starts from the same three numbers: new logos, lost logos and lost MRR. Two people in the same meeting can quote different churn figures and both be right, so name the measure in every report. Logo churn counts customers lost.

Revenue churn counts recurring income lost, including downgrades. Net revenue churn goes further and subtracts expansion. If upgrades and seat additions outweigh cancellations and downgrades, net revenue churn reads as negative. That is a good result, not a spreadsheet error.

The standard churn rate definition is customers lost in a period divided by customers at the start of it. Apply it consistently and your trend line becomes useful. The retention metrics reference holds the fuller definitions, so the meeting itself needs only the three numbers.

Run the review in five steps

A monthly routine beats an annual panic. Book 45 minutes, bring the same three numbers, and decide one action per lost account. The five steps below keep the meeting short and end with named owners rather than general concern.

Keep the reason in the customer's own words where you have it, and separate what was said from what you think happened. A reason the customer gave is evidence, while a guess is not. If the list contains a guess, label it as one.

Worked example, using illustrative figures. A UK B2B SaaS business holds 200 accounts on £500 a month each, so monthly recurring revenue is £100,000. Four losses a month is £2,000 of MRR and 2 per cent logo churn. Halving losses frees £12,000 of MRR a year.

That gain comes only if each lost account gets an owner and a date at step four, and if step five confirms the actions were done. A review that records losses but closes nothing leaves the next month's number where it was.

Check each lost account against the first 90 days

Most avoidable churn is decided long before a renewal conversation. Accounts that never reach first value drift quietly and then cancel at the first budget review, so step three asks the same question of every lost account.

Logins are a poor proxy. A customer can log in daily and still see no return, while a low-login account can renew happily if the product is doing its job in the background.

Define three activation events that predict renewal in your product. A shared dashboard counts. A completed import counts. A logged-in administrator who has invited a colleague counts more. Pick events a customer would notice, not milestones that flatter your team.

Then report activation, not logins, in the weekly customer success meeting, and keep it in your measurement and reporting routine. Each lost account that never hit an event gives the next review a specific onboarding gap to close.

Read a weak month against context

A weak month is not always your own. There is no single UK SaaS churn figure worth copying, because contract length and average contract value move the number more than geography does.

Use outside data as context, not as a target. The Office for National Statistics Index of Services publishes monthly movements in output for the services industries, including business services and finance, which helps you judge whether a weak quarter is yours or part of a wider slowdown.

Import US benchmarks with care. Annual prepay, longer sales cycles and pricing in pounds all change the shape of UK churn. Compare against your own cohort history first, then use the UK SaaS churn benchmarks for sector-level ranges by contract size.

Keep lost-account data lawful

Churn scoring uses personal data: names, usage logs, support tickets, sometimes payment history. Under the UK GDPR you need a lawful basis, a retention period and a way to answer access requests, and the churn scoring rules apply to a review spreadsheet as much as to software.

The ICO says you must determine your lawful basis before you start using the personal information, and that you must document it. Settle this before the first review meeting, not after.

If you use a processor for churn analytics, you need a written contract that sets out what they can do with the data. Keep churn dashboards inside your access controls. A health score is customer data, not internal gossip.

Common questions

How long should a monthly churn review take?

Book 45 minutes and keep to it. Bring the same three numbers each time, work through the five steps, and stop when every lost account has an action, an owner and a date.

How often should we review churn?

Monthly for trends, quarterly for the numbers you take to the board. Annual reviews are too slow to catch an onboarding problem.

Do we need retention software to run the review?

Not at the start. A spreadsheet and a monthly review will find the obvious losses. Platforms such as Gainsight, ChurnZero, Vitally and Planhat handle health scoring and renewal workflows, but they inherit your definitions and your review routine, so fix those first.