How to Measure ARR Lost to Competitors

ARR lost to competitors is the recurring revenue that left because a named competitor took the work. It is added up for each competitor over a period, usually a year. Three kinds of event produce it, and most reporting only sees the first.

Cancellations, cutbacks and concessions

A cancellation is the obvious one. The customer leaves and signs with a competitor. A cutback is quieter. The account renews, but a team or a region has moved to a competitor and the seat count falls with it. A concession is the quietest of all. The customer stays at full size, but only after you matched a competitor’s offer with a discount at renewal.

Count the first two in the headline figure. Keep concessions on a separate line. They are real revenue a competitor took, and they show which competitor pushes your prices down. That makes them a pricing question. They behave like a discount rate on renewals, and belong next to it rather than inside this total.

What stays out

Leave out losses where no competitor was involved. That means a budget cut, a closed business, an acquisition that brought its own tools, or a team that went back to spreadsheets. Leave out failed payments too. These are real losses, but they belong in revenue churn, the company-wide rate finance already reports. Mixing them in turns a competitive figure into a general one.

The figure is also easy to confuse with competitor churn, which runs the other way: a competitor’s own customers leaving them. ARR lost to competitors is your customers leaving for them.

An amount, not a rate

Most competitive metrics are a division. This one is a sum, and that is deliberate. A rate would need a denominator: the ARR a competitor could have taken from you. Nobody knows that number, because nobody knows which of your accounts a competitor is talking to. Dividing by your total ARR instead gives a small percentage that hides the point.

An amount also travels further inside a company. A product team can argue with a percentage for a whole meeting. It cannot argue with $550,000 that left for one competitor in a year, because that is a line it can put a price next to.

The one ratio that works

There is one honest ratio here: the share of all lost ARR that went to competitors. Its denominator is known, because finance already totals lost ARR. Watch it across years rather than quarters. A rising share while total losses stay flat means competitors are replacing other reasons for leaving. That changes who in the company should be working on retention.

Valuing a cutback

Take the ARR on the day before the change and subtract the ARR after it. Record it at the renewal where the change took effect, not when the customer first mentioned it. Then apply one test: did the work move, or did it stop? Forty seats removed after layoffs is not a competitive loss. Forty seats removed because a department now uses a competitor is one, and it is often the first half of a full cancellation a year later.

The competitor recorded on a lost account comes with very different levels of proof. Treat them as one and the total looks more certain than it is. Sort every lost account into one of four groups, and keep the groups visible in the report.

Read the competitive share from this table and you get a range, not a number. Confirmed losses alone are 41% of the $2.11 million lost. Add the inferred group and it is 52%. If every unknown account had left for a competitor, it would be 81%. The truth sits somewhere in that range, and the width of the range is the real finding.

Never share out the unknown line

The tempting fix is to split the $600,000 across competitors in the same proportions as the known losses. It makes the table add up, and it is wrong. It assumes customers who said nothing left for the same reasons as those who explained, and there is no evidence for that. Some customers stay silent precisely to avoid an awkward call about a competitor. Others simply stopped caring. Print the unknown group as its own line and let the reader see it.

Shrinking the unknown line

Only one thing narrows the range: recording the reason when the loss happens. Make the competitor a required entry on every cancellation and every cutback, the same way your CRM’s competitor field works on deals. Add a second entry for the proof group. For the backlog of older losses, churn reason analysis reads the cancellation notes and pulls out any competitor they mention. It will not recover everything, and it will say how much it could not read.

Every loss has two dates. The notice date is when the customer tells you. The end date is when the contract stops and the revenue goes. On annual contracts they can sit three to nine months apart. On a multi-year agreement, the notice may arrive a year before the money leaves.

Finance books the loss on the end date, and your totals should match theirs, so report on that date. Draw the trend on the notice date instead. A competitor that launched a cheaper plan in March shows up in notices by June and in ended contracts the following year. Read only end dates and you learn about the wave after it has passed.

One large account can be most of a year

Losses to a single competitor are few and uneven. One enterprise customer leaving can outweigh twenty small ones. So report three figures side by side: the ARR lost, the number of accounts behind it, and the largest single loss. If the largest loss is more than half the total, say so, and do not read the year as a trend.

The same unevenness is why one quarter on its own tells you little. Use a rolling twelve months, and compare each competitor with its own figure from the year before.

ARR lost to competitors is counted after the money has gone. Its forward-looking twin is ARR at risk: the ARR renewing in the next two quarters in accounts where a competitor is active. Active means something specific happened. A customer asked for a market comparison, a new executive arrived from a competitor, usage fell, or someone mentioned an offer.

Those are the signs customer success teams already watch for, one account at a time. The at-risk total is that same work added up per competitor. Where it grows faster than the lost figure, next year’s loss is forming now, and a renewal plan still has time to change it.

Where the two figures disagree

A competitor with high losses and little at risk has usually been answered already, or has taken the customers it suited best. One with small losses and a lot at risk is the one to plan for. A lost-ARR report on its own never shows that second pattern.

The figure matters for what it starts. Split each competitor’s total by the reason customers gave, and every reason gets a price. If $210,000 of one competitor’s total came from customers who needed an integration you lack, that gap now has a cost. Carry those costs into a feature gap analysis, where they sit next to the effort of closing each gap.

Sales reads the same split differently. A competitor taking your customers on price calls for a renewal offer. One taking them on a feature calls for proof of the fix before the next renewal. The reason decides the response, and the amount decides which one comes first.

Two metrics that sit beside it

The displacement rate against you counts the same movement in accounts rather than money. A competitor that takes a few large customers barely moves that rate and dominates this total, so show both. And once a lost account has a known reason, its return is tracked by win-back rate, which only works if the reason was written down when the account left.

Most of the inputs already exist in the CRM or the customer success platform. Few teams have them in one place. Export every cancellation and every contract that shrank at renewal in the period, one row per account, with these columns.

Add a column for lost ARR, the before figure minus the after. Then build a pivot table with competitors down the side, proof groups across the top, and lost ARR summed in the cells. Put a count of accounts next to each sum. That table is the whole report, and it takes an afternoon the first time.

By hand, by export, or through a platform

By hand works for a few dozen losses a year. Past that, a scheduled export from the CRM keeps it current, as long as the competitor is filled in when the loss is logged. A connected customer success platform can hold the same fields and push them into the sheet. A competitive intelligence platform adds what neither of them holds: the date of each competitor move. A cluster of notices can then be set against what that competitor did just before.

Losses to a competitor rarely arrive evenly. They bunch up after something that competitor did. It might be a cheaper plan or a switching offer with free migration. It might be a feature your customers had been asking for, or an integration with a tool they already use. By the time the bunch shows in ended contracts, the move is a year old.

Every one of those moves is public when it happens. Their pricing pages change, changelogs get new entries, and switching offers appear on their site and in their ads. The hard part is noticing them across several competitors, every week, and keeping a dated record.

That dated record is what Flares keeps. It watches what each competitor changes on pricing, product and messaging, and keeps the day it happened. A rise in notices can then be matched to the move that started it. The accounts most exposed to that move can be called before they give notice.

What it cannot see is a conversation between your customer and a competitor. That stays private until the customer tells you. Monitoring narrows the question from every account to the ones whose reason to leave just got stronger.