Customer Success is not broken. The job description is.
Most Customer Success leaders blame sales for not believing in CS. But I've sat in those rooms — at Cisco, at ServiceNow — and the real problem isn't the sales culture. It's that CS was never built to speak the language of the people who control the budget.
Why the hardest sales call I ever made was to my own colleagues — and what it tells us about the state of Customer Success.
A few months ago, I found myself sitting at the table with senior sales leaders at one of the largest tech companies in the world. I was not there to close a customer. I was there to convince my own colleagues that the CS product we were trying to sell was worth selling.
The product bundled intelligence tooling, a dedicated, senior CSM, and a solution architect — everything a customer needed to actually achieve value from the platform. It was, on paper, exactly what CS is supposed to deliver. And yet the room was hostile as the sales leaders didn't believe in it. They didn't think customers would pay or should pay for it. And when I tried to quantify the return — the retention uplift, the expansion rate, the reduced time-to-value — they questioned every number.
I have had that conversation more than once — at Cisco, at ServiceNow, in different rooms, with different slides, and the same result: polite skepticism at best, active resistance at worst.
For a long time, I thought this was a sales culture problem. But I was wrong — it's a CS mandate problem.
💡
Sales didn't fail to believe in CS. CS failed to build a case that revenue leaders could believe in.
Here is the pattern I have seen across almost every SaaS company: Customer Success is designed to be defended, not sold. The team is structured around relationships, health scores, and renewal rates; the language is about satisfaction and retention; the metrics are lagging and soft. And then someone puts a price tag on it and wonders why procurement pushes back.
The problem is not the work CS does because that work is often exceptional. The problem is that CS was never designed to speak the language of the people who control budget — and in 2026, with AI reshaping every commercial function, that gap is becoming a crisis.
When a sales leader looks at a CS product and asks "what is the ROI?" — and the CS leader responds with NPS trends and health score improvements — the conversation is already over. Not because the CS leader is wrong but because they are answering a different question than the one being asked.
The CS job description was written for a post-sale relationship era: build trust, manage renewals, escalate risk, run QBRs. All of that is real work, but none of it, on its own, is a revenue argument.
And now that AI has arrived, the pressure is intensifying. Boards want CS to justify its headcount. CFOs want CS to show a direct line to revenue. Sales leaders want CS to accelerate the commercial motion, not run parallel to it. The CS leaders who will survive this moment are the ones who can make that case — clearly, in revenue language, with numbers that hold up under scrutiny.
That is what this newsletter is about. Not CS as a support function that needs defending, but CS as a revenue function that earns its seat at the table.
In this first issue of CS in the AI Era, I want to leave you with a couple of practical items you can do right away — a framework assessment that helps you assess your CS org's commercial mandate and three AI prompts that can help you move the needle forward based on the assessment's results.
Framework · Issue 01
The CS Mandate Audit
Ten questions to assess whether your CS org has a commercial mandate — or just a relationship function dressed up in revenue language. Score each question 1–5. 1 = not at all true. 5 = completely true.
Commercial mandate
CS has a defined revenue target — not just a retention target.
__ / 5
CS is included in the commercial strategy conversation, not just the post-sale handoff.
__ / 5
CS leaders can articulate the ROI of their function in the language a CFO would accept.
__ / 5
If the CS function disappeared tomorrow, the revenue impact would be immediate and quantifiable — and the exec team would know the number.
__ / 5
AI readiness
My team uses AI to synthesise account risk, expansion signals, and renewal narratives — not just for task automation.
__ / 5
My team has documented which CS workflows AI now owns, and which require human judgment.
__ / 5
The CS team's use of AI has reduced time spent on low-value activity and increased time on commercial conversations.
__ / 5
Executive visibility
CS leadership has a direct line to the CRO or CEO — not only to the COO or VP Operations.
__ / 5
CS presents in the board or exec team meeting with revenue-framed outcomes, not just health and satisfaction metrics.
__ / 5
Sales and CS share a common definition of customer success — and a shared commercial incentive.
__ / 5
10–25Relationship managerCS is doing important work without a commercial mandate. The function is at risk in the next budget cycle.
26–39Value advisorCS has some commercial muscle but the mandate is inconsistent. Revenue language is emerging but not yet the default.
40–50Revenue leaderCS has a clear commercial mandate, AI-ready workflows, and executive visibility. This is where the function needs to be.
Use this with your team, your peers, or your own reflection. The questions that score lowest are the mandate gaps — and the mandate gaps are the ones that get CS cut when budgets tighten.
Prompt library · Issue 01
Prompt 01 — Audit your CS mandate
You are a senior CS strategy advisor. I am a [VP / Director] of Customer Success at a [company size] SaaS company in [industry]. My CS org has the following profile:
— [X] CSMs, each covering [X] accounts
— Total ARR managed: [X]
— CSM targets include: [e.g. GRR %, NRR %, expansion ARR quota, QBR completion rate, health score thresholds, time-to-value milestones]
— CS is currently measured on: [e.g. churn rate, CSAT/NPS, renewal rate, product adoption metrics]
— CS is not currently measured on: [e.g. pipeline influence, expansion revenue, revenue per CSM]
Based on this, help me audit whether my CS function has a genuine commercial mandate or is operating primarily as a relationship and retention function. Identify the three most important mandate gaps and give me a one-sentence recommendation for each.
Output: A prioritised gap analysis with actionable recommendations. Paste directly into a leadership team agenda or use it to frame the conversation with your CRO.
Prompt 02 — Write the board slide
Write a single board slide that makes the case for CS as a revenue function. The audience is [CEO / CFO / board]. The key metrics I have available are: [list your retention rate, NRR, expansion ARR, and time-to-value data]. Frame the slide so that the ROI of CS is expressed in revenue terms — not satisfaction or health score terms. Include a headline, three supporting data points, and a one-line call to action.
Output: Board-ready slide content. Copy into your next deck — edit the numbers, keep the structure.
Prompt 03 — Rewrite the CS job description
Here is my current CS job description: [paste it]. Rewrite it so it reflects a revenue-generating CS function in the AI era. The new version should: use revenue language throughout, include AI fluency as a core competency, remove or reframe any language that positions CS primarily as a support or relationship function, and signal clearly that this role is accountable for commercial outcomes. Keep the same length but change the framing entirely.
Output: A revised job description ready to post — or to share internally to start the mandate conversation.
Next issue
Issue 02 is about the part of CS that AI is already replacing and the part it cannot touch. The gap between those two things is where revenue-generating CS leaders live.
— Iliyana
CS in the AI Era is a bi-weekly newsletter for Customer Success leaders in European SaaS. If someone sent this to you and you want to receive it directly, subscribe here. Or if you know a CS leader who should read it? Forward it.
