• Logins.

• Feature adoption.

• Session duration.

• Support tickets.

The data exists. It sits in dashboards, gets pulled into QBR slides, and shows up in monthly reports.

And still, accounts churn.

The conversation around connecting product data to CS data has been happening for years.

The consensus is settled: product telemetry matters. Nobody is debating that anymore. The real question is why teams that have the data still miss the signal.

The answer has nothing to do with the data itself but about what happens between the moment a signal fires and the moment a CSM acts on it.

Product data has a shelf life.

A usage drop that shows up on a Tuesday means something different than a usage drop you discover at next month’s pipeline review.

A feature abandonment signal that sits in a dashboard for three weeks while a CSM manually assembles the account picture is a signal that already expired.

The insight existed. The system to move it into action didn’t.

This is the assembly gap. It is the most expensive operational failure in Customer Success right now, and most teams have no idea they’re running it.

Here are the four ways it shows up.

1. The Scavenger Hunt

A CSM gets a flag. Usage dropped. Now what?

They open the product analytics tool. Then the CRM. Then the support platform. Then email. Then a spreadsheet where the real account notes live because nobody trusts the CRM fields.

Four to five systems.

Thirty to forty minutes per account. And by the time they finish assembling the picture, the signal that started the review is already days older.

Most “data-driven CS” programs die right here.

They solve the access problem and completely ignore the assembly problem.

Ask yourself: how many minutes does it take your team to go from “this account got flagged” to “I know what to do about it”?

If the answer is more than ten, your product data is decaying in transit.

2. The Dashboard Graveyard

Product signals move at the speed of user behavior. Daily. Sometimes hourly.

Most CS workflows run on weekly or biweekly rhythms. Monday pipeline reviews. Biweekly forecast calls. Monthly health audits.

A power user stops logging in on Wednesday. The CSM sees it the following Monday.

By the time they assemble the context and send outreach, the signal is over a week old. In mid-market and SMB, that window is already closing.

The dashboard did its job. It showed the number. The operational layer around it failed because nobody designed the workflow to match the tempo of the signals.

I covered why most health scores fail at the measurement layer in Your Health Score Is Lying to You. This post is about the layer that sits between measurement and action.

Even a perfectly designed health score is useless if the system around it can’t keep pace.

3. The Interpretation Bottleneck

A 40% drop in daily active users could mean four completely different things.

One requires executive outreach. Another requires product escalation. Another requires no action at all.

Raw product data can’t tell you which one you’re looking at.

And the layer of context that separates a real fire from a false alarm (support history, stakeholder mapping, contract timeline, recent communication patterns) is almost never attached to the alert when it lands on a CSM’s screen.

So they either overreact. Or underreact. Both responses erode trust. One with the customer. One with the renewal.

I broke down the qualitative decay signals that sit underneath product data in Silent Churn Detection: The QUIET Method.

Product data tells you what changed. The QUIET Method tells you why it matters.

4. The Action Gap

This is the most frustrating failure mode because it happens after the team did everything else right.

The data was pulled. The context was assembled. The signal was interpreted correctly. The CSM knows the account is at risk, knows why, and knows the timeline pressure.

Then they open a blank email and start writing from scratch.

Every intervention is a one-off. Every outreach is invented in the moment. The quality of the response depends entirely on which CSM happens to be working the account that day.

The teams that protect revenue consistently have eliminated this gap entirely. When the data says “act,” the system already has the play loaded.

The decision was made before the signal arrived. How they built that system is what separates a reactive book from a controlled one.

If your team is still running interventions as one-offs, the habits framework in 5 CS Habits That Prevent Renewal Surprises gives you the weekly rhythm to start systematizing.

What This Costs You

Every hour a CSM spends assembling data is an hour they aren’t in front of a customer.

Every day a signal sits unread is a day the customer’s internal narrative hardens without your voice in the room.

Those costs don’t show up on a renewal report. They show up 90 days later when the renewal conversation starts and the customer’s decision was already made six months ago.

Every week you spend running the scavenger hunt is another week your signals expire before they reach a CSM’s screen.

The leaders who closed this gap stopped assembling and started acting.

They run a system where the signal arrives scored, the context is already attached, and the play is loaded before the CSM opens their inbox.

Here’s what you’re building:

• Step 1 replaces your dashboard with a priority queue.

• Step 2 kills the scavenger hunt.

• Step 3 eliminates the blank email.

The Excel workbook is included. You can deploy it this week.

Read more

The replacement carries a new title, leading global client experience, professional services, and renewals.

The company didn’t eliminate the function.

It renamed it.

The Data Confirms It

This 2026 survey of 2,350 professionals puts a number on the pattern.

Chief Growth Officers outnumbered new CCO appointments nearly three to one.

At B2C companies, the gap was even wider.

Recruitment specialist Jodie Clayton at Major Players confirmed she hasn’t seen a new CCO role come across her desk in some time.

In a companion piece, nearly one in four brands said they are creating new positions specifically to redefine who owns the customer-facing function.

The question boards are asking has shifted from “who owns the customer?” to “who owns growth?”

That answer is increasingly a CRO or CGO, not a CCO.

The Function Is Rising. The Title Is Compressing.

The work CS owns is expanding.

Renewals, retention, NRR, expansion revenue, executive trust. Every one of those is growing in strategic importance.

Boards know it. CFOs know it. That is why companies keep hiring for this mandate.

But the label is losing ground.

When boards ask “who owns growth?”, the answer is increasingly a Chief Growth Officer, a Chief Revenue Officer, or a hybrid title that folds customer, revenue, and marketing under one umbrella.

The CCO title is being absorbed into broader commercial roles faster than it is being created as a standalone seat.

If you have been following the broader shift, I wrote about the bifurcation of the CS function three weeks ago.

The C-suite is pulling CS upward. Automation is replacing the bottom.

This week’s data adds a third pressure: the title itself is being absorbed into growth and revenue roles, even when the underlying mandate stays the same.

What This Means One Level Below the C-Suite

Why does this matter if you are a CS Director, VP, or senior leader who doesn’t carry a C-suite title?

Because the reorg conversation starts without you.

When your CEO or board decides to restructure the customer function under a CGO or CRO, the people one or two levels below that shift absorb the consequences.

Your reporting line changes. Your budget authority shifts. Your access to the executive team gets rerouted through someone whose priorities may differ from yours.

By the time you hear about it, the decision is already made.

The CS leaders who survive these shifts share one pattern: their work is already wired into how the company makes revenue decisions.

The title above them can change, the org chart can shuffle, and their function stays because removing it would break something the CEO and CFO depend on.

The leaders who don’t survive built their influence on proximity to a specific executive, a specific title, or a specific org structure.

When any of those moved, their influence moved with it.

If the role you’re chasing today looks more like an account management seat than a CS leadership seat, that vulnerability is already baked in.

This post gives you the system to make your work impossible to reassign, regardless of what the org chart calls the person above you.

The System

Below is the three-step system that CS directors and VPs use to make their function survive a reorg.

You'll know exactly where your influence is exposed, which of your metrics are invisible to Finance, and how to build the executive communication rhythm that makes removing your function visibly expensive.

Plus the Influence Durability Audit (Excel) that scores your current exposure automatically.

Read more

The title says “RVP, Agentic Customer Success Leader.” The compensation band is $230K to $350K. The function is Customer Success.

The job description says something else entirely.

It reads like a product engineering brief crossed with a management consulting mandate.

• Value engineering.

• Platform telemetry.

• Consumption-based P&L ownership.

• Customer Centers of Excellence.

• Real-time KPI dashboards replacing static QBR decks.

• Product roadmap authority driven by agent performance data.

This is the clearest signal yet of where CS leadership is heading. And five requirements buried in this listing reveal exactly why most CS leaders are building the wrong skill set for the roles opening above them.

The 5 Capability Shifts Hiding in This Listing

1. Value Engineering replaced relationship management

The role demands “proven ability to build financial models and business cases that quantify the impact of AI” and “continuous monitoring of these metrics post-deployment.”

Read that again.

• Financial models.

• Quantified impact.

• Continuous monitoring.

The executive sponsor who loved your QBRs retired. The new one wants a financial case that survives a CFO review. Relationship equity still matters.

It just stopped being sufficient.

The listing treats value engineering as a lifecycle discipline, running from pre-deployment business case through post-deployment ROI tracking.

That is a fundamentally different muscle than building a success plan after onboarding and hoping the renewal holds.

2. Telemetry fluency replaced health scores

The listing requires “expert ability to interpret platform telemetry and usage data to derive actionable insights” and being comfortable “talking data with engineers and talking value with CEOs.”

Your Gainsight dashboard is the floor.

The ceiling is reading raw agent performance data, correlating it to customer business outcomes, and translating that into both an engineering recommendation and a boardroom narrative. In the same conversation.

Most CS leaders can speak to executives.

But only a few can sit with an engineering team, interpret telemetry patterns, and direct feature prioritization based on what the data shows.

This listing requires both. Fluently.

3. Consumption P&L ownership replaced renewal ownership

This role “proactively manages the roadmap for contracted licenses and consumption credits” against “high-impact, mission-critical processes.”

Renewal rate is a lagging indicator. This listing measures success by the customer’s ability to fully utilize their investment.

That is a commercial operating model, not a retention metric.

It means owning a consumption-based P&L, forecasting utilization against contracted capacity, and building the roadmap that ensures customers hit their contracted usage before the renewal conversation even starts.

Most CS leaders own the renewal.

This role owns the commercial engine upstream of it.

4. Customer Center of Excellence architecture replaced onboarding

The listing calls for leading “C-suite stakeholders in building and nurturing internal CoEs,” training “Agent Champions,” and “empowering customers to independently iterate, govern, and scale their AI footprint.”

This is the opposite of the CS playbook most leaders run today.

The standard model: CS owns adoption, drives usage, holds the customer’s hand through each milestone.

This listing flips it.

The CS leader builds the internal capability so the customer can operate independently. You are designing the governance model, training the internal champions, and then stepping back so the customer scales without you.

The shift: from owning the customer’s adoption to architecting the customer’s self-sufficiency. CS leaders who still measure themselves by how much the customer depends on them are holding the wrong end of the lever.

5. Product roadmap influence replaced feature requests

