Ask a CS leader why an account renewed and you’ll usually get a story. The champion loves the team. The CSM caught a problem early. Somebody picked up the phone at the right moment.
Ask the same question during diligence and that story becomes a liability.
Seven posts into this series, the pattern underneath every one of them has been the same. GRR climbs while the mechanism holding it up is discounts nobody’s tracking. The board sees an NRR number that isn’t the number that matters. A company says it has a CS team and means three people answering tickets. None of that shows up as a red flag in the metrics an operating partner is watching, because the metrics were never built to catch it.
There’s a reason all of it hides so well. It hides behind a person.
The Test That Actually Works
Here’s the question I’d put in front of any portfolio company before a process starts: Can someone outside your company explain why an account stayed or left, using only what’s written down?
Not “does the team know.” Everyone’s team knows. The CSM can tell you exactly why the account almost churned in month nine and what saved it. That knowledge is real, and it’s usually right. It’s also worthless in diligence, because it lives in one person’s head and it leaves the building when they do.
Run the test on a save. If the honest answer is “Sarah has a great relationship with the champion,” the account was retained by a person. If the answer is “the health score flagged adoption risk in month four, the playbook triggered an intervention, and usage recovered before renewal,” the account was retained by a system. Same outcome on paper. Completely different asset underneath it.
Run it again on a churn. A company that can produce the trigger, the intervention, and the reason it didn’t work is showing you a process with a known failure mode. A company that can only produce “the customer just went quiet” is showing you nothing. One of those is fixable. The other is a mystery that will repeat itself with the next account and the next CSM.
Why This Is the Tell, Not a Metric
I’ve worked with CS leaders who can rattle off their churn and downsell numbers, sort every loss into a reason code, and tell you exactly what their team needs to change so it doesn’t happen again. I’ve watched some of those same leaders walk straight into a process overhaul or a team restructure on the strength of that read. What I haven’t seen nearly as often is a leader who can tell me how many plays were run, in which situations, which actually worked, and what changes will raise the success rate next time. The churn number was accurate. The reason codes were accurate. None of it was evidence of a system. It was evidence of people who are good at their jobs.
This is what separates a company that’s built a CS function from one that’s built a very good CSM team. The $25M-ARR org running on instinct and hustle isn’t wrong to run that way — it’s often the only way to move fast enough to survive that stage. But instinct doesn’t transfer, and it doesn’t survive an acquisition, a departure, or a scale-up. A system does.
Exit-ready CS isn’t a maturity score or a headcount ratio. It’s the difference between an operation a buyer can inspect and one they have to take on faith.
This is exactly the blind spot our Outcome Readiness Assessment is built to surface, before a diligence process finds it for you: see how it works →
The Honest Version of This Series
Every post in this series has pointed at some version of the same blind spot: The number looks fine, and the number is not the whole story. This is where that turns into a question you can actually ask in a portfolio review.
Start with the KPI test. What is CS showing you that proves a system, not a person, produced the outcome? Playbook adoption across the client base and intervention-to-save conversion by trigger type are a start. Documented playbook coverage on at-risk accounts is the real proof it’s systemic, not anecdotal “proof.”
Then run the account test. Pick one renewal from last quarter. Could someone outside the company explain why it happened, using only what’s documented, not who they’d have to track down and ask?
If the answer is nobody, you don’t have a CS function yet. You have a very good person, standing in for one.
This closes the eight-post series on what PE-backed CS actually looks like. If you want to see where your own portfolio company lands on the tests in this post, our Outcome Readiness Assessment gives you the diagnostic to find out: see the framework →
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 →