Quick summary: We analyzed 50 live CSM job descriptions from leading SaaS companies and found that hiring specifications haven’t kept up with the CSM role itself.
Thought experiment: You hire a CSM today based on your company’s most recent CSM job description. How confident are you that they’ll be equipped for what the role requires in 18 months’ time?
We analyzed 50 live CSM job descriptions from leading SaaS companies—across edtech, AI, healthtech, cybersecurity, adtech, fintech and other verticals—and found the vast majority to be out of date.
It may not feel like the most pressing issue. But, if you expect CSMs to be revenue-ready, outcomes-focused, and confident with AI-powered workflows, your job requisition needs to make it clear. There’s a first-mover hiring advantage to getting it right.
Here are the patterns, consensus, and conspicuous omissions we found, along with how to get your CSM job descriptions in shape for 2026 and beyond.
What’s in a typical CSM job description in 2026?
As of May 2026, the standard mid-market or scaled CSM job description looks like this:
- Mission: Retain customers; drive renewals; identify expansion opportunities.
- Primary metric: NRR or GRR (present in ~85% of job descriptions).
- Secondary metrics: Product adoption, health scores, QBR completion.
- Daily duties: Monitor health signals, run QBRs, handle escalations, maintain CRM hygiene.
- Core skills: Relationship management, stakeholder communication, data analysis, cross-functional coordination.
- Tools: CRM (~85%), customer success platform (~40%), conversation intelligence (~25%).
- Book size: 20–300 accounts depending on segment and seniority.
What’s missing from the typical CSM job description?
We identified three major gaps between the typical hiring spec and the role of a modern, revenue-driving, AI-equipped CSM.
Gap 1: Outcome ownership.
Does the job description frame customer success as the delivery of the outcomes that customers are trying to achieve, and whether CSM is accountable for them? Present in only 3 out of 50 job descriptions (6%).
Gap 2: Using AI as a workflow tool.
Does the job description go beyond “AI productivity” language to position AI as an active, specific part of daily workflows—for example, in health scoring, personalized outreach at scale, QBR preparation? Specific examples are mentioned in just 4 out of 50 job descriptions (8%).
Gap 3: Commercial fluency.
Does the job description require CSMs to have the knowledge and skills to navigate budget cycles, build business cases, understand buying processes, and hold commercial conversations? Mentioned in only 9 out of 50 job descriptions (18%).
Outcome ownership: what’s missing and how to include it.
A major customer success trend for 2026 is the realignment of CS around customer outcomes, with programs redesigned to meet customer goals. After all, a CSM who runs every QBR on schedule and never misses a check-in can still lose a customer to surprise churn because the product never solved their core problem.
“CSMs will move from relationship owners to outcome architects,” Sabina Pons of Growth Molecules told ChurnZero earlier this year, “fully adopting tools for precision in delivering customer needs, rather than focusing on being proximate.
However, the vast majority of job descriptions in our sample continue to define success in the vendor’s terms: NRR, churn rate, health score, or even QBR cadence. Almost none define success in terms of what the customer was trying to achieve when they bought the product.
While the term “value realization” does appear in roughly one-third of our sample, nowhere is it defined in practice: who measures it, how it’s tracked, or how a CSM’s might course-correct when customers are off-track.
The descriptions that come closest reference what the customer is trying to achieve.
One specifies that CSMs should align success plans to “the customer’s core engineering and business goals” rather than a platform-generated score. Another includes a weighted KPI table that includes the customer’s own perception of value as a primary performance measure.
How do I reflect outcome ownership in our CSM job descriptions?
“Define and track customer success in the customer’s own terms.”
“Agree on measurable outcomes at the start of the relationship, and report against them throughout the lifecycle, not just against internal health metrics.”
“Distinguish between product adoption and value realization. A customer using the platform is not the same as a customer achieving their business goals. Own the gap between the two.”
“Build and maintain success plans grounded in the customer’s definition of success, not ours. Keep them updated as each customer’s business context changes.”
AI as a workflow tool: what’s missing and how to include it.
AI has been transforming the way CS teams work for three and a half years. By this point, your job descriptions should specify distinct AI workflows or outputs, rather than just “productivity”.
Yet, specifics on AI as a workflow tool appeared in just four of the 50 job descriptions we reviewed. Most treated AI as a vague force multiplier to be familiar with—“enhance customer engagement” or “drive efficiency”—instead of specifying distinct workflows or outputs such as:
- Health scoring: AI-driven scoring predicts what’s likely to happen and surfaces why. CSMs should be able to investigate a prediction and compare it to their own understanding of the account.
- QBR prep: Scratch the idea of a CSM spending four hours on a deck. AI can generate the narrative, surface key metrics, and flag anomalies. The CSM’s job is to edit and contextualize.
- Scaled outreach: AI-powered outreach, personalized at the account level based on usage, behavior, and sentiment, is the key to real scale. CSMs need to know how to make it work.
- Proactive escalation: AI can flag risks in their infancy thanks to agentically detected risk signals. The challenge for a scaled CSM is to decide how to handle it once AI flags it.
How do I reflect AI-powered workflows in our CSM job descriptions?
“Interpret AI-generated health predictions and apply account knowledge to validate, adjust, or override them.”
“Manage scaled account books using AI-assisted outreach, reviewing, and editing output to maintain quality and relevance.”
“Operate as an AI-augmented CSM: prompt effectively, edit critically, and maintain quality standards on all customer-facing content regardless of how it was generated.”
Commercial fluency: what’s missing and how to include it.
In a recent poll by ChurnZero, 44% of CSMs said their sales and negotiation skills are holding them back. 40% identified their analytical skills as a weakness, and 28% pointed to business strategy as a skills gap.
Unfortunately, most CSM job descriptions seem to be experiencing a similar issue.
While roughly 20% of our sample name commercial outcomes like “ meet or exceed ARR targets”, none of them specify how to get there.
Details such as understanding when a customer’s budget cycle opens, who controls discretionary spend, what the approval chain looks like for a renewal, or how to time the switch from “trusted advisor” to “commercial conversation” don’t exist at all.
Call it revenue readiness, or commercial fluency; a modern CSM needs to understand how commercial conversation, budget cycles, business cases, procurement, and budgets work.
While most job descriptions mention stakeholder management or executive engagement, almost none distinguish between the end-user, the champion, and the person who controls the budget. Each represents a different conversation, and requires specific fluency that relationship skills alone don’t cover.
How do I reflect commercial fluency in our CSM job descriptions?
“Understand the customer’s budget cycle and procurement process.
“Time commercial conversations effectively, knowing when budget is available, who controls it, and what the approval path looks like for renewal or expansion.”
“Build business cases for continued and expanded investment in the customer’s language. Use the customer’s metrics, success definitions, and internal ROI framework.”
“Build the internal case for investment through champions. rather than relying solely on direct vendor-to-buyer selling.”
“Navigate the distinction between the day-to-day user, the internal champion, and the economic buyer. Engage each with the right conversation at the right time.”
Why it matters, and what to do next.
“A clear, detailed, and well-written customer success job description is essential to attract the right candidate while providing important information about the company,” says CS hiring expert Swati Garg.
When you publish an out-of-date description, it doesn’t just fail to show CSMs what skills are important or what success looks like—it also fails to position your company as an employer of choice.
Here’s what to do.
1. Audit your current CSM job description against the gaps above.
Check each of our three gaps against your active CSM hiring spec. If you’re missing them, you’re hurting your chances of hiring the best people.
2. Write AI literacy into the role.
If you expect CSMs to use standalone AI tools, name the tools and make it clear. Inventory what your team uses (or should be using), define what ‘good’ looks like for each one, and add those expectations explicitly.
3. Pay attention to the metrics section.
This section should be the most honest snapshot of what the role is. If you expect CSMs to fully own revenue, for example, list metrics like NRR and forecasting accuracy, rather than health scores or activity metrics.
4. Use this project to get more aligned.
Updating your job description comes with a hidden opportunity. You can use it to align your cross-departmental peers and C-suite on what the CSM role—and your CS team’s role—actually is.
Happy hiring! You can find more tips on creating better CS job descriptions here.
Our analysis is based on 50 live CSM job descriptions collected in May 2026, spanning SaaS, digital health, cybersecurity, DevOps, AI, legal tech, fintech, and education technology.
