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

One makes $85,000 and answers weekend calls. The other makes $250,000 and logs off at four.

Same job on paper. Triple the pay.

So many CS pros have no idea which one they are. They have a number, a sense it might be low, and no way to check.

So they sit. A year passes. Then two.

Underpaid the whole time, and still guessing.

The spread is not about experience

I have seen five-year CSMs stuck at $90k and three-year CSMs clearing $200k.

Three things move the number, and tenure is not one of them.

Run all three on yourself.

Segment: who you carry

An SMB book of 200 accounts and an enterprise book of 8 clients are different jobs that happen to share a title.

Enterprise pays more because the renewals are bigger and the buyer is harder.

A high-volume, low-ACV book puts you on the low scale by default, no matter how well you run it.

Revenue ownership: what you actually own. This is the biggest splitter

• One version of the CSM role owns renewal and expansion numbers, carries a quota, and sits in the revenue conversation.

• Another version owns health scores, adoption, and QBRs, then hands the number to an account exec.

The first gets paid like sales. The second gets paid like support.

Open your comp plan.

A plan with no variable tied to a number you own puts you in the second group.

If you want to see how the variable side is built, the CSM compensation guide breaks down the commission and bonus structures employers actually use.

Company tier: who signs the check

Late-stage SaaS and AI-adjacent companies pay a different scale for the identical job description.

The same resume that gets $110k at a Series A gets $180k at a category leader.

Funding stage, margin, and how strategic retention is to the business set your ceiling before you negotiate a single dollar.

The two traps that cost people two years

The first trap is waiting for your manager to fix it.

A boss who agrees the pay is wrong is not a raise.

Recognition and budget are separate conversations, run by separate people. Your manager naming the problem out loud changes nothing in your bank account.

The second trap is asking for more with nothing behind the ask.

The lever that reliably moves a current employer is a competing offer with a real number on it.

Sentiment does not move comp bands. A written offer does.

So many people get the raise only once they were one signature away from leaving.

Getting to that signature means winning the final round, and the one question that decides senior CSM offers is where most candidates lose it.

Here is the wall you hit

Run those three levers and you still cannot answer the question. Y

ou can see your segment, your comp plan, and your company tier. The market is the one thing you cannot see.

You live inside a single data point every day: your own company’s pay.

That is the worst possible sample to benchmark against, because it is the exact thing you are trying to evaluate.

This is the gap I built the TopCSJobs Salary Calculator to close.

Put in your seniority, location, and segment.

It hands back the band you should anchor to for your exact situation, instead of a national average that blends an SMB CSM in Ohio with an enterprise lead in San Francisco.

Next to it, open the anonymous salary database I am building from real CS submissions worldwide.

• The calculator gives you your number.

• The database shows you the full spread you are sitting inside: real, anonymous comp from CS people by company stage, segment, and city.

Find the people whose role matches yours. That is your evidence.

Contribute your own number while you are there. It’s anonymous, and the next person checking gets a sharper read.

The whole thing only works because CS people are willing to put their pay on the table.

What changes once you know

Three conversations get easier the moment the number stops being a guess.

The raise ask turns from a feeling into a benchmark you can point to. The offer decision gets clean, because you can tell a real bump from a lateral move dressed up with a title.

The “should I leave” question answers itself once you can see the band your title commands somewhere else.

All of it runs on one thing: a number you can defend.

The number is the floor you negotiate from.

Closing the offer is a separate skill, and this is what that shift looked like for a CS pro I worked with.

• Once you know where you stand, the next move is climbing.

  The eight ways CSMs reach $150k covers the levers that pull a comp number up rather than sideways.

• UK-based readers should anchor to a different scale entirely, which the 2026 UK CSM salary guide lays out by city and company type.

Hakan | Founder, TheCScafe.com

The account manager does.

They run the calls, pick who’s in the room, and control how much you get to see.

When the renewal slips, it lands on your number, not theirs.

Some account managers will lock you out, and it works

Some account managers guard their accounts hard.

They leave you off calls. They answer the customer before you can. A few will tell you straight out that they don’t think CS is worth much.

The reason barely matters.

The result is the same: you’re responsible for keeping the customer, and you can’t get near them.

Befriending them or reporting them won’t fix it

Most people try one of two things.

Win the account manager over and become friends. Or go to the boss and explain how difficult the account manager is being.

• The first might buy you one good quarter.

• The second usually backfires, because the moment you complain about a coworker, you become the problem, and they keep their long leash.

Every renewal comes down to one question

Here is what actually moves it.

Every renewal answers one question: will this customer renew, and why?

Right now nobody can really answer it.

The account manager can’t, because they’re already chasing the next deal. You can’t, because you’re locked out.

Whoever becomes the person who can answer that question, with proof, ends up owning the account. And that person is very hard to lock out.

The reason you get gatekept so easily is that nothing you do is essential to the renewal yet.

As long as your job looks like “help with adoption” and “keep the relationship warm,” you’re nice to have.

Nice-to-have people get left off the calendar.

A renewal you can’t see is one you can’t call

This is bigger than a bad working relationship.

An account you can’t see is a renewal you can’t call. Those are the ones that blow up at the last minute and make your whole book look out of control in front of your boss.

And once leadership stops trusting your forecast, you lose the thing that protects your team and your budget.

Every account you’re locked out of chips away at that trust.

Stop asking to be let in

Build the one thing that makes leaving you out the risky move: a clear, proven answer to whether each account will renew and why.

Once that's yours, the account manager can't keep you out without looking like the person putting the renewal at risk.

Here’s what changes once you own that answer, even on accounts where the AM is actively keeping you out:

• You walk into the account meeting holding the one thing nobody else has: a clear picture of where the renewal stands and what could kill it.

• The account manager can’t leave you out without being the one who blocked the renewal plan.

• Your forecast becomes something your boss repeats upward without double-checking it.

