When PE operating partners review CS health at a portfolio company, the conversation usually centers on the same set of signals: GRR, NRR, CSAT, NPS, support backlog, implementation utilization. Those numbers tell you whether the function is operating. They don’t tell you what the function is built to do.
As we discussed in the last post in this series, reactive CS and proactive CS can produce identical GRR for as many as eighteen months. The divergence comes later, and by the time it shows up in the numbers, the window to effectively and quickly act has already closed. The question worth asking now — before the divergence — is not whether CS exists at a portfolio company. It’s what that CS team is actually built to optimize.
The Function Is Not the Model
Nearly every portfolio company you review has a CS team. They have CSMs assigned to accounts. Maybe there are technical account managers or solution consultants, too. Most have a QBR cadence, a health score of some kind, and a renewal process. The function is staffed, and the people in it are working hard. That’s not in question.
What the org chart and the dashboards don’t show you are the results of all of that effort. A team can be fully staffed, well-documented, and genuinely committed to their customers, and still be running a model that was designed for a different era of B2B SaaS — one where the relationship itself was enough to keep customers.
That era is over.
Table Stakes Are Not a Retention Strategy
The teams struggling right now aren’t those that stopped caring about relationships. They’re those that never moved past them.
Customers still want a named person they can call when something goes wrong. They want someone who will advocate for them inside the organization, go the extra mile, and make them feel like a priority. Those things matter. They will always matter. But they are entry fees now, not differentiators. If a portfolio company’s CS team isn’t doing those things, the customer will leave, for sure. If they’re only doing those things, there is no guarantee the customer will stay.
Think of it this way. A person can bring flowers every week, keep the house clean, and show up reliably — and still have a partner who feels unseen, because none of that effort was ever aimed at understanding what actually matters to them. The care is real. The model is wrong. B2B SaaS customers experience exactly this. They receive attentive, responsive, genuinely caring service and still quietly conclude that their vendor doesn’t understand what success looks like for their business. The calls are pleasant. The CSM is helpful. But when the executive sponsor asks what value they’ve gotten from the product this year, nobody in the CS conversation has a clean answer — because the model was never built around finding one.
That’s what an operating partner should be looking to identify. Not whether the team is trying. Whether the model they’re running was built to understand and deliver each customer’s definition of success, or whether it was built to manage the relationship and hope the value speaks for itself.
What the Model Is Actually Optimizing
A relationship model measures itself by whether customers are satisfied, whether saves happened, whether renewals closed. Those aren’t irrelevant metrics. They’re just answering a question about survival, not growth.
An outcome model measures something different: Whether each customer is achieving what they need to achieve, whether that success is real, visible, and documented, and whether the trajectory of the account reflects it. It doesn’t ask “did they renew.” It asks “do they have more value from this product today than they did two quarters ago, and can we show them that.”
The tell is what happens in a quarter where nothing dramatic occurs: No fire drill, no save, no early renewal. A relationship model has nothing to report in that quarter, because it was never watching for anything that didn’t require intervention. An outcome model has a full story: Which accounts are progressing, which are plateauing, and what each CSM did to move the needle before the customer noticed it needed moving.
A relationship model survives because customers tolerate it. An outcome model compounds because customers grow because of it.
The Question That Surfaces It
You don’t get to this distinction through the standard CS dashboard. GRR tells you what happened. It doesn’t tell you why or whether the model that produced it will hold.
The question that actually separates the two is simple: Ask the CS leader what a good quarter looks like when nothing renews early and nothing needs saving. Ask them how they know customers are getting the value they need and expect and how that is tracked, reported, and celebrated. More importantly, ask what CS does when customers are not realizing the outcomes they need to get real value and renew and grow year after year.
A relationship-oriented team will struggle to answer cleanly. Their definition of success was always built around the crisis: The save, the early close, the QBR that went well. Remove the crisis and there’s no story.
An outcome-oriented team has an answer ready because they’ve been working toward and measuring it the entire time. They can tell you which accounts expanded, why, what signal told them it was coming, and what the CSM did to ensure the expansion.
That’s the diagnostic: Not headcount, not whether a playbook exists, but what the team calls a win when nothing went wrong.
The answer will tell you more about whether that CS function is actually a model than any dashboard in the QBR will.
Post 6 in this series: The NRR number your board sees — and the one that actually matters.
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 →