Forecast review. Your manager pulls up an account. Green. Renewal in 60 days. The last note says “Good call, all on track.”

Everyone moves on.

A few weeks later, you email the champion. It bounces. She left the company months ago.

Nobody did anything wrong. You wrote “all on track” after a good call, as a quick note for yourself. Nobody updated it when things changed.

But on the forecast call, that old note was all your manager had to go on.

The Job Asks For The Forecast And Skips The Inputs

I wanted to see if companies even expect this to work, so I went to the job posts.

I took the 279 CSM roles on the TopCSJobs board, posted since mid-July and still open this week, and extracted what each one asks the CSM to do.

• 54 ask you to forecast renewals or expansion.

• 8 ask you to keep CRM records accurate.

• Only 2 ask for both.

One of them is 1Password. It asks for “strong Gainsight and Salesforce hygiene; consistent forecasting discipline” in the same line.

Almost everyone else treats the forecast and the data behind it as two separate jobs.

And the forecast is often the only one that makes it into the job description.

Sales Handoffs Show It Best

Think about the handoff doc.

The Account Executive fills it in after the deal closes. But the AE won’t use it. You will.

So it gets done fast, to tick a box, and you end up learning what was promised on your first customer call.

The teams that fix this don’t write a better template. They give the AE a reason to care about what happens next:

• Part of the AE’s commission depends on the customer still being there at 90 days.

• No commission until the handoff and kickoff are done.

• The AE joins the first customer call.

Once the person writing the notes has a stake in what happens next, the notes get better.

Your CRM Works The Same Way

Think about how notes get written on your team.

You write them fast, for yourself. A few words, enough to remember the call next time.

Then your manager reads those same notes to build the forecast.

And everyone logs things differently. One CSM writes a risk in the notes. Another changes the health field. A third mentions it on Slack and moves on.

Same risk, three places, and the forecast only sees one. It’s easy to blame busy CSMs. But the real issue is simpler.

When the person who writes a field is the same person who uses it, it stays accurate.

But when they’re different people, it slowly goes stale, and nobody notices until the forecast call.

Most teams have never checked which of their fields are which.

One Fix You Can Start This Week

Start with the easiest one: the field everyone fills in differently because nobody ever showed them how.

Pick the task that goes wrong most on your team. Logging a call, updating renewal notes, or flagging a risk.

Write down the exact steps, in the order you click, with a screenshot for each.

Then hand it to your newest CSM. If they can follow it without asking you a question, it’s done.

A simple doc works fine.

Tools like Tango, one of my recent sponsors, make it faster. It captures the steps while you click and turns any workflow into a step-by-step guide with screenshots.

So that fixes one field. Now let’s find the rest.

Find The Stale Fields First

Pick one account in your next forecast. Which of its fields would you actually bet the renewal on?

The 30-min audit I built tells you, field by field. It’s right below, and Q4 renewals are already on the calendar, so start there.

Step 1: Run The Writer–Reader Audit

List every field that feeds your forecast, health score, or handoff.

Most teams land on 8 to 15: renewal risk, health status, champion, next step, renewal date, last contact, ARR, handoff notes.

For each field, fill in five columns:

• Writer

  Who enters it?

  Name the role → CSM, AE, CS Ops, or a system.

• Reader

  Who makes a decision with it?

  CS leader, finance, the next CSM.

• Writer uses it (0 to 2)

  0 if the writer never looks at it again.

  1 if sometimes.

  2 if they use it every week.

• Consistency (0 to 10)

  Pull 10 accounts at random.

  Count how many have the field filled in the same way, current, and in a format the reader can act on.

• Decision weight (0 to 3)

  How much does a renewal or forecast decision depend on it?

• Risk = Decision weight × (10 − Consistency)

  Any field with risk of 15 or more is red.

  Any field where the writer scores 0 and the decision weight is 2 or higher is red too, even if it looks clean today.

  That’s a gap waiting to drift.

→ Expect three or four reds.

They’re almost always the fields your forecast leans on hardest.

Found Your Reds? Here’s What To Do With Them

Steps 2 and 3 show you the right fix for each red field and the 15-min monthly check that keeps them accurate.

Paid members also get the full Forecast Fields Workbook, which does the scoring for you, and can send me their renewal plan or exec update for review before it reaches leadership.

Upgrade → · Expense it →

PS. What’s the one renewal, QBR, or exec conversation you’re most worried about between now and year-end? Hit reply, one line is enough. I read every answer and will point you to the right playbook.

Read more

You’re the person everyone asks. Tango gives you backup.

Do a task once, and Tango turns it into a step-by-step guide with screenshots, ready to share as a link or pin right inside the tool. Next time someone asks, send them a Tango and take the repeat questions off your plate.

Free to start. Try Tango free →

Ask a CS leader how many accounts one CSM should carry, and you’ll get a benchmark.

Ask the job description, and you’ll usually get silence.

On Sunday, I showed that most CSM job postings never say how many accounts the role carries. This week I read the ones that do.

The 13 That Name A Number

Of the 318 CSM roles on TopCSJobs posted since mid-July and still open today, 13 name a number.

They range from 10 accounts to 150, with the middle at 50:

• High-touch enterprise roles: roughly 10 to 60 accounts

• Mid-market roles: roughly 40 to 75

• High-volume roles: 100 to 200

Those ranges broadly line up with the industry benchmarks for CSM to customer ratio. The difference is where they come from. These are numbers companies chose to put in writing, before hiring anyone.

When a company writes the number down, it has already done the capacity math. That’s the conversation you’re trying to start.

The Work Nobody Counts

Account load is only half the picture.

Of the 76 senior CSM roles live on TopCSJobs this week, 24 mention mentoring teammates, on top of carrying their own book.

So your most experienced CSMs carry a full book, plus every “quick question” from every new hire.

• How do I log this call?

• Where do renewal notes go?

• How do I hand off an account?

None of that shows up in an account count. All of it comes out of the week, and most of it comes out of your strongest people.

Build Your Number Before The Meeting

You don’t need a perfect model. You need a number you can defend.

1. Write your load down

   Accounts and ARR per CSM today. If you’ve never framed it in revenue terms, start with ARR per CSM.

2. Put it next to the market

   Use the 13 postings above and the ratio benchmarks for your segment.

3. List the work nobody counts

   Mentoring, onboarding new hires, repeat questions, internal requests.

   Name who carries each one.

4. Clear what you can first

   The questions answered ten times a week are the easiest hours to win back.

   A step-by-step guide for each process turns them into a link.

Walk in with those four, and your capacity stops being a feeling. It becomes a number the room has to respond to.

The hours nobody counts get spent first. Count them before the meeting.

Heading Into That Meeting Soon?

Sunday’s edition gives paid members the full system → a ranked stop list in hours, a one-line answer to “can AI do this?”, and the rule that keeps stopped work stopped. Read it here →

Paid members can also send me their exec update, and I’ll review it by email before it reaches leadership. Upgrade to paid →

Prefer to rehearse the meeting 1:1? Book a coaching session with me →

Share

You brought the list. Onboarding. Renewals. QBRs. Escalations. The advocacy program. Enablement for the next launch.

You explained it no longer fits. They nodded.

Then they said, “Maybe AI can help.” And, “Maybe the team can tighten up.”

You came in to make a decision. You walked out with the same list and a little less credibility.

I pulled 615 CSM job postings to see why this meeting keeps ending the same way.

The answer was sitting in the job description, before the first CSM was ever hired.

The Job Description Already Admits It

TopCSJobs pulls these postings straight from employer hiring systems.

All of them went live between July 13 and October 11, 2026. I counted duties only from the responsibilities section, leaving out requirements, benefits and pay.

The typical posting lists four separate areas of work, and just over half include renewals.

Almost 9 in 10 never say how many accounts the role carries.

Read that from the exec’s side of the table.

Scope is written down. Capacity is left open. The company defined what a CSM does and skipped how much of it one person can carry.

So every new request lands on a role with no ceiling. Every added account looks free.

And when you say the team can’t do it all, you are pointing at a limit nobody ever set.

Why Leadership Says Keep Everything

Three patterns repeat.

1. The ask is shaped as “more”

A request for another head opens a debate about efficiency.

Leaders who win that debate bring revenue numbers, the case I built in ARR Per CSM and the CS capacity model.

Leaders who skip the numbers end up defending effort.

2. Silence on the AI question

In 2026, the first reply to any capacity problem is “Can AI absorb this?”

Most CS leaders answer with a general sense of what the tools can do. The room hears a team that never checked.

