AI Skills for Customer Success Managers: What Employers Want

Open any customer success job advert in 2026 and you will meet the word AI within the first paragraph. It is easy to conclude that the role has been rewritten and that you are behind.

We read the postings instead of counting the word. Across live post-sale listings at about 900 B2B software companies, seven in ten mention AI somewhere in the text. On the strictest count, one in nine asks the person being hired to use it, and checking the cases our rule missed puts the real figure nearer one in six. The gap between those two numbers is the whole story, because almost everything in it is the employer describing itself, its product or its funding, and not a word of that is a requirement you need to meet.

What counts as an AI skill in a customer success job

An AI skill, as employers write it down, is a sentence that attaches AI to something you will do. "Hands-on AI fluency." "Experience using AI tools to automate manual parts of your workflow." "You use AI to build tools and automate workflows."

That is a narrow definition and it is deliberately narrow, because the alternative produces nonsense. A posting that opens "we are an AI-native workspace for legal teams" has told you about the company, not about the job. A posting that lists its customers as Anthropic and Perplexity has told you about its logo wall. A posting carrying a notice that AI assists the recruiting team has told you about its applicant tracking system, which is a fact about how your CV gets read rather than a skill you need once you arrive.

All three of those contain the word AI. None of them asks you for anything. Any figure built by counting the word rather than reading the sentence folds all of them into the same bucket, which is how a role that has changed modestly comes to look like a role that has been rebuilt.

Seven in ten postings mention AI. Almost none of it is about you.

Of the postings that mention AI at all, roughly one in six goes on to ask the candidate for anything. The other five are talking about themselves.

This matters more than it sounds, because the mention rate is the number everyone feels. You read twenty adverts in an evening, you see AI in fourteen of them, and you conclude the market has moved past you. The requirement rate is the number that governs whether you get the interview, and it is far lower and far more modest in its demands.

It also explains a specific kind of discouragement. A posting whose technical language is describing the product reads as a bar you do not clear, and the role gets scrolled past by someone qualified to do it. The CSM at an AI company is still a CSM. The question of whether that stays true is a live one, and worth reading separately on whether AI will replace customer success managers, but it is not what these postings are saying today.

What employers actually ask you to do with AI

When a posting does make a request, it is usually unglamorous.

The most common form is a general expectation that you use AI in ordinary work. One posting asks for "daily use of AI tools for meeting prep, account research, and synthesis", and adds that it should be "a genuine work habit". Another says the team is "expected to leverage AI daily" and that fluency is assessed during hiring. A third sets the bar deliberately low: "you don't need professional experience using AI tools, but we'd expect you've experimented with them."

That is not a technical requirement. It is an expectation that you have opened the tools and formed an opinion. Several postings say so explicitly, asking for "the judgment to know where they help and where they don't", or for "responsible use of AI" with privacy, bias awareness and a human in the loop named alongside it.

The second form names a specific assistant. Claude, ChatGPT, Copilot, Cursor and Gemini appear by name as tools the person is expected to have used, sometimes in a list beside the CRM and the spreadsheet. One posting asks for experience "beyond basic chat".

The third form is genuinely technical, and it is the smallest. These postings ask for prompt engineering, retrieval, evaluation work, or building agents. One asks that you can "explain the difference between RAG and agentic reasoning to a skeptical technical" audience. Another asks you to "use Claude daily and build agents yourself, then teach the team to build their own."

The three things they name, in order

Read in order, the distribution says something useful. Six in ten of the requirements are satisfied by habitual use. Fewer than one in four names a product. Fewer than one in six asks for the engineering-adjacent skills that dominate the conversation about AI and customer success.

If you have been putting off learning prompt engineering because it sounded like a career change, the data says you have mostly been avoiding the smallest category. The thing being asked for in the majority of cases is that you already use these tools, in your own work, well enough to have a view on where they fail.

The CRM is still asked for more often than AI

Counted on the same postings on the same day, the CRM is still asked for more often than AI, and by a wide enough margin to survive the corrections below. Excel and SQL sit below both. A named customer success platform sits below all of them, which is the finding we reported separately when we looked at what customer success teams actually run on, and it has not moved.

This is the line worth keeping. AI has arrived in the post-sale job description faster than almost anything before it, and it has still not displaced the CRM as the thing employers most want you to be comfortable in. A candidate who reads the market as "AI or nothing" is reading it wrong in both directions: AI is real and rising, and the unglamorous tooling is still what most of the work runs on.

The comparison needs one correction, and it cuts in AI's favour. A CRM has a name, so it is easy to count. AI is a capability that often appears with no product attached, and our rule only catches it where a sentence ties it to the candidate, so it undercounts. Reading a sample of the postings the rule skipped suggests the real AI figure is nearer one in six than one in nine, which closes most of the gap without quite closing it. Treat the ranking as safe and the distance as provisional. We would expect these two lines to cross, and soon.

Where the AI ask is strongest, and where it barely exists

The requirement is not spread evenly across post-sale roles.

On the same strict count used throughout, technical account manager postings ask most often, at about one in five. Onboarding and implementation roles come next, at roughly one in six. Customer success manager postings sit at about one in ten. Account management postings ask least, at roughly one in fifteen. The ordering is what matters here. The correction described above applies to all four, and we did not measure it role by role, so read the order rather than the gaps.

