A named owner for a spread-out loss
A cost split across four budget lines belongs to nobody, and a loss nobody owns is never on anyone's agenda to fix.
Enterprise
Nobody is in crisis, so the leak keeps growing.
Enterprise revenue operations are mature, and the leak stays expensive because everything looks stable. Nothing is on fire, so the loss grows for years before anyone puts a number on it.
The transition
Stable, and quietly expensive.
The quarterly review shows pipeline coverage at three times target, as it has for four years. Nobody mentions that the three regions calculate coverage differently, that the approval path for a discount has eleven steps because removing one needs a sign-off nobody wants to give, or that two teams run parallel versions of the same renewal process because each works locally. The trend is flat. Flat reads as healthy.
The loss has no single owner: it is spread across functions and absorbed into quarterly reporting, where it reads as the cost of doing business. Raising it costs the person who raises it more than leaving it alone, so the one thing stability never gets is a second look.
Signs you are here
Nothing is failing, and that is what stops anyone from looking.
- No commercial leader owns the loss, because it sits across regions and departments
- Operations, finance and product owners each see a piece of the cost and none see the whole
- The last process review removed nothing, and nobody expected it to
- Regional definitions differ, so the same metric is calculated three ways and reported as one
- Review boards keep every step, because removing one needs somebody to sign for it
- Duplicated workflows persist because each one works locally
When five of these hold, the leak sits in no single department's number, which is why no department's number shows it.
By function
Six functions, each within budget, and one loss between them.
At this size every seat has a mature process, a budget and a number it has met for years. The loss lives in what each process costs to keep, and nobody is measured on that.
What this stage demands
Someone has to own a loss that is spread across departments.
A settled process is the hardest kind to reopen. What this stage demands is the authority and the evidence to do it.
Evidence strong enough to reopen a settled question
Questioning a stable system carries career risk. The only thing that lowers it is a number from the organisation's own records, which nobody in the room can file as opinion.
The cost of keeping things in step, made visible
At this size the expensive thing is rarely a broken process. It is the amount of work spent keeping several working processes lined up with each other.
A routine look at what is not failing
Nobody is paid to reopen a process that meets its number. A review that asks what a process costs, not only whether it ran, belongs in the operating calendar with a date on it, not in an escalation.
The evidence
Stable, in four numbers that are not.
Four published figures for companies above $100M ARR, where the trend has been flat long enough to be trusted. Each one moved in the wrong direction while every quarterly review read as healthy.
- 01
21% of SQLs
SQL to closed-won conversion at $100M-$250M ARR in 2025, the lowest of any band, from 27% in 2023. A mature pipeline converts worse than a young one, and nobody's number shows it because every region reports its own.
ICONIQ, The State of Go-to-Market in 2025, survey of GTM executives 2023 to 2025, June 2025
- 02
$10,500
Cost per opportunity at $100M-$250M ARR in 2025, from $8,500 in 2024, the highest of any band. An eleven-step discount approval and three definitions of coverage are paid for one opportunity at a time.
ICONIQ, The State of Go-to-Market in 2025, survey of GTM executives, n=37 companies at $100M-$250M ARR, June 2025
- 03
33% growth
Top-quartile year-on-year ARR growth above $100M ARR in the second half of 2025, from 40% in the first half of 2023, while the $50M-$100M band moved from 69% to 91%. The only band whose best quartile slowed over the period, and a slow decline is the shape a stable leak takes.
ICONIQ, The State of Go-to-Market in 2026, quarterly operating data from public SaaS companies and ICONIQ portfolio companies, 2013 to Q4 2025, top quartile, companies under $10M ARR excluded, March 2026
- 04
82%
Gross revenue retention at the 25th percentile above $100M ARR, with the median at 89%. A quarter of companies at this size buy back close to a fifth of last year's revenue every year, through a renewal process that has been in place long enough for nobody to question it.
Benchmarkit, 2025 B2B SaaS Performance Metrics Benchmarks, calendar 2024 data, N=225
The usual entry at this stage
The Diagnosis puts a number on the loss nobody owns.
Diagnosis
€15,000 flat · two months from the day we get access
Two months across regions and functions: coverage as each region counts it, the discount approval path, the parallel renewal processes, and interviews by role with whoever runs them. You leave holding the loss located, priced at the rates on your own payroll, and the process to reopen first. Operation then carries the change through with an owner: €50,000 more if booked within 30 days of the briefing, or €65,000 with the Diagnosis included.
Book a strategy callDetails →Not sure it is the right one? Compare all five →
FAQ
Before you assume stable means fine.
Our numbers are healthy. Why would we need a Diagnosis?
Healthy numbers say nothing is failing. They do not say what the same organisation would produce with the duplicated work removed, which is a different question with its own number.
We have run internal audits before. How is this different?
An internal audit is run by people inside the thing being audited, which limits what gets questioned. The Diagnosis is run from outside it, interviewing people by role across regions and functions rather than asking a team to review itself.
How disruptive is this to a large, established organisation?
The interview list and scope are agreed with you before anything starts, and the work runs alongside normal operations rather than interrupting them.
Who typically sponsors this internally at enterprise scale?
The chief revenue or commercial officer, or a CFO who can see across departments. The loss at this stage rarely sits inside one team, so the sponsor has to be someone who can act across the boundary, and whose budget line the number lands in.
Get started
Nothing looks broken. That is why the loss is worth pricing.
Thirty minutes on the process nobody questions and the records that could price it. If the loss is too small to matter, that is what you are told.