• Your next QBR runs on your story, because you’re the one who wrote down what the customer wants and what’s standing in the way.

Three steps. Plus, a workbook that runs all three.

Read more

HR, recruitment, workplace, culture. The company ruled out AI as the cause.

The internal memo said the teams had grown “too far from the businesses and partners they support.”

Read that again.

A function that sits far from revenue, and cannot show how close, becomes the cost line. Most CS teams cannot show how close.

And the cost line is the first thing a budget review looks to trim.

So here is the question that decides how that review goes for you.

How much revenue does your team protect this quarter?

Not roughly. The number.

Why the numbers you have do not survive

Ask most CS leaders that question and the answer comes back as CSAT, NPS, or a health score that turns green and red for reasons the rest of the company does not fully trust.

None of those is a number a finance team accepts.

They are not denominated in dollars. They are not tied to renewal dates. They cannot be checked against the contract book.

A CFO discards them on the first follow-up question, and the honest answer underneath, for most teams, is that the revenue figure does not exist.

That gap is what gets a function reclassified as overhead.

When the only number anyone can see is your cost, your cost is what the conversation is about.

The number that survives, and the trap inside it

There is one figure that holds up in a finance review.

The revenue your team is actively protecting, expressed in dollars, tied to the renewals it maps to.

Building it is harder than it sounds, and most attempts fail in a specific way.

The leader sums the ARR under management and walks in with “my team protects forty million dollars.”

The CFO asks one question. “All of it would have churned without you?” The number collapses, and so does the credibility behind it.

The real number is smaller, defensible, and survives the second and third question.

The method is what separates the two.

You have seen what happens to the leader who walks in with the wrong number.

Below is how to walk in with the right one.

A single protected-revenue figure in dollars, mapped to real renewal dates, with a defensible range, and an answer ready for every question a CFO will throw at it.

The budget review stops being the meeting where you defend your headcount. It becomes the meeting where you state a number and the room moves on.

The full method is below

Free editions of The CS Café give you the diagnosis. The pattern, the problem, and the language to name it in your own org.

Paid editions give you the execution.

Today, that is the Revenue-at-Risk Scorecard and the full method behind it.

Across the archive, it is renewal plans that close early, QBRs that end with decisions, and escalations that stop bleeding, each with the templates and tools that make it repeatable.

Two ways to get today’s workbook

1. Upgrade to The CS Café paid subscription

   The Revenue-at-Risk Scorecard is included with your paid subscription, along with every workbook in the archive and every new operating system I publish. You also get direct email review on your renewal plans and exec updates before they reach leadership. Upgrade →

2. Buy the workbook 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.

Leading a CS team? The CS Café offers group subscriptions for teams of 3 or more at 20% off. One invoice, one list to manage, add or remove team members any time. Get the team plan.

Read more

They open with rapport. They walk the deck cleanly. They take the hard question and hand back a calm reframe.

The customer nods. The call ends on time. Everyone leaves feeling good about the relationship.

Ask that CSM what number they moved this quarter, and the room goes quiet.

The calls happened. The decks shipped. The relationships stayed warm. Nothing on a revenue line changed because of any of it.

These people are easy to miss, because on paper they look like the strongest CSMs you have.

They have the title, the named accounts, the polish. They sit in the meetings where decisions get made.

Pull the thread on what they actually did, and there is a strange gap where the work should be.

You can find out which kind you are in about ten minutes.

The two-week test

Open your calendar for the last two weeks.

Take out everything that was a call, a check-in, a QBR, a prep block, an internal sync, or a deck build. Look at what is left.

That residue is your real work.

It is the part that moved a renewal forward, changed a number, or pushed an executive toward a decision they were not going to make on their own.

For a lot of CSMs, the residue is close to empty.

Two weeks of motion. Two weeks of warmth. Nothing underneath it that anyone above you could tie to revenue.

The tells

Once you know what you are looking for, the pattern is hard to unsee.

The call ends warm and nothing was agreed.

You left feeling good about it.

Go back through your notes and there is no commitment captured, no next decision named, no date the customer owns.

The QBR closes with your follow-ups, not their decisions. You walk out with a task list. They walk out with nothing on the table.

You will spend the next quarter chasing actions you assigned yourself.

The work is called strategic and no one can describe it in a sentence.

If your manager cannot say what you moved last quarter without opening a spreadsheet, that is the answer.

The renewal closed and you cannot name the moment it was actually secured.

It renewed. You were on the account. You are just unsure whether you were the reason.

None of these are about effort.

The polished CSM works hard. The hours are real. The accounts are real.

The gap is between activity and the thing activity is supposed to produce.

The part nobody says out loud

Many of these roles were hollow long before anyone said the word AI in a board meeting. The seat existed. The work did not.

AI is just the thing that will get blamed when the seat disappears.

That is what’s happening in this market right now.

The roles getting cut are not random.

They are the ones where the honest answer to “what did this person move” was always thin, and the budget finally got tight enough for someone to ask.

What this leaves you with

The job is hard. That part is real.

What should worry you is how much of your week kept you busy without moving a number anyone above you can see.

The polished CSM and the one who is impossible to cut can run the identical meeting.

They can use the same deck, ask the same questions, get the same nods. Only one of them can tell you what changed because they were in the room.

You already know which calendar is yours.

Hakan | Founder, The CS Café

Find your next role on TopCSJobs. 1,000+ candidates already signed up. 500+ jobs, updated daily, worldwide. No noise. Customer Success only.

Not a scheduling question. A concern about whether the thing they bought is going to land the way Sales told them it would.

Your system answered it.

A timed check-in. Polished. On cadence. Built to make sure nobody forgets to follow up.

It also made sure the customer learned something. The channel is automated. The concern they raised went into a queue, not to a person.

They will not raise the next one.

The robotic tone is the small problem

