The corporate world is obsessed with a lie.
Every enterprise software company on the planet is currently pouring millions of dollars into building bloated Customer Success (CS) departments. They hire armies of well-meaning "Success Managers" to jump on quarterly business reviews, send automated anniversary emails, and beg users for feedback. They call it proactive churn management. Don't forget to check out our recent post on this related article.
It is actually a multi-million-dollar band-aid for broken products.
I have spent fifteen years building and advising enterprise software companies. I have watched boards greenlight massive headcount expansions for CS teams because net revenue retention dipped by two percent. It is a predictable, expensive reflex. And it almost always fails. If you want more about the history of this, Business Insider provides an informative summary.
When a customer churns, it is rarely because they did not get enough phone calls from an account manager. It is because your software failed to deliver value, or your sales team sold a hallucination to the wrong buyer.
The CS Crutch is Killing Your Product
Let us isolate the mechanical flaw in the standard SaaS operating model.
When you build a massive CS department, you create an organizational insulation layer. The product team builds a confusing UI or ships a buggy feature. Instead of the user abandoning the tool or demanding a fix, a Customer Success Manager (CSM) steps in to hold their hand. The CSM builds a custom workaround, writes a 40-page training document, and manually coaxes the client through the friction.
On paper, the account is saved. In reality, you have masked a systemic product failure.
[Broken Product Feature] ➔ [User Frustration] ➔ [CSM Intervention / Workaround] ➔ [Delayed Churn]
This feedback loop is toxic. Because the CSM "handled it," the product team never feels the pain of their bad design. The engineering backlog remains crowded with flashy new features meant to capture the next logo, while the core product remains a UX nightmare. You are paying a team of humans to act as human middleware for software that should just work.
If your product requires a human being to explain it to an enterprise user every three months, you do not have a customer success problem. You have a product debt crisis.
Dismantling the Product-Led Growth Illusion
The standard defense for big CS budgets is that enterprise tech is inherently complex. "We aren't a simple consumer app," executives argue. "We need people to drive adoption."
This premise is fundamentally flawed. Look at the data from companies that actually scaled efficiently. At its IPO, Atlassian famously spent next to nothing on traditional sales and customer success. They poured that capital directly into product R&D and self-serve documentation. They forced the product to bear the burden of adoption.
When you remove the CS safety net, something fascinating happens:
- The product team is forced to care about retention. If a feature is too complex, users quit, metrics drop instantly, and the product team has to fix the root cause.
- The sales team stops selling vaporware. If there is no CSM to clean up the mess after a bad handoff, selling to a bad-fit customer becomes an immediate operational nightmare.
Consider a thought experiment. Imagine a scenario where you fire your entire CS team tomorrow. Every customer is left alone with your software. Where do the support tickets spike? Which features cause users to close the tab? That is your real product roadmap. Every dollar you spend on a CSM to smooth over those exact friction points is a dollar spent hiding the truth from yourself.
Why Quarterly Business Reviews are a Waste of Time
Nothing epitomizes the emptiness of modern CS quite like the Quarterly Business Review (QBR).
We all know the routine. The CSM spends three weeks chasing the client to book a 45-minute Zoom call. They build a deck filled with arbitrary usage metrics: "Look, your team logged in 400 times this month!" They present data the client already knows, ask vague questions about strategic goals, and try to subtly pitch an upsell.
It is theater. Busy executives do not want another meeting on their calendar to review charts about software they already pay for. They want the software to quietly make them money or save them time.
If you want to know if a customer is getting value, stop looking at login frequency or QBR attendance. Look at utility metrics. Are they exporting data? Are they integrating your tool into their core operational stack? If a customer is deeply integrated, they do not need a quarterly meeting to remind them why they use you. If they are not integrated, a PowerPoint deck will not save the account.
The Dangerous Allure of NRR Manipulation
Let us look at the financial engineering that keeps this myth alive. Net Revenue Retention (NRR) is the darling metric of Venture Capital and Wall Street. If your NRR is over 120%, you are a unicorn. If it drops below 100%, you are radioactive.
To keep NRR artificially high, companies weaponize CS teams to force expansion revenue. They incentivize CSMs to upsell additional seats or add-on modules to existing clients.
This works in the short term, but it creates a bubble. If you push an upsell onto a client who is already struggling with core adoption, you are merely increasing the size of the eventual cliff. When that contract finally comes up for renewal, the client does not just downsize; they walk away entirely because they feel cheated.
True retention cannot be manufactured by an aggressive account management strategy masquerading as "success." It is a lagging indicator of utility.
+-----------------------------------+-----------------------------------+
| Old Way: CS-Driven Expansion | New Way: Utility-Driven Expansion |
+-----------------------------------+-----------------------------------+
| • CSM forces upsell during QBR | • Product triggers auto-expansion |
| • High friction, manual negotiation| • Low friction, usage-based |
| • Correlates with future churn | • Correlates with genuine value |
+-----------------------------------+-----------------------------------+
| Result: Short-term revenue bump | Result: Long-term compounding growth|
+-----------------------------------+-----------------------------------+
The Downside of Going Cold Turkey
To be fair, dismantling this apparatus is agonizing. If you suddenly shrink your CS team and demand that your product stand on its own two feet, your churn metrics will get worse before they get better.
You will lose the customers who were only staying out of professional courtesy to their friendly CSM. You will expose every flaw in your onboarding flow. The transition is violent, chaotic, and terrifying for a leadership team accustomed to smooth, human-managed retention curves.
But the alternative is worse: a slow, expensive death where your customer acquisition cost skyrockets because your product requires a human army to sustain it.
The Hard Shift: What to Do Instead
If you want to build a resilient, highly scalable enterprise architecture, you must reallocate your capital. Stop hiring account managers to do the job of engineers.
- Move 50% of your CS budget to Product Operations and Documentation. If a user gets stuck, they should find a definitive, clear answer within the app or a searchable repository in five seconds, not wait twenty-four hours for a CSM response.
- Tie product management bonuses to retention metrics. Stop rewarding product teams solely for shipping new features. Reward them when user drop-off rates decrease during onboarding.
- Enforce strict product-market fit parameters in sales. If a prospect requires three custom features and a dedicated CSM just to get live, walk away from the deal. They are an operational liability.
Fire the middleware. Fix the product. Stop hiding behind customer success.
