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.

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.

An account that was drifting toward risk renews without any drama. No escalation call, no war room, no Friday-night save. The number lands, the account stays, and there is no story to tell about any of it.

Now watch someone who let an account slide into a crisis and then pulled it back at the last minute.

That one comes with a story.

Slack threads, an exec who got looped in, a renewal that looked dead and somehow came back to life. Everyone remembers it, and everyone knows exactly who did it.

Same outcome. Opposite optics. And if you are honest about how your reviews work, most of them are built to reward the second person.

That is the paradox I want you to sit with for a minute, because it gets uncomfortable once you really see it.

Doing this job well tends to look like doing nothing at all. The better someone gets at prevention, the less there is to point to when it counts.

So if your gut tells you to promote the person with the dramatic saves, your gut has been trained on the wrong signal.

Prevention Leaves No Mark

Here is why this happens, and it is worth being clear that it is structural. It is not a manager being lazy or playing favorites.

A problem that gets solved leaves a trace behind it.

A ticket, a thread, a timeline you can walk back through when you sit down for the review. A problem that never forms leaves nothing at all.

There is no artifact for the churn that did not happen, the expansion conversation that stayed on the rails, or the exec who never once lost confidence because the CSM kept them close the whole way through.

So a healthy account reads as luck, and a rescued crisis reads as skill.

Your review process ends up measuring the residue a problem leaves behind, which means the person who stops problems from ever forming is invisible by design.

This is the same reason green accounts still churn on you: the most predictive signals live in the texture of the relationship, weeks before any dashboard catches up.

I see one version of this every week.

A CSM carries a heavy book, hits above target, closes out a quarter with zero churn, and hears nothing about it.

Then capacity churn they flagged a year earlier finally lands, and all of a sudden they are the one taking heat for it.

They did the hardest version of the job, in the background, and the system read the whole thing as a flat line.

Nothing happened, so nothing got rewarded. Then something happened, and they wore it.

The Cost Is Yours, Not Just Theirs

Set the CSM’s exhaustion to one side for a second, because there is a business case here that should worry you more than the morale one.

Your best preventer is hitting target and getting no recognition for it, so eventually they leave.

They are the most employable person on your team, and they walk straight into a role that actually sees them.

The capacity churn they warned you about arrives right on schedule, because the warning was real and you staffed against it too late.

Now you are absorbing the churn and you have lost the one person who was holding it off.

And notice what the prevention itself did to you.

It hid the risk. When someone is keeping ten fragile accounts stable, all you see is ten stable accounts.

You do not see the fragility underneath, and you have no idea how much load one person is carrying to keep it that way.

The work that protected your revenue also masked the signal you needed to act on. By the time the mask slips, the person holding it up is already gone.

Here Is What Changes When You Fix It

Picture your next quarterly review.

• The CSM with the healthy book walks in, and instead of a flat line, there is a number on the table showing the churn they stopped before it started.

• The account that would have slipped is on the record as a save, credited like the renewal it protected.

• And your best preventer, watching the job finally count the work, stops taking the recruiter’s call.

Keep running the old model and you train your team to let accounts drift so they can be the hero who saves them later.

You reward the fire and overlook the person who kept the room from catching.

Do it long enough and your preventers leave, and you inherit a team that is excellent at rescues you never needed.

The fix is a system, and it starts below with the exact weights that put a save next to a renewal and the three questions that settle any churn.

P.S. That line about your best preventer being the most employable person on the team, that's the one that stuck with me writing this. I build WowThisCV, an ATS resume checker, and the people who lean on it most are exactly those folks: excellent, overlooked, quietly updating their resume. If that's you, the free check is here: https://wowthiscv.com/resume-checker

If that's you, here's why customer success resumes get filtered before a human ever reads them.

Read more

It was sold something your product does not do. It has needed custom work since the very beginning.

The success plan has never had traction, and no amount of relationship work will change any of that, because the mismatch was there on the day the contract was signed.

• The CSM knows.

• The support lead knows.

• The engineer who built the third custom export knows.

It has been on that list for two quarters. It will be there next quarter, and the quarter after, unless somebody makes a call.

Meanwhile your strongest CSM spends their day on it. Then the next day. Then the escalation call that runs long and pushes the review of four healthy accounts to next week.

Everyone can see it. Nobody will decide it.

Today’s post is about how to price that account and make the call.

The Account Has Two Prices and You Only Track One

Open your CRM and look at that account. You will find a number. Annual contract value, renewal date, owner.

That number is what the account pays you.

Look for what the account costs you to hold. That figure exists nowhere in the system.

The hours, the custom builds, the escalations, the exec time, the roadmap slots it consumed on the way here. Your CRM was built to track revenue and it does so.

→ You are running portfolio decisions on half the ledger.