Most CS leaders audit their automation for tone. They worry the emails sound robotic. The robotic part is the small problem.

What matters the most is the conclusions customer makes.

When a real signal gets a generic reply, the customer reads it as proof that nobody is listening.

So they stop sending signals. They stop volunteering hesitation. They stop telling you when something is drifting.

The account goes quiet.

And quiet is the most dangerous reading on your dashboard, because silence gets coded as health. The green score walks you into a renewal you should have seen coming a quarter out.

Automating the wrong follow-up does not just annoy the customer. It removes the early-warning system you were counting on for the renewal.

The question most teams cannot answer

Look at every automated touch your team sends this week.

Which ones protect the relationship, and which ones are quietly eating signal?

Most leaders cannot draw that line.

Worse, every CSM on the team draws it differently, in their own head, with no shared rule.

• One automates renewal nudges and keeps objections human.

• Another automates everything and hopes.

• A third reviews each one by feel and misses half.

The line exists. It’s just invisible, inconsistent, and undocumented.

That gap is where your renewal signal disappears.

What changes when you draw the line once

Catching this changes 3 things in your week:

1. Your renewal forecast stops going quiet on you

The accounts that went silent by choice get separated from the accounts that went silent because automation trained them to.

You know which is which before the renewal call, not after.

2. Your QBR stops running on stale assumptions

The high-signal moments reach a human while they still matter.

The account walks into the QBR with its real concerns surfaced and addressed, instead of buried under three months of on-cadence check-ins nobody read.

3. Your team draws the same line the same way

The judgment calls stop living in five different heads.

One rule, applied the same way across the book, so a touch that needs a person gets a person regardless of who owns the account.

Below is the operating system that produces those outcomes

Three steps, one scoring tool, one decision framework, with an Excel workbook you can use Monday that maps 1:1 to the steps.

Free editions of The CS Café give you the diagnosis. The pattern, the problem, and the language to name it in your own org.

Paid editions give you the execution:

• Renewal plans that close early.

• QBRs that end with decisions.

• Escalations that stop bleeding.

• All with the templates and tools that make it repeatable.

Two ways to get today’s workbook

1. Upgrade to The CS Café paid subscription

   The Touch Signal Audit is included with your paid subscription, along with every workbook in the archive and every new operating system I publish each week. You also get direct email review on your renewal plans, QBR narratives, and exec updates before they reach leadership. Upgrade →

2. Buy the workbook 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.

Leading a CS team? The CS Café offers group subscriptions for teams of 3 or more at 20% off. One invoice, one list to manage, add or remove team members any time. Get the team plan.

Read more

The CS community is arguing the wrong question.

Should you learn to code? Is the CSM role dead? Should you panic?

While you study coding tutorials, your customers are changing how they buy software.

The shift is contractual, and it is pulling the CSM role away from engineering.

The technical angle is a sideshow.

What Changed Without Anyone Noticing

A B2B contract used to read like a license.

You paid for seats. The renewal was about usage and satisfaction.

A growing share of B2B contracts now read like a finance instrument.

The price is tied to a business outcome. The vendor’s revenue depends on the customer hitting a number. Both sides agree, in writing, what good looks like.

When that is the contract, the renewal is a finance conversation. Period.

No relationship or technical buzz.

The CSM who can hold that conversation keeps the job.

What This Means For Your Week

The CSM who survives outcome-based contracts looks more like a finance analyst with empathy than a meeting host with a deck.

Your work is:

• Forecast each account in dollars, not in adoption metrics.

• Defend that forecast in front of the customer’s finance team.

• Close the gap between what Sales promised and what the CFO sees.

This is about learning what gross retention, payback period, and net revenue per customer mean inside your own company.

Then learning what they mean inside your customer’s.

The CSMs who already speak this language are getting promoted past the ones who do not.

Why The FDE Argument Is A Red Herring

• Engineers solve product problems.

• CSMs solve commercial problems with the product in the room.

Different jobs. Always have been.

The new contract model does not collapse them.

It splits the role into three layers:

1. AI agents handle the coordination layer.

2. Technical specialists handle the configuration layer.

3. The CSM who survives owns the financial layer.

That is the layer customers care about when the renewal is on the table.

Two of my previous posts map to this directly:

• Running QBRs as proof-of-value reviews instead of status updates.

• And borrowing the investor language Salesforce uses with Wall Street to position your own accounts.

The Move For This Week

Open the contract for your largest account. Find the renewal date.

Now write down, in dollars, the business outcome that account will use to justify the renewal to their CFO.

• If the answer is not in the contract, you have a positioning problem.

• If you cannot calculate it from your own data, you have a measurement problem.

• If you have not spoken to the customer’s finance team this year, you have an access problem.

Pick the most broken one. Fix it before the buzzwords change again.

Hakan | Founder, The CS Café

Free editions of The CS Café give you the diagnosis. The pattern, the problem, and the language to name it in your own org.

Paid editions give you the execution:

• Exec updates that get the budget approved.

• Expansion conversations that don’t sound like sales.

• Risk calls that surface in week 2, not week 11.

Upgrade to paid to run it on real accounts.

Leading a CS team? Group plans for 3+ seats, 20% off, one invoice, one admin panel.

If you’re exploring your next move, start at TopCSJobs for live roles, follow the TopCSJobs Newsletter for the weekly market signal, and use WowThisCV to land more interviews.

Share The CS Café

The CCO title is supposed to signal that customer outcomes have a seat at the executive table. The data from May 2026 tells a different story.

Three patterns are converging at once.

The biggest companies in the world do not have a Chief Customer Officer on their executive committee.

The CCOs who do hold the title are quietly leaving, getting reassigned, or selling their equity. And the companies still hiring for the role are doing so with narrower scopes than the title implies.

If you are tracking the CS leadership market for your own career, your hiring plan, or your board-level conversations, this is the moment to look at what is actually happening instead of what the title is supposed to mean.