The role “acts as the ultimate bridge” and “translates the operational realities of global supply chains and financial institutions back to Product and Engineering to ensure our roadmap solves real-world hurdles before they impact the market.”

Filing a feature request is a ticket. Product influence means directing engineering priorities with telemetry data the product team cannot see from the inside.

This listing requires someone who can take what they see in customer deployments, pattern-match across a global portfolio, and direct engineering priorities based on data the product team cannot see from the inside.

That requires domain expertise deep enough to identify the problem, analytical fluency sharp enough to prove the pattern, and executive presence strong enough to change the roadmap.

Most CS leaders have one of those.

The listing requires all three.

The Gap Nobody Is Scoring

Here is what makes this listing different from a unicorn job posting.

Every one of these five capabilities already shows up in fragments across CS leadership roles at mature SaaS companies.

• Value realization conversations.

• Data-driven health scoring.

• Consumption tracking.

• Customer enablement programs.

• Product feedback loops.

The difference: this listing treats them as integrated requirements for a single role. And it prices that integration at $230K to $350K.

Most CS leaders reading this can demonstrate strong performance in the job they have today.

The problem is that the job opening above them requires a fundamentally different operating model.

The leaders who fill roles like this will be the ones who started building these capabilities before the listing went live.

If you have already mapped which track your CS career sits on, you know whether these gaps are urgent or existential. If you have not, start here. If you want to go deeper on CS career positioning, I publish tactical career systems on TopCSJobs.

The scored self-assessment below tells you exactly where you stand across all five capability shifts, which gap to close first, and whether to build inside your current role or position externally.

The scorecard alone will tell you more about your next 18 months than your last performance review did.

This post continues for paid subscribers with the CS Leadership Readiness Scorecard, 90-Day Gap Closure Sequence, and Build vs. Position Decision Framework, plus the downloadable Excel kit.

Read more

Then you get on the call.

The first ten minutes are about pipeline. Then quota. Then commission structure. Then expansion targets.

The hiring manager keeps using the word “hunter.” Nobody mentions adoption or value realization.

The word “churn” comes up once, in the context of churn prevention as a sales play.

This is not a Customer Success role but just an Account Manager role with a CS title on top.

And it is happening more often than most CS leaders want to admit.

Why the title keeps getting misused

The mislabeling is not random. It follows a pattern, and it starts with a decision companies have not made.

When a company has not defined what CS actually owns, the role gets shaped by whoever has the most pressure.

If the CRO is pushing for more revenue coverage and does not want to add headcount to the sales team, the CSM role absorbs that pressure.

The title stays. The function changes.

The result is a role that carries CS expectations on the outside and sales expectations on the inside.

No clear base. High variable. Full accountability for expansion revenue. Minimal structure around onboarding, adoption, or outcomes.

There is a secondary driver too.

Some companies use the CS title because it attracts a different type of candidate than an AM posting would.

Candidates with relationship depth, technical credibility, and customer trust. Those are valuable traits for a revenue-generating role. The title is the recruiting mechanism. The job is something else.

This is a design failure, not a market trend.

The Venn diagram problem

CS and sales do overlap.

A well-run CS motion surfaces expansion signals, supports commercial conversations, and protects renewal revenue. That is not in dispute.

The issue is accountability.

In a real CS role, the CSM supports the commercial motion. In a mislabeled role, the CSM IS the commercial motion. The difference is where the accountability line sits and who carries the number.

When a company cannot answer the question “who is accountable for the sale versus who is accountable for the outcome,” the CSM role fills the gap.

Both. All of it.

Undefined comp. Vague title. High pressure.

That is the structure that produces the bait-and-switch experience.

The comp structure tells you everything

You do not need to wait for the job description to mislead you. The comp structure reveals the actual role before the first call ends.

• A CS-oriented role has a competitive base that reflects the complexity of the book of business.

  Variable pay is tied to retention, renewal, and expansion assist, not direct sales quota. The CSM is measured on outcomes the customer achieves, not transactions they close.

• A sales-oriented role dressed as CS has a low base with heavy variable.

  Top earners are held up as proof the comp works. The assumption baked in is that high performers will sell their way to a livable income.

  That is an AM structure. Calling it CSM does not change the accountability model.

If the recruiter cannot give you a clear base in the first conversation, you already have the answer.

What this costs everyone

For CS leaders: mislabeled roles generate bad hires.

• Strong CSMs who want to drive adoption and value will leave fast.

• Strong AMs who want to close and move on will struggle with the relationship depth CS requires.

The role ends up unfilled or perpetually churning through candidates who figured out the mismatch faster than the job description did.

For senior CSMs: taking a mislabeled role sets back the career narrative.

Eighteen months of commission-heavy expansion work does not tell the story of strategic CS leadership. It tells the story of inside sales. That affects the next job search, the comp trajectory, and the ability to move into CS leadership.

The cost runs in both directions. And neither side benefits from the mislabeling.

There is a third cost that does not show up in the hiring report.

When the CS role is built as a sales role in disguise, NRR becomes a lagging indicator of a structural decision made at hiring.

Churn gets blamed on the product. Expansion misses get blamed on the market.

By the time the number moves on the board slide, the design problem is eighteen months old and three hiring cycles deep.

That is the version of this problem that lands on the CEO’s desk. It rarely arrives with a clear cause attached.

The structural fix exists. It runs in both directions.

• CS leaders who get this right stop cycling through candidates who figure out the mismatch in month three. The hire stays. The role delivers.

• Senior CSMs stop trading eighteen months of their career narrative for a commission structure that was never built for CS.

Below, I walk through both.

The CS Role Design Scorecard gives CS leaders the accountability split and comp structure to build before the job posting goes live.

The Pre-Interview Audit gives senior CSMs five questions that reveal the real role in the first thirty minutes before they commit.

Read more

The CS community will celebrate it. Another senior appointment. Another signal that CS is getting its seat at the table.

Read the actual brief before you celebrate.

Cowen’s mandate at Entrust covers customer success management, technical support, and professional services.

All of it. Reporting directly to the CEO.

Her stated focus: driving measurable outcomes that produce long-term customer retention and growth.

Her own words: “Customer success is built on trust and partnership, but it’s measured through the outcomes we help our customers achieve.”

That second sentence is the brief. And it is not the brief most CSMs are currently operating against.

This is the second major signal in two weeks.

SAP merged its Customer Success and Customer Services organizations into a single board-level unit under a Chief Customer Officer with the same commercial mandate.

Two separate companies. Two separate sectors. The same structural decision.

A pattern is forming.

CS is being handed the full post-sale revenue motion and told to own outcomes, not just relationships.

The function is not being leveled up in the way most CSMs picture it.

It is being redefined around a commercial standard that the majority of the CS workforce has never been formally evaluated against.

The appointment itself is not the story. What happens to the CSMs sitting underneath a leader with this mandate is the story.

When a company hires an SVP of CS with ownership of support, services, and a growth brief, the evaluation lens for every CSM on that team shifts.

Activity metrics lose weight. Meeting counts stop mattering.

The question that gets asked in every review, every QBR debrief, every renewal conversation is the same: what did this CSM produce that moved retention or growth?

CSMs who are already operating commercially, controlling renewal timelines, surfacing expansion signals before sales does, building exec relationships that produce decisions rather than updates, are positioned for this shift.

Their work already answers that question.

The CFO-level renewal framing most CSMs still treat as advanced is the baseline in the model these leaders are building.

The CSMs still operating on the old brief are facing a harder reality.

The new standard does not announce itself.

It arrives in the form of a new manager with a different lens, a restructured comp plan, and a set of expectations the team has never been formally prepared for.

Most CSMs will read the Entrust announcement and move on.

The ones paying attention will ask a different question: when a leader with this brief reviews my book next quarter, what does she see?

If the answer is uncertain, that uncertainty is the risk.

The standard has shifted.

The gap between where you operate today and where Cowen’s brief sets the bar is closeable.

The CSMs who close it do not get reevaluated. They become the example used to evaluate everyone else.

Inside is the system to get there: a scored diagnostic that shows you exactly where you stand, a 60-day account-level playbook to shift what leadership sees, and a visibility framework that makes your contribution the one that requires no translation.

The CS Commercial Brief Toolkit runs all three.

Download it once. Use it every quarter →

Read more

Eight months to renewal. You pull the usage data, prep a recovery plan, and walk in ready to turn things around.

The customer is polite. They answer your questions. They agree to next steps on the call.

Then nothing happens.

The follow-up sits unanswered. The plan stalls. And three months later, the account is still flat.

The sequence was wrong before you dialed in.

The assumption that kills re-engagement calls

Most CSMs walk into a low-engagement account review treating adoption as the problem to fix.

It is a symptom.

The actual problem sits one layer deeper, and until you surface it, every recovery plan you build lands on sand.

Low engagement traces back to one of three root causes. Each one requires a completely different response:

• The problem they bought to solve has changed.

  The use case that justified the purchase is no longer a priority. The product is still there. The urgency behind it is gone.

• The champion who owned it internally has left.

  Nobody replaced them. The tool kept renewing on inertia, but there is no one inside the account who cares whether it succeeds.

• Nobody has ownership of the tool.

  It was purchased at the leadership level and handed down with no clear owner. Everyone assumes someone else is driving it.

These are not versions of the same problem.

A champion departure requires a different conversation than a shifting use case.

A tool with no internal owner requires a different escalation path than one whose business problem evolved.

Running the same re-engagement play across all three is how you spend time on accounts that were never going to recover.

What most CSMs skip before the call

There is a step that happens before the re-engagement conversation that almost nobody takes seriously: the pre-call audit.

Five minutes. Three questions.

1. What signals in the account actually changed, and when?

   Usage drop, champion departure, support volume, exec engagement history.

   Pick the sharpest one.

2. What do you know versus what are you assuming?

   A brief handoff and a usage dashboard are not the same as context. Know the gap before you walk in.

3. What is the one thing you are not going to assume in the room?

   Low adoption has a cause you have not confirmed yet. Park the recovery plan until you know which one it is.

CSMs who skip this step walk in with answers to questions they have not asked yet.

The customer can feel it. The call becomes a presentation to a room that has not decided it wants to be saved.

The wrong question anchors the wrong call

Most re-engagement calls open on adoption

Usage is down. Here is what we can do about it. Here is a 30-60-90 day plan.