Why the Cost Stays Invisible

The cost is real. It splits across 4 budgets, and the split is what hides it:

1. CS pays in hours

Your CSM spends half a day every week vs. just a few hours on a comparable account.

In the system that time is logged as account management, identical to every other line, so the week reads normal.

What it costs shows up somewhere else.

Two healthy accounts got a rescheduled check-in. An expansion conversation slipped a month.

The CSM starts Monday already behind.

2. Engineering loses sprint capacity

The requests arrive one at a time, each one small, each one reasonable on its own.

• A custom export in March.

• A field mapping in May.

• A webhook nobody else uses in July.

The manager approving the eleventh request sees one ticket rather than a pattern, so it gets a yes.

Two sprints later a feature hundreds of your other customers asked for slips to next quarter.

3. Support carries the escalation load

The tickets look like regular tickets with a similar level of priority like any other customer.

What the queue does not show is that:

• This account raises 5 times what its peers raise,

• Half those tickets are the product working as designed against a use case it was never built for,

• Your two most experienced agents now handle them by default because nobody else knows the workarounds.

4. Product gives up roadmap slots

A build went to a feature one logo uses.

The features that lost that slot were wanted by tens of other customers. That trade never appears in a review, because the roadmap shows what shipped rather than what it displaced.

→ Each owner sees a rounding error and approves it, and the rounding errors all belong to the same account.

Nobody assembles the total, because assembling it is nobody’s job.

What Happens When the Total Is Missing

An account with no cost attached to it stays in save status by default.

Save status generates work. That work lands on the person closest to the customer, which means it lands on a CSM who cannot change product fit, pricing, or what Sales promised.

→ That CSM will do the work anyway.

They will build the recovery plan, run the extra sessions, chase the champion who stopped replying, and produce something that looks like effort to everyone watching.

A year later the account churns, inevitably.

The review asks what CS did. Your RYG scoring system already has a status for this.

Black covers accounts that were never the right fit.

Hardly any team uses it, because moving an account into Black means somebody has to defend the decision, and defending a decision requires a number.

The List You Cannot Produce

Every CS leader can name the 5 biggest accounts in the book from memory.

Almost none can name the 3 most expensive.

Those are different lists.

The first one shapes your forecast. The second one shapes your capacity, your team’s attrition, and how much of your best coverage reaches the accounts that would actually respond to it.

The second list is the one that decides your year, and it is the one you have never built.

→ Leaders who build it walk into the at-risk review already knowing which accounts to drop.

Here is how to build it.

Below: three steps and the Cost-to-Serve Workbook, a tab for each, yours with a paid subscription along with every workbook in the archive.

Read more

Now they chase the ones that were always silent, and miss the one that just went silent.

Your health score turns red weeks after the customer left, so you started reading the conversations instead.

Right instinct, but it breaks the moment you scale it.

The Two Silent Accounts You Cannot Tell Apart

1. One account was always terse

Three-word replies since onboarding.

One contact who answers when it matters and ignores the rest. That is the relationship, and it renews every year without drama.

Your silence alert fires on it constantly, and every time your CSM burns an hour confirming nothing is wrong.

2. Another account used to send paragraphs

The champion replied same day, looped in three colleagues, showed up early to every call. Last month the replies dropped to one line.

The colleagues fell off the thread. The champion reschedules now, then attends with the camera off. Your silence alert says nothing, because the account still technically replies.

The first account is fine and eats your attention. The second is leaving and gets none.

Both failures come from the same missing piece. Your alert reads silence as an absolute.

Silence only means something against what that account normally does.

You are measuring volume. You need to measure change.

Today your team has no record of what normal looks like for any single account, so every silence reads the same, and the two accounts above are identical on your dashboard.

That is the gap.

A CSM who has carried the account for two years feels the difference in their gut.

That instinct falls apart across a book of eighty accounts, it walks out the door when the CSM leaves, and it shows up in no review your VP can run.

What Changes When You Fix It

The champion going one-line and camera-off gets flagged the week it starts, while the renewal is still months out and still winnable.

The always-terse account stops generating false alarms, and your CSM stops spending Fridays chasing accounts that were never at risk.

Every silence that reaches your at-risk review arrives with a reason attached. A specific move off a specific baseline, ready to tier and act on.

The instinct that used to live in one CSM’s head becomes a record any CSM can read and any leader can audit.

Below is the system that produces that.

Three steps. One workbook →

Read more

See churn risk before the renewal call, not after it. PilotPM is one AI brain for your whole customer lifecycle. It scores account health, picks the next best action for every account, and drafts each customer reply from real history and ARR. Your team approves in one click. Live today: the AI resolves 89% of tickets on its own, ~$0.45 each.

See it on your accounts in 30 minutes →