FAANG, Walmart, and JPMorgan Have No CCO on the Executive Committee

CX Network published a piece this month called "The silent CX crisis".

The most cited data point: Apple, Amazon, Meta, Walmart, and JPMorgan Chase do not have a Chief Customer Officer on their executive committee.

Walmart created the role in 2018 and then let it dissolve back into other functions over the following years. The other four never elevated it in the first place.

This matters more than it sounds.

These are five of the companies that set hiring benchmarks for the rest of the market.

When the world’s largest retailer, one of the world’s largest cloud providers, the world’s largest e-commerce platform, the world’s largest social platform, and one of the world’s largest banks all decide the customer function does not need a dedicated C-suite voice, the rest of the market reads that signal.

The signal is not “customer outcomes do not matter.” Rather, “customer outcomes get owned by a CRO, a COO, or a product leader instead of a standalone CCO.”

That distinction is the whole story.

The Insider Selling Pattern at Kaltura

Kaltura’s Chief Customer Officer Natan Israeli has been selling company stock on a near-weekly cadence since the start of May 2026.

The disclosed transactions include 13,965 shares on May 20, 13,229 shares on May 19, and an earlier sale of 3,600 shares, all executed under a Rule 10b5-1 trading plan adopted on December 15, 2025.

The weighted average price across the disclosed sales was around $1.51 per share.

Total cash out of the company stock position across these filings: approximately $47,000. The broader pattern, visible in the SEC Form 4 filings, shows additional sales on May 13, May 14, and May 18, bringing the May total well past 70,000 shares.

The 10b5-1 plan structure is the standard mechanism executives use to schedule equity sales in advance to avoid insider trading exposure. The legal cover is real. The market signal is also real.

Three filings in one week from a single CCO at a single mid-cap public company would not matter on its own. The pattern across the broader news cycle does.

In the same week:

• Westfalia’s Chief Customer Officer Wim Destoop announced his departure after three years.

• OCS appointed its CCO Bob Taylor to a new role as Managing Director of Public Sector FM, removing the CCO title from his portfolio.

• A UK housing organization announced that its newly hired CCO Matt Foreman would be responsible for “neighbourhoods, independence and wellbeing (supported housing), and customer” services, a title applied to a four-function operations role.

• A New Zealand grocery chain announced organizational changes through its “Acting Chief Customer Officer,” a title that indicates the permanent role is either being redefined or quietly downgraded.

None of these are individually scandalous. Together they describe a market where the CCO title is being absorbed, fractured, or transitioned out of.

What Is Actually Happening to the Role

Three structural shifts are running in parallel.

The CCO function is being absorbed into the CRO org

A growing number of B2B SaaS companies are folding customer success, customer support, and customer operations under a single Chief Revenue Officer.

The CRO owns the full revenue lifecycle including renewals, expansion, churn, and customer health.

The CCO becomes a VP of CS reporting up, or the role gets removed entirely.

The CustomerThink piece on sales-to-CS handoff failure published this month confirmed the pattern from the inside: "While CS teams can report to the CRO, many times these teams report to a Chief Customer Officer or the VP of Services."

The "many times" framing is doing a lot of work in that sentence. Five years ago it would have been "almost always."

Today it is one of three viable structures.

The CCO function is being absorbed into operations

Outside of pure software, the CCO title is increasingly used for broad operations roles that include customer service, retail experience, supported housing services, and similar functions.

The OCS appointment of Bob Taylor to Managing Director of Public Sector FM is a clean example.

The CCO title was a stepping stone to a P&L leadership role, not a destination.

The CCO title is being kept but the seat is not at the executive committee

This is the FAANG pattern.

Companies retain the CCO role for external positioning, internal coordination, and customer optics. They do not put the role on the executive committee.

Strategic decisions about customer outcomes get made by the CEO, the CRO, and the COO. The CCO executes.

All three shifts point the same direction.

The standalone CCO with executive committee voting power and full ownership of the customer outcome P&L is becoming rare.

What This Means for Your Career Path

If you are a CS director or VP plotting your next move, the implications are direct.

The path to CCO is narrower than it was three years ago. Fewer roles are being created at the standalone CCO level.

The roles that do exist increasingly come with fragmented scopes: CCO of a region, CCO of a product line, CCO with operations responsibilities outside customer success.

The path to CRO is wider than it was three years ago.

CS leaders who can credibly own the full revenue lifecycle, including new business attach, are being considered for CRO roles in a way that was unusual before 2024.

The skills that get you to CRO from CS are different from the skills that get you to CCO from CS.

Pipeline ownership, deal mechanics, and forecast accountability matter more than program design and customer maturity models.

The path to COO is opening for senior CS leaders at services-heavy companies.

If your CS function includes implementation, professional services, support operations, and customer education, the COO conversation is increasingly available.

For more on how the underlying CSM role is being repriced at the operator level, see the Microsoft CSAM 2026 role and career path breakdown on the Café. The signal at the IC and front-line manager level is parallel to what is happening at the C-suite level.

What This Means for Hiring CCOs

If you are a CEO, board member, or executive recruiter evaluating whether to hire a CCO, the questions to answer are sharper than they used to be.

What outcome does this role own that no other role can own?

If the answer involves renewals, expansion, and churn, that is now a defensible CRO scope. If the answer involves customer maturity, advocacy, and lifecycle program design, the role can be filled at the VP level without needing a C-suite title.

What is the reporting line to the executive committee?

If the CCO will not attend executive committee meetings, the role is positional rather than structural. Candidates evaluating the role will notice. Strong candidates will negotiate around it.

What does the scope look like at year three?

If the scope at year three converges on either CRO or COO responsibilities, the company is hiring the wrong title today.

What This Means for Vendor and Stack Decisions

The CS technology vendors built their go-to-market motion on the assumption that the CCO is the buyer. That assumption is weakening.