A 30-60-90 built before you have surfaced the root cause is not a plan. It is a guess with formatting.

And customers at low-engagement accounts have already had several of those conversations. They know what they look like.

The right opening question has nothing to do with the platform.

It is about what a successful year looks like for their team. That question tells you whether there is a priority to attach to, an owner to build with, and a reason to stay.

Without those three things, no recovery motion will hold.

Related: What Does Your CSM Say When the Churn Flag Fires?

Leading with renewal risk makes this worse

Eight months feels long until the quarter turns. Making a customer feel like a retention problem in the second meeting kills the relationship before it starts.

The goal of the re-engagement call is not to save the account. It is to find out if saving it is possible, and in what sequence.

Related: How Top CSMs Make Renewals Boring

The gap nobody is addressing

Diagnosing the root cause tells you what you are dealing with. It does not tell you what to do next.

That depends on one question most re-engagement content skips entirely: is recovery viable at all?

Some accounts are not recoverable.

The problem changed, the champion left, and there is no exec awareness of the risk.

Running a full re-engagement play on that account costs time you could be spending on accounts that can actually move.

Before you build a plan, you need a way to score what you are hearing. A structured method for qualifying recovery potential. And a clear decision on what happens when the score says no.

That is what the paid section covers.

Related: The Engagement OS: Turn Post-Sale Into Renewal Control

Paid members get the three-step re-engagement system, the scoring tool, and the exact sequence for what to do when the account cannot recover.

Including the Account Recovery Diagnostic Scorecard and the conversation most CSMs avoid entirely.

Read more

One of the first hires on the list: Customer Success, focused on Fortune 500 clients.

Somewhere in that org, a CS leader just inherited a problem they didn’t see coming.

That’s not cynicism. It’s pattern recognition.

Funding rounds don’t just add runway. They add pressure to close, and that pressure lands in your book of business 90 days later.

Here are the three structural realities CS inherits every time a raise closes.

1. The sales motion shifts before CS knows about it

Pre-raise, sales closes whoever will sign.

Quotas tighten, discounts flow, and ICP discipline loosens.

The logic is simple: hit the numbers that justify the round, then fix fit later.

CS gets those accounts later with no flag on which ones were exceptions. Bad-fit customers don’t arrive labeled as bad-fit.

They arrive looking like any other new logo, until month six, when the support tickets start stacking and the success plan has no traction.

2. Onboarding gets de-prioritized at the exact wrong moment

Headcount goes to AEs and SDRs first.

CS stays lean while volume spikes. The gap between “closed” and “fully onboarded” widens, and that gap is where churn starts.

A $1M account that never completes onboarding is not a customer. It’s a countdown.

That dynamic is more predictable than most CS teams want to admit.

3. Executive expectations reset without CS in the room

New board members want ARR velocity. The CRO responds to that pressure.

CS is left managing customers whose success metrics were never aligned to what the company promised them.

The customer signed a vision. CS is handed the reality.

The churn wave doesn’t show up on renewal reports for 12 to 18 months. By then, the raise is old news and CS owns the number.

If you want the system for surfacing that risk before it surfaces you, this is the starting point.

The accounts are already in your book. The question is whether you have a system to score them before they score you.

Paid members get the full 3-step post-raise risk audit below, including a scoring workbook that RAG-rates every account in your book, sequences the right intervention by tier, and flags escalations automatically before they hit your renewal pipeline.

Read more

Most CS leaders have not named that gap yet. Cisco just named it for them.

On April 7, Cisco published a blog post introducing a centralized Customer Success resource center on their company website.

Self-serve adoption guides. AI-powered search. Video tutorials. And Renew.Cisco.com, described as “a seamless way to view, manage, and order renewals.” The language is customer-facing. The implication is structural.

Cisco just automated the renewal layer. And they named it publicly.

This is not a cost-cutting move. It is a capability architecture decision made by one of the largest enterprise technology vendors in the world.

The transactional layer of CS, the onboarding nudges, the adoption check-ins, the renewal processing, is now a product.

What remains above it has to be built deliberately.

If you have not yet mapped which track your role sits on, start with The CS Career Split: Elevation Track or Automation Target.

“Strategic CS” is not a posture. It is an operating gap

Most CS leaders who operate above the transactional layer get there on instinct.

Strong exec relationships. Sharp risk reads. The ability to hold a hard commercial conversation without blinking. That instinct earned the position. It will not protect it.

Instinct is not a system.

And when the automated floor starts absorbing what used to fill the calendar, what’s left has to be explicitly defensible.

Leadership does not ask “are you strategic?” They ask “what did CS produce this quarter that the platform could not?”

Most CS leaders do not have a clean answer to that question. The strategic value was real. The evidence for it was not built.

Three surfaces where the gap becomes visible

The gap does not show up in a performance review.

It shows up in three specific places, and by the time it is visible there, the window to fix it has already narrowed.

1. The first is the renewal conversation.

Most CS teams are still entering renewal quarters without a commercial narrative.

They have data. They have relationship history.

They rarely have a sequenced argument for why the contract value is justified, why the switching cost is higher than the customer has modeled, and why the next 12 months represent a compounding return rather than a repeated fee.

That argument has to be built upstream, not assembled under pressure.

2. The second is the QBR.

A QBR that reports outputs is not a strategic asset.

It is a status update with better slides. The exec sitting across the table does not need a recap of what happened.

They need a decision to make and a recommendation they can act on. The renewal risk hiding inside healthy-looking accounts is often the direct result of QBRs that report instead of drive.

3. The third surface is the exec relationship itself.

Most CS teams have exec access.

Fewer have exec relationships that generate expansion signals, surface political risk before it reaches procurement, or create internal sponsorship when a renewal hits friction.

Access and relationship are different things.

The difference is whether the exec calls CS before something becomes a problem, or only after.

These are system gaps.

They surface precisely when the automated layer beneath is working correctly, recovering CS capacity, and leadership starts asking what that capacity is being redirected toward.

The org-level risk CS leaders are not naming

Individual CSMs doing transactional work get displaced. That story has been told.

The story that has not been told is the leadership version.

CS leaders who fail to build a strategic operating model above the automation floor get restructured.

The automation floor does not just eliminate CSM headcount. It removes the justification for a CS leadership layer that cannot articulate what it produces above the platform.

Cisco’s blueprint is not a warning for CSMs alone.

Every VP and Director should read it as a preview of the audit their own leadership will run inside the next 12 months.

The question is whether CS has built something above the automation floor that leadership can see, sponsor, and defend to the board.

Most CS organizations have not. The strategic work is happening. The proof of it is not being built.

The automated layer is being built around you. The strategic layer above it has to be built by you.

Deliberately. Repeatably. In a format that leadership can read without asking follow-up questions.

Three places to start, depending on where you are right now:

1. If you have not mapped which track your current role sits on, the diagnostic is here: The CS Career Split: Elevation Track or Automation Target.

2. If your renewal conversations are starting too late and without a commercial narrative, the upstream system is here: The Enterprise Renewal System.

3. If your QBRs are reporting outputs instead of driving decisions, the architecture fix is here: Stop Counting QBRs. Start Counting Decisions.

The automation floor is not arriving. It is already being installed.

The CS teams that survive the next reorg are the ones building above it now, with systems, not instincts.

Hakan, Founder | The CS Café

The issue is the positioning.

Customers who have only ever experienced you as operational support hear one thing when you pitch a more strategic meeting: “we want more of your time so we can upsell you.”

That suspicion kills the transition before it starts.

You are talking to the wrong person

Monthly check-in contacts handle operational concerns. They care about what is broken today. They have no stake in a 12-month roadmap conversation.

The QBR audience is the person who signs the contract.

That person cares about business outcomes, risk, and spend. They are almost never in the monthly check-in.

The transition stalls when CSMs try to level up the conversation with the wrong person in the room. You cannot get a strategic outcome from an operational contact.

That is a structural problem, and a new agenda does not fix it.

The trust sequence is out of order

A strategic conversation requires a foundation of operational credibility first.

If customers experience you as a reactive support contact, they will treat you as one.

The shift from ticket-closer to trusted advisor happens because the customer has watched you solve their problems consistently, bring them something they did not ask for, and show up with evidence rather than questions.

Most QBR transitions skip this step entirely.

CSMs get a directive to run QBRs by end of quarter. They pitch the new format to accounts that have no reason to trust them at that level yet. Customers say yes on the call and disappear on scheduling.

That is a trust gap. A better calendar invite does not close it.

What customers actually hear

“I want to understand your goals” lands as: please do my job for me so I can fill out my template.

“I would love to set up a QBR” lands as: longer meeting, unclear upside, probably a pitch.

Customers with operational pain read every new meeting request through one filter: what does this cost me and what do I get back? If the answer is not immediately obvious, they deprioritize it.

Bring a specific hypothesis instead. Show usage data. Name the risk or the opportunity. Give them something concrete to react to.

That is how you earn the meeting.

The metric is making it worse

When QBR count becomes a KPI, CSMs optimize for the easiest version of done.

They chase low-resistance accounts. They hold meetings that look like check-ins with a new name. They build decks that nobody reads.

Signal gets worse. Teams get cynical. Customers feel the chase and pull back further.

QBR count measures activity. It does not measure whether a decision was made, a risk was named, or a path to expansion was opened. Those are the outcomes that protect revenue.

The question worth asking internally:

Where are you creating measurable impact, and how often are you having those conversations?

Get that right and the meetings take care of themselves. If your team is currently measured on QBR volume, this post covers how to redesign those KPIs without losing renewal visibility.

Paid members get the full execution system below, plus the QBR Transition Workbook to run it without building anything from scratch.

The workbook scores your accounts automatically, tracks each one through the 90-day sequence, and builds a decision-ready agenda before every QBR.

Open it, add your accounts, and you know exactly where to focus this quarter in under 30 minutes.

Read more

L&G. Federato. InStore.ai.

Two of the three are newly created roles.

Every single mandate is the same: revenue delivery, customer outcomes, account expansion. This is a signal.

Revenue risk now lives inside CS. That is why CS is being pulled into the C-suite.

• The renewal.

• The expansion.

• The executive relationship that determines whether a $500K account becomes a $1.2M account or a churn notice.