Salesforce Will Let You Work Remote. Harvey Will Not.

Right now, Salesforce has 56 open Customer Success roles on the TopCSJobs board. Remote and hybrid.

Harvey has 14. Onsite. Heidi, 10. Onsite. Anthropic, 9. Onsite.

If you filter for remote only, Harvey, Heidi and Anthropic vanish from your search.

The Pattern

Of the 30 companies hiring CS hardest on our board right now, 21 list onsite only.

Across all 552 open roles we track, 366 are onsite. Two thirds.

The ones offering remote are mostly names you already know. Salesforce. Samsara. Vanta. Adobe. ServiceNow. Motorola. Thomson Reuters. Datadog.

The ones that want you at a desk include Harvey. Heidi. Anthropic. Notion. Stripe. Pylon. Synthesia.

Many established names sit there too. MongoDB. Veeva. Intercom. HPE.

Most people carry the opposite story. Startups flexible, enterprise rigid.
The startup half of that does not hold.

Of the 552 roles live on our board, 10 are junior. Two percent.

Why It Matters To Your Search

If you filter on remote first, you skip most of the companies actually hiring.

That is the whole point. Remote is not gone. It is concentrated in fewer companies, and most of them are names you already know.

Worth knowing before you spend another month on a filtered list.

How To Read This

We track companies we think are worth watching, so read this as a signal about notable employers rather than a map of the whole market.

The tags are how each company labels its own roles, and the same job gets tagged differently at different companies.

Many onsite roles negotiate to hybrid once you are in the loop.

Treat it as the posture they advertise.

One More Thing In The List

Harvey, Heidi, Anthropic, Synthesia, Pylon, Nooks, Laurel.

All hiring CS right now.

Two months ago I wrote that 882 tech jobs were disappearing per day and CS was next. The companies building AI are staffing Customer Success while they do it.

What they pay and screen for is in the AI Customer Success Jobs guide.

Counts move daily. Harvey was 16 yesterday. See who is hiring today on the board.

The companies hiring Customer Success hardest want you onsite. The ones that will let you work remote are the ones you already knew about.

Hakan | Founder, The CS Café

A customer escalation blows up on a Thursday. The root cause is a bug Engineering has sat on for six weeks.

You flagged it. You chased it. You have the Slack threads to prove you chased it.

None of that matters on the call, because the customer is looking at you, and so is your leadership. The fix was never in your hands.

The blame is.

This is the job most Customer Success pros actually have.

You are accountable for the outcome and hold authority over none of the teams that decide it.

• Product ships without telling you.

• Sales promises a feature to close.

• Engineering closes your escalation with a one-word reply.

When the account is at risk, three people were watching it and none of them owned the number.

You did.

Cope Or Quit Are Both Losing Moves

Search for help with this and you get two answers.

Cope, or quit.

• Cope means stop caring, collect the check, do the minimum, protect yourself by going numb.

• Quit means leave Customer Success entirely and go do something with your hands.

Both answers lose.

One hollows you out while you stay. The other throws away the decade you spent getting good at this.

The absorption is a missing system.

Ownership was never drawn, so everything defaults to the person closest to the customer.

That gap shows up in three specific places, and you will recognize all three from this week.

This is the same overload I broke down in The Completion Signal Your CS Operating System Is Missing, seen from the ownership side instead of the workload side.

Where The Ownership Gap Breaks

The line was never drawn

Look at your at-risk list right now.

A stalled onboarding, a pricing objection, a bug, a quiet champion, a missing integration. Some of those you own. Most of them you do not.

You carry them all the same, because nobody separated the risks you can move from the risks you can only report.

Undrawn lines default to whoever is closest to the customer, and that is you.

The escalation disappears

You post in the channel. You tag the person. You get a thumbs-up react and then silence.

There is no sequence behind the ask, no cost attached to ignoring it, and no record that survives past the scroll.

A request with no leverage and no paper trail is a request the other team is free to deprioritize, and they will.

The flag was only ever verbal

You did raise the risk. You raised it on a call, in a hallway, in a sentence at the end of a standup.

Verbal risk = unprovable risk.

When the account churns and the review starts, “I mentioned it” is not a defense. It reads as an admission that you saw it coming and let it stay in the air.

None of this is a discipline problem.

It is a missing system, and the system is mechanical.

Below is how you draw the ownership line, move a team that does not report to you, and put every risk on record so the blame lands where the authority sits. The Excel log runs all three.

Upgrade to run the full system →

Not ready to subscribe? The log is also available on its own. Get it here for $49 →

Read more

Demand for the role has climbed as more software companies route revenue through partners instead of direct sales alone. This guide covers what a PSM does, what the job pays in 2026 across the US and UK, the skills that get you hired, and how to move into the role.

What Is a Partner Success Manager?