When the buyer shifts from CCO to CRO, the buying criteria shift with it.

CROs care more about revenue attribution, pipeline integration, and forecast accuracy than they care about health scoring sophistication or customer journey orchestration.

The vendors that adapt their messaging to the CRO buyer will keep growing. The vendors that continue to sell to the CCO function as if it owns the budget will see deal cycles lengthen.

This has implications for how you evaluate vendors during your next renewal cycle.

The CSM tool you bought when your CCO was on the executive committee may have been priced and positioned for a stakeholder who no longer exists at your company.

The Best Customer Success Platforms guide on the Café walks through what to look for when the buying decision moves up to the CRO.

Three Signals to Watch Inside Your Own Company

Three internal signals will tell you which direction your own company is moving.

1. Who chairs the renewal forecast call

If it is the CCO, the customer org still owns the revenue outcome.

If it is the CRO or the CFO, the customer org is a contributor to a forecast owned elsewhere. The forecast chair is the de facto owner of the outcome.

2. Who presents customer health to the board

If it is the CCO, the role has executive-committee weight even without the title. If it is the CRO presenting CS metrics alongside sales metrics, the customer function has been absorbed.

3. Who approves the CS budget

If the CCO approves it, the role is structurally protected.

If the CRO approves it, the CS function is a cost center inside the revenue org and will be optimized accordingly during the next budget cycle.

Any one of these signals shifting is normal. All three shifting in the same quarter is the structural move.

The Quiet Restructuring

The CCO role is not disappearing in 2026.

It is being restructured quietly enough that the trade press is still writing about CCO appointments as if the title meant the same thing it meant five years ago.

The data from this month says otherwise.

The biggest companies in the world have moved on. The CCOs who hold the title are leaving, being reassigned, or cashing out their equity. The companies still hiring for the role are giving it scopes that would have been called something else in 2021.

For CS leaders, vendors, and operators, the takeaway is the same.

Map the role you actually want by the responsibilities and the executive committee access, not by the title. The title is becoming the least reliable signal in the market.

Stay ahead of what is changing in CS

The CCO market is one of many shifts The CS Café tracks each week.

Get one CS insight every week covering what is driving churn risk, what is changing in renewal and QBR practice, and how the CS leadership market is evolving.

Hakan | Founder, TheCScafe.com

But eleven months later, the customer churns.

The post-mortem always lands in the same place. The team was blindsided. The score said the relationship was healthy.

The score was looking at the wrong thing.

One detail went unchecked. Whether the customer kept the spreadsheet alive.

• The Slack thread that still tracks the workflow.

• The manual export run every Friday.

• The side process the buyer’s ops team trusts more than the platform you sold them.

• The parallel workflow with an owner, a cadence, recovery logic, and social trust.

That workaround is your retention signal.

The customer already trusts a working system. Your product replaces that trust, or coexists with it. Until the trust moves over, usage exaggerates change.

Adoption metrics measure participation. They do not measure migration.

I covered the formula problem in Your Health Score Is Lying to You. Today’s edition is about what the score cannot see, even when the formula is correct.

3 things happen silently in accounts where the workaround survives.

1. The buyer who signed the deal stops citing your product in internal reviews.

   They cite the outcome and skip the source. The platform becomes an implementation detail in their own story.

2. The team running the workflow knows who to ping when the spreadsheet breaks.

   They do not know who to ping when your platform breaks. The social ownership still points at the old system.

3. By Day 14 after onboarding completion, the customer has not opened the product a second time without a CSM nudge.

   The first session was scheduled. The second session never happened on its own.

None of this shows up in the health score. All of it predicts the renewal.

Catching this changes 3 things in your week:

1. Your renewal forecast stops surprising you

   The accounts that would have shown up in next quarter’s churn list are flagged this week, with a documented intervention path.

   The CFO question that always comes after a green-account churn (”how did we not see this”) stops being a question you have to answer.

2. Your QBR cycle stops feeling like theater

   The accounts flagged by the override walk into a QBR built around displacing a specific legacy workflow, not reviewing adoption slides.

   The conversations get harder and the renewals get easier.

3. Your executive update changes shape

   Leadership stops asking why the dashboard is green and the renewal forecast is yellow.

   The override delta becomes the metric the VP CS takes to the executive team, and it moves in a direction the team can defend.

Below is the operating system that produces those outcomes.

Three steps, one diagnostic layer, one decision framework with an Excel workbook you can use Monday that maps 1:1 to the steps.

Two ways to get this workbook

1. Upgrade to The CS Café paid subscription

The Workaround Audit is included with your paid subscription, along with every workbook in the archive and every new operating system I publish every week. You also get direct email review on your renewal plans, QBR narratives, and exec updates before they hit leadership. Upgrade →

2. Buy the workbook 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

• She handled the renewal escalation.

• Sent the QBR pre-read.

• Replied to the procurement email.

• Updated the health score on three accounts.

• Joined the cross-functional standup.

Every task on her list, done.

Well... actually, nothing is done.

The 47 accounts in her portfolio reset overnight.

Tomorrow morning, three will have new questions. Two will have moved up in priority. One will have gone silent in a way that matters.

The work she completed today does not subtract from the work she has tomorrow. It only delays it.

This is the structural problem most CS leaders address with the wrong tool. They add headcount. They re-tier portfolios. They buy a new platform.

None of those moves answer the underlying question.

What does “covered” actually mean at the account level, and how does the CSM know when she is done?

Without that definition, the work has no completion signal.

And work without a completion signal is unmanageable by design, regardless of how many accounts each CSM holds.

Why ratios and tiering solved the wrong problem

CS leaders have spent the last five years solving for portfolio quantity.

• The 90/10 rule.

• Tier 1/2/3 segmentation.

• Pooled models for the long tail.

• The CSM-to-account ratio benchmarks.