All of it is sitting inside CS. Boards and CEOs are responding to that reality by putting a commercial operator at the top of the function.

The CCO is becoming the owner of the revenue engine, not the service layer.

Look at the language in the announcements.

• Federato hired Tim Mossing to “scale customer delivery and long-term outcomes.”

• L&G created the role specifically to deliver a better-connected experience across retail and institutional retirement.

• InStore.ai hired Kevin Farley to lead frontline customer intelligence across its entire commercial operation.

These are commercial briefs. Every one of them.

The shift is real. It is accelerating. And it is attached to a specific kind of CS leader.

Now the other half of this week’s story.

While three CCOs were being appointed, , Founder & CEO of @SaaStr, published a piece claiming their AI agent outperforms 95% of human CSMs.

The piece is provocative. It is also directionally correct.

Reactive CS work is being automated.

• Check-in calls with no clear agenda.

• Manual health score reviews.

• Status update emails.

• QBR prep that starts two weeks before the meeting.

• Low-signal touchpoints that consume calendar time and produce no commercial movement.

AI handles that work better, faster, and without fatigue.

So the function is doing two things at once. It is being pulled upward at the top. It is being automated at the bottom. The space in the middle is compressing.

This is the bifurcation.

One track leads to the C-suite. The other is being replaced.

Every CS professional reading this is on one of those tracks right now, whether they have named it or not.

What separates them is not seniority. It is not years of experience. It is not whether you are liked by your accounts.

It is a specific set of operating behaviors.

The behaviors that separate the two tracks are specific and learnable.

The paid section below shows you exactly how to build them, and a scored diagnostic tells you where to start.

If you are already a paid subscriber, keep reading.

If you are on the free tier: the diagnostic alone will tell you more about your career trajectory than any performance review you have had this year.

Read more

It was made in a room you were never in, when the customer quietly arrived at four conclusions at the same time:

• The use case was simple enough to rebuild,

• The contract was expensive enough to question,

• Too few senior people would feel real pain if the vendor disappeared,

• And nobody had made the relationship important enough to defend.

What lands as a sudden loss is a late reveal of a conversation that was already over.

Low escalations. Decent usage. No champion turnover. The health score sitting comfortably in the green.

None of it mattered because when those four things are true at once, software quality is almost irrelevant.

The product got you in. The account strategy is what keeps you there.

The question most post-sale teams are still getting wrong

The instinctive response to this risk is to ask: how do we work for products customers cannot replace?

That question points in the wrong direction.

Many useful software can be rebuilt badly, partially, or “well enough” by an enterprise with budget, engineers, and patience.

That pressure is accelerating. As AI changes how fast software gets built and how thoroughly buyers evaluate the total cost of ownership, the gap between “good product” and “safe renewal” is getting wider, not narrower.

The sharper question is: how do we make the account hard to remove, even when the customer has the ability to build?

If your only defense at renewal is “the product is good,” you do not have much of a defense. A CFO evaluating that contract does not think in feature terms.

And the accounts that survive a serious build-vs-buy conversation are never the ones where the product was just well-adopted.

They are the ones where the account strategy built something that the product team never could.

What actually protects an account

The accounts that survive internal replacement pressure often have four distinct layers in place.

Most vulnerable accounts have one, maybe two.

Operationally embedded

The product is part of how work gets done.

Not just liked. Woven into workflows, handoffs, approvals, reporting, and team habits. Real history lives in the system. Dependencies have formed around it.

Removing it would interrupt work, not just change a login.

This is where a lot of CS teams confuse adoption with protection. They are not the same. A product can be used every day and still be easy to replace.

The question is more than just about whether teams are active inside the product. It’s rather if the work survives without it.

Commercially defended

The value is connected to money, risk, speed, or continuity.

• Not “they love the dashboard.”

• Not “feature adoption is healthy.”

• Not “NPS is up.”

That is exactly why CFO-level renewal pressure keeps catching teams off guard.

If the value story lives at the activity layer, it will not survive a cost conversation.

Protected accounts have a cleaner answer: what cost rises if you leave, what risk returns, what workflow slows down, what revenue or retention outcome gets harder to sustain.

That is the language that travels upstairs and holds under pressure.

Politically protected

At least one executive would push back if someone proposed replacing you.

Not out of loyalty.

Because removing you would create a problem for them personally.

This only happens when the team has built real stakeholder coverage, not just a warm relationship with one champion. The equal-coverage trap is part of what quietly undermines strategic accounts.

The accounts with genuine replacement risk do not need polite consistency. They need deliberate pressure across the stakeholder map.

Future-relevant

The customer believes staying will keep outpacing whatever they could build internally.

This is the layer most teams miss.

An account can be embedded today and still become vulnerable if the customer starts to believe the product is no longer moving fast enough to justify the contract.

Protection is not only about the pain of leaving. It is also about the cost of falling behind. Both have to be true.

The signal most teams catch too late

Internal replacement almost never appears without warning.

The signals show up earlier.

• Engineering starts asking deeper API questions.

• Data export requests become more specific.

• Budget conversations shift from outcomes to total cost of ownership. Your champion stops sounding decisive.

• Roadmap interest drops while architecture questions rise.

• Technical stakeholders you have never met appear late in the conversation.

• Procurement starts driving things it was not driving before.

None of these signals means churn by itself.

Together, they often mean the account has moved from “how do we use this better?” to “how hard would it be to replace this?”

That is a very different internal conversation.

And if your team is not built to detect it early, you will be running a standard renewal motion on an account that is already evaluating alternatives.

The mistake that accelerates the problem

When quiet replaceability rises, most teams do more of the same.

More check-ins. More recap emails. More feature education. More QBR polish.

That is the wrong response.

You do not protect a strategic account from replacement risk by increasing activity.

You protect it by increasing consequence.

• Wider stakeholder coverage.

• Deeper workflow integration.

• A sharper commercial case for staying than for rebuilding.

• A proof layer that shows business pain, not product usage.

That is the gap in most proof-of-value systems.

Most teams are still proving that users touched the product. The accounts that hold under pressure are the ones where CS has already proven that removing the product creates business pain that someone senior would have to own.

Motion does not protect accounts. Consequence does.

The one principle worth carrying

Apart from when they love the product, customers keep vendors because removing them creates more pain than keeping them.

That is the actual standard.

And it is why your product does not need to be irreplaceable.

Your account strategy does.

If you are carrying a strategic account right now that looks clean on paper but would fold quickly if finance and engineering sat in a room together for an hour, what follows is built for exactly that problem.

Below is the full operating system, including a downloadable Excel scorecard that ranks your entire book of business by replacement risk, auto-calculates each account’s tier, and tells you where to act first.

Read more

Usually, they have a system problem.

Ask what should exist because a CSM touched an account.

Not what they said in meetings. Not how responsive they were. Not whether the customer “felt supported.”

What should actually exist?

A plan. A risk view. A stakeholder map. A value narrative. A renewal path.

If those artifacts are missing, inconsistent, or trapped in someone’s personal notes, you do not have a CS operating system.

You have helpful chaos.

The Fastest Way To Spot A Weak CS System

The sign is simple.

Strong CSMs often compensate with instinct, memory, and extra effort. That creates false confidence for leadership. The team looks functional until scale, turnover, or renewal pressure exposes the gaps.

When only your best CSMs can run an account well, that is not maturity.

That is dependency.

The question is whether the work becomes visible in a form that the next person could inherit, inspect, and improve.

If the answer is no, you do not have best practices.

You have isolated talent.

Not Every CS Deliverable Deserves Attention

Before I go further, one clarification.

This is not an argument for more documentation. Most CS teams already have too many half-filled templates that nobody looks at.

The point is to standardize the few artifacts that actually change account outcomes: the ones that reduce ambiguity, shorten ramp time, and give leaders something to coach against.

Good artifacts make the work real. They make it teachable. They make it survivable when your best CSM leaves.

That is artifact discipline, and most teams do not have it yet.

The goal is not more documents but fewer, better ones that the whole team can produce consistently.

If I had to reduce Customer Success to seven core artifacts, these are the ones I would keep.

The 7 Artifacts That Make Customer Success Real

1. Onboarding Plan

If onboarding lives in someone’s head, the account is already exposed.

An onboarding plan is a clear, structured document that defines milestones, owners on both sides, dependencies, timeline, and the first meaningful proof of value, not just training completion.

This is where preventable churn often starts.

When onboarding lacks structure, ownership gets fuzzy, timelines slip, and customers drift before they ever fully land.

It should define who owns what, what “live” actually means, and when the customer should see their first result.

What good looks like: named owners on both sides, key milestones and dates, critical dependencies called out, a clear definition of what “live” means for this customer, and a first value milestone that is specific enough to celebrate.

Common failure mode: treating a kickoff call like a plan.

2. Success Plan

A success plan is where product usage becomes business logic.

A success plan is a living document that connects customer goals to the outcomes, use cases, adoption motions, and checkpoints required to achieve them.

It is not a list of tasks. It is not a feature rollout tracker.

Without a success plan, adoption becomes motion without direction. Customers use the product, but no one can explain whether it is moving the business forward. That ambiguity is how renewals start slipping quietly.

The success plan should exist early in the lifecycle, once the team understands what the customer is trying to accomplish and what success means in their world.

What good looks like: clear business goals, measurable desired outcomes, use cases tied to those outcomes, owners and timelines, and a defined review cadence.

Common failure mode: calling a task tracker a success plan.

3. Stakeholder Map

If your strategy depends on one friendly contact, you do not have coverage.

A stakeholder map is a structured view of who matters on the account, what they care about, how much influence they hold, and where support or resistance sits.

CS teams often believe they know the account because they know the day-to-day contact. That is not account coverage.

Renewals are often decided by people the CSM barely knows. Expansions stall because no skeptic has been identified. Risk increases because no one mapped who could pull the plug.

The stakeholder map should exist early, then get updated when stakeholders change, priorities shift, or executive sponsors appear or disappear.

What good looks like: economic buyer, executive sponsor, power users, blockers or skeptics, preferred communication style, and role in the renewal or expansion decision.

Common failure mode: confusing access with influence.

4. Decision And Action Recap

A good recap protects momentum. A weak one wastes the meeting twice.

A decision and action recap is a short, high-quality written summary after important meetings that captures decisions made, commitments given, owners named, deadlines set, and items still open.

