Why Customer Success Platforms Won't Disappear In The Age Of Claude

Over the past year, the same question has surfaced in nearly every executive conversation I've had with revenue leaders. It usually goes something like this: If Claude can connect directly to Salesforce, Zendesk and our product data in real time, why do we still need dedicated customer success software at all?

It's a genuinely fair question, and I've stopped trying to dismiss it quickly. The demos are impressive. In under five minutes, you can connect an AI model to your CRM and watch it summarize enterprise accounts, surface churn risks and draft executive follow-up emails. The first time I watched one of these live, even I had to sit with the implications for a moment.

But enterprise operations are not demos. The gap between a compelling pilot and a reliable production system is becoming one of the most consequential misunderstandings in enterprise AI today.

What Breaks After The Pilot​

As the head of customer success at NbliK AI, managing thousands of customers and leading a team of 20 customer success managers, I've seen this pattern emerge repeatedly. A team connects an AI model to its customer data stack and asks which enterprise accounts are most likely to churn. Within seconds, the model surfaces health summaries, usage patterns, renewal risks and recommended next steps. The productivity gains are immediately obvious, and leaders quickly begin imagining how much more efficient customer success could become.

Then the pilot ends and the real work begins. The challenge is no longer generating insights but ensuring those insights remain consistent and trustworthy when dozens of customer success managers rely on them across different workflows, regions and customer segments.​

When AI Meets Real Customer Operations

Part of the reason I remain skeptical of the idea that reasoning models alone can replace customer success platforms is because we've experimented with these workflows ourselves. At NbliK AI, we explored how large language models could help customer success teams prepare for renewal conversations, identify at-risk accounts and uncover expansion opportunities, and while the initial results were undeniably impressive, it quickly became clear that the value of the recommendations depended as much on the quality of the underlying operational context as the model itself. As the system pulled together information from CRM records, support conversations and product usage data, we found that inconsistencies in customer health definitions, account ownership and business logic across systems could lead to recommendations that were individually reasonable but difficult to act on with confidence, highlighting that the challenge was not a lack of intelligence but the reality of asking a model to reason across fragmented and inconsistent sources of truth.

The Governance Gap

That experience changed the way I think about enterprise AI. The limiting factor was rarely the model's ability to summarize, infer or recommend. The limiting factor was whether the surrounding systems had enough consistency, governance and shared business logic for those recommendations to be trusted and acted upon at scale.

Interestingly, this challenge is not unique to customer success. According to McKinsey's State of AI research, organizations continue to accelerate AI adoption, but many struggle to translate experimentation into measurable business value because of governance, integration and operational readiness challenges. Deloitte's State of AI in the Enterprise research similarly highlights governance, risk management and data readiness as some of the most significant barriers to scaling AI successfully.

The Myth Of Clean Enterprise Data

One of the most persistent misconceptions I encounter is that enterprise data is essentially structured and clean, waiting to be queried. In practice, the opposite is almost universally true. A typical SaaS company stores customer information across Salesforce, HubSpot, Zendesk, Slack, product analytics platforms and a graveyard of spreadsheets that no one officially maintains but everyone quietly depends on.

None of these systems fully agree with each other. Product teams define an active customer one way. Customer success defines it differently. Finance calculates renewal eligibility using its own logic that neither team fully understands. I've sat in rooms where three senior leaders spent 40 minutes arguing over a single customer's health status because their respective systems showed three different answers. Humans at least bring institutional memory and judgment to those disputes. AI systems only understand the information they're given.

Reasoning Engines Vs. Operational Infrastructure

The market is slowly finding a more honest vocabulary for what AI models actually are. They are extraordinary reasoning systems. They summarize, pattern match, synthesize and generate recommendations at a speed and scale no human team can match. What they are not, and what many companies are mistakenly trying to make them, is operational infrastructure.

Operational infrastructure requires consistency, governed access and standardized business definitions that hold across teams and quarters. A customer success organization managing millions in recurring revenue cannot run on systems that reinterpret customer health based on prompt phrasing or missing metadata. Enterprise renewals and executive relationships don't tolerate ambiguity the way a consumer chatbot might. When the same account generates conflicting churn signals depending on which CSM runs the query, the tool has become a liability rather than an asset.

The Infrastructure-Led Future

I don't believe AI will replace customer success platforms. Rather, I believe AI becomes dramatically more valuable when it operates on top of trusted operational infrastructure built specifically for enterprise workflows, where customer intelligence, governance and business logic provide the context needed to produce reliable outcomes at scale. The model provides the reasoning, but the infrastructure underneath provides the operational truth that allows that reasoning to be applied consistently. What I keep telling founders and revenue leaders is that the companies most likely to succeed in the enterprise AI transition will not necessarily be those with access to the most capable models but those that build the strongest operational foundations around them, ensuring that AI-generated recommendations are trustworthy enough to inform real business decisions.​

Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?