All of this is real progress. It answers “how much work.”

It does not answer “when is the work finished for any given account.”

A CSM running 30 strategic enterprise accounts can feel as overwhelmed as a CSM running 200 digital accounts.

The cognitive load is driven by the absence of a definable end state per account.

Every relationship reopens. Every conversation extends. Every email thread continues.

Tiering reduces the frequency of touchpoints. But it does not reduce the surface area of attention each account requires.

A Tier 2 account that gets a quarterly touch still occupies cognitive space the rest of the year. The CSM is monitoring it. Watching for signals. Responding to ad-hoc requests. Pre-empting risk.

Headcount makes this worse.

Adding a CSM redistributes the volume but increases coordination cost, handoff friction, and the number of accounts where ownership feels ambiguous to everyone in the chain.

The fix is defining what completion looks like for each account interaction so the CSM has a clear answer to “am I done with this?”

The 4 interactions where “done” needs a definition

Four interaction types account for most of the cognitive load in a CSM’s week. Each one needs a defined completion state to stop bleeding attention.

1. The check-in

Most CSMs treat check-ins as ongoing.

The conversation ends, the calendar invite closes, the work continues mentally.

Defined completion: a written summary captured, one named follow-up logged, the next touchpoint scheduled.

Done.

2. The health score review

Most CSMs treat this as continuous monitoring.

Defined completion: the score was reviewed on a defined cadence, any movement was investigated, and either an action was logged or the score was acknowledged as stable.

Done.

3. The renewal risk assessment

Most CSMs carry this as background anxiety for 90 days.

Defined completion: a written brief exists at 90 days out, the risk level is assigned, the named action is in the calendar, and the leadership chain has visibility.

Done.

4. The escalation handoff

Most CSMs carry escalations indefinitely because there is no clear exit.

Defined completion: the escalation has a named owner outside CS, the resolution path is documented, and the CSM’s role in the escalation is explicitly closed or transitioned.

Silent accounts need the same treatment.

The pattern: every cognitive-load interaction needs a written artifact that signals completion.

Without the artifact, the work continues mentally. With the artifact, the CSM closes the task and reclaims the attention.

This is why the seven-artifact CS operating system matters at the cognitive level, not just the documentation level.

Artifacts are the completion signal.

They are how the CSM knows the work is done.

What changes when leadership defines “covered”

Three things change once an organization defines what “covered” means at the account level.

Burnout signal becomes visible

CSMs who are running cleanly produce the artifacts.

CSMs who are drowning do not.

Missing artifacts are a leading indicator of capacity stress, six to eight weeks before performance reviews surface it.

The team that used to lose its best CSM in Q3 with no warning now has a six-week heads-up to redistribute load or add a hire.

Handoffs stop losing context

When the completion state of every interaction is documented, a CSM going on leave, leaving the company, or transitioning to another role hands off accounts in days, not months.

The work is legible because the work was completed, not just performed.

Renewal coverage becomes auditable

Leadership asks “show me every Tier 1 account with a current renewal risk assessment” and gets a real answer, not a verbal one.

The accounts without the artifact are the at-risk accounts, by definition.

Ratio benchmarks tell you whether you have enough CSMs. Artifact audits tell you whether the CSMs you have are actually covering the portfolio.

The CSM gets her evenings back.

The work she did today is actually done. The mental load of carrying unresolved interactions into the next day, the weekend, the next week stops compounding.

This is the operating-model decision that ratios and tiering cannot make for you.

It has to be defined at the leadership level, codified in the operating system, and enforced through the artifacts the team is required to produce.

The leadership move

Name the four completion states

Write them down. Make them mandatory. For each interaction type, define the artifact that closes it.

• The check-in note

• The health review log

• The renewal risk brief

• The escalation handoff document

Each one short. Each one mandatory. Each one filed in a shared location every CSM and every leader can audit.

Audit weekly

The audit is a capacity diagnostic.

Missing artifacts mean the CSM is overloaded, the artifact requirement is wrong, or the interaction should not have happened in the first place.

Any of those answers is actionable.

Stop measuring activity

Touch counts, meeting volume, and email response rates do not tell you whether the work is being closed.

Artifact production does.

A CSM running 15 clean closures a week is operating at full strength. A CSM running 40 unfinished interactions is one quarter from leaving.

The CSMs who are one bad month from updating their resume already know what the TopCSJobs job board shows for their seniority and segment.

And the listings are moving faster than your retention plan.

Defend the closure standard

The first time a CSM tries to skip the artifact because “the customer already knows,” hold the line.

The artifact is for the CSM’s cognitive load and for the operating system’s auditability.

Both matter more than the five minutes the artifact takes to write.

Takeaway: The CSMs who stay are the ones who finish their work

Define what done looks like. Require the artifact. Audit the closures.

The leaders who keep their best CSMs are the ones who define what finishing means.

Hakan | Founder, TheCScafe.com

Free editions of The CS Café give you the diagnosis. The pattern, the problem, and the language to name it in your own org.

Paid editions give you the execution:

• Renewal plans that close early.

• QBRs that end with decisions.

• Escalations that stop bleeding.

• All with the templates and tools that make it repeatable.

Upgrade to paid to run it on real accounts.

Leading a CS team? The CS Café offers group subscriptions for teams of 3 or more at 20% off. One invoice, one list to manage, add or remove team members any time. Get the team plan.

If you're exploring your next move, start at TopCSJobs for live roles, follow the TopCSJobs Newsletter for the weekly market signal, and use WowThisCV to land more interviews.

Share The CS Café

Content writing built a specific set of instincts in you.

Audience awareness. Research discipline. The ability to make complex information readable to someone with no prior context. Deadline accountability. Structured thinking under ambiguity.

Those instincts are rare inside CS teams.

Most CSMs learned the job by doing the job. They understand the process, the tools, and the renewal cycle.