This is one of the most underrated artifacts in CS.

It creates accountability on both sides, reduces drift between conversations, and gives the customer a clear record of what was agreed. It also surfaces risk early because writing it down forces clarity.

It should exist after onboarding calls, risk reviews, executive meetings, roadmap discussions, and any meeting where clarity matters.

What good looks like: what was decided, what remains open, who owns what, dates and next milestones, plain language, no bloat.

Common failure mode: sending polished recap emails that document conversation but not commitment.

5. Risk Register

Risk gets ignored fastest when it stays vague.

A risk register is a structured internal view of adoption gaps, stakeholder concerns, product blockers, commercial pressures, support patterns, and timeline risks for the account. It is a live record, not a one-time flag.

Most churn does not arrive as a surprise. It arrives undocumented first.

Teams notice the signals but leave them in call notes, Slack threads, and gut feel. By the time the account is formally escalated, the risk has often been visible for months.

The risk register should exist continuously for managed accounts, and especially as the renewal window approaches or adoption weakens.

What good looks like: specific risk statement, evidence behind it, severity level, current impact, mitigation owner, next action, date to reassess.

Common failure mode: labeling an account yellow without a real risk statement behind the color.

6. QBR Or EBR Narrative

The best reviews do not report the quarter. They shape the next one.

A QBR or EBR narrative is a structured review built around business progress, outcome movement, honest friction, and the decisions required from both sides going forward.

Too many reviews are still activity theater.

The CSM presents product usage, the customer nods, and everyone leaves no clearer on whether the partnership is actually working. A real QBR gives leadership a reason to trust the relationship and a reason to continue investing.

This artifact should exist before formal business reviews, renewal approaches, major stakeholder transitions, and any moment where executive alignment matters.

What good looks like: reminder of original goals, what changed since the last review, business outcomes rather than usage charts, honest friction and risk, smart recommendations, and clear next-step decisions.

Common failure mode: presenting product activity as proof of value.

7. Renewal Plan

A renewal should never suddenly become risky.

A renewal plan is a forward-looking document that covers renewal timing, the stakeholders involved in the decision, value proof points, commercial risks, internal support needed, and the action path required to reach a clean close.

Renewals go sideways when teams manage the date instead of the decision process.

The renewal plan forces the team to work the account before urgency forces their hand.

It should exist well before the renewal date, with more structure for larger, riskier, or more strategic accounts.

What good looks like: renewal date and decision milestones, stakeholders involved in approval, value proof points, open risks and objection areas, internal support needed, and a clear owner for each next step.

Common failure mode: beginning renewal planning only when procurement enters the picture.

Which Artifacts Should Be Shared And Which Should Stay Internal

Not every artifact belongs in front of the customer in its raw form.

Strong CS teams do not share everything. They translate everything.

The customer needs alignment. The internal team needs clarity. Those are different documents serving different purposes, and conflating them weakens both.

• Customer-facing or shared: onboarding plan, success plan, decision and action recap, QBR or EBR narrative, and parts of the renewal plan.

• Mostly internal: risk register, stakeholder map, and the internal renewal strategy.

The customer version of the renewal plan might show value proof and next steps. The internal version shows the objections you are preparing for, the stakeholders you are managing around, and the commercial risk you have not surfaced yet.

That separation is not politics. It is professional account management.

What Leaders Need To Standardize Before They Ask For More Strategic CSMs

The seven artifacts above are what a strong CSM should produce. Producing them consistently across a team is a leadership problem, not a hiring concern.

If the standard lives only in your top rep’s head, it is not a standard.

Before asking for more strategic CSMs, leaders need to define which artifacts are mandatory by segment, when they must exist in the lifecycle, what good looks like, where they live, who owns them, how they are reviewed, and what gets updated before a renewal, QBR, or escalation.

You cannot coach consistency against vibes.

You coach it against artifacts.

Customer Success Feels Fuzzy When Nothing Durable Gets Produced

Customer Success gets dismissed fastest in companies where the work disappears into conversations, instincts, and good intentions.

That is why artifact discipline matters.

Revenue protection, executive trust, and renewal control depend on a small set of outputs being produced clearly and consistently.

It becomes easier to inspect when the work is visible. It becomes harder to dismiss when it leaves durable proof behind.

If your CSMs cannot produce these seven artifacts well, the issue is bigger than enablement.

The system is still too loose.

And loose systems are exactly where churn, surprises, and internal mistrust like to hide.

Related Reads

• Why Most Customer Health Scores Are Meaningless

• Why QBR Count Is A Bad KPI

• The 4-Part Renewal Narrative For CFO-Level Scrutiny

• How A Standardized Engagement System Sits Underneath These Artifacts

The CS Artifact System: Templates You Can Deploy On Real Accounts

The harder part is building them under pressure, on messy accounts, with stakeholders who do not read long documents and timelines that are already too tight.

Most templates do not account for that. They are too clean, too hypothetical, and too far from what a CSM faces when an account is drifting, and a renewal is six weeks out.

Paid members get the working system behind all seven artifacts. Built to surface risk early, control the renewal path, and give leaders something to coach against:

• Onboarding plan template

• Success plan template

• Stakeholder map

• Risk register

• QBR narrative structure

• Renewal plan worksheet

• Meeting recap format

I designed each one for real account conditions, not clean textbook ones.

One CSM with a renewal plan and five without one is not a CS operating system. Group subscriptions are available for teams of three or more at 20% off, because artifact discipline only compounds when the whole team has it.

Read more

Usage looks stable. NPS came back at a 7. Three meetings logged last quarter. Exec sponsor replied to the last email.

Two weeks later, the account churns.

The CSM wasn’t incompetent. The health score wasn’t hacked.

It just measured the wrong things with complete precision. Nobody caught it until the cancellation notice arrived.

This is the most expensive blind spot in Customer Success right now. Most teams have no idea it's there until the cancellation notice arrives.

And when it does, the reason is almost always the same:

The health score was built to be easy to maintain, not hard to fool.

The Three Types of Broken Health Score

Name what you’re dealing with before you try to fix it.

Most broken health scores fall into one of three categories.

1. The Vanity Score

Built around engagement metrics because they’re easy to pull from the CRM.

Logins, email open rates, meeting counts, NPS. All visible. All exportable. None of them reliably connected to whether the customer is achieving anything.

The Vanity Score looks like a dashboard. It behaves like a decoration.

2. The Gut Feel Score

CSM-weighted, which means it reflects relationship warmth.

It’s a CSM’s greatest strength, and in this context, their biggest liability. The score trends green when the relationship feels warm. It trends red when the CSM is anxious.

This produces one consistent outcome: the accounts that churn are usually the ones nobody was worried about, because the relationship felt fine right up until it didn’t.

3. The Frankenstein Score

Built by committee.

CS wanted adoption metrics. RevOps wanted CRM activity. Product wanted feature usage. Leadership wanted NPS.

Everyone got a field. Nobody owns the logic.

The result is a score that changes meaning depending on who’s reading it and what narrative they need to tell.

Each one fails differently. But they all share the same root problem.

The Proxy on a Proxy Problem

A login doesn’t tell you if the user accomplished anything.

• NPS tells you how someone felt on a Tuesday.

• Email open rates tell you about your subject lines.

• Support ticket volume tells you about your product’s friction, not your customer’s outcomes.

These are all signals that are one or two steps removed from the thing you actually care about: whether the customer is getting measurable value from the product.

When you stack proxies on top of proxies and call the result a health score, you get a number that is internally consistent but externally meaningless.

Green accounts churn. Red accounts renew.

And your CSMs spend 20 minutes pulling usage data, checking in with the AE, and reviewing account notes every time the score moves, because the score triggers a scavenger hunt instead of an action.

The signal problem is only half of it. The other half is timing.

Most health scores are built on lagging indicators. They tell you what already happened.

A customer can look perfectly healthy in your dashboard for 60 to 90 days while the real churn signal, the one a tool cannot capture, is already in motion.

What Qualitative Decay Actually Looks Like

The most predictive churn signals are not in your CRM.

They live in the texture of the relationship, and experienced CSMs feel them long before any dashboard reflects them.

Call it qualitative decay. It looks like this:

• A champion who used to ask forward-looking questions about the roadmap stops asking. They stop pushing for new integrations. Their replies get shorter.

• In QBRs, the energy shifts from “what’s next” to “this is fine”, and that shift from curiosity to comfort is one of the clearest early warning signals in Customer Success.

• The internal advocate who used to cc colleagues on your emails quietly stops doing it. Their internal selling has gone dark. You still have access. You have lost reach.

The renewal conversation where the customer says “let’s just keep it the same.” That phrase sounds cooperative. It is inertia language, not value language.

A customer who is genuinely getting value from the product does not want to keep it the same. They want to do more.

These three signals have nothing in common with login data. They have everything in common with how a customer relationship actually ends.

The problem is that no health score in any tool today is built to capture any of this.

Which means the most reliable predictor of churn is sitting entirely outside your scoring system, dependent entirely on whether your CSM notices it and logs it somewhere.

This is why at-risk account frameworks need to sit alongside your health score. Not replace it, but cover the gap that the score structurally cannot fill.

What Actually Predicts Health

Stop asking “Is this account healthy?” Start asking, “Is this customer getting outcomes?”

The distinction matters because health is a state, and outcomes are a trajectory. A state can look fine while the trajectory is declining. Outcomes force you to answer a harder question.

Three outcome anchors that actually predict renewal direction:

1. The First Value Moment

Did the customer hit it, and how long did it take?

Time-to-first-value is one of the strongest leading indicators of long-term retention. Customers who take too long to reach their first meaningful win rarely recover the momentum.

2. The Recurring Value Motion

Are they using the features that deliver the outcome they bought for, consistently, not just at onboarding?

Shallow usage that covers only the most basic functionality is a risk signal even when the login count looks healthy.

3 The Expansion Signal

Are they asking for more, or just maintaining?

A customer who is genuinely getting value asks questions about what else is possible. A customer who is staying out of inertia goes quiet.

Underneath all three is a question most CS teams fail to answer cleanly at kickoff: did the customer ever define what success looks like?

If they didn’t, every health score you build is measuring activity against a blank target.

Fix goal identification at onboarding, and your health score immediately becomes more predictive, because now it has something real to measure against.