The ordering is not random. It tracks how close the role sits to the product. A technical account manager is already expected to be hands-on, so adding AI tooling to that expectation costs the employer nothing. An onboarding or implementation specialist is configuring things for a living, and a good share of what they now configure is an AI feature, which is a different point we unpack in what AI customer success agents can and cannot do. Account management is the most commercial of the four and the least technical, and its AI requirement rate is less than half the technical account manager rate, which fits the wider split between the two jobs we measured in customer success vs account management.

One small number deserves a warning rather than a conclusion. Customer success operations postings also look high, but there are only a few dozen of them in the whole market at any one time, so that rate is noisy and should not be read as a trend. The shape of that role, and why so few companies staff it, is a separate subject we covered in customer success operations.

What nobody is asking for

The absences are as informative as the requirements, and there are three of them.

Almost no posting asks for a formal AI qualification. There is no certification, no course and no credential that recurs often enough to be worth naming. If you were waiting for the market to tell you which course to buy, it has not, and the postings that are most specific about AI ask for evidence of use rather than evidence of study.

Almost no posting asks you to build or train models. The technical tail asks for prompting, retrieval and evaluation, which are configuration skills, not machine learning skills. The distinction matters because it is the difference between a weekend of practice and a degree.

And almost no posting describes AI as a reason the team is smaller. Employers write about AI as something that makes the person more effective, not as something that reduces how many people they need. That is what the adverts say rather than what companies do, and hiring plans are decided somewhere other than the job description. If you want the money version of that question, the cost side is worked through in cost to serve per account.

The postings want judgment. Most CSM weeks go on assembling the picture first.

What this changes if you are hiring

Three practical consequences follow for anyone writing one of these postings.

Say what you mean, because candidates are discounting the word. When seven in ten adverts mention AI and most of those mentions are marketing, the word has lost its signalling power. A posting that says "you will use AI to draft account summaries and prepare for calls, and we will ask you how you check its output" tells a candidate something. A posting that says "we are an AI-first company" has told them nothing they can act on.

Separate the requirement from the product. A large share of what reads as an AI requirement is really a request that the person can support an AI feature the company sells. Those are different jobs with different candidate pools, and running them through the same advert produces applicants who are wrong in both directions. The same confusion shows up in coverage design, which is the subject of digital customer success.

Set a bar you can test. The postings that handle this best name what they will actually check: a fluency assessment, a conversation about where the tools fail, or a request for examples of work the candidate changed by using them. Asking for AI fluency without defining it produces a filter you cannot apply fairly, and it will quietly screen out good people who did not know what they were supposed to claim.

What this changes if you are the candidate

The useful conclusion is narrower than the panic suggests, and it is cheap to act on.

Use the tools in your real work, this month, and keep the evidence. The most common requirement in the data is habitual use, and the most common way postings describe proof is an example. An account summary you now draft in a quarter of the time, a renewal brief you assemble from usage data, a set of notes you turn into a follow-up: each is a sentence in an interview and none of it requires a course.

Learn where they fail before you learn what they do. An unusual number of postings ask for judgment rather than capability. Being able to say what you do not let the tool touch, and why, is a more distinctive answer than a list of features, and it is the answer the better-written adverts are fishing for.

Keep the CRM sharp. It is still the most-requested tool skill in the post-sale market, ahead of AI on every count we ran, and allowing it to rust in order to chase a smaller requirement is a bad trade.

Ignore the technical tail unless you want it. Prompting, retrieval and evaluation work appears in the minority of AI requirements, and it clusters in the technical and onboarding roles. If that is the direction you want, the adjacent role to study is the technical account manager, where the rate is highest and the expectation is explicit.

How to build the fluency the postings describe

The requirement, stripped of its language, is that you can get a useful answer out of a tool, and that you know when the answer is wrong. Both halves are learnable in a working week.

Start with the work you already repeat. Pick the three tasks you do every week that consist of assembling information rather than deciding anything: the weekly account summary, the pre-call brief, the handover note. These are the tasks the postings name, almost without exception, and they are low risk because you check the output anyway.

Then build a habit of verification. Make a rule about what you never send without reading, and about which facts you check against the source every time. This sounds like caution and it is actually the skill, because the posting that asks for "the judgment to know where they help and where they don't" is asking whether you have been burned and learned.

There is a written version of that standard you can practise against. We publish thirty open source customer success skills under an MIT licence, built for the agent clients people already use. Every number has to carry the system, field and date it came from or it does not get used. Every analysis prints the signal families it could not check instead of quietly dropping them. Words like guaranteed and will churn are banned outright. Reading the rules is most of the value, even if you never run one of them.

Then widen the input. Most of the frustration people report with these tools in customer success comes from asking them to reason about an account they know nothing about. The answers improve sharply when the usage, billing and support history is in front of the model rather than summarised from memory. Getting that data into one place is the part that is hard, and it is the part the tools will not do for you.

How GainTrace helps

The requirement the postings describe is judgment, and the thing that gets in the way of judgment is assembly.

Most of the hours a CSM loses are spent gathering the picture rather than acting on it: pulling usage out of one system, billing out of another, tickets out of a third, and reconciling them before anyone can decide anything. GainTrace pulls product usage, billing, support and CRM into one explainable score per account, with the reason it moved attached, so the assembly is done and the account arrives already explained.

That is the division of labour the better postings are describing. The tool does the reading. You decide what it means and what to do about it, which is the half nobody is advertising to replace.

None of this is a substitute for the fluency employers are asking for, and the habit they want you to have is one you build in your own work. What it changes is the input.

If you want to see the raw material behind this article, the postings are on our customer success jobs board. It refreshes every morning, so the live set will not match the snapshot these figures were counted from.

Want to stop assembling the picture before every call?