A Partner Success Manager (PSM) is the person responsible for making a company’s partners successful with its product. Partners here means resellers, system integrators, agencies, and technology platforms that carry your product to their own customers. The PSM enables those partners, drives joint revenue, and keeps each partnership healthy over time.

The job sits between customer success, sales, and partnerships. A CSM keeps a single end customer renewing and expanding. A PSM does that same work one layer up, through partners who reach many customers at once. That leverage is the entire reason the role exists.

Titles vary by company. You will see Partner Success Manager, Partner Success Specialist, Partnership Success Manager, and Partner Success Enablement Manager describing versions of the same function. The seniority and scope change. The core mandate stays the same: partners that grow, and partners that stay.

What a Partner Success Manager Actually Does All Day

The daily work breaks into enablement, co-selling, and partner health.

Enablement means getting partners ready to sell and deliver. You onboard new partners, train their teams on the product, and build the assets they need to position it well. When a partner’s reps can talk about your product without you in the room, enablement is working.

Co-selling means driving revenue alongside the partner. You map accounts together, join partner deals, and pull in your own sales team when a partner surfaces an expansion. The best PSMs treat a partner’s pipeline as their own forecast.

Partner health means catching problems early. You run partner reviews, track whether each partner is growing or stalling, and spot the ones about to go quiet before they disappear. A partner that stops booking deals is the channel version of a customer that stops logging in.

A strong PSM reads a partner’s activity the way a CSM reads product usage. Both are early signals. Both tell you where revenue is about to move.

Partner Success Manager vs CSM

The two roles share a mindset and split on who they serve.

Who they serve. A CSM serves the end customer using the product. A PSM serves the partner who resells or builds on it.

Their goal. A CSM drives adoption, renewal, and expansion. A PSM drives partner enablement, joint revenue, and ecosystem growth.

Revenue model. A CSM works revenue directly. A PSM works revenue through the partner, at scale.

Core skill. A CSM reads product usage. A PSM reads partner pipeline.

The short version: a CSM works with the company that uses the product, and a PSM works with the company that sells or delivers it. For a full breakdown of the differences, skills overlap, and which path fits your background, read the complete comparison in CSM vs Partner Success Manager.

Partner Success Manager Salary in 2026

Salary figures for this role look wildly different depending on where you check. One source says $62K. Another says $149K. Both are right. They measure different things.

The lower numbers report base salary. The higher numbers report total pay, which folds in bonus and equity. Partner Success sits close to revenue, so a real chunk of the package is variable. Read every offer as base plus on-target earnings, and the confusion clears up.

Here is the base salary ladder for 2026, US first, then London.

Partner Success Specialist (entry). US base $55K to $80K. London base £35K to £48K.

Partner Success Manager. US base $62K to $100K. London base £45K to £73K.

Senior Partner Success Manager. US base $100K to $140K. London base £70K to £100K.

Partnerships or Alliances Lead. US base $135K and up. London base £90K and up.

Add bonus and equity and the picture shifts up. Glassdoor puts average total pay for a US Partner Success Manager near $149K in early 2026, with a range from roughly $117K to $195K. Senior PSMs land higher, averaging around $162K and reaching past $200K at the top. In London, base pay averages about £53K, with top earners near £100K.

Company matters as much as level. The top payers named across salary sources include Google, Microsoft, Cisco, and AWS, where partner ecosystems are large and the role carries real revenue weight. A PSM title at a 50-person startup and a PSM title at a hyperscaler describe very different jobs and very different numbers.

You can check these bands against live, self-reported figures in the TopCSJobs salary database. Add your own number while you are there. It is anonymous, and it sharpens the data for the next person.

Skills That Get You Hired as a PSM

Four skills show up in almost every Partner Success Manager job description.

Partner enablement is the base skill. You need to teach, build training, and turn a partner’s team into people who can sell and deliver without you.

Commercial fluency comes next. You are close to revenue, so you have to talk pipeline, forecast, and deal mechanics with both partners and your own sales team.

Cross-functional influence carries the role. A PSM has no direct authority over partners or over internal sales, and moves both anyway through clarity and follow-through.

Data fluency is the multiplier. Reading partner activity, spotting the stall, and building a simple health view separates a PSM who reacts from one who sees it coming.

Ecosystem thinking sits underneath all of it: understanding how your product fits inside a partner’s wider portfolio, and aligning your plan to their business, not just yours.

How to Become a Partner Success Manager

Most people arrive at Partner Success from one of three doors.

From Customer Success. This is the most common path. The success mindset transfers directly. You already read health signals, run reviews, and drive renewal and expansion. You swap the end customer for the partner. If you are still building the CS foundation first, start with How to Become a Customer Success Manager.

From account management or sales. If you have run quota and closed deals, the co-sell motion feels natural. Your gap is usually the enablement and success side, which you can learn on the job.