The structural issue with most health scores is this: they were designed to be reportable, not actionable. A score exists to answer one question: what do I do next?

If your score doesn’t produce a clear answer to that question, it’s not a health score. It’s a status update.

This connects directly to renewal risk systems that surface problems early. Goal clarity at onboarding is what gives your risk scoring its teeth.

You now know the three failure modes, the proxy problem, and what qualitative decay looks like before any tool flags it. What you don’t have yet is the system that runs it.

The architecture below is built into a ready-to-use Excel workbook.

Drop in your accounts, and your composite score, risk tier, and next action calculate automatically, including the qualitative signals your current tools can’t see.

If you manage a book of business and renewals are on the line, this is the tool that changes your Monday morning.

Upgrade to access the full architecture and download the template below→

Read more

Not your champion. Not the department head who signed last year. The CFO.

Most CSMs don’t know this yet, or they sense it but can’t name it. They walk in with solid adoption data, a narrative they believe in, and a deck they spent real time building.

And they still get surprised.

Because the purchasing authority has moved up. Quietly, decisively, and in most of the accounts you’re managing right now.

The department head who used to sign off because “the team loves it” no longer has that latitude. Every renewal, regardless of size, is now passing through a financial review.

And the question being asked in that review is not the one your QBR was built to answer.

The Structural Shift Behind It

This isn’t a vibe shift. It’s structural.

Finance leaders have been tracking a hard trend across SaaS for the past two years: net revenue retention, the metric that measures how much revenue a company keeps and grows from its existing customers, has been declining steadily and now sits barely above 100% at the median.

Existing customer bases are barely growing. Contraction and churn are eating expansion.

And when that happens, the entire financial logic of a SaaS business starts to strain. Boards ask hard questions. CFOs tighten every line item.

The result is a new default: every renewal is now a financial audit, not just a relationship checkpoint.

Your champion can genuinely love what you do. They can advocate for you internally, brief their manager, push back on procurement.

And the renewal can still get killed two levels above them by someone asking a fundamentally different question:

What is the verifiable financial return on this spend, and what is the risk if we stop?

Not “are users happy.” Not “is adoption strong.” Those things inform the answer, but they are not the answer.

Waiting until the renewal call to surface that answer is already too late. The CFO has usually formed a preliminary view long before you’re in the room.

The Mismatch That’s Quietly Killing Renewals

Here’s what typically happens.

A CSM walks into a renewal (or sends a renewal deck async) with three things:

• Usage data showing healthy adoption,

• A story about how embedded the product is in the team’s workflow,

• And a relationship with a champion who’s on their side.

These are legitimate signals. They matter. But watch what happens when they hit a CFO-level filter:

• “87% feature adoption and rising NPS”

  The CFO hears: “But what did we actually get? Did this move a number I report to the board? Or is this telling me users clicked around a lot?”

• “Deeply embedded in the team’s workflow”

  The CFO hears: “Switching cost is real. But we’re consolidating three tools this quarter. Embedded isn’t the same as irreplaceable. Which bucket does this fall into?”

• “Strong relationship with your champion”

  The CFO hears: “Champions leave. Champions get overruled. What’s the financial case for this renewal that exists independent of any individual in the room?”

This isn’t cynicism on their part. It’s their job.

CFOs are trained to pressure-test every spend against one standard: does this generate a verifiable return, and is that return worth the cost and the risk of staying?

This is also why QBR volume has become a misleading metric. Running twelve QBRs a quarter doesn’t protect a renewal if none of them are building the financial narrative the CFO is looking for. Activity isn’t evidence. Decisions are.

If your renewal narrative doesn’t answer the CFO’s question, it doesn’t matter how good the rest of it is. You’ve lost ground before the conversation starts.

Four Things That Shift the Conversation

You don’t need to become a finance person to win at CFO-level renewals. You need to walk in with four things, each one designed to answer a version of the question they’re already asking.

1. The revenue your work protected

Not “customers are satisfied.”

Specifically: what did your CS motion prevent or enable? If you flagged a risk account and brought it back from the edge, that’s revenue protected.

If your outreach framework kicked in before the churn signal became a churn event, there’s an ARR number attached to that.

If your QBR unlocked an expansion conversation, that’s revenue generated. Attach a figure, even a rough one.

A conservative estimate with transparent assumptions beats a qualitative story every single time in a financial review.

2. The real cost of replacing you

Switching costs are real, and CFOs know it. But they need you to surface them, not assume they’re obvious.

Migration time, retraining, integration rebuild, productivity loss during transition: these are budget line items that make renewal look inexpensive by comparison. Not a scare tactic. A factual breakdown.

The CSMs who can put a range on this, calmly, without defensiveness, completely change the tone of the budget conversation.

3. The outcome gap story

This is the shift from activity to impact.

Instead of showing what customers did with your product, show the delta: where they started, where they are now, and what’s still ahead.

The before/after/next frame directly answers the CFO’s implied question: “are we getting better over time, or just maintaining a cost?”

It also sets up the renewal as an investment in what’s next, not just a repetition of what came before.

4. The expansion case

A renewal that holds flat is a cost. A renewal with a credible expansion path is an investment.

CFOs are under pressure to find growth from existing spend because the best CS teams understand that longer commitments come from proof built well before the renewal date, not from a pitch at the end of the contract.

One specific, evidence-backed expansion opportunity in the renewal conversation changes the entire frame from “should we keep this?” to “how do we grow this?”

These four things don’t replace the relationship work.

They arm it. Your champion cannot advocate for you upstairs if they don’t have the financial language to do it.

You’re not just preparing your renewal. You’re preparing their internal case.

The Mindset Shift

Most CS training frames the CFO as an obstacle. Someone to neutralize with the right slide, or win over with the right data.

That framing produces defensive renewal narratives that feel like justification rather than strategy.

The CFO isn’t your adversary.

They’re just operating from a completely different information set than the one you’ve been presenting.

And the reality is that if you can show them that your product protects revenue, eliminates unnecessary spend, and creates a credible path to growth, they become your strongest internal advocate.

Not despite being a CFO. Because of it.

The equal coverage mistake most CS teams make (managing every account the same way regardless of ARR or risk profile) is part of what creates this problem.

When your CS motion isn’t differentiated, you can’t build the financial narrative for the accounts that need it most.

The CFO conversation is a symptom of a resource allocation problem that starts months earlier in how you cover your book.

Stop preparing to defend your renewal. Start preparing to make the financial case so clear that saying no becomes the riskier option.

That’s a different skill than what most CSMs were trained on.

It’s learnable, and the CSMs building it now, before it becomes table stakes, are the ones who will own renewal conversations for the next several years.

What that looks like in practice, specifically, is what I cover below.

What follows is the full operational layer that I built exclusively for paid subscribers.

You get the four-slide CFO renewal narrative framework, the pre-answers to every question that kills renewals in the room, the opening script, and the one-pager you send 48 hours before the meeting.

You also get two downloads that make this immediately usable in your next renewal:

1. CFO Renewal Intelligence Workbook

   The Excel file that calculates your ARR protected, switching cost range, and expansion opportunity size automatically, then generates your CFO Renewal Brief in under 10 minutes.

2. CFO Renewal Narrative Deck

   The PowerPoint template that I pre-built with all four slides, the CFO Lens coaching sidebar on every slide, and every placeholder labeled with exactly what to put there.

Run the Workbook first. The numbers flow straight into the deck. Walk into the meeting with both.

If you’ve been on the fence about upgrading, this is the post to do it on.

Read more

Not because you now need to become a security expert.

Because it is another loud signal that a growing share of enterprise renewals will be won or lost on something many post-sale teams still inspect too late:

Trust.

The $32B Signal You Should Bookmark

Google officially completed its $32 billion acquisition of Wiz on March 11, 2026.

The industry giant says Wiz will join Google Cloud, keep the Wiz brand, and continue supporting major cloud environments, including AWS, Azure, and Oracle.

Google did not spend $32 billion to add a nice security logo to an enterprise slide.

It made a huge bet on the idea that in the AI era, customers will increasingly choose platforms they trust to operate securely across fast-moving, messy, multicloud environments.

Wiz is making the same point from its side: teams are building at AI speed, and security now has to keep up without slowing the business down.

That is where this becomes YOUR problem.

The Post-Sale Model That Is Getting Weaker

For years, many post-sale teams could treat security as something that mattered mostly in pre-sales, procurement, or implementation.

Once the account went live, the operating model shifted back to familiar ground: adoption, usage, stakeholder coverage, QBRs, renewal prep.

That model is getting weaker.

Because more enterprise accounts now carry what I call silent trust debt.

Silent Trust Debt

The gap between how safe the customer assumed expansion would feel, and how safe it actually feels once scrutiny rises.

At first, nothing looks broken.

• The account is active

• The champion is positive

• The business case still makes sense

• The renewal forecast still looks reasonable

Then the account gets heavier.

Security comes back into the room. AI governance gets questioned. Identity controls get re-opened. A new executive joins late and asks a much harder question than the original buyer ever asked:

“Are we actually comfortable expanding on top of this?”

That is the shift.

The failure mode is no longer always weak adoption. Sometimes it is silent trust debt.

• Not a loud incident.

• Not a red health score.

• Nor an angry email thread.

Just a slow increase in friction because the customer’s trust requirements evolved faster than your post-sale motion did.

That is why healthy-looking accounts can still become fragile. And it is why so many “surprise” renewals are not surprises at all. They are late inspections.

This builds directly on what I laid out in Why Enterprise Renewals Fail Before The Renewal Call. This news makes that argument harder to ignore.

The AI Layer Makes This More Urgent

Google says companies are increasingly feeding AI systems with business-critical data, while attackers are using AI to increase the speed and sophistication of attacks.

Wiz is saying the same thing in different words:

Customers are building and shipping faster, and they need security that protects AI applications and workloads without becoming a brake on innovation.

That changes the job for Customer Success.

Customers are no longer only buying software that works.

They are buying confidence that the workflows, data, permissions, integrations, and AI usage around that software will still feel governable when scrutiny rises later.

What Strong CS Teams Do Differently

It is not just about security getting bigger.

It is about trust becoming more operational, more commercial, and more visible inside the renewal motion.

• Average teams ask: “Is the customer engaged?”