What many of them struggle with is the work that happens in writing: the risk brief that surfaces at the right moment, the QBR pre-read that lands before the meeting starts, the executive update that builds trust instead of creating more questions.

That gap is where a content writing background pays off fast.

This guide covers the salary reality of the move, the skills that transfer directly, the gaps you need to close, and the step-by-step path from content writer to CSM.

The salary reality

Content writers in the US earn a median base salary of around $58,000 (PayScale, 2026). At senior levels, that ceiling typically sits between $85K and $88K at most companies outside top-tier tech.

• Entry-level CSM roles start between $65,000 and $96,000.

• Mid-career CSMs with three to five years of experience earn between $80,000 and $114,000.

• Senior CSMs managing enterprise accounts or teams reach $138,000 to $200,000 and above.

The move is not lateral.

An entry-level CSM role represents a meaningful step up from the median content writing salary, and the ceiling is substantially higher.

The variable pay component in CS, typically 15 to 20% tied to renewals and expansion, adds further upside that writing roles rarely offer.

The comparable transition from teaching to CS follows the same financial logic. That guide covers the $60K to $114K+ trajectory in detail and is worth reading alongside this one.

Why content writers make strong CSMs

The standard CS hiring filter screens for SaaS experience, CRM familiarity, and prior quota attainment. Those are environmental credentials. They confirm you have been in the room before.

They do not predict whether:

• You can write a renewal risk summary that a VP can read in two minutes and act on.

• Your QBR pre-read gives an executive sponsor confidence before the meeting starts.

• Your account handover document preserves the relationship or loses it.

Content writers solve exactly those problems every day, just in different contexts.

Here is how the skills map directly.

Audience awareness

Content writers do not write for themselves.

Every piece is built around a specific reader, a specific knowledge level, and a specific question that reader needs answered.

That instinct, applied to customer communication, produces exec updates that land differently from what most CSMs send.

The reader finds the point immediately.

Research discipline

Understanding a customer’s industry, their competitive pressures, their CFO’s renewal priorities; these are research problems before they are relationship problems.

A writer who enjoys the research phase of a project brings that same instinct to account preparation.

Most CSMs treat customer context as background noise.

Writers treat it as the brief.

Clarity under ambiguity

Content writers regularly face the challenge of making a contested, underspecified, or technically complex topic legible to a general reader.

That is precisely what a CSM does when writing a renewal brief for a leadership team that does not know the account history, or when building a QBR narrative for an executive who joined the company after the original deal was signed.

Structured communication

A well-structured article moves the reader from problem to insight to action.

A well-structured renewal email does the same. The underlying skill is identical: sequencing information to produce a specific outcome in the reader.

The developer-to-CS transition and the marketing-to-CS transition both involve non-traditional backgrounds entering CS with a transferable skill the standard filter undervalues. The content writing move follows the same pattern.

The gaps you need to close

Transferable skills get you in the room. Environmental fluency keeps you there.

Three gaps are real and worth addressing before or during the job search.

CS process familiarity

Renewal timelines, health scoring, QBR structures, onboarding milestones, these are learnable frameworks.

You do not need to have run them to understand them.

Reading CS-focused publications, taking a structured CS course, and completing simulated case work builds enough familiarity to speak the language in interviews.

CRM and CS tooling basics

Salesforce, Gainsight, HubSpot, and Totango show up in most CS job descriptions.

You do not need certification-level expertise to land an entry-level role, but basic familiarity with how CRMs track accounts and how CS platforms surface health signals removes a common objection from hiring managers.

Commercial vocabulary

NRR, GRR, churn rate, expansion revenue, time-to-value, these terms are the native language of CS teams.

Building fluency in the metrics that CS leaders track daily makes your application and your interviews read as CS-native rather than transition-adjacent.

The transition roadmap

Step 1: Build CS-specific vocabulary and process knowledge

Spend four to six weeks reading CS-focused content, completing a structured CS course, and studying real job descriptions at target companies.

Pay attention to the metrics each company prioritizes and the tools they list. This is research work. You already know how to do it.

The best CS courses guide on The CS Café covers the certifications worth pursuing and which ones hiring managers at B2B SaaS companies actually recognize.

Step 2: Rebuild your portfolio around outcomes, not deliverables

Content writers list articles, campaigns, and word counts. CS hiring managers look for evidence that you influenced customer behavior, drove adoption, reduced friction, or improved retention in some form.

Go back through your writing work and reframe it.

• Did your onboarding documentation reduce support ticket volume?

• Did your help content improve product adoption rates?

• Did your case study work contribute to renewal conversations?

Every piece of customer-facing writing you produced can be reframed around the business outcome it enabled.

This is the same repositioning that the CS Portfolio Method recommends for developers entering CS: same accomplishments, different language.

Step 3: Target the right company profile

SMB-focused SaaS companies are the most accessible entry point for writers transitioning into CS.

They run smaller CS teams, carry broader role scopes, and hire for adaptability more than for existing CS credentials. You learn the full renewal cycle faster in a smaller account environment.

EdTech, marketing technology, and content platforms are particularly strong fits.

These companies sell into audiences that content writers understand natively. Your familiarity with the buyer’s world is an immediate value-add on the account team.

Step 4: Position your writing background as the asset

The instinct during a career transition is to minimize the prior background and emphasize how quickly you are becoming something new.

Reverse that.

CS leaders at growing B2B SaaS companies have a consistent hiring problem: they can find CSMs who understand the process, but they struggle to find CSMs who can communicate risk clearly to executives, document account health in a way that survives handovers, and write QBR narratives that build sponsor confidence before the meeting starts.

Your background addresses all three directly.

Step 5: Prepare for the interview process

CS interviews typically include a situational round, a customer scenario exercise, and an executive round at senior levels.

The situational round tests judgment: how would you handle a disengaged account, a pricing objection, a sponsor change 60 days before renewal.

