I started my SaaS career in Customer Success.

Not the version of CS that exists in most companies today. The version where you were responsible for the full customer relationship — adoption, outcomes, retention, and growth. Where upsell and cross-sell were part of the job, not someone else's quota. Where working with partners to drive expansion was expected, not exceptional.

I was 24. I had never done anything sales-related in my life.

And I loved it.

I loved it because it made sense. If a customer was succeeding with the product, achieving real business outcomes, getting value they could measure — of course they would want more. And who better to spot that opportunity than the person who had been working alongside them, understanding their business, guiding their adoption journey?

That year, I made President's Club. Not as a salesperson. As a CSM, on the channel side.

Not because I was selling. Because I was succeeding — and success, when it's genuine, creates its own commercial momentum.

Then Something Changed

There's a common assumption in CS leadership: CSMs don't act on AI signals because they don't trust them. That's not quite right. In most cases, the signal isn't the problem. The gap is what comes after it.

A CSM sees a risk score drop. An alert fires. A flag appears in the dashboard. And then — nothing. No context. No direction. No clear next step.

So they do what any reasonable person does when faced with ambiguity: they fall back on what they know. Their instinct. Their relationship read. Their experience.

Not because they're resistant to AI. Because the system handed them a problem without handing them a path.

Why CSM don't trust AI Signals

Every Customer Success leader I know is under pressure to adopt AI. The tools are being deployed. The dashboards are being built. The announcements are being made.

And yet — adoption stalls. CSMs quietly ignore the signals. Workarounds emerge. People revert to instinct over insight. This isn't a technology problem. It's a human one.

After years of building and running Customer Success and Customer Health operations across three major SaaS organisations, I've seen this pattern repeat. AI gets introduced. Behaviour doesn't change. Leadership assumes the team needs more training. What they actually need is something much harder to fix.

The real reasons AI fails in CS teams

Many organisations say Customer Success is a growth engine. Very few are actually designed for it.

In practice, Customer Success is still treated as a defensive function: protect renewals, manage risk, keep customers “happy enough” to stay. Expansion is encouraged, but rarely owned. Growth is expected, but inconsistently enabled. And when targets are missed, the root cause is often unclear.

AI has not changed this reality on its own. What it has done is make the gap between intention and execution impossible to ignore.

AI gives Customer Success unprecedented visibility into customer behaviour, risk, and opportunity. But visibility alone does not create growth. Leadership decisions do.

This post builds on the earlier parts of this series — from the evolution of the CSM role, to AI-ready operations, to trust, governance, and board relevance — to answer a harder question: what actually has to change for Customer Success to become a true growth engine?

Why “Customer Success as a growth engine” is mostly a myth today

For years, Customer Success has struggled to earn a consistent seat at the board table.Not because it wasn’t important — but because it was hard to translate.

Too often, CS updates sounded like anecdotes instead of evidence, sentiment instead of signal, reassurance instead of foresight. Boards don’t lack interest in customers; they lack predictable, decision-grade insight.

AI changes that.

Not because it suddenly makes Customer Success strategic — but because it makes it legible at the highest level of the organisation.

This post builds on the earlier parts of this series, where I explored how AI reshapes the role of the CSM, the systems that support Customer Success, the experience customers have at scale, and the trust and governance required to make AI usable. The final step is understanding what all of this means at the board level.