Customer Success Doesn’t Need Reinvention. It Needs an Operating System.
Why changing roles, incentives, and technology won’t fix retention, and why selling outcomes raises the stakes.

I’ve been participating in some interesting conversations about the future of Customer Success lately.
Should we return to Account Management? Should CSMs stay out of Support? Does Customer Success need to be reinvented around AI? Are we doing enough to demonstrate our value to the business?
And now, increasingly, we’re talking about selling outcomes instead of software.
These are all worthwhile conversations. But I think we’re missing something fundamental.
We keep debating roles, responsibilities, incentives, and technology without addressing how retention and growth are actually produced.
We’ve spent years trying to improve Customer Success one component at a time. New organizational structures. Better health scores. More sophisticated playbooks. Different compensation models. More automation.
And yet we continue to struggle with the same questions.
How do we consistently help customers achieve their goals? How do we know whether a customer is progressing toward renewal or expansion? What work actually contributes to retention? How much does that work cost? And how do we make the revenue from existing customers more predictable?
These aren’t simply Customer Success problems.
They’re operating system problems.
We’ve Been Trying to Fix Customer Success from the Outside In
Think about some of the debates happening across the industry.
We want CSMs to be strategic, but we fill their days with reactive work.
We want better discovery, but we don’t always connect what we learn to the work required to move customers forward.
We want people accountable for retention, but they often lack the resources or organizational support to influence the outcome.
We want AI to make teams more productive, but productive at what?
And we want Customer Success to demonstrate its ROI, but we haven’t necessarily defined the work or established the economics needed to measure it.
There’s a common problem here.
We’re starting with the people, tools, and organizational structure rather than the customer experience we’re trying to produce.
Consider the debate about whether Customer Success should return to Account Management.
I understand the argument. Sales organizations have historically rewarded new customer acquisition, sometimes at the expense of retaining and growing existing relationships. Aligning compensation and accountability with retention makes sense.
But changing someone’s title or compensation doesn’t give them a strategy for producing retention.
An Account Manager compensated on renewals can’t independently resolve product limitations, implementation failures, or the customer’s inability to change how they operate.
Those challenges require coordinated action across the business.
The same is true of the argument that CSMs should stop doing Support work.
Sometimes jumping in to solve a problem is exactly the right thing to do. It builds trust and demonstrates commitment.
But if CSMs spend most of their time responding to whatever comes up next, when are they supposed to execute the work that moves customers toward their goals?
That’s not simply a role-definition problem. It’s a failure to design the work and the capacity required to deliver it.
We can’t expect strategic outcomes from an operating model built around reactive activities.
Customer Progression Needs to Be the Strategy
I believe we need to start somewhere different.
Before deciding what a CSM should do, what technology to purchase, or how to compensate an Account Manager, we need to define how customers should progress.
What did the customer purchase the software to accomplish?
What needs to change in their business?
What decisions must they make? What capabilities must they develop? What behaviors need to change? What obstacles are likely to prevent progress?
And what work can we do to help them move forward?
These questions should inform a deliberate strategy for customer progression.
In The Post-Sale Operating System, I describe customer progression through meaningful inflection points in the relationship, from the initial purchase and onboarding decisions through first value, goal attainment, ongoing alignment, and renewal.
Each inflection point represents something important that needs to happen for the customer.
And each requires intentional work.
That work might involve helping stakeholders align around business goals, guiding implementation decisions, addressing barriers to value, or helping the customer establish new operational habits.
It might require Sales, Professional Services, Product, Support, or Customer Success.
The point isn’t which department owns the activity.
The point is whether the organization has designed and coordinated the work required to help the customer progress.
This also changes how we think about discovery.
Discovery shouldn’t end when the sale closes, and it shouldn’t simply produce better meeting notes.
Every meaningful customer interaction should help us understand where the customer stands, what has changed, what’s preventing progress, and what needs to happen next.
And that understanding should inform action.
Otherwise, we’re having better conversations without necessarily producing better outcomes.
Selling Outcomes Without a Delivery Strategy Is Just Making a Bigger Promise
This is where I think the industry is heading toward a particularly uncomfortable problem.
We’re increasingly talking about selling outcomes instead of software.
I understand the appeal.
Customers don’t buy software because they want another application. They invest because they want to improve something about their business.
Reduce costs. Increase revenue. Improve productivity. Make better decisions. Create capabilities they didn’t have before.
So why not sell the outcome?
I’m supportive of that direction.
But here’s my concern.
You can’t change the promise in the sales conversation and expect the post-sale organization to figure out how to deliver it.
If we’re going to sell outcomes, we need to understand what producing those outcomes actually requires.
That means understanding the customer’s starting point, the changes they need to make, the resources both organizations must commit, and the work required to help them progress.
It also means recognizing that outcomes aren’t entirely within the software provider’s control.
Customers must participate.
They need to make decisions, allocate resources, change processes, develop skills, and sometimes fundamentally change how their organizations operate.
Software alone doesn’t produce those changes.
Neither does adoption.
A customer can use a product regularly without achieving the business results that justified the investment. Conversely, meaningful value may depend on a relatively small number of users performing a critical activity exceptionally well.
We need to understand not just whether customers are using the software, but how they’re consuming its capabilities and whether that consumption is producing the intended outcomes.
This requires an iterative post-sale strategy.
We establish goals, help customers make progress, evaluate the results, and adjust as their business changes.
Because the value that justified a purchase two years ago may not be sufficient to justify the next renewal.
Software companies cannot assume that the value they delivered yesterday will be enough to keep customers tomorrow.
And without a deliberate strategy for customer progression, selling outcomes is little more than making a bigger promise.
Retention Requires Evidence of Commercial Progression
Helping customers achieve outcomes is essential, but there’s another piece we need to address.
We also need to understand how customer progression translates into commercial decisions.
For years, we’ve relied on metrics such as Gross Revenue Retention (GRR), Net Revenue Retention (NRR), product adoption, customer health scores, and satisfaction surveys to understand the condition of our customer relationships.
These measures are useful.
But they don’t necessarily tell us how revenue is developing or what work needs to happen next.
GRR and NRR tell us what happened to revenue over a period of time.
They don’t explain the coordinated work that produced those results or provide sufficient evidence to forecast what will happen next.
Consider how we manage new-logo sales.
We establish pipeline stages, define qualification criteria, inspect opportunities, identify obstacles, and determine the work required to advance a deal.
We expect salespeople to explain where an opportunity stands, what evidence supports their assessment, and what needs to happen before the customer makes a commercial commitment.
Why should existing-customer revenue be managed any differently?
In The Post-Sale Operating System, I introduce a post-sale pipeline that connects customer progression to commercial progression.
The stages (Identify, Align, Advocate, Intent, and Net Revenue Close) provide a way to manage the development of commercial opportunities after the sale.
The important distinction is that opportunities advance based on evidence, not simply activity or optimism.
A customer achieving an operational milestone is evidence of progress toward value.
A customer confirming that the outcome remains a business priority is evidence of continued alignment.
An economic buyer affirming a renewal decision, with a credible approval path, is evidence of commercial intent.
These are related, but they aren’t interchangeable.
A customer can be achieving value without having made a commercial commitment. And a customer can indicate an intention to renew even when the value supporting that decision is deteriorating.
We need visibility into both.
When customer progression and commercial progression are connected, leadership can begin to understand not just whether revenue is at risk, but why, what needs to happen, and who needs to participate.
That’s a much stronger foundation for managing retention and growth than relying on a health score or waiting for the renewal date to approach.
We Also Need to Understand the Economics of Retention
There’s another question that deserves considerably more attention.
How much does it cost to deliver the customer experience we’ve designed?
We talk about improving CSM productivity, increasing account coverage, and using AI to serve smaller customers.
But those conversations often begin without a clear understanding of the work required to deliver the experience.
If we don’t know what work needs to happen, how frequently it needs to happen, and how much effort it requires, how can we make informed decisions about staffing, segmentation, pricing, or automation?
This is why capacity planning needs to be part of the strategy, not an annual exercise in dividing accounts by CSM headcount.
Start with the customer experience.
Define the work required at each stage, including preparation, execution, and follow-through.
Estimate the effort required to perform that work.
Then determine whether the organization has the resources and capacity to deliver it consistently.
Different customer segments may require different experiences, levels of engagement, and delivery models.
That’s fine.
But those decisions should be intentional and grounded in the economics of the relationship.
This also gives Finance, Revenue Operations, and executive leadership a much clearer understanding of the investment required to produce retention.
We can begin asking better questions.
Which activities contribute to customer progression? Where are we spending resources without producing meaningful results? Which experiences can be delivered more efficiently? Where does human involvement create enough additional value to justify the cost?
And how should those answers influence our packaging, pricing, and gross margin expectations?
Retention isn’t free, and we shouldn’t manage it as though the cost of producing it is unknowable.
AI Can Transform Execution, but It Can’t Replace the Strategy
This brings us to AI.
I’m excited about what AI can make possible in the post-sale.
We can reduce administrative work, prepare for customer conversations, analyze account information, identify emerging obstacles, and coordinate activities across teams.
We can potentially deliver experiences to customers who previously received little proactive attention because the economics didn’t support it.
And we can give experienced professionals more time to focus on the complex work that requires judgment, relationships, and collaboration.
But I keep coming back to one question.
Faster at doing what?
If we haven’t defined how customers should progress, the work required to move them forward, and the evidence that tells us whether that work is effective, what exactly are we asking AI to execute?
We risk automating an operating model that was never particularly effective in the first place.
More alerts won’t solve that.
More summaries won’t solve that.
And automatically generating another business review won’t solve that either.
The opportunity is much bigger.
Imagine AI operating within a defined strategy for customer progression.
It understands the customer’s goals, where they stand in the journey, what work has been completed, what evidence has been collected, and what needs to happen next.
It can help prepare and execute the appropriate plays, coordinate resources, identify missing information, and recommend actions based on the customer’s current situation.
Human judgment remains essential, particularly when customer circumstances are complex, commercial decisions are consequential, or relationships require direct engagement.
But the work becomes more consistent, visible, and scalable.
That’s the direction I believe we should be pursuing.
Not AI as a replacement for Customer Success.
AI as a way to help execute a deliberately designed post-sale operating system.
The Post-Sale Needs to Be Managed as a Growth Pipeline
All of these issues are connected.
Customer progression provides the strategy.
The post-sale pipeline makes commercial progression visible.
Evidence supports more reliable forecasting.
Coordinated plays turn strategy into execution.
Capacity planning and ROI analysis establish the economics required to deliver the experience sustainably.
Together, these components form an operating system for managing the revenue and customer relationships that exist after the sale.
And importantly, this isn’t simply a Customer Success operating system.
Sales, Marketing, Professional Services, Product, Support, Finance, and executive leadership all influence whether customers achieve their goals and continue investing.
The post-sale needs to coordinate those contributions rather than leaving one department responsible for outcomes it cannot independently control.
That’s also why I believe the post-sale should be managed with the same strategic attention and commercial discipline we apply to new customer acquisition.
Existing-customer revenue isn’t automatically predictable just because it’s recurring.
We need to understand how that revenue is developing, what evidence supports our expectations, and what work will improve the likelihood of future commitments.
Customer Success Doesn’t Need Another Identity Crisis
I’ve spent much of my career working on these problems, leading post-sale organizations and helping companies improve retention, customer outcomes, and growth.
More recently, I’ve brought that experience together in The Post-Sale Operating System.
And the more conversations I have about the future of Customer Success, the more convinced I become that we’ve been approaching the problem from the wrong direction.
We don’t need to start by deciding whether someone should be called a Customer Success Manager or an Account Manager.
We don’t need to start with a new compensation plan, another health score, or the latest AI agent.
And we certainly shouldn’t start by promising customer outcomes without understanding how we’re going to help produce them.
We need to start with the customer.
What are they trying to accomplish? What must change for them to succeed? What work will help them make progress? What evidence will demonstrate that progress? And how do we connect those results to a durable commercial relationship?
Then we can design the roles, processes, technology, and economics required to deliver that experience.
We need to stop organizing the post-sale around what we want CSMs to do and start organizing it around what customers need to accomplish.
The rest should follow from there.
And if we’re serious about selling outcomes, we’d better have an operating system for delivering them.
Explore The Post-Sale Operating System, an interactive book about designing customer progression, coordinating post-sale execution, and making retention and growth more predictable.
Tim Conder is the author of The Post-Sale Operating System, a framework for connecting customer progression, post-sale execution, and revenue predictability in B2B SaaS businesses.