3. Approvals that evaporate

This one does the most damage, because it happens after you win.

The exec agrees to stop the monthly health review for low-tier accounts. Everyone leaves aligned.

A few weeks later, a sales leader asks why a small account went dark, and the stopped work is back on the team’s plate with a deadline attached.

You argue the same case again, this time from a weaker position, with a churned logo as the backdrop.

Each pattern ends the same way. The workload stays, and the people doing it absorb the blame.

Renewals Pay First

Overloaded CS teams drop work unevenly. The first casualty is whatever has nobody chasing it this week.

Escalations get answered. The executive’s pet project gets done. Onboarding has a customer waiting on the other end. Renewal prep has none of that pressure until 90 days out, and then it has all of it at once.

So the account review that would have caught the champion leaving gets pushed. The usage dip goes unread. The risk surfaces on the forecast call, too late to change.

If your team is stretched today, it is already running a stop list.

Nobody chose it, nobody signed it, and a renewal in the next two quarters is on it.

You just can’t see which one yet.

Choose What Stops Before Leadership Chooses for You

Planning season is here.

Next year’s scope gets set in the next few meetings, and the same list gets you the same meeting.

Each pattern above has a fix that works with the team you already have.

Below, paid members get the system that closes all three:

• The “more” trap

  A ranked list of what stops, so the exec sees the trade-off in hours before you mention headcount.

• The AI question

  A one-sentence format that answers “can AI do this?” for every activity, before anyone asks.

• Approvals that evaporate

  The rule that keeps stopped work stopped, and the exact line to use when a sales leader asks for it back.

• The hidden renewal

  A 45-minute scoring pass that shows which renewal work your team is already dropping.

Same team. Same list.

A different meeting, with a signed answer at the end of it →

Read more

Stay two more years. Keep your accounts green. Wait for the promotion cycle.

The job ads tell a different story.

If you're new here: I run TopCSJobs, a job board that syncs Customer Success roles straight from employers' own hiring systems. So I analyzed every CS listing from the last 120 days → 1,396 listings, from June to early October 2026.

Then I split them by level.

373 senior CSM roles at 97 companies. 504 mid-level CSM roles at 152 companies. People managers (Directors, Heads of CS, VPs) are out of the count. This is about individual contributors.

One caveat: these are job ads. They show what employers advertise, which can differ from what people end up being paid.

Here is what separates the two groups.

TL;DR (the short version):

• Senior CSMs earn about 25% more base pay in the US ($150K vs $120K).

• About 43% of senior roles don’t say “Senior” in the title.

• Senior ads are 2.4x more likely to ask you to coach other CSMs.

• Senior CSMs manage fewer, bigger accounts (20 vs 55).

• Customer Success certifications appear in 2 of 373 senior ads.

Senior CSM Salary in 2026

In the US, the median advertised base salary for a senior CSM is $149,960. For a mid-level CSM, it is $120,000.

That is a 25% premium, about $30,000 a year, for the same job family.

The spread inside each level:

• Senior CSM: most roles pay between $122,000 and $182,000 base.

• Mid-level CSM: most roles pay between $102,000 and $149,000 base.

These numbers come from 54 senior listings at 30 companies and 60 mid-level listings at 36 companies, all with a published pay range.

Two things to keep in mind.

First, the ranges overlap. A strong mid-level CSM at a well-paying company can out-earn a senior CSM elsewhere. Company matters as much as title.

Second, salary transparency is mostly a US habit. 46% of US senior ads list a pay range. In the UK, only about 5% do. That is why this section is US-only. I would rather show you no number than a guessed one.

If you are weighing a big-company path, I broke down one of the most searched senior CS roles here: Microsoft CSAM role, salary and career path.

Senior Comes Under Many Names

Here is the first thing that surprised me.

About 43% of senior CSM roles never use the word “Senior” in the title.

How senior roles are titled:

• Senior or Sr. CSM: 57%

• Enterprise CSM: 21%

• Strategic CSM: 10%

• Principal CSM: 7%

• Other (Key Accounts, CSM III, Lead): 5%

If your job alert only searches “Senior Customer Success Manager,” you miss almost half the market.

Search for Enterprise, Strategic and Principal too. And when you read a “CSM II, Enterprise” title, read the scope. That role is often senior in everything but name.

I wrote about why companies label this inconsistently here: the senior CSM mislabeling problem.

What Senior Ads Ask For That Mid Ads Don’t

This is the core of the analysis. I compared the language in senior and mid-level ads, after stripping out the boilerplate each company copies into every posting.

Five differences stand out.

1. You Make Other CSMs Better

Senior ads are 2.4 times more likely to ask you to mentor or coach other CSMs. 19% of senior ads mention it. 8% of mid-level ads do.

This was the biggest gap in the whole dataset. It also held when I looked only at companies that posted both levels, so it is not one company’s template.

Senior means your impact goes beyond your own book.

2. You Work at the Executive Level

43% of senior ads mention executive or C-level stakeholders. 34% of mid-level ads do.

Mid-level CSMs talk to admins and champions. Senior CSMs are expected to hold a room with a VP or a CFO, and to connect the product to their business goals.

3. You Speak in Retention Numbers

Senior ads mention NRR or GRR 1.7 times more often than mid-level ads.

That is a vocabulary shift. Senior CSMs are expected to talk about their book the way finance does: revenue kept, revenue grown.

4. You Own Fewer, Bigger Accounts

The median senior CSM manages 20 accounts. The median mid-level CSM manages 55.

Few ads state portfolio size, so treat this as a signal rather than a rule.

Senior is depth over volume. Fewer logos, more revenue on each, more complexity per account.

5. You Bring Five or More Years

78% of senior ads that state experience ask for five years or more. For mid-level ads, it is about half.

Experience matters. But look at items 1 to 4 again. None of them are about time served. They are about scope.

Do Certifications Help Senior CSMs?

This is one of the most common questions I get. So I checked.

Out of 373 senior CSM ads, a Customer Success certification appeared in only 2. Both came from the same company.

SuccessHACKER: zero.

Gainsight certification: zero.

PMP showed up in 17 ads, but from only 3 companies, mostly in technical or implementation-heavy roles.

So no, employers are not screening senior CSMs on certificates. They screen on the five things above.

A course can still help you learn. Just don’t expect it to carry your promotion case. If you are still deciding which one is worth your time, here is my take: best certifications for Customer Success Managers.

Your 90-Day Promotion Case

If you want the senior title, build the case before you ask for it.

Here is how I would use this data.

Days 1 to 30: Pick Your Proof

Choose three accounts where you can operate at the senior level.

• One with an executive you can get in front of.

• Another with a retention or expansion story.

• And one where a newer CSM needs help.

Days 31 to 60: Do the Senior Work

• Mentor one newer CSM on purpose. Run a weekly 20-minute session.

• Get one executive meeting per strategic account. Bring a business outcome instead of a product update.

• Report your book in NRR and GRR, even if nobody asks you to.

Days 61 to 90: Write It Down in Their Language

Map your wins to the words in senior job ads → coaching, executive alignment, retention, portfolio depth. Bring that one-page summary to your manager, and use the same words on your resume.

You are no longer asking for a title.

You are showing you already do the job.

Want Help Building Your Case?

If you are going for a senior role or a promotion this year, I can help you build the case, tighten your story, and prepare for the conversation. See my 1:1 coaching options here →

The executive-level work in this post is what paid members of The CS Café practice every week: exec updates, QBR narratives, renewal plans.

Paid members get the templates and scripts, plus direct email review before your update hits leadership. Upgrade to paid here →

Looking for your next job? Browse the senior Customer Success roles live on TopCSJobs. Before you apply, run your resume through WowThisCV to see how it reads against the job description.

Hakan, The CS Café

Wednesday edition, a free weekly read on what protects your accounts and your career.

Your customer’s best quarter can be your worst renewal.

Hiver is hiring a Senior CSM in the Bay Area. The job is to help support leaders automate workflows with AI. From the customer’s side, that means fewer agents doing the same work.

Now read it from yours.

If that customer pays per agent seat, every automation win shows up at renewal as a smaller contract. Nobody churns. The invoice just shrinks.

I checked how common this is.

Across 1,681 Customer Success listings on TopCSJobs (January to September 2026), 40.7% of Q3 roles used AI or automation language.

Fewer than 1 in 50 gave the CSM any responsibility for what that automation does to the customer’s team.

The vendor sells the shrink. Nobody in the account owns it.

The Seat Math Nobody Puts in the Forecast