• Strong teams ask: “What could make this account feel unsafe to deepen six months from now?”

Average teams run check-ins and show activity. Strong teams run inspections and show executive confidence.

That is also why this fits naturally with my previous note about The Engagement OS: Turn Post-Sale Into Renewal Control.

If post-sale activity does not produce earlier signals, clearer owners, and better proof, it is not really controlling the renewal. It is just creating motion.

The ONE takeaway from the Google-Wiz deal:

The next generation of enterprise renewals will be won not only by proving value, but by proving that value sits on top of a system the customer still trusts.

And the teams that keep treating security, AI governance, and late-stage trust friction as “someone else’s department” are going to feel that shift at exactly the wrong moment: inside the renewal window.

If you have had a renewal stall in the last 90 days because security, AI governance, or a late-stage executive objection appeared “out of nowhere”, I built the section below for that specific topic.

It is the inspection system to catch silent trust debt before it turns into procurement drag, forecast wobble, or a last-minute save.

Read more

In a recent conversation, asked M13’s Courtney and Carter Reum about portfolio construction, ownership, and conviction.

The takeaway for Customer Success leaders is bigger than venture capital: great operators do not spread attention evenly.

That idea is obvious in investing.

But it is still underused in Customer Success.

Many CS and revenue leaders say they believe in prioritization. But inside the actual operating model, the team still behaves as if equal coverage is the safest path. Similar meeting cadence.

• Similar review cycles.

• Similar escalation energy.

• Similar executive attention.

That may feel fair.

It is usually bad portfolio management.

And in a tighter market, bad portfolio management shows up fast. Not only in churn. In soft renewals, weak expansions, late-stage surprises, and leadership frustration, the team looks active without clearly changing the revenue outcome.

That is the part many organizations still miss.

Customer Success is not only a relationship function.

At scale, it is an allocation function.

The question is not whether customers matter.

The question is where deeper ownership, sharper inspection, and earlier intervention actually change the commercial result.

The Hidden Cost Of Equal Coverage

Most post-sale teams do not fail because they distribute expensive attention too evenly.

That creates three predictable problems.

1. First, the accounts that could materially affect retention or growth often do not get enough strategic pressure early enough.

2. Second, low-leverage work expands to fill the calendar.

3. Third, leaders lose trust because the team cannot clearly explain why time, headcount, and executive involvement are being placed where they are.

This is why so many organizations feel busy but not in control.

The operating system was built around activity.

The outcome requires judgment.

That gap is where the real damage happens.

It is also why teams that still optimize around meetings and decks instead of decisions eventually stall. If that pattern sounds familiar, read Stop Counting QBRs. Start Counting Decisions.

Why This Matters More Now

When budgets tighten, every post-sale team is forced into choices whether they admit it or not.

You cannot give the same level of human depth to every account forever.

Nor escalate every issue.

You cannot run every renewal like it is strategic, or ask leadership to join every call that feels important.

Sooner or later, every CS org reveals what it actually believes by where it places senior time.

That is why this is not a philosophical question.

It is a revenue design question.

The strongest teams already understand that some accounts require protection, some require orchestration, some require expansion pressure, and some should move through a lighter-touch motion because added attention will not materially improve the result.

The weak teams try to avoid this truth by calling everything high priority.

That only works until you miss your numbers.

What Venture Logic Gets Right

Strong investors do not assume every position deserves equal conviction.

They know portfolios are shaped by asymmetry.

A small number of decisions drive most of the outcome.

Ownership matters. Timing matters. Concentration matters. Operator support matters. Moderate wins rarely carry the full result.

That same logic applies inside Customer Success.

• Not every account has the same retention impact.

• Not every risk is equally real.

• Not every expansion path deserves the same effort.

• Not every renewal is equally saveable.

• Not every logo deserves the same executive time.

Yet many post-sale teams still operate as if treating accounts differently is somehow less customer-centric.

It is not.

The opposite is closer to the truth.

A mature CS organization serves customers better when it places the right motion on the right account at the right time.

The Question Most Leaders Ask Wrong

Most teams ask:

How do we make sure every account gets enough coverage?

That sounds responsible.

It is not the best leadership question.

A better one is:

Where does additional ownership materially improve the outcome?

That question changes everything:

• Which renewals get inspected 120 days out instead of 30?

• Which accounts deserve executive sponsor pressure?

• Who owns the value narrative?

• Which risks should trigger intervention?

• Or whether your best operators are spending time where the portfolio can still move.

And once you start asking it consistently, you stop managing the book like a calendar problem and start managing it like a revenue system.

The Core Shift

Many organizations still run Customer Success like a service layer attached to revenue.

The next generation of strong teams will run it like a portfolio discipline inside revenue.

That means moving from:

• equal coverage to deliberate concentration

• account activity to commercial leverage

• reactive escalation to early inspection

• broad customer care to outcome-based ownership

That is where the role gets sharper.

That is where leadership trust improves.

And that is where CS stops sounding important and starts operating like it is.

Paid subscribers get the practical model below: which accounts deserve concentrated coverage, when to intervene before renewal risk hardens, and how to show leadership that the strategy is working.

Read more

It is not.

Renewal is the lagging result. The real work happened months earlier, when the customer decided whether your product had become important enough, risky enough to remove, and valuable enough to commit to for the long term.

That is why contract duration matters.

What Guidewire’s Quarter Shows

Guidewire’s recent quarter results are a useful reminder. Yes, the company is growing. Q2 revenue was up 24% year over year, and ARR reached $1.121 billion.

But the bigger story is what that growth says about customer trust.

Guidewire said gross ARR retention stayed above 99% across key parts of its customer base. It also said new deals averaged more than six years, even though its standard cloud term is five years.

That matters because it suggests customers are not just renewing. They are choosing to commit for longer than the default term.

And that points to something bigger for CS.

What That Means For CS

That combination matters.

It suggests something deeper than “customers renewed.”

It suggests customers trusted the platform enough to stay longer, buy bigger, and embed it more deeply in how the business runs.

That is not a support outcome or a customer-happiness outcome.

That is an operating-system outcome.

Guidewire’s CEO put it plainly on the call: “Success on a Guidewire project is the single most important KPI” in the company.

That is the evergreen lesson.

The best CS teams do not just save renewals at the end. They create the conditions that make a longer commitment feel rational much earlier.

Why Renewal Alone Can Mislead

A logo can renew for the wrong reasons.

• Budget inertia

• Switching pain

• Political timing

• Procurement delay

• An executive who is too busy to re-evaluate

• A champion who buys one more year to avoid disruption

None of that means the relationship is strong.

A renewal can happen because change feels harder than staying. That is very different from a customer making an active long-term commitment.

What Longer Contract Length Signals

A longer term says something else.

It says the customer believes your platform is going to matter over a meaningful stretch of time.

It also says the buyer is willing to reduce optionality because the expected value is high enough. And the executive team believes the risk of staying is lower than the risk of replacing.

In Guidewire’s case, management tied those longer commitments to customer confidence, larger deals, and durable adoption in mission-critical environments.

That is why many CS dashboards are too shallow.

They measure activity. They measure touches. They measure meeting count, QBR completion, training attendance, NPS, health score movement, and maybe product usage.

Useful, yes.

But none of those, on their own, answer the most strategic post-sale question:

Has this customer become confident enough in our value and operational fit to commit further into the future?

That is the question leadership actually cares about.

Because longer commitments do three things at once.

• They stabilize revenue.

• They reduce renewal drama.

• They prove trust at the executive level.

Guidewire’s own results make that visible.

The business is not only growing ARR and revenue. It is also showing signals of stronger future durability through contract length, retention, and RPO.

What Actually Earns A Longer Commitment

• Not a nicer QBR.

• Not a prettier deck.

• Not a last-minute discount.

Longer terms are usually earned when four things become true.

1. First, the customer has seen real operational proof, not just a theory of value. Not a roadmap promise. Not “we are partnering closely.” Something concrete changed in the business.

2. Second, executive confidence is ahead of the paper.

3. The leaders who control the budget and risk believe the platform is helping them run the company better, not just helping one team stay busy.

4. Third, the product is connected to workflows that the customer does not want to disturb. The more your platform sits inside core operating decisions, the more term length becomes easier to justify.

5. Fourth, your team has reduced enough uncertainty that a longer commitment feels safer, not scarier.

That is why the strongest CS organizations behave less like service teams and more like trust-building systems.

They are constantly reducing doubt.

They reduce doubt about adoption, business impact, executive alignment, delivery risk, and future relevance.

Do that well enough, and the renewal discussion changes shape.

It stops being, “Should we keep this?”

It becomes, “How far forward are we willing to commit?”

The Mistake Many CS Teams Make

They wait for the renewal window to start proving strategic value.

By then, it is late.

If a customer is going to sign a longer term, the logic for that decision usually needs to be built well before commercial discussions begin. Procurement may handle the paperwork late, but the real decision is made earlier.

This is where weak CS motions get exposed.

• The team has a health score.

• The account looks “green.”

• Usage is decent.

• The champion likes the product.

But no one has translated that into an executive-level case for why the relationship should deepen.

So when the commercial moment arrives, the company is forced into the usual pattern:

• A scramble for proof.

• A reactive deck.

• A generic value summary.

• A pricing conversation with no strategic context.

That is how companies end up renewing year by year, even when the product is important.

They did not earn a longer commitment in the customer’s mind early enough.

What follows is the complete system I use to help CS pros and teams earn longer commitments earlier, not scramble for them at renewal time.

Paid subscribers also get the Multi-Year Renewal Readiness Model.

It is the worksheet I would use to decide whether an account is truly ready for a multi-year ask or just looks healthy on the surface.

Read more

That’s key for Customer Success because WorkOS is building the exact layer many SaaS teams still treat as secondary until an enterprise buyer forces the issue: SSO, SCIM, permissions, and audit logs.

In its March 2, 2026 announcement, WorkOS said customers, including OpenAI, Anthropic, xAI, Cursor, Perplexity, Replit, and Vercel, hit enterprise requirements almost immediately, and that buyers expect SSO, SCIM, permissions, and auditability from day one.

The controls that many teams still label “later,” “IT will handle it,” or “backlog” are already part of the enterprise standard.

