Net revenue retention is one of the four numbers that decide what a company is worth. It sits in the valuation model, it gets asked about in diligence, and a company at 130 percent is a fundamentally different asset from an otherwise identical company at 95.
It's also, in most organizations, owned by one department that can't move most of it.
Five functions move the number
Ask what NRR is actually made of and then ask who decides each part.
Sales decides what got promised, what got discounted, and what got left to sell. That is the largest single input and I have argued it separately: NRR is substantially a report on what your sales team did. A deal sized for the quarter rather than for the customer produces contraction at the first renewal. Everything sold at once produces an account with no room to grow.
Product decides whether the thing is good enough to be worth more of. No amount of relationship makes a customer buy a second module of something that half works.
Support decides how much friction accumulates between renewals. Nobody expands into a vendor they're currently fighting with, and the number of open tickets at renewal is not a customer success decision.
Finance decides what a discount does at year two, what the renewal uplift looks like, and whether the price the customer sees next year reads as fair or as a penalty for staying.
Customer success decides how much of the value actually gets realized, and whether anybody notices when a customer reaches the point where the next thing would help.
All five move it. One gets reviewed on it.
Why it lands where it lands
Not conspiracy, and not stupidity. Proximity.
Customer success is nearest the customer, so retention feels like theirs. That's a reasonable first instinct, and it's where the reasoning stops. The metric gets assigned, the assignment hardens into an org chart, and within a year "who owns NRR" has an answer that nobody revisits.
So when the number softens, the review happens in the function with the least leverage over most of its inputs.
Watch what that produces. Customer success is asked for a plan. They build one, because they're competent and it's their number. The plan addresses adoption, because adoption's the lever they actually hold. And adoption may have had nothing to do with it. The quarter gets spent on the one input that wasn't binding, and the inputs that were binding belong to people who weren't in the room.
Then next quarter it's still soft, and now there's a performance conversation.
Being precise about what customer success does own
This is where the argument usually turns into a cop-out, so I want to be exact.
Customer success has real agency, and it's mostly unused or misapplied.
It owns whether value gets realized rather than just delivered. It owns whether a customer reaches a milestone at all, and how fast. It owns whether anyone notices when they arrive, and whether the conversation that should happen at that moment actually happens. That's a genuine and substantial lever on expansion, and in most companies nobody's running it. Or worse, it gets run at the wrong input: the team is working hard, on adoption, in a quarter where adoption was never the thing holding the number down.
So the honest version is not that customer success is blameless. It's that customer success is accountable for one input and reviewed on the total.
Those are different, and the difference is the whole problem.
Assigning a distributed outcome to a single owner produces a scapegoat
That's the general form and it isn't special to this metric.
When several functions determine an outcome and one is measured on it, two things happen and both are bad. The owner absorbs a number they can't move, which over time selects for people who're good at explaining rather than people who change things. And everyone whose decisions actually moved it is measured on something else, hears nothing, and keeps making the same decisions.
The rep who sized the deal for the quarter got paid on the quarter and was promoted before the contraction showed up. Nothing in that loop tells them what happened next, and nothing was ever going to.
What a company metric needs instead
Boring, and rare.
Named contributors, each accountable for the input they control. Sales for what got sold and what got deliberately left. Product for whether more of it is worth having. Support for friction at renewal. Finance for what the second-year price does. Customer success for realized value and for whether arrival gets noticed.
One review, everybody in it. Not a customer success meeting with an NRR slide. A company meeting about a company number, where the person who set the ceiling is in the room when the ceiling gets discussed.
And each contributor measured on their own input, not on the total. Nobody should be graded on a number four other functions move. Grade them on the part they decide, and let the total be what it's for: a report on whether the organization is coherent.
The test
You don't need a reorg to find out whether you've got this problem.
Look at your next NRR review and ask one question.
Who in that room decided what got sold?
If nobody, then you're not reviewing net revenue retention. You're reviewing customer success, using a number that four other departments wrote.
Lincoln Murphy formally named and popularized Customer Success starting in 2010 and has spent 15 years connecting it to expansion revenue and commercial outcomes. Read The Premise.