McKinsey Studied 98 B2B SaaS Companies. A 15-Point NRR Gap Was Worth a 24x vs. 5x Valuation Multiple.
McKinsey's 98-company study ties a 15-point NRR gap to a nearly 5x swing in valuation multiple, and names the practices that actually close it.
Every SaaS board gets the NRR slide. Fewer get the slide after it — the one showing what the market actually pays for that number. McKinsey put the two together in a November 2025 study of 98 B2B SaaS companies, and the gap is bigger than most finance teams model it to be. It also did something more useful than publish another benchmark: it scored maturity across 20 specific go-to-market and customer success practices against each company's NRR, and found that most of them don't matter nearly as much as the ones that do.
The number that actually gets a CFO's attention
We've covered what counts as a good NRR by segment, and separately how NRR compounds into growth rate rather than moving it in a straight line. McKinsey's study sits one layer above both: it's not asking whether 110% NRR is healthy. It's asking what the market will pay for the difference between 98% and 113%, and the answer is a lot more than a linear read of the gap would suggest.
| Quartile | Median NRR | Median EV/Revenue multiple |
|---|---|---|
| Top quartile | 113% | 24x |
| Bottom quartile | 98% | 5x |
Source: McKinsey, "The Net Revenue Retention Advantage: Driving Success in B2B Tech" (Nov 2025, 98 B2B SaaS companies).
Fifteen points of NRR is not a small operational gap, but it's one that plenty of SaaS companies close or open within a couple of years of deliberate (or neglected) retention work. A roughly fivefold swing in valuation multiple attached to that same gap is the kind of number that changes which initiatives get funded. McKinsey's follow-up analysis, run on a separate cut of 55 B2B SaaS companies, found the premium held through both bull and bear markets — top-quartile NRR performers weren't just getting a multiple bump during a hot fundraising cycle. The market was pricing the retention quality itself, consistently, regardless of what the broader environment was doing to multiples generally.
That's the part worth sitting with before the tactics: this isn't a study about which NRR number looks respectable on a pitch deck. It's a study about which specific, buildable practices separate the companies the market prices at 24x from the ones it prices at 5x — and McKinsey went looking for exactly that, not just the correlation between NRR and valuation that most of us already assumed existed.
Twenty practices went in. Nine came out mattering.
The methodology is the part that makes this study different from the usual "top performers do X" trend piece. McKinsey surveyed more than 100 commercial, revenue, sales, and customer success leaders across those 98 companies, asking each one to self-assess maturity across 20 named practices spanning pricing, customer success operations, product instrumentation, and go-to-market motion. Scored against each company's own reported NRR, only 9 of the 20 showed a strong enough relationship to call them real difference-makers. The other 11 — things plenty of SaaS leadership teams spend real budget on — didn't show a meaningful gap between companies that did them well and companies that didn't.
That's the useful filter here, and it's the opposite of how most "best practices" content gets written. Instead of a checklist of twenty things to go do, the study tells you which investments are actually correlated with the number the market pays a premium for, and which ones are activity without a measurable retention return.
Source: McKinsey, "The Net Revenue Retention Advantage: Driving Success in B2B Tech" (Nov 2025).
Two of the nine practices carry individual point values specific enough to quote with confidence. Companies with the most mature product usage telemetry — meaning they can actually see, account by account, how customers use the product day to day — ran more than 15 points higher NRR than companies with basic or no telemetry. Companies with sophisticated value-realization and customer-adoption-journey programs ran about 7 points higher than companies doing the bare minimum there. A separate, broader cut of the same dataset found that companies executing well across the go-to-market and customer-experience practices as a set, not any single lever in isolation, averaged roughly 16 points higher NRR than companies still running basic versions of all of them — which tells you the nine practices aren't nine separate bets so much as one compounding operating model.
Why telemetry is the single biggest lever in the study
Fifteen points is a large number for one practice to carry, and the mechanism behind it isn't exotic: it's a timing problem. A CSM running quarterly check-ins finds out an account's usage has flatlined roughly once a quarter, after the fact. A support team finds out a workflow is broken when someone files a ticket, which assumes the someone bothers to file one instead of quietly building a workaround or starting to look elsewhere. Usage telemetry collapses that lag to days or hours. An account that stops touching a core feature, a seat that's gone untouched for three weeks, a usage curve that's flattened right where it used to keep climbing — all of that is visible in the data stream well before it shows up in a renewal conversation, and well before the subscriber has mentally checked out.
This is the same mechanism we've written about from the churn side rather than the expansion side: a disengaged "zombie" account doesn't announce itself, and a company that's only watching MRR and support tickets doesn't see one until it cancels. Telemetry is the instrument that turns silent disengagement into a number someone can act on — and it's doing identical work whether the account in question is drifting toward a downgrade or sitting on an expansion-ready usage curve nobody's reached out about yet. The reason it shows the largest point gap in the study is that it's upstream of almost every other lever: you can't run a good value-realization program, can't time an expansion offer, and can't catch a renewal risk early if you're not instrumented to see any of it happening in real time.
"Anchoring customers in value" is the practice McKinsey leads with
The report's own framing opens with a practice it calls anchoring customers in value: quantifying what the product is actually worth to a specific account — hours saved, revenue influenced, incidents prevented — and communicating that back to the buyer proactively, rather than assembling the case retroactively when a renewal is already at risk. The logic behind leading with this one is buyer behavior, not vendor preference. Procurement teams are scrutinizing every line of SaaS spend harder than they were three years ago, and a vendor that can produce a concrete ROI number on demand is answering a question the buyer was already going to ask at renewal — just earlier, and on the vendor's own terms instead of under a deadline.
In practice this is a quarterly business review with real numbers in it instead of a usage recap, or a dashboard the customer can check themselves instead of a slide a CSM builds once a year. It's the same instinct behind a well-run churn health score — proactive visibility into account health before the moment you need it — pointed at the opposite end of the account lifecycle, where the goal isn't catching risk but making the renewal decision close to automatic because the value was never in question.
Pricing model is doing more of the work than most teams staff for
The study's dataset includes a pointed example on pricing: a B2B tech company reached 115%+ NRR by pairing consumption-based pricing with a product-led, self-serve sales motion — without a dedicated expansion team driving it. That's worth sitting with against the staffing instinct most SaaS leaders default to, which is to hire more account managers when expansion revenue is soft. If the pricing model itself charges more automatically as usage grows, expansion doesn't require someone to notice a usage threshold and make an outbound call. It happens on the invoice.
This lines up with ground we've covered on usage-based billing's churn mechanics: consumption pricing makes expansion structural rather than something a CS team has to go generate, but it also means a usage dip shows up as revenue contraction immediately instead of waiting for a renewal date to register it. The pricing model that makes NRR climb fastest when usage is growing is the same one that makes it fall fastest when usage stalls — which is exactly why it has to be paired with the telemetry practice above, not substituted for it.
What this means if you don't have 98 companies' worth of data to benchmark against
You don't need McKinsey's sample size to act on the ranking it produced. The practical order, in roughly the sequence the point gaps suggest:
- Get usage data into a system someone actually looks at weekly. Before adoption journeys or value-realization programs can work, someone needs to see the account-level signal those programs are supposed to respond to. This is the highest-leverage gap in the study and the one most companies under-invest in relative to CSM headcount.
- Build one proactive value touchpoint per account, per quarter, with a real number in it. Not a check-in call — a specific, quantified answer to "what did this cost us, and what did you get back," delivered before the customer has to ask.
- Check whether your pricing model structurally captures expansion, or depends entirely on someone noticing it. A flat per-seat fee with no usage dimension means every point of NRR above 100% has to be manually generated by a human watching for it.
- Treat the fourth lever as the floor the other three sit on. None of this compounds if avoidable cancellations are draining the base at the same time — a cancellation flow that captures a real reason and responds with the right offer is what keeps expansion gains from being offset by preventable losses on the other side of the ledger.
McKinsey's 24x-versus-5x number is the kind of stat that's easy to read as a valuation curiosity and move past. The more useful read is that it's describing the exact same operating discipline a smaller SaaS company needs for an entirely different reason — not to impress a public-markets analyst, but because the mechanics that produce 113% NRR instead of 98% are visibility into usage, a value case the customer doesn't have to ask for, a pricing model that captures growth automatically, and a floor under all three that stops the cancel button from undoing the work. Run your own numbers through our dollar retention rate calculator to see what even a few points of that gap is worth on your base before deciding which of the four to build first — and if the leak you're chasing is happening at the cancellation moment specifically, that's the piece CancelFlow is built to catch before it hits your NRR at all.
Frequently asked questions
How much does net revenue retention actually affect SaaS valuation?+
McKinsey's November 2025 study of 98 B2B SaaS companies found top-quartile companies carried a median NRR of 113% and traded at a median 24x EV/Revenue, while bottom-quartile companies carried 98% NRR and traded at 5x. That's a 15-point NRR gap lining up with a valuation multiple nearly 5 times larger. A separate McKinsey cut of 55 B2B SaaS companies found top-quartile NRR performers held that premium through both bull and bear markets, so it isn't just a frothy-market artifact.
What specific practices did McKinsey find move NRR the most?+
McKinsey scored maturity across 20 go-to-market and customer success practices and narrowed them to 9 real difference-makers. Two of the clearest, with numbers attached: companies with the most mature product usage telemetry outperformed peers with basic telemetry by more than 15 points of NRR, and companies with sophisticated value-realization and adoption-journey programs ran about 7 points higher than companies with basic versions of the same thing. 'Anchoring customers in value' — quantifying and proactively communicating ROI instead of waiting for a renewal conversation to make the case — is the practice the report leads with.
Does product usage telemetry really move net revenue retention, or is that correlation?+
McKinsey's study is correlational, not a controlled experiment, so causation in either direction is possible in principle. But the mechanism is straightforward enough to trust: a team that can see usage data in near-real time catches a shrinking account, a stalled onboarding, or an expansion-ready account months before a CSM would notice from quarterly check-ins alone. Without telemetry, every signal arrives late — at renewal, or when the subscriber already has their hand on the cancel button.
Should an early-stage SaaS company build NRR-focused infrastructure before it has product-market fit?+
No. McKinsey's sample skews toward companies with an established customer base large enough for expansion and churn patterns to show up in the data at all — the practices in the study assume you already have paying customers whose usage and renewal behavior you can instrument. For a pre-PMF company, the higher-leverage move is still finding product-market fit. The lesson transfers once you have enough customers that a renewal motion exists to measure: the operational discipline is worth building deliberately, not backing into after retention has already started slipping.
Stop losing subscribers today
One script tag. One function call. A live cancellation flow in under 10 minutes.
Start free trial →