From partnerships or channel roles. If you already work with partners on the business-development side, moving into success adds the retention and growth mandate to relationships you understand.

Certifications help at the margin, mostly for candidates without a CS background. A recognized customer success credential signals you understand the success motion. See which ones carry weight in Best Certifications for Customer Success Managers. Real partner or customer results on your resume beat any certificate.

Career Path: Where Partner Success Leads

Partner Success is a launchpad. The role opens doors up and sideways.

The direct line runs up: Specialist, Partner Success Manager, Senior PSM, then Head of Partner Success or Alliances. Each step widens the number of partners and the revenue you carry.

The sideways moves are just as open. PSMs move into channel sales, partnerships leadership, and broader revenue roles, because they already sit at the intersection of product, sales, and delivery. Some move into core CS leadership, where the partner experience translates cleanly into running a customer-facing team.

For a look at how another adjacent role builds its own ladder, the Customer Success Engineer 2026 guide maps a similar skills-to-salary progression. And if you want a parallel named-role breakdown, the Microsoft Customer Success Account Manager role shows what the CSAM version looks like inside a hyperscaler.

Is Partner Success Manager a Good Career in 2026?

Yes, for the right person. Software companies keep shifting revenue through partners, which keeps demand for the role steady. The pay is solid and rises fast for anyone who can tie their work to booked revenue. The skills transfer across success, sales, and partnerships, so you are rarely stuck.

The role suits people who like building relationships at scale and enabling others to win. It suits people who read data and act before the number moves. It rewards anyone who can turn a quiet partner into a growing one.

Partners that grow. Partners that stay. That is the job, and companies will keep paying for it.

Partner Success Manager FAQ

Is a Partner Success Manager a sales role? Partly. A PSM carries revenue through partners and joins co-sell deals, so the job has a commercial edge. The success side, enablement and partner health, keeps it from being pure sales.

What is the difference between a Partner Success Manager and a Partner Manager? A Partner Manager usually focuses on recruiting and signing partners. A Partner Success Manager takes it from there and makes those partners productive and lasting. Some companies merge both into one role.

Do you need a degree to become a Partner Success Manager? Rarely. Most employers care more about relevant experience in customer success, sales, or partnerships than about a specific degree. Results with partners or customers matter most.

What is a Partner Success Specialist? It is the entry-level version of the role. A Specialist supports partner onboarding and enablement, often across a larger pool of smaller partners, before stepping up to full PSM scope.

How much does a Partner Success Manager make in 2026? US base pay runs roughly $62K to $100K, with total pay reaching $120K to $195K once bonus and equity are counted. London base averages about £53K. Senior roles pay well above these figures.

Hunting for a Partner Success or CS role? Browse live listings on TopCSJobs.

1. Commercial,

2. Technical and data,

3. AI fluency,

4. Executive communication,

5. Operational execution.

The bar moved. Relationship skill alone used to carry the role.

Now owning the numbers and using AI decide the offer more than years on the job, and CSMs who show real results in interviews are commanding 8-15% higher base salary than peers who cannot.

Here is the full list, what each one means to someone hiring you this year, and how to see where you stand.

What Changed in 2026

The job title stayed the same. What people expect from it did not.

A couple of years ago, a good CSM was someone customers liked and whose renewals mostly closed.

Today the same title comes with a number attached.

Hiring managers want to know if you can own renewals and upsells, read an account from the data yourself, and use AI as a normal part of your week.

The difference between a $90K CSM and a $150K CSM is a skills gap, and it is a specific one.

1. Commercial Skills: Own the Renewal Number

The biggest change is salary.

More companies now pay CSMs partly on results, the way they compensate salespeople. The CSMs who earn the most own the renewal and the upsell, instead of passing that number to a sales rep.

Said simpler, you know what your accounts are worth. You can talk about a price increase without dreading it. You treat keeping and growing revenue as your own target, not someone else’s.

A CSM who walks into a review with their own retention and growth numbers is a level above one who only reports what they did that week.

This shows up in interviews.

They ask what your accounts did on renewals last year, and whether you drove any of the growth. The CSM Compensation Guide covers how this pay shift works, and the SaaS price-increase playbook covers the hardest version of that conversation.

2. Reading Data and Health Scores

You do not need to write code.

But you need to answer questions cold about your own accounts instead of waiting for someone to pull a report.

That means getting basic usage data yourself, knowing what a dashboard is telling you, and questioning a health score instead of trusting the color.

A green account can still be about to leave.

The CSMs who read their own data spot trouble weeks earlier than the ones who wait for the next review.

If this is your weak spot and you want to go further, the technical path is in the Customer Success Engineer guide.

3. AI Fluency: The Skill That Moved Your Base in 2026