Take a support platform priced per agent.

The customer runs 120 agents on a three-year deal. Their AI agent starts resolving a third of incoming tickets.

They lay off nobody. They stop backfilling. Attrition does the rest. By renewal, the team is 80 agents. The customer renews happily, at 80 seats.

That is a 33% contraction with zero conflict.

No one threatened to churn. No one opened a negotiation. Procurement simply counts heads and sends the number.

Meanwhile, your forecast still says 120. The renewal sat in the commit column all year. The contraction only appears the week the new seat count arrives, and by then the quarter is already gone.

This is what makes AI seat compression different from classic churn.

Every signal you track looks healthy. Output per agent goes up. The champion hits their efficiency target. The account looks like a success story right up to the invoice.

It is also a different risk from the customer who replaces you with an in-house tool, which I covered in The Churn You Are Calling Budget Is Often a Build.

Here, the customer stays and renews with you.

They just need fewer seats.

What 1,681 CS Job Listings Show

The AI talk lives in the company pitch, and the job itself rarely touches it.

Company descriptions, benefits and legal text made up 44% of the listing text I analyzed. That is where most of the automation language sat.

The few roles that do assign it to the CSM are explicit:

• An Intercom CSM role measures success by getting support teams to top automation rates with its AI agent.

• A ServiceNow role posted earlier this year made the CSM accountable for getting licensed AI agents deployed and producing outcomes.

• A ThoughtSpot role posted earlier this year had the CSM help Fortune 5000 customers deploy AI agents.

The second signal is pricing.

The share of CSM listings that make consumption part of the job nearly doubled this year. Explicit seat language barely registers.

Q1 2026 → 6.0% of 235 CS listings made consumption part of the role. Seat language appeared nowhere.

Q2 2026 → 8.2% of 692 listings. Seat language appeared in 1.0%.

Q3 2026 → 10.9% of 754 listings. Seat language appeared in 0.5%.

The shift holds when Salesforce is removed (6.0% to 11.6%) and within the same 53 companies hiring in both Q1 and Q3 (7.9% to 13.5%).

Some vendors now write both models into one job.

Anthropic CSM roles ask the CSM to manage underutilization across consumption-based API products and seat-based products in the same book.

Put the two signals together.

The vendors selling automation are moving their own CS teams toward consumption.

Most seat-based vendors still define the CSM role without mentioning the number that contracts.

How I measured this: the data comes from TopCSJobs, the CS job board I run, which pulls listings directly from employers' hiring systems. The sample covers 1,681 English-language CS listings from January to September 2026, with reposts and company boilerplate removed. Each figure was checked by hand on a random sample of matches. The customer-automation figure is an upper bound, and the consumption trend holds within the 53 companies hiring in both Q1 and Q3.

Three Places the Blind Spot Hides

1. The forecast

   Renewal forecasts roll the current seat count forward. Contraction gets entered by hand once procurement sends a number.

   By then it is a fact, and your options are gone.

2. The QBR

   Your customer presents their automation win in your business review. Ticket deflection is up. Handle time is down. You celebrate it with them.

   You are applauding the preview of your own downsell.

3. The champion

   The person who knows the headcount plan is often the person whose team is shrinking. They have every reason to keep it quiet. Some are protecting their team. Others are protecting their own role.

So the question that matters is simple.

Which accounts in your book will renew with fewer seats, and how many months do you have to change the conversation?

Most CS teams find out at the invoice.

The accounts that will renew smaller are already in your book.

Below, paid members find them this week and settle the seat conversation four months before renewal.

What changes this week:

• Monday morning → you know which accounts will shrink at renewal, ranked by exposure.

• Your next QBR → their automation win opens a pricing conversation you lead.

• Your next forecast call → you bring a seat number your VP can defend, before procurement sends theirs.

Read more

Ella Cullen, a technical CSM at PostHog, came from 7 years in sales with no computer science degree. Her main habit fits in one line.

When a customer asks a technical question, try to answer it yourself before you forward it to an engineer. Her full piece is here.

Many CS teams measure speed, and forwarding is the fastest move you have.

Here’s how to build the habit anyway.

Why Most CSMs Never Build the Habit

Look at what your team tracks → response times, resolution times, and SLA compliance.

Picture two CSMs getting the same question about why a customer’s data stopped syncing.

1. The first forwards it in 5 mins.

2. The second spends 30 mins reproducing the issue, then escalates with a likely cause.

On the dashboard, the first one looks better for weeks. The second one’s payoff shows up later, in fewer repeat tickets and in engineers who answer her messages first.

The metric decides the habit.

To become technical on a team that rewards speed, you need a method that protects your numbers while you learn.

The Time-Boxed Escalation

Give every technical question a fixed window before you escalate. 30 mins is a reasonable starting point. Adjust it to your SLA.

Inside the window:

1. Reply to the customer right away to confirm you’re on it. That covers your first-response SLA and buys you the window.

2. Reproduce the issue.

3. Check the docs and internal knowledge base.

4. Look at error messages, logs, the browser console, and integration settings.

5. Write down your best guess at the cause.

Many of the hardest issues live on the customer’s side, where your monitoring can’t see them. The SOLVE framework covers how to find those.

If the window runs out, escalate anyway, with what you tried, what you ruled out, and your best guess.

Every escalation still teaches you something.

Engineers tend to notice the difference, and some will start pulling you into the fix. That’s where most of the learning happens.

Keep a Resolution Log

Log every technical question in one row → the question, what you tried, whether you solved it, and what the fix taught you. It takes two minutes per row.

After a quarter, patterns appear.

The same few problems keep coming up. Those are what you should learn next. Your customers pick your lessons for you.

The log is also your proof.

“I’ve become more technical” is hard to show a manager. A quarter of logged questions, showing how many you closed without engineering, is easy to show.

Use it to ask for one change: have technical questions routed to you first, or get access to the tools engineers use to debug.

What Technical CSM Interviews Actually Test

Technical CSM interviews often include a troubleshooting round. You either walk through a broken setup live or describe a technical problem you solved.

There are two easy ways to mess it up. One is escalating too early in the scenario. The other is bluffing through details you don’t know.

Your log protects you from both. Pick three stories and tell each one the same way:

1. The issue, from the customer’s point of view.

2. What you checked first, and why.

3. What you found.

4. When you brought in engineering, and what you handed them.

Here’s a sample answer:

"A customer's leadership dashboard stopped updating two days before their board meeting. The only recent change was their new single sign-on setup, so I started there. I reproduced it in a test account and found their data connection had lost access when their user permissions changed. I brought in engineering with the logs and the likely cause. They confirmed it the same day, the customer had their dashboard back before the meeting, and I wrote it up so the next CSM could fix it in minutes."

Step four is the one that sets you apart.

Explaining when and why you escalated shows judgment, and judgment is what the hiring manager is testing.

Put the same proof on your resume.

One bullet does it, for example: “Resolved integration and data-sync issues directly, escalating only with a diagnosed cause.”

WowThisCV can tailor your resume around this for the roles you’re targeting.

The Habit Starts With One Question

Ella’s story shows the path is open without an engineering degree. What's tough is building it inside your team's metrics.

So start small.

Take one technical question, set the timer, and write down what you find.

• Want to go further?

  The Customer Success Engineer guide maps the path. TopCSJobs lists live technical CSM, CSE, and TAM roles.

• Interviewing for a technical CSM role?

  My async Interview Intensive gets you ready for every round, including the troubleshooting round, in 7 days.

  Not sure it fits? Send me your resume and target roles, and I'll tell you. See coaching options →

• Already in the role, or starting soon?

  Walk into your first renewal with a system instead of a guess. Paid members get the renewal and QBR operating systems, plug-and-play templates, and scripts for the tough conversations. Upgrade to paid →

Hakan, The CS Café

Wednesday edition, a free weekly read on what protects your accounts and your career.

But most of your customers still use the product the way they did at go-live.

That gap is sitting in your book right now, and nobody owns it.

Onboarding Used to Have an End Date

For years, onboarding was a phase. Kickoff, setup, training, first value, hand to the CSM. Done.

That model assumed the product stayed roughly the same after go-live.

It no longer does.

AI-first companies ship new agents, integrations, and workflows every few weeks. The product a customer bought is not the product they have three months later.

One fast-shipping AI company now measures its CSMs on a single number: the share of customers activated on new capabilities within one quarter of release.

Read that again.

Onboarding is no longer a one-time step. It is a loop that restarts with every release.

Nobody Owns the Distance Between Released and Used

Here is how most teams handle a release today.