Your research instinct is your asset here. Prepare specific, structured responses using real examples where your writing or communication work influenced a business outcome.

Frame each example in CS language: the risk you identified, the action you took, the outcome it produced.

The CSM interview guide on The CS Café covers what hiring managers score in each round and how to prepare. The single interview question that decides most senior CSM offers is worth reviewing separately if you are targeting director-level roles from the start.

What the first 90 days look like

The first 30 days in a CS role are product immersion.

You are learning the platform, the customer segments, the renewal calendar, and the internal vocabulary. This phase favors the research instinct. Take notes. Ask structured questions.

Build your own documentation of what you learn because that documentation will matter later.

Days 30 to 60 shift toward account ownership.

You start shadowing renewals, joining QBR prep, and building your first account health assessments. The communication skills you already carry start activating here. Where other new CSMs struggle to write a clear renewal summary, you do not.

Days 60 to 90 are when the writing background creates visible separation.

You are producing cleaner pre-reads, clearer risk flags, and more legible account updates than most CSMs produce after a year in the role.

That visibility matters early.

CS leaders notice the CSM whose written work they can forward directly to a VP without editing it first.

Companies actively hiring writers into CS

HubSpot, Notion, and Webflow each hire CSMs from non-traditional backgrounds and explicitly value candidates who can communicate complex product value in plain language.

Intercom, Contentful, and similar content-infrastructure platforms are natural fits because your writing background maps directly to the buyer’s world.

For a broader view of current CS roles filtered by company type and seniority, TopCSJobs tracks live CS openings updated daily and is built specifically for CS professionals navigating the job market.

The move is real. Start with the repositioning.

The content writing background you have built is not something to minimize on a CS application.

It is the capability most CS hiring filters never surface, and the one that CS leaders consistently wish their teams had more of.

The gap between where you are and a CS role is learnable: process familiarity, commercial vocabulary, and a reframed portfolio.

None of those require starting over. They require recontextualizing what you already know.

Hakan | Founder, TheCScafe.com

Share The CS Café

Shopify’s CEO Tobi Lutke uses that exact reasoning to refuse KPIs and OKRs at the company level.

In Customer Success, the application is sharper. The metrics that get gamed first are the ones on your board slide.

By the time they reach the CFO, every number on that slide has been a target for someone on your team for at least two quarters, and the slide has stopped telling you the truth.

3 signs the board has already stopped trusting your slide

You already feel this without naming it. Three patterns that probably happened this quarter.

1. The NRR number that drops mid-meeting

The CS leader walks into the board review with NRR holding at 112%.

The CFO asks one follow-up. How much of that came from net-new logo conversion versus existing-account expansion.

The CS leader does the math live and the number drops to 104%. Two questions later it drops again. The room gets quiet.

The next slide gets less attention than it deserves.

2. The dashboard that lies while it stays green

The CS Ops dashboard shows logo retention at 94%.

Steady for three quarters.

Below the surface, the renewal forecast for the upcoming quarter is being held together by two CSMs running almost impossible recoveries on accounts that should have been flagged 90 days ago. Plus three discounted renewals that protect the logo count and quietly compress NRR.

The dashboard is right. The dashboard is also lying.

3. The CSAT trend that mistakes silence for satisfaction

CSAT has trended up for four quarters.

The CS leader is proud of it. Inside the top 10 accounts, every exec sponsor has turned over in the last 18 months.

The people answering the CSAT survey now are operational users who learned what answer to give to keep their CSM out of their inbox.

The score is real.

But the relationship underneath it has been hollowed out.

Why every metric on the slide has the same problem

Each metric on a CS leader’s board slide has the same problem in a different costume.

• NRR has been a target for the renewal team for two quarters.

• Logo retention has been a target for the CSM team.

• CSAT is reported by customers who learned what the system rewards.

• Adoption rate has been a target for the onboarding team and now reflects seat activation, not value realization.

Each one, the moment it became a target, started measuring the team’s effort to hit the number instead of the customer reality underneath it.

How the CFO smells the pattern before you do

A CFO who has done two budget cycles in SaaS can smell this pattern.

The way they see it is by asking the second and third follow-up question on the same metric.

If the answer gets softer each time, they have stopped trusting the slide. They will not tell you. They will quietly start scheduling renewal forecast reviews with the CRO instead of you.

If a CFO has asked you three questions about the same metric in a row and the answers got progressively softer, that metric is no longer telling the truth, and the CFO already knows it.

What changes when this system is in place

Three things shift the moment the system is in place.

1. Board reviews where every metric on the slide survives three follow-up questions, because the integrity check sits underneath each number before you walk in.

2. Renewal forecasts that hold their shape from the start of the quarter to the close, because the inputs to the forecast were never the gameable ones in the first place.

3. A reporting cadence that lets your team operate against the metrics that actually drive movement, without forcing those same gameable numbers to do double duty as the board narrative.

The metrics still belong on the slide.

The CFO still gets NRR, GRR, logo retention, CSAT, adoption.

What changes is the layer of work underneath each number, and what shows up in your voice when the CFO asks the second follow-up.

Why this work has to happen before your next board review

CS leader tenure is averaging 18 months. The fastest path to the next 18-month restart is a board that has quietly stopped trusting your numbers.

Most CS leaders find out this has already happened the week the CRO gets the renewal forecast meeting and they do not.

The work below starts with the audit that names which numbers on your current slide are already telling the CFO to stop trusting you.

It ends with the exact sentence you use when the second follow-up question hits.

Two ways to get this workbook

1. Upgrade to The CS Café paid subscription

The Board Metric Stress Test is included with your paid subscription, along with every workbook in the archive and every new operating system I publish every week. You also get direct email review on your renewal plans, QBR narratives, and exec updates before they hit leadership. Upgrade →

2. Buy the workbook 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