This barely mattered 18 months ago. Now it moves your compensation.

The test is simple.

Do you use AI tools in your actual week, and can you point to one thing you built with them?

“I tried ChatGPT” does not count. You need something you can show, like a routine that preps your account reviews, or a faster way to spot customers who are slipping.

In interviews, one concrete AI example beats any amount of buzzwords, and it is what earns the salary bump.

For the fuller picture of how AI is changing the role, see the AI Customer Success Guide.

4. Talking to Executives

At the senior level, part of the job is standing in front of leadership and being taken seriously. That skill gets tested in the final interview round and in every big account review.

In practice, you run a review that talks about results the customer cares about rather than a list of features you shipped.

You write an update an executive can read without your manager fixing it first. You handle a tense conversation with a customer’s exec and get to the point fast.

This is what separates a $120K CSM from a $180K one, and it is the skill most people practice least.

The exact question that decides most senior offers on this is broken down in The One Interview Question That Decides Senior CSM Offers.

5. Running a Full Book Without Dropping Accounts

The last skill looks boring and decides everything else. It is running a long list of accounts without letting the important ones slip.

Decide where your hours go before the week starts.

Use the same reliable steps on every account instead of winging each one. Keep your tools tidy enough to trust.

When your book is large, this is the skill that decides how much revenue you actually protect.

If your accounts have grown faster than your system for handling them, start with the CSM-to-customer ratio breakdown.

Rate Yourself Across the Five

Score yourself 1 to 5 in each area before you read on.

Here’s what weak means (be honest):

• Owning the numbers: you can describe your accounts but not your renewal rate or how much they grew.

• Reading data: you wait for someone to pull the report and you trust the health score color without asking questions.

• AI: you have tried a tool once or twice and cannot point to anything you built.

• Talking to executives: your reviews are feature lists and your manager rewrites your updates.

• Running the book: your week is driven by whoever emailed last.

Most CSMs are strong in one or two areas and soft in the rest. Where you are soft is often what is holding your salary down.

The Two Skills That Move Your Pay Most

The five are not equal in 2026.

Owning the numbers and AI move your pay the most, because they are the two things most companies now check for and the two most CSMs still lack.

A CSM who is great with customers and organized, but weak on numbers and AI, sits in the middle of the pay range and stays there.

The same CSM who learns to own the renewal and builds one real AI habit moves toward the top of the range, and into the roles at AI-native and fintech companies that pay at the top of every band.

You can see which companies are hiring CSMs right now on the TopCSJobs board. I laid out the pay behind these skills in How to Know If You’re Underpaid in Customer Success.

Before you push for more, know the real numbers.

I am building an anonymous CS salary database to show what CSMs are actually paid by level and company type.

→ Add your own salary. It is anonymous, takes a minute, and it sharpens the data for the next person checking.

Where to Start This Week

Take your lowest score and pick one action.

• If numbers are your gap, find your renewal rate this week and learn to say it out loud.

• If AI is your gap, build one thing that saves you an hour, and write down how you did it so you can explain it in an interview.

• If data is your gap, learn the handful of queries that answer your most common account questions.

One move on your weakest area beats a vague plan to fix all five.

Once you have closed a gap or two and you are ready to move, the live CS roles are on TopCSJobs.

The skills get tested. Your weakest one caps your offer. Close one gap and the next pay conversation looks different.

Recommended reads:

• CSM Compensation Guide

• AI Customer Success Guide

• Customer Success Career Progression Guide

That plan records what everyone agreed to in week one.

It does nothing to change what happens in week twenty. A plan that only stores the past is a status doc disguised as “strategy.”

Why Most Customer Success Plans Fail

Here is where it breaks.

The Same Plan Runs on Every Account

The 500K renewal and the 20K renewal get the same fields, the same cadence, the same attention.

The accounts that decide your number get treated like the accounts that barely move it.

The Plan Is Built on Stale Kickoff Goals

The objectives were set the week the deal closed.

By month three, the customer reorganized, the champion changed teams, and the goals on the plan describe a company that no longer exists.

The plan was designed to be filled once, so nobody goes back to update them.

The Plan Stays Silent Until Renewal

When the renewal lands, the plan cannot answer the one question that decides it.

Why should this customer renew, said in the exec’s language, tied to dollars. The template has a goals section.

It has no space for that answer.

No Book-Level View of Renewal Risk

Look at your plans right now.

You cannot say which accounts are covered and which are exposed. The signal is spread across twenty documents that each read “on track.”

So the exposure surfaces at T-14, in the one week there is no room left to fix it.

Turn the Customer Success Plan Into a System

The template is fine. The plan has to become a system. One that scores itself, tiers by account weight, and shows where the dollars are exposed before the quarter starts.

That system is three moves.