1. Product ships it.

2. Marketing announces it.

3. Release notes go out as one email to the whole customer base.

Then everyone moves on.

The customer who needed that feature most never reads the email. The champion who would have loved it is buried in their own quarter. The value you shipped stays on your side of the table.

Product thinks their job ended at launch. Marketing thinks their job ended at the announcement. The CSM thinks it is marketing’s job.

So the distance between “released” and “used” grows by a little every month, inside every account.

I checked every Customer Success role added to TopCSJobs between April and September: 1,530 unique roles.

About 1 in 10 asks the CSM to drive adoption of new features or releases. It’s already in the job.

One posting puts it in simple terms: the CSM delivers ongoing training “that keeps value visible” across the client lifecycle.

Not one uses the words "re-onboarding," "continuous onboarding," or "ongoing onboarding." Fewer than 1 in 100 even mention ongoing training or enablement for customers.

The work is expected. Nobody has named it, and nobody has built a process for it.

Where It Shows Up: The Renewal

You feel this gap at this one moment → the renewal call.

The customer’s finance lead asks what they are actually getting for the price. Your champion says, “honestly, we only use a fraction of it.”

A year of shipped value never made it into their story.

The price went up with the product, and the usage stayed at go-live. That is the conversation where discounts and downgrades start.

Three Signs the Gap Is Live in Your Book

1. Your release notes go out as one email to everyone, with no account-level follow-up.

2. Your health score tracks logins and seats, and ignores whether accounts touch anything shipped in the last two quarters.

3. Your QBR deck shows the same features it showed last year.

If two of those are true, your customers are paying for a product they have never met.

Every release you ship without re-onboarding widens the gap you will be asked to explain at renewal.

Today I’m sharing the system I’d put in place to close that gap before your next renewal.

Most CSMs walk into that renewal call with a usage chart. The ones who hold the price walk in with something else.

Paid members build it one release at a time, starting with the accounts that matter, 20 minutes each.

Here is how you can run it this week →

Read more

Discover why the most successful organizations won't be those that replace people with AI, but those that use AI to elevate human capability. Drawing on insights from industry leaders, this white paper examines how organizations can balance AI-driven efficiency with the empathy and judgment that build lasting customer trust.

Download your free copy now →

The Role Most Candidates Scroll Past

Many senior candidates filter out contract roles before they read the scope.

I understand why.

A contract can feel like a step backward when you’ve spent years building toward a permanent senior title.

A senior contract at the right company can move your career further in 12 months than a permanent role where you stop learning.

What matters is knowing which kind of contract you’re looking at.

By the end of today’s post, you’ll be able to tell in one conversation.

Take Hootsuite.

This week I flagged one of its roles on the TopCSJobs LinkedIn page: a Bilingual Senior Customer Success Manager in Canada on a 12-month contract, with a base range of $80,000 to $112,000 CAD plus variable pay.

The scope matches any senior enterprise CSM job: a book of Fortune 1000-sized customers, Mutual Account Plans, success reviews, and a Personal Net Renewal Rate target.

Everything a permanent Senior CSM does is in there. The only difference is the end date.

Why Companies Hire Senior CSMs on Contract

Three reasons come up again and again.

1. Leave cover

   Someone on the team is going on leave, and the company needs their book covered.

   12-month terms often line up with the length of a parental leave. Asana's fixed-term CSM role for the UK and Ireland, which TopCSJobs tracked in the last 90 days, was exactly that: a 12-month parental leave cover.

   In this case the seat has an owner who is coming back, so your conversion depends on whether new headcount opens while you’re there.

2. Headcount test

   The company wants to test a new segment, region, or language market before committing to permanent headcount.

   If you prove the demand, you become the business case for the permanent role. This setup often gives you the best odds.

3. Budget flexibility

   Finance approved the spend but not the headcount.

   Your future depends on the next budget cycle, so ask when that decision gets made and who makes it.

   The contract itself tells you very little. The reason behind it tells you most of what you need to know.

What TopCSJobs Data Shows

I track Customer Success hiring every day on TopCSJobs, which pulls listings directly from employers' own hiring systems and is live in the Ashby Marketplace. Ashby is the hiring platform behind companies like Ramp, Zapier, and Perplexity.

I scanned the title and full job description of all 1,129 CS roles posted over the last 90 days, including the ones that have since closed.

Six were contract or fixed-term positions, at companies like Asana and Upguard. All six were mid-level roles. Zero senior individual-contributor roles were advertised as contracts.

Contract roles are rare in Customer Success, and at the senior level they barely exist.

So when one shows up at a company like Hootsuite, most candidates have never had to evaluate one before. Knowing the right questions to ask is your edge.

If you’re weighing a contract, compare it against the permanent roles open at the same level right now. Browse senior CS jobs on TopCSJobs →

Four Questions to Ask Before You Say Yes

Ask these in the recruiter screen or the hiring manager interview.

Asking them well also signals seniority, because it shows you think about a role the way a hiring manager does.

1. What Is This Contract Covering?

A strong answer is specific: “We’re testing demand in a new market before we open permanent roles.”

A weak answer is vague, like “we just want some flexibility right now.” A vague answer often means nobody has a plan for month 13.

2. What Happened to the Last Person in a Contract Role Here?

A strong answer names outcomes: “Two of our last three contractors converted.”

A weak answer is “we haven’t really tracked that.” Past behavior is the best preview of how your own term will end.

3. Which Accounts Will I Own, and Will I Carry a Renewal Number?

A strong answer describes a named book with renewal dates that fall inside your 12 months.

A weak answer sounds like “you’ll support the team with whatever comes up.”

You want ownership, because ownership is what you’ll be able to prove later. The Hootsuite role passes this test on paper, since Personal Net Renewal Rate is one of its core metrics.

4. How Does Variable Comp Work If the Contract Ends Mid-Cycle?

A strong answer is a prorated payout on renewals you closed. A weak answer is a bonus paid only to people still employed on the payout date.

On a senior role, variable pay can be a big share of the package, so get this in writing.

The Hootsuite posting is a good example. Variable pay runs through the company’s Sales Compensation Program, with details shared “during the interview process.”

That’s normal. On a 12-month contract, it’s also the exact moment to ask what happens to a payout if your term ends before a renewal closes.

What You Should Walk Away With After 12 Months

Most people frame the decision as permanent versus contract. A more useful question is this: what will I leave with if the contract ends on schedule?

Look for three kinds of evidence:

• A renewal you owned end to end, from forecast to close.

• An enterprise logo and a portfolio tier you can name on your CV.

• A named executive sponsor, on the customer side or internally, who will vouch for you.

If the role can’t give you at least two of these, it’s a weak deal at any pay rate.

If it gives you all three, you’ll walk into your next interview with stronger proof than many candidates who stayed in a permanent seat for years.

Before you accept, read the offer line by line. I broke down how in how to read a customer success job offer.

If you take the role, the renewal is where you earn your evidence.

Paid members of The CS Café get the renewal operating system to run renewals from forecast to close, with the templates and scripts included. See what’s in the paid plan →

Red Flags That Make a Contract a Bad Trade

Walk away, or at least negotiate hard, if you see any of these:

• Support overflow under a CSM title

  There’s no book and no renewals, just tickets. You’ll leave with nothing you can prove.

• Variable pay that disappears at the end date

  If the renewals you worked on close after you leave, someone else gets paid for your work.

• No seat in the renewal conversation

  If the AE owns renewals end to end, you’re doing adoption work without the commercial evidence hiring managers now screen for.

• The same seat run on back-to-back contracts

  Check LinkedIn for people who held the role before you. A string of 12-month tenures tells you how it usually ends.

• No review date

  If nobody can tell you when the conversion decision gets made, nobody is planning to make it.

Pay on contract roles varies more than most people expect, and it depends heavily on the company and its stage.

To benchmark an offer, check the range against the TopCSJobs CS salary database, then read why CSM pay varies so much.

How to Frame a Contract Role on Your CV Later

List it like any other role, with the contract noted clearly:

Senior Customer Success Manager (12-month contract), Company
Owned X enterprise accounts worth $Y ARR. Renewed X of Y accounts in term, including one named win.

In interviews, give it one confident sentence and move on: “I took a 12-month enterprise contract to get this segment or market experience, and I renewed X of Y accounts.”

A contract only looks like a gap when the line underneath it is empty. Fill that line with outcomes, and recruiters will read the role as a deliberate move.

Key Takeaway

The next time you see “contract” in a senior CS job title, read the scope before you scroll past.

