Most CS leaders I talk to can tell you how many accounts are red. Few can tell you what that costs in euros, or when the cash lands. That’s the gap between a CS team that reports and one that gets a seat in the forecast conversation.

Post-sales performance sets revenue timing, renewal confidence and forecast accuracy. Yet customer success, service delivery and finance still run as three separate functions in most organisations. Put them on the same account-level data and the same planning assumptions, and you see future cash inflows earlier. You also spot retention risk while there’s still time to act, and you put your best people on the accounts that matter.

Service delivery is now a revenue job

Service delivery used to mean fulfilling a contract and closing tickets. Subscription and outcome-based models changed that; post-sales now owns adoption, customer goals and anything that blocks renewal.

A defined post-sale process gives Finance a steady stream of operational signals. Onboarding usually takes 45 days, and one customer is still stalled at day 70; that’s a weaker renewal forecast, and it’s visible months before the renewal date.

Build one standard account timeline: onboarding, first value, adoption reviews, renewal preparation. Give every milestone an owner and a date. A delay then shows up as an operational flag, not as a financial surprise.

If you've followed this blog for a while, you know I've written about Customer Success alongside Inbound PR, channel programs, leadership, career, and life across six countries. It's been a mix — deliberately so. This space has always reflected who I am, not just what I do over the last 12+ years.

That's not changing. But something is shifting.

I've made the decision that the CS content needs its own home and focus.

This is why I've launched CS in the AI Era — a bi-weekly newsletter with one specific focus: helping Customer Success leaders reinvent CS as a revenue function, using AI to make that shift irreversible, and helping CS folks move from relationship managers to revenue leaders.

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

Most Customer Success organisations are not designed to fail. They're designed to survive.

Survive renewals. Survive escalations. Survive the quarter.

And that survival instinct — built into the org structure, the hiring profiles, the incentives, the mandate — is precisely what prevents growth.

This isn't a people problem. It's a design problem. And until CS leaders are honest about it, no amount of AI investment, tooling, or training will change the outcome.

The Narrow Design Problem

When most companies build a CS organisation, they start with two things in mind: onboarding and retention.

Get the customer live. Keep them happy. Renew the contract.

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