The first one takes ten minutes and tells you which of your plans are real and which are decoration.

Run it and renewal season changes shape.

You walk in knowing which accounts are exposed in week one, not week fifty. Your forecast answers the CFO question before it gets asked. Your team runs the same motion when you are out of the room.

Renewal season is already on the calendar. The accounts that decide your number are sending signals today, while the quarter still has room in it.

Get the Customer Success Plan Operating System

This is the system I run with CS leaders, and it sits on one workbook. Score any plan, tier the book, and see the dollars at risk in one place, before renewal season starts.

Two ways to get it:

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

2. Standalone, $49. One download, no subscription. Buy it here →

Read more

You built a number finance could not wave away, tied it to renewals, put a range on it, and walked in ready for every question you could think of.

This was the meeting where you finally got the headcount, the tool, the budget, whatever you came in for.

Then the case died anyway.

It started fine. People were nodding. Your number was holding.

Then someone got pulled onto the call who had sat in none of your prep. A new face, and a skeptical one.

They asked a single question, the kind you cannot answer in one line, and the whole room turned to them instead of you.

That was the moment.

The goalposts moved. For the next few minutes you were defending a number that had been winning when you walked in.

You know how it ended.

“Let’s revisit this next quarter.” You walked out and could not point to the exact second it slipped away.

The number was right. So what happened?

Most advice stops one step too early

Almost everything written about winning budget from finance is about the number.

• Make it defensible.

• Tie it to revenue.

• Put a range on it so it survives the follow-up questions.

That advice is correct.

It is also where the help stops. And it leaves out the part that kills more cases than a weak number ever has.

A business case breaks in one of 3 places:

1. Never having a credible number to begin with.

2. Having a number nobody upstream trusts.

   Both of those are real, and both are solvable. If that is where your cases die, the fix is the number itself, and I have written the full method for building one finance accepts here: How to Prove Customer Success Revenue to Your CFO.

   Go build that first, then come back.

3. The one nobody writes about => The number is fine. The case still dies, because of who saw it, and when.

The meeting was the first time half the room had seen your number

Here is the mistake.

You spent your prep time on the number and almost none of it on the path the number takes before the decision gets made.

So the meeting becomes the first time several people in the room are meeting your case.

One of them has budget power you underweighted. Another one was not even on the invite, and gets consulted right after.

And the moment a fresh set of eyes lands on a number for the first time, in front of everyone, the natural thing for them to do is push on it.

That push is the goalpost moving.

Now your number is being relitigated by someone who was not there when you built it, and you are explaining your assumptions live instead of having them already agreed.

This is also why “who delivers the number” feels like it matters so much.

It does not, much.

A pre-wired room approves a number delivered by anyone. A cold room relitigates a number delivered by your CEO.

The difference is whether the people who could kill it had already seen it.

If a case of yours died right when approval looked close, look back at who entered the room late and what they asked.

The number was probably never the problem.

The path was.

What changes when the number travels first

When you stop walking your case in cold, the meeting stops being a debate and becomes a confirmation.

You know every vote before you sit down.

Nobody reopens your number, because everyone who could has already seen it and pushed on it in private, where pushing cost you nothing and bought you a better number.

The person who used to blow up your pitch is handled before the pitch.

And a year later, when finance asks whether the number you promised actually held, you have the answer ready.

That answer is what gets you the next yes without a fight.

The full kit below turns each step into a tool you can run this week: the Stakeholder Kill-Map with the room-readiness score built in, the pre-wiring sequence with the objection-handling fields, and the room-ready checklist with the assumption log.

It is included with your paid subscription, along with every workbook in the archive and every operating system I publish next.

You also get direct email review on the work that reaches leadership, your renewal plans, QBR narratives, and exec updates, so a second set of eyes sharpens them before they land.

Prefer just this one? Buy the Stakeholder Kill-Map on its own. No subscription.

Read more

It gets decided in the 4 months before it, in signals most teams never write down.

By the time the renewal lands on the calendar, the outcome is mostly set. The call is where you find out.

Most CS teams run renewals as a Q4 scramble.

• A list of accounts.

• A round of one-off saves.

• A few heroic recoveries that get celebrated and never turned into a system.

The team that saved a logo in week 50 had no system. They had luck and a good week.

Next quarter the same fire starts somewhere else, and the same people run at it with the same bucket.

A renewal is not an event. It is the last page of a motion that started four months earlier.

When that motion is missing, four failure points show up in order. Each one makes the next one worse.

This motion runs on a strong account plan. Build it with the account-level plan operating system that feeds these five stages.

Where Renewals Are Lost Before The Quote Opens

Ownership is fuzzy

Three people are “watching” the account. None of them owns the number.

• The CSM thinks the AE has it.

• The AE thinks the CSM has it.