Ask the four questions. Then decide based on what you’ll walk away with, because that’s what your next employer will ask about.

Interviewing for a senior CS role right now? I do async career coaching, so it fits around your search and timeline. We build your story bank with the Interview Intensive and sharpen your answers for every round in 7 days, with direct feedback.

Not sure which package fits? Send me your resume and target roles, and I’ll tell you. See coaching options →

Already in the role, or starting soon? Walk into your first renewal with a system instead of a guess. Paid members get the renewal and QBR operating systems, plug-and-play templates, and scripts for the hard conversations. Upgrade to paid →

Hakan, The CS Café

Wednesday edition, a free weekly read on what protects your accounts and your career.

Share

I read live CS job postings every week for the TopCSJobs board. The shift is crystal clear.

The title still says CSM. The work underneath it does not match anymore.

One person used to do all of it. Now companies are splitting that job up and hiring specialists for the pieces.

The split is happening on four fronts: the work itself, the industry, the location, and the leader’s mandate.

Here is each one, straight from the roles going live now.

Function: Technical Success Is Becoming Its Own Career

A company posts three CS roles, and the third says it all: a Customer Success Architect, sitting next to two standard CSMs.

The CSM owns the relationship and the outcomes.

The Architect owns the technical layer, data modeling, query optimization, keeping the deployed solution healthy over quarters.

The deep technical work is splitting out of the CSM role into its own specialization.

A generalist covers it until an account gets complex enough that “figure it out” stops holding.

By then the risk is already in the number.

Vertical: Domain Fluency Is Beating General SaaS CS

A legal-tech vendor hires a Senior CSM whose users are attorneys.

The whole role leans on change management, because the billable hour fights adoption, and every minute learning a tool is a minute not billed.

A campus-recruiting platform hires an Enterprise CSM whose customers run on the academic calendar, where value concentrates in recruiting seasons.

In both, knowing the customer’s world matters more than knowing SaaS CS.

A generalist learns that cycle from scratch and loses a quarter doing it.

Geography: Customer Success Is Going Global

A US SaaS company posts a CSM role in LATAM. Same core job, own renewals, drive engagement, executive communication, at a fraction of US comp.

CS is following engineering and support offshore.

The talent pool is no longer only where the company is headquartered, and the accounts a generalist used to cover at full US cost are exactly the ones moving.

For what the US end of that pay band now looks like, I read 658 live CS job descriptions here.

Mandate: The Leader’s Job Is Being Rewritten

A company hires a Director of CS and asks for an “AI-forward mindset.”

When you read the requirements, the phrase is doing heavy lifting.

The role expects them to rebuild how the whole team operates: automated health scoring, AI-driven workflows, more customers covered without more headcount.

Another posts a Senior Manager to build a CS function from zero in regulated fintech.

The bar for a CS leader is no longer coaching a team and running playbooks. It is re-engineering the operating model itself.

What the Map Says

Read the four axes together and they say one thing. The generalist seat is the one being squeezed.

The roles that are created reward a specific edge. The roles being cut are the ones that could be anyone.

For a leader, that lands closer to home than a career trend.

The team you built for generalists is now covering four jobs with one profile, and the market is pricing each of those jobs separately.

Today I walk you through which axis your book is straining against, and how to rebuild the team around it without dropping coverage.

Paid members get the full system: the audit, the split, and the comp structure that keeps your new specialist from leaving.

Here is how you can run it this week.

Read more

As your accounts scale from your first customers to a global base, Crisp scales with you. One platform that supports enterprise and worldwide capacity, so you keep the same system instead of a rip-and-replace every few years. Free trial on us →

You know your base salary cold.

But if I asked what your equity is worth, could you tell me?

Most CSMs can’t. I’ve seen people with ten years in the field go blank on this. They don’t know which kind of equity they hold, what it rests on, or whether it’s worth anything at all.

The headline number on your offer is the least reliable one on the page.

The gap between what an offer looks like and what it pays you is almost always hiding in the equity.

Your Comp Has Three Layers, and You Only Read One

A CS offer has three parts: base, variable, and equity.

Base is the number you can trust. It shows up every month and it does what it says.

The other two are where offers diverge from reality.

I wrote about the variable side in the Datadog breakdown, where the split and the metrics behind it decide whether the on-target number is real.

Equity is the layer most people miss, and it is often the one companies lean on hardest to make an offer look big.

Options and RSUs Are Not the Same Thing

The first thing to know is which kind of equity you were actually offered, because the two behave differently.

• Options give you the right to buy shares later at a fixed price, called the strike price.

  They are worth something only if the company’s share price climbs above that strike, and worth nothing if it does not.

• RSUs are shares granted to you outright as they vest, so they hold value as long as the company does.

A big options number and a big RSU number are not comparable, and treating them as the same figure is how people overvalue an offer.

If you cannot tell from your paperwork which one you hold, that is the first question to ask.

Why the Equity Headline Lies

Say the offer includes equity described as worth a large sum. That figure rests on assumptions that may not hold.

It depends on 4 things:

1. The current price per share, which for a private company is a number set at the last funding round and not a market price.

2. The total share count, which decides what your grant is actually a slice of.

3. The vesting schedule, often four years with a one-year cliff, meaning you get nothing if you leave inside the first year.

4. The distance to a liquidity event, because equity you cannot sell is not money in your pocket, it is a claim that pays out only if and when the company exits.

Change any one of those and the headline number moves a lot.

The figure on the offer letter is the most optimistic reading of all of them at once.

Company Stage Changes the Whole Picture

This is where the offer’s shape depends on where the company sits.

• At an early-stage startup, comp leans on equity, and that equity is a lottery ticket.

  The base is often lower, the upside is real but unlikely, and you are being paid partly in the hope of an exit.

• As a company scales to become a global, late-stage, or public footing, the mix flips.

  Base rises, equity becomes RSUs with a knowable value, and the whole package gets more predictable and less of a gamble.

Neither is better in the abstract.

They are different bets, and the offer only makes sense once you know which bet you are being asked to take.

A large equity figure at a seed-stage company and the same figure at a public one are two completely different offers wearing the same number.

What to Ask Before You Sign

Five questions turn the black box into something you can read.

Ask:

1. Which type of equity it is, options or RSUs.

2. The strike price and the current price per share.

3. The total shares outstanding, so you know what fraction you hold.

4. The vesting schedule and the cliff.

5. The company’s own view on timeline to a liquidity event, knowing the answer is a hope, not a promise.

You will not always get clean answers, and how a company responds to these questions tells you something too.

A team that treats them as reasonable is one that respects what it is offering you.

If you want a second read before you respond, I'll go through the offer with you and help you avoid leaving money on the table. Book your coaching →

Before You Sign, Remember This

The base is the number you can trust.

Read the variable for whether the on-target figure is real, and read the equity hardest of all, because that is where an offer inflates.

Know which kind you hold, what it rests on, and which bet the company’s stage is asking you to make.

For the fuller picture on what CS roles pay and how to negotiate the whole package, the compensation guide will help you dig into it.

If you’re looking for your next offer, the strongest CS roles are on the TopCSJobs board.

-Hakan, The CS Café

Wednesday edition, a free weekly read on what protects your accounts and your career.

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 →

Every support reply shapes whether a customer stays. Crisp brings AI, an all-in-one inbox, and CRM together, so every answer is fast and consistent, and the accounts you’re working to renew stay happy. Free trial on us →

You feel it before you can prove it.

The renewal you always ran gets handed to someone else. You are looped in later instead of asked first. A second name shows up on your biggest account.

Nothing official has happened, and that is what makes it hard to act on.

Most people do one of two things here.

They wait for it to get clearer, or they open a browser and start job hunting. Both give away the one advantage you still hold: time, while the accounts are still yours.

You have more leverage right now than you will at any point after the decision is made.

This is how to use it.

You Already Know the Signs. This Is the Response.

You have probably read similar signals at some point already.

The meetings you are left out of, the work reassigned, the manager who stops bringing you the tough accounts. I wrote about reading those signals in a separate piece, so I will not repeat it today.

What matters is what you need to do next.

So here is a 30-day plan I built for a CSM who still holds the accounts and still has time to change the story.

Week 1: Make Your Value Legible

The reason they sideline you is rarely about your work.

It is that the work is invisible to the people deciding. When leadership cannot see what you carry, they assume it is carryable by anyone else.

→ Fix the visibility first.

Start a short weekly account note to your manager. Three lines per key account:

• where the renewal stands,

• the risk you are managing,

• the next move you are making.