And when they were skipped during onboarding, left half-configured after go-live, or quietly deferred for speed, they tend to show up again at the worst possible moment:

Right inside the renewal cycle.

The Risk Most Teams Surface Too Late

Here is how this usually plays out.

• Your champion is happy.

• Usage is healthy.

• Executive sentiment feels stable.

• Expansion is still possible.

Then procurement, security, or IT gets pulled into renewal.

Suddenly, the questions change:

• Is SSO enforced?

• Is SCIM actually live?

• Are admin roles still clean?

• Can audit logs be exported?

• Does IT trust this setup?

Now the account is exposed.

Not because the customer stopped seeing value.

Because an identity or security gap sat untouched for months and surfaced when there was no real runway left to fix it.

This is why so many enterprise renewals look “surprising” from the outside.

They rarely are.

They are deferred implementation debt, collected with interest.

What The WorkOS Raise Actually Tells You

The lesson here is that the fastest-growing software companies are treating enterprise-readiness as core product infrastructure from the start, not as an enterprise upsell later.

That is exactly how WorkOS framed the round.

Your customers’ IT and security teams have already moved to that standard.

The only question is whether your post-sale team is working ahead of it, or waiting for it to resurface during renewal.

The Hidden Renewal Blocker

A lot of CS teams are good at spotting weak adoption.

Far fewer are good at spotting hidden security risk inside accounts that otherwise look healthy.

That is the gap.

• A customer can love your product and still fail renewal review because the account was never hardened properly.

• A customer can be expanding and still stall because SCIM was promised, partially configured, then forgotten.

• A customer can say they are happy and still reduce scope because a new security leader reviewed the vendor stack and found too many loose ends.

Most organizations reported at least one SaaS security incident in the past 12 months, even while most said they were confident in their SaaS security posture.

That matters because it changes the posture of every serious IT and security team.

They are getting stricter. And renewals are where that posture shows up.

What Your CSMs Actually Need To Understand

Your team does not need to become security engineers.

But they do need enough fluency to identify risk early, ask better questions, and route the issue to the right owner before time becomes the real problem.

Here is what it means in practice.

SSO

Single Sign-On means users access your product through their company identity provider, usually Okta, Azure AD, or Google Workspace.

For enterprise teams, this is usually baseline control, not a nice-to-have.

If users are still logging in through standalone credentials when the customer expects centralized identity control, that is renewal risk.

SCIM

SCIM is what keeps user access synced.

When someone joins, changes roles, or leaves, SCIM updates access automatically based on the identity provider.

Without it, deprovisioning often becomes manual. Manual deprovisioning is where orphaned accounts, stale permissions, and audit concerns start piling up.

Audit Logs

Audit logs answer the question security teams eventually ask:

Who did what, and when?

If those logs are incomplete, hard to access, or impossible to export into the customer’s workflow, your product becomes harder to defend in a review.

The core controls work together:

1. Identity provider

2. SSO authentication

3. SCIM provisioning and deprovisioning

4. Audit logs

When one part of that chain is weak, the account carries more renewal risk than the health score suggests.

Implementation Debt Does Not Stay In Onboarding

This is where a lot of teams lose the plot.

They treat the rushed setup as temporary.

It rarely is.

• If SSO was deferred because “IT will handle it later,” that decision did not disappear.

• If SCIM was skipped to get the customer live faster, that shortcut is still costing you.

• If roles were set once at launch and never revisited, that gap did not disappear.

It just moved forward in time.

Most teams have already seen this before: onboarding shortcuts quietly turn into expansion risk.

The same pattern shows up here, except the consequence is often harsher because security and identity gaps give procurement a clean reason to slow, reduce, or challenge the renewal.

This is the frame that separates operators from account managers:

You are not only managing a relationship. You are managing risk on behalf of ARR.

The best CSMs do not wait for procurement to expose the weak point.

They surface it first.

The Real Job

The goal is not to sound technical.

The goal is to make enterprise renewals predictable.

That means finding the ugly stuff early:

• SSO not enforced

• SCIM half-configured

• Admins missing MFA

• Audit logs never tested

• IT owner unmapped

• Security debt carried forward from onboarding

The renewal call should confirm readiness.

It should not be the first time anyone notices the gaps.

That is why this audit should happen 120 days before renewal, not 30.

By the time procurement raises a concern inside the renewal window, your room to solve it is already shrinking. The best teams are trying to make renewals feel boring on purpose, because boring is what control looks like.

Paid subscribers get the full 120-Day Pre-Renewal Security Audit I’d run to catch hidden renewal blockers before they cost you time, leverage, or revenue.

You’ll be able to:

• Identify security and identity gaps before they hit procurement

• Assign the right owner to every issue

• Prioritize what matters most with built-in risk scoring

• Pull IT and security in early, without creating alarm

• Show renewal readiness clearly in one page

Inside the playbook:

• Excel tracker with automatic risk scoring, gap registry, and one-page readiness summary

• Four audit tracks with pre-filled questions

• Owner mapping by gap type

• IT stakeholder discovery script

• T-60 escalation protocol

Download The Full Playbook →

Read more

Not a product launch. Not an AI feature drop.

It’s an org restructure.

SAP merged its Customer Success and Customer Services & Delivery organizations into a single new Board area called the Customer Value Group, effective April 1, 2026, led by Thomas Saueressig, now elevated to Chief Customer Officer.

CEO Christian Klein put it plainly:

“In a business where adoption and renewal define success, the lines between selling and delivering disappear.”

Read that sentence again.

This isn’t a €36B+ company optimizing headcount. This is a €36B+ company admitting something the industry has danced around for years:

The gap between “we’ll deliver value” (CS) and “we’re delivering value” (Services & Delivery) has been quietly killing renewals, and customers are done tolerating it.

Why This Is Bigger Than SAP

SAP is not a startup. They don’t restructure on a whim.

When a company at this scale explicitly collapses two major customer-facing organizations under one leader and calls it a “Customer Value Group,” it’s sending a signal to the entire market:

The era of handoffs is over.

Here’s the tension that’s been building for years in SaaS:

• CS owns the relationship, the QBR, and the renewal conversation

• Professional Services owns the implementation, the go-live, and the delivery timeline

• Support owns the ticket queue

Three teams. Three success definitions. One customer trying to figure out who to call.

The customer doesn’t care about your internal org chart. They care about outcomes.

And when outcomes are split across three owners, nobody truly owns them.

SAP just bet their entire post-sale organization on fixing this. The question for every CS leader reading this is: Is your company next? And are you positioned to lead that change, or get reorganized around it?

If you’ve ever wondered whether the CCO role belongs in your company, SAP just answered it for you.

What Paid Subscribers Get Next

Most insights stop at the signal. I give you the operating model.

If you are dealing with PS handoff friction, slow adoption after go-live, or renewals that get tense late, the next section is for you.

You will leave with:

• One journey map (who owns what, by phase)

• One dashboard spec (what to track weekly across CS + Delivery)

• One renewal anchor cadence (what must happen before T-90)

What’s included:

• The Customer Value Journey Tracker

  A plug-and-play Excel workbook that operationalizes every layer of the framework below, with auto-calculated renewal health scores, a red-flag alert trigger, and a live NRR snapshot.

  Open it Monday morning and be running the framework by noon.

• The 4-Part Customer Value Framework

  Layer by layer, with ready-to-use templates, decision rules, and the one sentence that will change how your leadership team talks about customer outcomes.

• The Renewal Ownership Map

  Where the three Anchors go, why Anchor 2 is your most important leading indicator, and the exact questions to ask in a Value Realization Review.

• The CS Career Play

  What this org shift means for professionals targeting leadership/executive roles, and the single positioning move you should make before this model lands at your company.

This is the full framework. So let’s get into it.

Read more

That’s a pattern. And patterns are data.

Most CS teams are sitting on the most valuable product intelligence in their company and don’t even know it.

They log it in the CRM, mention it in a Slack message, maybe bring it up in a team meeting, and then it disappears.

The same conversation happens again next quarter, with the next customer, as if nothing was ever said.

And here's what that silence is actually saying:

If your customers are repeating themselves, it’s because nobody acted on what they said the first time.

The Two Versions of CS, And Why Only One Has a Future

There’s a version of CS that reacts.

• Renewal calls, churn saves, health score alerts.

• Always one step behind the problem.

And there’s a version of CS that leads.

Walking into a product meeting with three customer patterns backed by data, a revenue number attached to each one, and a clear recommendation.

The first version is replaceable. The second is irreplaceable.

Teams that run a consistent CS-to-Product cadence ship fixes sooner, reduce repeat complaints, and stop relearning the same lessons every quarter.

That gap doesn’t happen by accident.

It happens because someone on the CS team decided to stop being the messenger and start being the strategist.

The Pattern-to-Roadmap Framework

Start with one simple habit: every week, flag the top 3 things customers said that surprised you, frustrated them, or came up more than once.

Then ask three questions for each one:

• What are they actually saying?

  The exact words, not your interpretation

• What does it signal?

  Adoption gap, misaligned expectations, product gap, packaging issue

• What’s the business impact?

  How many accounts, what MRR is at risk, what expansion is blocked

That’s your product meeting currency.

Here are the four most common patterns, and exactly what to bring to Product each time:

1. I can’t find X feature.

Signal: Adoption gap or UX failure

What you bring to Product: A feature discoverability request, plus where users get stuck

2. We expected Y after onboarding.

Signal: Misaligned promise between sales and delivery

What you bring to Product: Onboarding redesign input, plus the exact expectation customers walked in with

3. We pay for Z but don’t use it.

Signal: Churn risk and packaging issue

What you bring to Product: Pricing and packaging feedback tied to specific retention risk

4. Your competitor does this better.

Signal: Competitive gap

What you bring to Product: A prioritization case with ARR, segment, and renewal timing attached

Even one pattern per month, brought consistently to the right meeting, changes how Product sees you.

🔐What follows is exclusive to paid subscribers:

• A downloadable CS-to-Product Intelligence Tracker (Excel) that turns your Friday call notes into a quantified product brief in 15 minutes. Ready to send before your next product meeting.

• Plus the exact scripts, briefing templates, and influence tactics CS leaders at high-growth SaaS companies use to own a seat at the product table and get compensated like it.

Join other leaders who use The CS Cafe to protect revenue and drive boardroom-level impact.

Read more