The first person to truly own it does so at T-30, when owning it means triage rather than strategy.

Signals never get logged

The champion stops replying within a day. Usage holds flat while sentiment rots.

A workaround becomes the workflow, and the team stops complaining because they gave up expecting better.

None of this reaches the CRM. None of it reaches the forecast. The data says green.

The account is amber and falling.

The forecast is a feeling

“Probably fine” is not a forecast.

When Finance asks why an account sits at 80 percent, there is no scored answer, just a vibe and a hope.

Renewals that should have triggered a play in August get attention in November.

Value proof shows up late

The QBR runs as a status update instead of a decision.

The first time anyone assembles the ROI story is the week before the renewal, which is the one week there is no time left to close a gap the customer has been carrying for two quarters.

These four compound.

• Fuzzy ownership => nobody catches the signal.

• The missing signal => the forecast lies.

• The lying forecast => value proof gets built too late.

By the renewal call you are negotiating from behind, and the customer can feel it.

The signals are there before the renewal is.

Read how dark accounts go quiet before they churn, why a customer workaround is a renewal signal, and how silent trust debt builds where nobody is looking.

A renewal you meet at T-14 is a renewal you hope for.

What Changes When Every Renewal Runs One Motion

Run every renewal through a single sequence and the quarter changes shape.

Risk surfaces at T-120, while you can still act on it.

• Your forecast survives a CFO question, because every number traces back to a logged signal.

• The renewal conversation becomes a confirmation of a story the customer already believes.

• Saves stop being heroics and start being the output of a system anyone on the team can run.

Renewal season is already on the calendar.

The accounts that decide your number are sending signals today, while the quarter still has room in it.

The only open question is which accounts get the full motion and which ones you let ride.

That call is the whole game, and most teams make it at T-14 by accident.

Get The System That Runs This

It runs on one tool: the Renewal Operating System workbook.

Two ways to get it. The subscription is the one to take.

• Subscribe, $25/mo. This workbook, the full archive, and every system I publish next. Plus 24-hour replies when you need my feedback on a renewal, QBR, or exec update. → Upgrade

• Standalone, $49. One download, no subscription. → Get the workbook

The first month of subscribing costs less than this workbook alone.

Read more

By Friday, the account was an email chain with Sales, Support, and a VP.

The problem was that no one owned the issue, so the customer picked a name.

They always pick the name closest to them.

On your team, that is the CSM. And every time it happens, a renewal gets harder to forecast.

Default Ownership Is a Tax on Your Number

When an inbound issue has no named owner and no promised update time, it does not sit still. It attaches to whoever is visible.

On your team, that is the CSM who picked up.

From that moment, every delay, every cross-team gap, and every unanswered question routes to them, because they are the only name the customer has.

The work was never theirs. The silence assigned it.

You do not see this as it happens. You see it later, in the shape of your number.

• Renewals that should have been clean turn last-minute.

• Escalations arrive with no clean trail of who owned what.

Your strongest CSMs spend their weeks absorbing problems other teams created, and the best of them start taking calls from recruiters.

Default ownership is a tax, and it comes straight out of retention.

The Fixes That Do Not Move the Number

Most teams respond at the symptom.

• Tell CSMs to screen calls and prep before calling back.

• Roll out a booking link with a required topic field.

• Push faster response times.

Each one lowers call volume. The owner of the issue stays the same.

A CSM can respond in five minutes, sound sharp, and still end the week as the default owner of a problem that belonged to Support.

Speed with no named owner and no clock leaves the account where it started, and leaves your forecast just as blind.

Handling escalations better keeps your team in the chair. The standard that gets them out is a different thing.

You make ownership explicit before it defaults, so every issue lands on the name that should carry it, and the customer always knows where to look.

Somewhere other than the CSM you cannot afford to lose.

Install this and default ownership stops eating your renewals.

• Every escalating account has a named owner the customer can see, a clock the customer trusts, and a trail you can inspect.

• Your forecast reviews get honest, because the accounts quietly defaulting back to your team surface weeks earlier.

• Your 1:1s get sharper, because you are coaching a standard instead of chasing fires.

The system that closes the vacuum is below. Three steps, and the first one shows you every exposed account by Friday.

Get the workbook that runs this system

The system below runs on one tool: The Default Owner System workbook. It scores every open account for default-owner risk, hands your CSMs the word-for-word reassignment scripts, and turns the log into your forecast early-warning list.

Two ways to get it:

1. Included with your paid subscription. This workbook is yours, plus the full archive and every operating system I publish next. You also get direct email review on your renewal plans and exec updates before they reach leadership. Upgrade →

2. Buy it standalone. Single download. No subscription. $49. Get the workbook →

If you plan to build more than one operating system this year, the subscription pays for itself in the first month.

Read more