Your goal is to become the name leadership attaches to the renewal number, so that moving you off the account feels like moving money.

Don’t think about it like self-promotion. Consider it as putting your judgment on the record where the decision gets made.

If you want the sharper version of this, making your value legible all the way up to finance, I wrote the CFO-facing version here.

Week 2: Re-Anchor to the Accounts That Matter

Sidelining works by drift.

You get pulled toward the low-stakes accounts while the strategic ones migrate to someone else. So your goal is to reverse the drift, on purpose.

Pick your two highest-value accounts and get back in the room on both. Ask for the next executive conversation. Volunteer for the renewal that leadership is watching.

Proximity to revenue is protection, because the person visibly steering the biggest renewal is the hardest one to remove.

Week 3: Land One Visible Win

Nothing changes a narrative faster than a result they can’t ignore.

• An expansion conversation you opened.

• A save on an account everyone assumed was gone.

• An executive meeting you set up and ran well.

One concrete win, seen by the right people, does more than a month of careful positioning.

Aim for a single outcome you can point to by name and make sure your manager hears about it from you first.

Week 4: Have the Direct Conversation

By now you have evidence instead of anxiety, and that changes the whole tone of the conversation.

Ask your manager for a direct read on where you stand. Bring the account notes, the wins, the renewals you are steering.

Walk in with a record, not a worry.

You are not asking for reassurance. You are showing what leadership would lose, and asking what they want from you next.

Sometimes that conversation resets the relationship. Good.

But it can also tell you the decision is already made, and you leave on your terms with your best accounts fresh on your resume.

Either way you stop guessing.

And if it’s time to go, the strongest CS roles are on the board.

Where This Leaves You

Being sidelined is a slow process, which means you have time to stop it.

Make your value visible, get back on the accounts that matter, land one win in the open, then have the honest conversation with a record behind you.

The version of you that does this for 30 days is in a stronger position whether you stay or go.

Hakan, The CS Café. Wednesday edition, a free weekly read on what protects your accounts and your career.

More than 1/3 of enterprises have already replaced at least one SaaS tool with something they built in-house, and most plan to build more this year.

You hear it more and more.

A customer goes silent for a few months, and at renewal they tell you they are consolidating tools and building the workflow in-house.

You log it as a budget loss. Leadership asks what happened. The decision was made a quarter ago, and nobody in CS was in the room.

The churn you are calling budget is often a build. And a build you never priced is a renewal you already lost.

I covered the pricing model in a previous post: Outcome-Based Pricing Is Killing The SaaS Renewal Model.

Today I’m focusing on the build side.

The Build Decision Leaves Fingerprints

The customer does not announce that they are building your tool themselves.

They scope it while your health score still reads green. The signals look like ordinary account activity, which is why most teams read right past them.

Here are the 4 tells that an account is drifting toward replacing you, while there is still a quarter left to change the outcome.

1. The technical buyer starts asking about export and API access

   Framed as a data-portability question, it is the first step of a migration off you. Nobody scopes an exit they are not considering.

2. The workflow you own gets described as “just a” something

   When a customer flattens your product into a generic noun, they have already decided it is commodity.

   Commodity is what teams rebuild.

3. The account goes silent right after an internal AI mandate

   A top-down “find what we can build ourselves” directive lands, and your champion stops replying within the week.

   That is evaluation running in the background.

4. The conversation shifts from outcomes to cost per seat

   When the champion moves from “what can this do” to “what are we paying,” procurement already has the file, and procurement compares you against a build estimate you have never seen.

If two or more of those are live in your book, you have a build-risk account and a clock.

What you do in the next 90 days decides whether the renewal is a confirmation or a fight you walk into blind.

The system that walks you in with the build already priced is below.

Paid members get the full operating system. You walk in with the comparison already made and the internal case for staying already written in their own language. The QBR stops being a value pitch and becomes the moment the customer talks themselves out of the build.

Here is how you can run it this week.

Read more

The job is part account strategist, part product expert, part commercial partner to the customer. It sits inside one of the largest CS organizations in software, and the pay reflects that.

Here is the first thing worth knowing before you read a single salary number.

Salesforce does not hire Customer Success at the entry level. It hires experienced managers and above, almost always tied to a specific product or industry. If you are looking for your first CS role, this is rarely the door.

If you already run accounts and want to know what the ceiling looks like, this is one of the clearest maps in the industry.

This page covers what Salesforce pays across the CS ladder, what the role actually involves, and how the path runs from manager to the senior leadership roles now built around Agentforce.

What Salesforce Pays a Customer Success Manager

Salesforce CS compensation tracks its internal level structure. The public benchmarks below reflect United States base ranges for 2026. Total compensation runs higher once variable pay, bonus, and equity are added, and it varies by cloud, segment, and location.

• Manager level (Customer Success Manager). The core of the CS organization. This is where most Salesforce CS hiring happens.

• Senior level (Senior Customer Success Manager, Senior Manager). More complex accounts, larger books, or a named product or vertical specialization.

• Director. Owns a team and a segment.

• Vice President. The top of the ladder, now shaped heavily by the shift to agentic customer success.

A note on how to read these. Salesforce CS roles carry a variable component tied to renewal and expansion outcomes, so base alone understates the number. When you compare against a public figure, check whether it is base or total compensation before you draw a conclusion. The two are often confused, and the gap between them at Salesforce is wide.

For a broader read on whether your own number is where it should be, see How to Know If You’re Underpaid in Customer Success.

What Salesforce Is Actually Hiring For

This is where the public salary sites go quiet, and where the picture gets useful.

Salesforce hires Customer Success almost entirely at manager level and above. The pattern is consistent: manager and senior-manager roles make up the bulk of open positions, with a smaller layer of director and VP roles above them. Entry-level CS postings are effectively absent. If you are targeting Salesforce, you are competing as an experienced practitioner, not as a career starter.

The roles are specialized in two directions at once. By product: Marketing Cloud, MuleSoft, Tableau, Commerce Cloud, Sales and Service Clouds, Slack, Informatica. And by vertical: healthcare and life sciences, public sector, financial services, higher education, manufacturing. A generic CS background is rarely enough. Salesforce wants a CSM who already knows the specific product or the specific industry the account lives in. That specialization is the real entry requirement, more than years of experience alone.

Location matters too, and the answer will disappoint remote-only searchers. Salesforce CS is a hybrid function. Roles cluster around its major hubs, in the United States and across Europe, India, and Asia Pacific, and nearly all expect time in an office. Remote Salesforce CS roles exist but they are the rare exception, not the norm.

You can see every Salesforce Customer Success role open right now, with its level, product focus, and location, on the TopCSJobs board here. The board updates as roles open and close, so it is always the current picture rather than a snapshot.

The Salesforce CS Career Path

Because Salesforce hires at manager level and up, the path through its CS organization is a climb between bands rather than an entry ramp.

You typically arrive as a Customer Success Manager, already carrying account experience and a product or industry specialization. From there the move to Senior Manager comes with larger or more complex accounts and, often, a named cloud or vertical you own. Director means a team and a segment. Above that sits the VP layer.

The top of this ladder is worth watching closely, because it is changing fast. Salesforce’s most senior CS roles now center on Agentforce and agentic customer success, and they demand a fundamentally different skill set than the CSM job that feeds them. Value engineering, platform telemetry fluency, and commercial ownership are becoming table stakes at the top, not nice-to-haves. I broke down exactly what those roles now require, and where most CS leaders are building the wrong skills for them, in this analysis of a Salesforce leadership role that pays up to $350K.

The practical takeaway: the CSM role gets you in, but the specialization you build inside it decides how far up you go. A CSM who owns a product deeply, learns to read an account from the data, and speaks the commercial language of renewal and expansion is the one who moves toward the director and VP roles. A CSM who stays generalist tends to stay at the manager band.

The Bottom Line

Salesforce pays well for Customer Success, but it pays for depth. It hires managers and above, it wants product or industry specialization, and it expects you in an office more days than not. The salary follows the level, and the level follows the specialization you can prove.

If you are mapping a move into Salesforce or a company like it, the fastest lever is not another year of general CS experience. It is owning a specific product or vertical well enough that a hiring manager sees a specialist, not a generalist.

You can browse the companies hiring CSMs right now, Salesforce among them, to see where the real demand sits this quarter.

Know a CSM eyeing a move to Salesforce? Forward this to them.

Crisp’s AI answers the routine support questions, so your CSMs aren’t stuck on tickets and can stay on the accounts up for renewal. Your team handles the conversations that actually need a person. Free trial on us →

