Net Revenue Retention is the most commonly cited metric for CS effectiveness. NRR tells you whether your existing customer base is growing or shrinking after accounting for churn and expansion. It's a useful number.
It's also a lagging indicator. By the time NRR reflects a problem, you're already looking at the outcome of decisions made six to twelve months ago. You can't manage to NRR in real time.
What CS needs — and what most CS organizations are missing — is a leading operating metric that tells you what's actually happening in the motion right now.
That metric is Revenue Under Management.
RUM is the total ARR that your CS organization is actively responsible for, segmented by expansion potential and stage in the lifecycle.
At any given moment, your CS team is managing a book of business. Some of those customers are in early stages, still reaching their initial value milestones. Some are in the expansion window — they've hit milestones that indicate readiness, and the plays should be running. Some are approaching renewal with accounts that need to be secured before they enter the negotiation.
RUM makes that breakdown visible. It tells you: of the $X million in ARR your CS org is managing, how much is in the expansion pipeline right now? How much is at risk? How much is trending toward flat renewal versus growth?
When you manage to RUM instead of just NRR, the conversation in CS leadership changes completely. Instead of looking backward at what happened last quarter, you're looking at the current state of the pipeline and asking: where are the opportunities, what's blocking them, and what plays do we need to run to capture them?
This is how every other revenue function manages its pipeline. It's how CS should too.
NRR is the outcome. RUM is the operating discipline that produces it.
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.