HomeSeller Claims

The seller says: “we intentionally churned our bad customers”

Deliberately removing unprofitable customers is a legitimate and sometimes excellent decision. It also leaves a specific, checkable signature in the data. Intentional pruning is selective, bounded in time, and improves the metrics of what remains. Churn reframed as pruning after the fact is none of those things.

TL;DR: Deliberate customer pruning is a real strategy with a distinctive data signature. Here is how to distinguish it from churn that is being reframed after the fact.

What the claim usually means

This claim usually arrives after a buyer points at a bad period, and it is often true. Founders do fire customers, sunset cheap legacy tiers and exit segments that consume all the support capacity. The reason it needs testing is not dishonesty but hindsight: the same founder is being asked to explain a period they lived through, and a decision that was partly reactive at the time is easy to remember as strategy. The data does not have hindsight.

What it can hide

Four mechanisms account for most of the gap between this claim and what the raw rows show. They are not mutually exclusive and they compound.

1. Churn that was not selective at all

Real pruning concentrates in an identifiable segment — one plan, one price point, one usage band. If the departures are spread evenly across plans, tenures and sizes, nothing was targeted.

2. A support or product failure that pushed everyone out

The accounts that leave under strain are disproportionately the demanding ones, which makes indiscriminate churn look selective. Check whether the remaining base's engagement also fell in the same period.

3. Revenue quality that did not actually improve

The whole point of pruning is that what remains is better. If revenue per account, gross retention and expansion are unchanged afterwards, the strategy either was not executed or did not work.

4. A pruning event that never ended

Intentional removal is bounded: a decision, an execution window, a return to baseline. If elevated churn continues in the same segment for a year, that is not a decision, it is a condition.

How to verify it from the raw subscription export

Every step below runs on a subscription-level export in a spreadsheet. None of it needs access to the seller's live billing account, which matters, because as a buyer you will not get one.

  1. Establish the window the seller says the pruning happened in, in writing, before you look at the data.
  2. Inside that window, segment departures by plan, price point, tenure and usage. Compute what share of churned revenue came from the segment the seller says was targeted.
  3. Compare the churn rate inside the targeted segment against the rest of the book in the same window. Pruning gives you a wide gap.
  4. Compare the three months before and the three months after the window on the remaining base: gross revenue retention, revenue per account, expansion rate, support load if available.
  5. Check that churn returned to baseline after the window. Plot the targeted segment separately from everything else for twelve months on each side.
  6. Look for the mechanism. Deliberate removal usually leaves a trace: a sunset notice, a plan discontinued in the price history, a migration deadline, a coupon that stopped being honoured. Ask for it.
  7. Check whether the pruned segment still exists. If the cheap legacy tier is still being sold, the decision was not made.

Reading the result

These are the thresholds we use in our own reports. They are working thresholds rather than industry standards, and the right line for a given deal depends on contract length, tenure and how transferable the customer relationships are.

What you findVerdictWhat to do about it
Churn concentrated in one segment, bounded window, retention improved afterGreenThe claim holds and the strategy worked. Credit it.
Concentrated and bounded, but revenue quality unchangedInvestigateThe decision was made and did not deliver. Not a red flag, but do not price in a benefit that did not appear.
Churn spread evenly across plans and tenuresPrice it inNothing was targeted. Treat the period as ordinary churn and re-read the explanation as hindsight.
Elevated churn in the same segment continues past the windowPrice it inThis is a condition, not a decision. Model it as ongoing.
No documentary trace of a sunset, migration or plan discontinuationInvestigateDeliberate removal normally leaves paperwork. Ask for it; absence is not proof, but it shifts the burden.

What to ask for in the data room

Ask for these before the LOI. After the LOI you are renegotiating rather than negotiating, and a seller who will not produce subscription-level rows has told you something useful either way.

A worked example

Illustrative. Churn runs at 3.5% and hits 9% across one quarter. The seller says they sunset a $9 legacy tier that consumed most of support. The data agrees: 71% of churned revenue in that quarter came from the $9 tier, churn in the rest of the book was 3.6% and unchanged, there is a migration email with a deadline, and the tier is gone from the price list. In the two quarters after, revenue per account rises 22% and gross retention improves by four points. That is a well-evidenced, well-executed decision and it should count in the seller's favour. The same claim against a spike spread evenly across five plans, with no notice and no subsequent improvement, is a different page in the memo.

Why it matters to the price

This claim is worth testing carefully in both directions, because a confirmed pruning event is genuinely good news that a mechanical churn screen would score as a red flag. Where it fails, the correction is not to distrust the seller but to move the period from the explained column back into the modelled one. What you must not do is accept the explanation and then also model the improved revenue quality that never showed up in the data.

The relevant tool on this site is the revenue quality scorecard, which runs the arithmetic above on a file you paste in. The full method is documented in the 5-risk buyer-side method and the due-diligence checklist.

Other claims worth testing

All twelve seller claims →

Verify it against the raw rows

Every check on this page can be run by hand in a spreadsheet, and if you have the time you should. If you would rather not: send us the target's subscription export and we run the full human-reviewed analysis — logo churn, revenue churn, customer concentration, annual-plan decay, zombie MRR and an A–F revenue-quality grade. The free Starter tier covers one CSV per month, which is enough to check a single deal.

See a sample report →  ·  Get the free 23-point checklist →

Frequently asked questions

Is it a red flag when a SaaS seller says they fired customers?

Not on its own, and it can be a positive. Deliberately removing unprofitable customers is a real strategy that leaves a checkable signature: churn concentrated in a specific segment, bounded to a defined window, followed by measurable improvement in what remains. Test for that signature rather than for the intent.

How can I tell deliberate customer pruning from ordinary churn?

Selectivity, boundedness and consequence. Pruning concentrates in one plan or price band, stops when the decision has been executed, and improves revenue per account and gross retention afterwards. Ordinary churn reframed after the fact is spread across segments, does not stop, and leaves the remaining base's metrics unchanged.

What documentation should I ask for?

The sunset or migration notice sent to customers, the plan history showing the tier being discontinued, and the dates of the decision in writing. Deliberate removal is a project and projects leave paperwork. Its absence does not disprove the claim, but it does move the burden of proof.

9%
Median B2B SaaS revenue churn
88%
Median gross revenue retention
23
Audit Checklist Points

The seller's churn number is almost always wrong. Send the CSV and find out before you wire.

Get the Free Checklist →

🛡️ Free Starter tier: 1 CSV analysis per month. No credit card. Verify a seller's churn claims before you commit.