Datadog has 24 live Customer Success roles open right now.

On the TopCSJobs board, where we track 613 live CS roles across every major tech company, that puts Datadog second, behind only Salesforce, and ahead of Harvey, Samsara, MongoDB, and Anthropic.

A company hiring CS that hard raises one question for anyone in the field.

What does the role actually pay?

The Real Salary Range

The public numbers disagree, and one hero figure would point you the wrong way.

• Levels.fyi puts total compensation for a Datadog CSM at a median near $105,000, with most packages landing between $120,000 and $142,000 once stock and bonus are counted.

• RepVue, which breaks out the commercial mechanics, reports base salary of $85,000 to $100,000 and on-target earnings of $100,000 to $120,000, with top performers reaching $130,000 to $150,000.

• Glassdoor’s estimates run higher and wider, which is what happens when a sample pools different levels and cities.

If you are looking at Datadog’s Dublin roles rather than a US seat, expect euro bands in the low-to-mid €70,000s for base, with OTE into the low €100,000s for a strong year.

The number that matters is the one attached to a specific level and a specific city. Treat everything else as a map, not a quote.

The Pay Structure Tells You What the Job Actually Is

Look past the total and at how it is built.

Datadog CSMs are paid on roughly an 82/18 split.

Base salary carries most of it, and the variable rides on retention and expansion: net revenue retention, renewal rate, and the ARR you add through upsell and cross-sell.

That structure is a job description in disguise.

Datadog sells on consumption. Customers pay for what they use.

So growth comes from customers using more, and the variable pay is wired to that same motion.

You get measured on whether accounts expand, renew, and consume, which are the exact metrics a strong CSM already lives in.

A support-flavored CS role pays you to keep people happy. This one pays you to grow revenue you can name.

Read the split before you read the total, because it tells you which job you are interviewing for.

Before You Take an Offer Like This, Pressure-Test the Variable

An 82/18 split looks clean on a slide.

The 18 is where offers drift from reality, and 4 questions decide whether that variable is real money.

1. Start with the quota.

   Ask for the expansion or NRR target in dollars, not percentages, so you can judge whether it is reachable.

2. Then ask the attainment rate, meaning what share of CSMs actually hit target last year.

   If almost nobody hits target, that variable is not real money.

3. Ask whether the plan caps out, because many stop paying accelerators past 110 or 120 percent and quietly limit what a great year is worth.

4. Last, ask how expansion gets credited.

   If sales owns the upsell, you may carry the number without holding the lever that moves it.

Get those four answers in writing before you sign. If you want a second read on an offer before you respond, I'll review it with you →

Where Datadog’s Roles Sit, and What Else Is Open

About 7/10 roles on the board sit at the mid CSM level, with senior CSM next.

2/3 of CS roles are onsite right now, so filter early if location decides it for you. You can see Datadog’s 24 current openings and their exact levels on my board.

Datadog is one name. The board added 84 CS roles in the last 7 days alone.

Before you apply, make sure your resume clears the ATS filter. WowThisCV checks it against what CS hiring teams filter for.

The Takeaway

Datadog is hiring CS harder than almost any company on the board, and the pay reflects a role built around expansion.

Read the split before the total, pressure-test the variable, and you will know which job you are signing up for before you sign.

Hakan, The CS Café

Related reading:

• Companies Hiring Customer Success Managers Right Now (2026)

• Microsoft Customer Success Account Manager: Salary & Path

• CSM Compensation Guide 2026: Salaries, Splits & Negotiation

Made in the kickoff, filled with dates nobody owns, never opened again until someone needs a screenshot for a QBR. The customer never touches it. You maintain it alone.

By renewal, it is a dead file.

The mutual action plans that protect a renewal are different.

They are built with someone who can commit their side, kept alive by both parties, and read as a risk signal the moment they stall.

Today I cover both: what a MAP is, when it earns its place, and the system that turns it from a decorative doc into the thing that moves the renewal.

What Is a Mutual Action Plan?

A Mutual Action Plan (MAP) is a shared, living document that maps the steps, owners, and dates both your team and the customer must hit to reach an agreed outcome, whether that outcome is a clean onboarding, a renewal, or an expansion.

The word that matters is mutual.

A plan only your side owns is a project plan. A MAP assigns action to the customer too, and holds them to it.

MAP vs Success Plan vs Project Plan

The three get used, and they do different jobs.

A success plan defines the customer’s desired outcomes and how your product gets them there.

It is the strategy. A project plan tracks your team’s delivery tasks. It is your side’s execution.

A MAP sits between them and adds the one thing neither guarantees: named customer-side owners with dates, so the work that depends on them stops being invisible.

→ Run a success plan for the why.

→ Run a MAP for the “who does what by when” across both sides.

When a Mutual Action Plan Is Worth Building

A MAP is overhead on a simple account and oxygen on a complex one.

Build one when the outcome depends on the customer doing real work, a phased onboarding, a technical integration, a renewal with open risk, or an expansion with multiple stakeholders.

Skip it where the path is short and self-serve.

The test is simple: if their side has to act for you to succeed, and more than one person is involved, you need a MAP.

Why Most Mutual Action Plans Fail

Three failures show up again and again, and they are the reason your last MAP died.

It was built with the wrong person.

Most MAPs get created with the day-to-day contact, the one who joins every call and can commit none of their own organization. They nod at the plan and cannot move it.

It was frozen on day one. The MAP got written once at kickoff, shared as a static file, and never updated. A plan that does not change is a plan nobody is running.

You owned it alone. The document lived on your side, in your tool, updated only by you. The customer never opened it, never owned a line, and felt none of it.

A plan one party maintains is everything but mutual. It is a to-do list you cc them on.

Recognize your own MAP in any of those, and the renewal it was supposed to protect is exposed.

This is the system you can run this week, and it sits on one workbook.

Pick the right owner, keep the plan alive on both sides, and read a stalling MAP as renewal risk in one place, before renewal season starts.

Two ways to get it:

1. Subscribe to The CS Café → $25/mo. Every system I publish, this MAP workbook included, the full archive, and direct email replies. A straight answer when you have a career question, and a second set of eyes on a renewal plan, a QBR narrative, or an exec update before it reaches leadership. This is the one to take.

2. Standalone, $49. One download, no subscription. Buy the MAP kit →

Read more

Now the posting for your own role says Technical CSM, and half the tasks on your plate belong to teams that no longer exist.

The role keeps absorbing whatever nobody else wants to own, and the title keeps changing under you.

Most people in customer success see the hottest job in tech right now as an engineering story and stop there. It is the next chapter of the job you already do.

The question for you is simple.

Do you move up this curve, or do you get restructured under it?

The Shift Is Real

The numbers are not subtle.

Forward Deployed Engineers went from a title most recruiters could not define to the fastest-growing role in tech.

Job postings grew more than 700% year over year into early 2026, and by some counts past 1,000%.

Palantir invented the model. OpenAI, Anthropic, Google, and Databricks are hiring for it at scale.

The money tells you how serious this is.

Total comp runs from roughly $300K into the low seven figures at the top, with senior people at the frontier labs clearing well past what a CSM earns for the same customer.

Then the giants moved.

• AWS announced a billion-dollar organization built around the title.

• Microsoft launched a business worth several billion to embed thousands of these people directly inside customers.

• Salesforce committed to hiring them by the thousand. The pool cannot keep up.

There are roughly 17,000 forward deployed engineers in the United States, and only a fraction have the full profile companies actually want.

Andela CEO Carrol Chang captured the shift in three words: FDEs, not FTEs.

The first step up that curve is becoming a technical CSM.

Read What the Person Who Built This Field Says Next

Nick Mehta built the customer success category at Gainsight. When he talks about where the role is heading, it is worth stopping.

His read is that the forward deployed engineer is potentially the next evolution of customer success.

The reason is the gap that always limited the CSM.

A CSM could advise the customer on what to do. The FDE goes in and makes it work in their environment, configures it, adjusts it, ships the outcome.

That reframes the whole panic. The shift toward Technical CSM stops being a threat to route around.

It becomes a direction to move in.

What Transfers, and What Fades

You already own half the profile.

Look at how an FDE actually spends the week. Close to half of it is customer-facing. Discovery calls, on-site work, design reviews.

One of the top things companies screen for is whether you can run a discovery conversation without a sales script.

That is a customer success skill. You have been doing it for years.

In his interview with Ivory Tang on The Last Mile Podcast, Nick makes the same point about where the value sits now.

