Two companies sit at the same ARR, with similar growth rates, similar markets, and org charts that look nearly identical on paper. Ask either CEO whether they have a Customer Success function, and both will say yes without hesitation, and both will be telling the truth as they understand it.
But the two functions they’re describing aren’t the same thing, even though they share a name and a line item in the budget. At Company A, CS runs on the instincts and relationships of the people doing the work. The CSMs know their accounts, know their customers personally, and get things done through hustle, familiarity, and a willingness to jump in when something starts to go sideways. It works, and it can work well, for a long time. At Company B, CS runs on something closer to a system. Health is modeled rather than felt. Renewal risk tends to surface in the data before it surfaces in a phone call. When something breaks, there is usually a process built to catch it before anyone needs to play hero.
Neither company is lying about having a CS function. They’re just describing two different stages of the same thing, and the difference between them has less to do with size than with maturity. It’s the same distinction that separates a teenager from an adult who happen to be the same height. One of them can get most things right most of the time, but still needs someone more experienced to step in when it counts. The other one is the person who has to be that someone.
That distinction rarely shows up in an ARR number. It shows up in moments like these three.
The Forecast
A CSM will tell you an account is healthy. Often, they’re right. Sometimes what they’re actually reporting is that the point of contact is friendly, and those aren’t the same thing.
One company we worked with had a POC who genuinely loved the team. She thanked the CSM by name in every meeting. She posted her kids in company swag on LinkedIn. By every relationship signal the CSM had, the account was in great shape.
Asked directly for an NPS score, in front of her own CEO and ours, she wouldn’t answer. She liked the people too much to give a bad score, and the product wasn’t delivering enough value for her to give a good one. So she gave nothing. That silence was the real signal, and it took a forced, structured moment to surface it. It was not something a CSM’s gut feeling was ever going to catch, because the gut feeling was reading warmth, not value delivered.
That account was a genuine churn risk. The forecast said otherwise, because the forecast was a feeling, not a model.
The Save
Some saves happen because a team ran a good playbook, caught a risk early, and worked the account back to health before anything broke. Those saves are repeatable. They also don’t make for dramatic stories, which is part of the problem: They’re invisible by design.
The saves that get remembered are the other kind. A mid-sized customer had a series of enhancement requests that were never going to make the roadmap, and a CSM who communicated that poorly, or not at all. The customer’s expectations went unmanaged until they were furious. The CEO and the founder flew out personally to hold the relationship together.
The account was retained. It was retained by giving away a chunk of free implementation work, pulling product resources off the actual roadmap, and burning executive time that should have gone somewhere else. Nothing about the save came from the CS motion working. It came from two senior people absorbing the cost of a motion that hadn’t worked at all.
Retention is not the same as a healthy account. Sometimes retention is just the price of a save that a functioning CS system would never have needed to make.
The Dependency
The clearest tell of all is who is allowed to be in the room.
One client, the CMO of a large company, refused to engage with the CS team directly. Every call required his own right-hand person and our CEO on the line, not because the CSM lacked the skill to run the account, but because the structure of the relationship had been set up so that only the CEO had standing to say yes to what he wanted.
That’s not a relationship problem. It’s an operating problem. The CS function existed on paper, but the actual authority to manage the account lived with one person, and only one person, at the top of the org chart.
Here’s the part worth sitting with: The team always sensed that this account carried real renewal risk. They knew the relationship was fragile long before any contract came up for review. But because the client would only engage at that level, the CSM had no path to surface the risk directly — the only response available was to wait for our CEO to notice and step in. Correctly forecasting a risk means very little if the structure only allows one person to do anything about it.
This is exactly the kind of gap our Outcome-Based CS Framework is built to surface — before diligence finds it for you: see how it works →
Same ARR. Different diligence outcome.
None of these three companies lacked a CS team. All three had titles, headcount, and a line item in the org chart that said “Customer Success.” What none of them had, in these moments, was a system that could forecast accurately, retain accounts without executive rescue, and operate without requiring one specific person in every room.
That’s the actual test a PE operating partner needs to run, and it’s rarely the test that gets run. ARR tells you size. It doesn’t tell you whether the motion underneath it can survive a diligence process, a leadership change, or a founder’s calendar filling up.
If you want to see where your own CS function lands on that test, our Outcome-Based CS Framework gives you the diagnostic to find out: see the framework →
Post 8 in this series: What good looks like at $25M ARR versus $75M ARR — and why the same GRR number means something different at each stage.
Andrea Mulligan is a B2B SaaS executive and advisor with 30 years of experience building Customer Success, Professional Services, and GTM organizations. She works with PE-backed and growth-stage companies on CS transformation, revenue retention strategy, and post-sale model design. Start a conversation →