I spent years owning net revenue retention as a Senior Enterprise CSM at Adobe, then led Customer Success as a Director at Delphix.
Owning renewals and expansion was the job, and I know the difference between being handed a number and being set up to hit one.
Now I run TopCSJobs, the job board for Customer Success.
So I did something you cannot find anywhere else: I pulled every live CS listing on it, 658 of them, and read what companies are actually asking CS people to do right now.
The pattern is clear, and one number in it should stop you.
Nearly 1 in 4 Customer Success Jobs Now Carry a Revenue Target
Of the 658 live CS roles on TopCSJobs, 155 of them, 23.6%, carry an explicit revenue-ownership signal in the job description.
That means the role names a net revenue retention target, a quota, or an upsell and cross-sell mandate as part of the actual work.
Almost 1 in 11 roles, 8.8%, name NRR by name.
Not “build relationships.” Not “drive adoption.” Net revenue retention, stated as a target the CSM owns.
One listing, Head of Customer Success at Pylon, says it without any softening: “Own the Number. Own NRR, GRR, and churn. Post-sales revenue is yours, forecast weekly and presented to the board.”
That is a Customer Success post. Read it again. Forecast weekly. Presented to the board. Post-sales revenue is yours.
The debate about whether CS is becoming a revenue function is over.
It is in the job descriptions.
The Data Says CS Owns the Number, But Only 2.1% Carry a Quota
Companies hand CS the revenue number. They mostly don’t hand over a quota.
Only 2.1% of these roles, 14 of 658, carry an actual quota.
Sales gets a:
Quota.
Commission plan tied to that quota.
Whole accountability structure built around the number: territory, pipeline stages, a comp plan that pays out when the number lands.
CS gets the target.
From the comp language in these same postings, CS mostly does not get the rest.
Where variable pay shows up at all, it often sits in the pay-range boilerplate, not tied to the CS outcome.
So the picture is this:
Companies want CS to own revenue. They are writing NRR and expansion into the role.
But they are asking CS to own the outcome without the infrastructure that makes owning a number workable.
Which version of the role you walk into decides a lot, including your pay.
One version owns the number, carries the variable comp, and sits in the revenue conversation.
The other hands the number to an account exec.
One gets paid like sales, the other like support.
I lived this.
Owning NRR at Adobe came with serious accountability. What made it survivable was structure: clear targets, a forecast rhythm, and support around the commercial conversation.
Hand a CSM a revenue number with none of that scaffolding and you have not given them a growth engine.
You gave them stress with a dashboard attached.
The Revenue Signal Concentrates at Senior CS Levels
The revenue signal is not spread evenly. It concentrates at the top.
Mid-level CS roles: 22.3% carry the hard revenue signal.
Director-level: 37.5%.
VP-level: 50%.
Half of the VP-level Customer Success roles on the board carry an explicit revenue-ownership mandate. A third of Director roles do.
Moving up in Customer Success means landing in a revenue seat.
The senior CS job is turning into a commercial leadership role, whether the person climbing into it trained for that or not.
What the Data Means for CS Professionals
Your company will measure you on a number. That is settled. The question is whether you walk in fluent in the mechanics behind it.
The CSMs who pull ahead over the next few years will be the ones who understand expansion motion, forecasting, and the commercial conversation as well as they understand adoption and relationships.
Relationships matter. But the number is now the scoreboard, and you cannot move a number you do not understand.
I wrote a full breakdown of how to make that shift without burning out your team here: turning CS into a revenue engine.
And if you lead a CS team, the reality is that writing NRR into the job description is easy.
But giving CS the structure to own it, the targets, the forecast cadence, the commercial support, the comp that reflects the accountability, is what most orgs skip.
The ones that skip it will keep losing the CS people who could drive the number. The ones that build it will keep them.
Owning the number without the tools is a recipe for burnout.
Which CS Role Are You In?
The data says there are two versions of the CS role now.
One owns the number, carries the variable comp, and sits in the revenue conversation.
The other hands the number off and gets paid like support.
Which one are you in?
Want the version that owns the number? My career coaching helps you land it → sharper positioning, better applications, interviews that prove you can carry revenue. Work with me →
Hi Hakan- How many of the roles call out GRR. I saw the one you quoted had both G and NRR. Both are important numbers, but companies shy away from GRR because it's never 100% and NRR hides issues with GRR.