What earns the premium is deep curiosity about the customer’s business and the instinct to walk in with a hypothesis.

The generic version of the job, being the pleasant relationship-holder who routes the customer to whoever can actually help, is a weaker hand every quarter.

"What is really valuable now is, oh my gosh, that person gets my business." -Nick Mehta

So the honest inventory looks like this.

Discovery, reading the business, holding the room, owning the outcome carry straight over.

Being liked and being a good router are fading fast.

The move up the curve is the move from advising on outcomes to owning them.

The Move Is Not the Frontier Lab

Skip the fantasy of walking into a 7-figure OpenAI seat next month. That path is closed to most people, and chasing it burns the runway you have.

The real on-ramp runs through the roles next door:

• Technical CSM, Customer Success Engineer, TAM, and the long tail of vertical-AI startups where customer instinct counts as much as code.

Those roles reward what you already have and let you build the technical fluency on top.

The skill-building path is its own subject, and I have mapped it before: start with the CSM-to-technical-roles framework and the Customer Success Engineer guide.

You can see who's hiring for them right now on the board.

One Thing Decides All of It

Strip away the titles and every one of these roles pays for the same thing.

Proven outcomes.

The FDE who wins the renewal is the one who walked in with a number the customer’s own executive could verify without a follow-up call.

• Hours saved with a real method behind them.

• Revenue protected against a documented baseline.

• Cost avoided the customer can audit.

That is the skill under the money, and it is the one most CSMs never build.

They can describe what the customer did. They cannot prove what it was worth.

So they read as advisors, and the premium goes to whoever shows the outcome instead of narrating the activity.

Proving outcomes is a system.

• Capture the evidence per account as it happens.

• Build the proof before the renewal, not the week of.

• Frame it in the language an executive already trusts.

Run that system and your title stops mattering, because at any title you are the person who owns the number.

Build the System Before the Market Makes You

The forward deployed engineer boom is the clearest signal customer success has had in years.

The work now rewards the person who can prove what changed over the one who can describe it. That is who gets paid.

That system is what I publish every week.

It starts with the Proof-of-Value operating system, the exact method for turning outcome ownership into proof an executive will sign off on.

Subscribe and it is yours, along with every operating system in the archive.

The title on your posting will keep changing. The skill underneath it will not.

Build the one that travels.

Hakan | The CS Café

Know a CSM watching their role get rewritten? Forward this to them.

Share

Your title or years of experience barely move it. One thing does.

Your Band Was Set Before You Started

Your pay in Customer Success is decided by the shape of your role, long before your performance in it.

You can be the best CSM on your team and still be underpaid.

The band was set the day you signed, by what your role is allowed to own.

Sharper QBRs, cleaner renewals, an exec update that lands, all of it makes you better inside the band. It rarely moves you to a new one.

A CSM with your title and your years can sit tens of thousands dollars above you.

The gap is rarely talent.

The Line That Splits CS Pay

Your pay band is set by whether your role owns revenue.

Roles that carry a number live in one band.

• Expansion targets, renewal ownership, a quota with real accelerators.

• Flat-base service roles, same title, live in another.

You can be the strongest flat-base CSM in the building and still earn less than an average one that carries quota.

The market pays for the number you own, not the effort you spend.

Which Side Of The Line Is Your Role On

Four questions settle it:

1. Does any part of your pay move with renewals or expansion? All base and no variable puts you on the service side.

2. Is there a target with accelerators, where a great year pays more than a good one? Flat plans cap you on purpose.

3. Do you own the renewal conversation start to finish, or does it hand off to an AE or a renewals desk? The person who owns the number is the person the money follows.

4. Is expansion written into your goals, or into someone else’s? Credit for the number is what becomes a raise.

Mostly base, with the renewal leaving your hands, is the structure holding your number down.

It is also the most changeable thing about your career.

Where Your Number Actually Sits

I mapped the 2026 US bands, base and OTE, by seniority and pay structure, in the CSM Compensation Guide 2026.

The three levers that move you between bands, and the one almost nobody pulls, are in How to Know If You’re Underpaid.

Then stop negotiating against a national average.

The TopCSJobs Salary Calculator runs your seniority, location, and segment and hands back the band you should anchor to.

The anonymous salary database next to it shows the real spread from CS people worldwide.

Add your own number while you are there. The next person checking gets a sharper read because you did.

Run Your Number And See The Database →

Pass It On

Know someone reading their pay wrong? Forward this before their next review.

Share

A client owes you one thing. They sit on it for weeks. Somehow you are the one standing in a status call explaining why the date slipped.

There is a hope that some AI tool will finally handle the client chase for you.

But the reality is that an AI cannot make their admin send the file and make their sponsor approve anything.

It can own the record and fire the reminder. The record and the reminder only matter when a system sits underneath them. That system is the whole job.

Picture the version that costs you a weekend.

You kick off a rollout with a clean 90-day plan. Before your team can configure anything, you need one thing from the client: their user roles and permissions mapping, exported from their old system.

You ask for it in week one.

Their project lead says “end of next week.” Week two passes. You send a friendly nudge, then a firmer one, then a third. The file lands in week four in a format your tool cannot read, with a third of the roles missing. The usable version shows up a week after that.

Your team spent a month waiting on a spreadsheet from the customer.

Then the client’s sponsor joins the steering call and asks why the rollout is behind.

You have the whole trail in your email. You could pull the exact date their project lead committed to that export.

Doing it live, in front of their sponsor, feels like a lawyer fumbling for receipts, so you say you will make up the time.

Another weekend gone.

So, here is what happened, and it has nothing to do with the file itself.

You were defending a date you never controlled.

The go-live was yours on paper. The dependency that gated it belonged to them. The commitment to deliver it lived in an email thread instead of a signed response window, so when the sponsor asked, your answer sounded like an excuse instead of a fact.

There is a second one hiding in the same project.

Somewhere in the sales cycle, someone told the client you would build them a custom integration to their billing tool. It never made the SOW, Scope Of Work.

Nobody on your side remembers promising it. You are building it for free now, because arguing costs more than the work.

That is a second scope you are carrying with no paper trail, and it will land again on the next deal.

Chasing harder will not fix either one.

But a solid system will.

It puts the committed date in front of the room before the file is ever late, resets the clock the day a client dependency slips without starting a fight, and closes the scope ambush while the project is still calm.

Run it on your next kickoff and the sponsor call answers itself.

Below is the 3-part operating system, with the Excel workbook you can load Monday.

Read more

The market is rough, sure, but there is a more common reason, and almost no one names it.

A machine screened you out before a human ever opened your resume.

That machine is the applicant tracking system, the ATS.

Most mid-size and large companies run every resume through one before a recruiter sees a single page. It scores you against the job description and ranks you.

Land below the cutoff and you are filtered out in the background. You get no real rejection, no feedback, just silence.

Customer success pros get filtered more than almost anyone.

Skill is rarely the reason.

How CS Work Sounds on Paper

Think about how you describe your job.

You partnered with clients. You drove adoption. You owned the relationship. You built trust with stakeholders. You made customers successful.

Every one of those is true. But they are invisible to an ATS.

The system reads for keywords, not relationships.

It matches your resume against the posting, and the posting is full of plain terms: net revenue retention, gross retention, churn, onboarding, QBR, expansion, escalation, the specific tools like Gainsight and Salesforce.

Hard nouns and numbers.

CS is a relationship job at its core, so CS pros write like it is one.

That is exactly the language the filter cannot score.

The gap between how you talk about your work and how the machine reads it is why strong CSMs get cut before a human is involved.

The Keywords a Customer Success Resume Is Missing

Your experience already clears the bar. The wording is what the machine cannot read.

One before and after:

• Before: Built strong relationships with my key enterprise accounts.

• After: Held 94% gross retention across a $2M book of 40 enterprise accounts through structured QBRs and exec alignment.

Same work. Now it carries the nouns the ATS scans for and the numbers a recruiter wants once the machine passes you through.

The relationship is still there. It is just no longer the only thing on the line.

Now look at your own resume. Every vague line is a place the filter can drop you, and you cannot see which ones.

See the Score You Never Get to See

Paste your resume in and you get the score an ATS gives it, plus the exact lines you should update.

I built the checker for this. Free preview, takes a minute.

Check my ATS Score free →

If you are applying right now and hearing nothing back, run yours before you send the next one.

The filter is the first reader you have to win, and most people never find out they lost there.

P.S. If you try it, I’d love your raw feedback.

Hakan | The CS Café

Share

Fixed the resume? Your next CS role is waiting on TopCSJobs.