For years, Customer Success has lived in an uncomfortable middle ground.
Not quite Sales.
Not quite Support.
And too often… not tied to revenue in a meaningful way.
So what happens?
CS gets labeled a cost center.
A necessary expense to retain customers.
A team that “protects” revenue, but doesn’t create it.
That framing is the problem.
Because the best CS teams today aren’t just protecting revenue…
They’re driving it.
The Shift Isn’t Philosophical. It’s Operational.
Most leaders talk about this shift like it’s a mindset change.
It’s not.
You don’t become a revenue-driving CS org by saying:
“CS should be more commercial.”
You get there by changing what the team is measured on, how they operate, and what conversations they’re having with customers.
Until those things change, nothing else matters.
Step 1: Give CS a Number (And Make It Real)
If your CS team doesn’t own a number, they don’t own an outcome.
And if they don’t own an outcome, they default to activity:
Check-ins
QBRs
Adoption metrics
“Relationship building”
All important. None sufficient.
The shift starts here:
CS must own a revenue number.
That could be:
Net Revenue Retention (NRR)
Expansion quota
Renewal rate with pricing discipline
But it has to be:
Clear
Measured consistently
Visible at the individual level
When a CSM knows:
“I am responsible for $X in retention and growth this quarter”
Their behavior changes overnight.
Step 2: Redefine the Job (From Service to Strategy)
Most CSMs are still operating like high-end support reps.
They react.
They respond.
They solve problems.
That’s not where revenue comes from.
Revenue comes from driving business outcomes.
The best CSMs:
Tie product usage to business KPIs
Quantify value realized (and unrealized)
Identify gaps that create expansion opportunities
Push customers toward decisions—not just activity
This is the shift:
Old CS Behavior | New CS Behavior |
“How are things going?” | “Here’s the impact you’ve achieved, and what you’re leaving on the table.” |
Tracks adoption | Translates adoption → revenue impact |
Runs QBRs - usage focused | Leads business reviews - strategic |
Waits for opportunities | Creates them |
Step 3: Change the Conversation
If your CSMs are still talking about:
Features
Usage
Tickets
They will never drive expansion.
Because customers don’t expand for features.
They expand for outcomes.
The conversation needs to sound like this:
“Based on your current usage, you’re capturing about 40% of the potential value.
If we expand into [X], we can drive an additional $Y in impact.”
That’s not a support conversation.
That’s a business case.
And most CS teams aren’t trained to do it.
Step 4: Build Commercial Skillsets (Not Just CS Playbooks)
Here’s the uncomfortable truth:
Most CSMs have never been trained to sell.
So when the moment comes to:
Handle pricing pushback
Navigate procurement
Multi-thread into economic buyers
Create urgency
They stall out.
This is where the shift breaks for most teams.
If you want CS to drive revenue, you have to train them on:
Discovery (real discovery, not check-ins)
Value articulation
Commercial negotiation
Expansion strategy
Stakeholder mapping
In other words:
You’re not building better CSMs.
You’re building hybrid operators, part consultant, part seller.
Step 5: Align Incentives to the Outcome
You get what you pay for.
If your CS comp plan rewards:
Renewals only
Flat retention
Activity metrics
That’s exactly what you’ll get.
If you want CS to behave like a revenue team:
Tie compensation to NRR + expansion
Reward pricing integrity (not just renewals at any cost)
Incentivize multi-year and upsell motions
The fastest way to change behavior?
Change how people get paid.
Step 6: Stop Separating CS and Revenue
One of the biggest structural issues:
CS is often disconnected from Sales.
Different goals.
Different incentives.
Different definitions of success.
That creates friction:
Sales pushes for growth
CS protects the relationship
The customer feels the disconnect
The best organizations fix this by aligning around one metric:
Net Revenue Retention.
When both teams care about NRR:
Sales brings in the right customers
CS grows them
Expansion becomes a shared motion
What This Looks Like in Practice
When the shift is working, you’ll see it clearly:
CSMs come to internal calls with revenue forecasts, not just account updates
QBRs turn into forward-looking business cases
Expansion is planned, not reactive
Customers view CSMs as strategic partners, not support contacts
And most importantly:
Revenue becomes predictable.
The Bottom Line
Customer Success doesn’t become a profit driver by accident.
It becomes one when:
The team owns a number
The role is redefined around outcomes
Conversations shift to value
Skills evolve toward commercial execution
Incentives reinforce the behavior
Until then, CS will continue to sit where it always has:
Somewhere between helpful… and under-leveraged.
For Leaders Building This Shift
If you’re leading CS right now, here’s the real question:
Are your CSMs responsible for revenue, or just adjacent to it?
Because in today’s environment, that distinction matters.
A lot.
If you have questions on making this shift just reply to my email!
Suggestions for future newsletters? Let me know.
