There is a version of customer success that looks fine from the outside.
GRR is holding. Renewals are closing. The board deck shows green. An operating partner reviewing the portfolio wouldn’t flag it. A CEO running the business wouldn’t lose sleep over it. And yet, somewhere in the organization, a CS team is grinding through every renewal like it’s a negotiation — because it is.
Reactive CS and proactive CS can produce nearly identical GRR numbers for a while. The difference doesn’t show up in the metric. It shows up in how the metric is being made.
What a retaining team looks like from the CEO’s chair
When CS is working, renewals don’t feel like events. They happen early, with little friction, because the customer has been building toward them. The CS team holds relationships at multiple levels of the account — not just the day-to-day contact, but the economic buyer and the executive who made the original decision. Those relationships exist because the team has been delivering against outcomes the customer actually cares about, tracking them, and making them visible.
The signal that tells you this is working isn’t the renewal rate. It’s what happens around the renewal. Customers are offering case studies nad providing reference calls without being asked. They’re raising new problems they want help solving. Sales isn’t fighting for expansion conversations — they’re getting pulled into them, because the customer’s experience with the product has created appetite for more.
Account plans exist and are genuinely actionable (tied to the customer’s business outcomes, not just product adoption milestones). Health scores are meaningful because they predict behavior; they don’t just reflect the state of the relationship with a single contact. When this is the reality, GRR is highly predictable. Not because someone is managing it closely at quarter-end, but because the work that produces retention happened months ago.
What a defending team looks like from the CEO’s chair
The defending team is not failing visibly. The renewals are still closing, but watch how they close. They go to the wire. They require executive involvement. They produce concessions (a discount, a free services commitment, a roadmap promise) that weren’t in the original deal and weren’t in the budget.
The CS team in this model spends its days reacting: Support tickets, escalations, and requests for enhancements that should have been surfaced earlier. Relationships in the account are shallow: One contact, maybe two, neither of them the economic buyer. When renewal time comes, the team doesn’t have a foundation to stand on, so it reaches for the same levers it always reaches for: Time, concessions, and effort.
I’ve watched this dynamic play out repeatedly, and the pattern is consistent: The CS team is working hard, even heroically. They just aren’t working in a way that builds anything durable. Every renewal starts from zero.
Sales knows this team well. They’ve stopped asking for expansion introductions, because the answer is always the same: The customer isn’t ready. The account isn’t stable. Give it another quarter, but that quarter never fully arrives.
The 18-month problem
The reason this matters for a PE-backed business specifically is the timeline. Eighteen months is long enough for a defending CS team to look like a retaining one: GRR holds and NRR doesn’t collapse. The board sees stability, so the operating partner isn’t asking questions.
Under that stability, though, the cost structure is expanding. Services commitments made to close renewals are consuming delivery capacity. Discounts are compressing ARR. Customers who aren’t getting value aren’t growing — and the accounts that should be driving NRR are flat or quietly shrinking.
By the time this becomes visible in the metrics, the window to fix it without affecting the exit story has shortened considerably.
The CS team isn’t broken. It’s just been defending instead of retaining — and those are different jobs, built on different foundations, producing different businesses. A defending team can sustain GRR. It cannot sustain NRR. It cannot build a referenceable customer base. It cannot support expansion motions that compound over time. And it will not hold together under the scrutiny of a serious acquisition or next-round diligence process.
What the CEO and operating partner need to ask
The question isn’t “are renewals closing?” They probably are. The question is how.
Are renewals predictable three months out, or are they uncertain until the final week? Is expansion happening because customers are succeeding, or stalling because they aren’t? When the CS team reports account health, do those scores predict outcomes, or do they describe the state of the relationship with the primary contact?
Does sales have a steady pipeline of expansion opportunities surfaced by CS, or are they prospecting their own book of business? Are customers actively providing references and case studies, or does every reference call require a favor?
A retaining team can answer those questions with specificity. A defending team will give you a narrative. The GRR number will look the same either way. For a while.
Post 5 in this series: What “we have a CS team” actually means — and why having the function isn’t the same as having the model.
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 →