Customer Success, Honestly Best seller

Why I rewrote it

Two years ago I published a CS guide called Mastering Customer Success, sold it at ₹499, and about 90 people bought it. Reading it back, the problem was obvious. It was a synthesis of every other CS guide on the internet, technically correct, and none of it could only have come from me.

This is the one I should have written the first time. Fourteen years of hiring CSMs, letting people go, defending retention numbers in board presentations, handling escalations that kept me up at night, and coaching CSMs from their first job through to Director. It's written for B2B SaaS, where a human CSM owns a portfolio and carries retention and growth.

It's also written from APAC. I lead CS across India, Southeast Asia, Japan, Korea and ANZ. The US playbooks assume a buyer, a set of communication norms and a timeline that don't hold here, and Part 4 is explicit about where the gap is.

It will tell you things you probably don't want to hear. That customer happiness is a lagging indicator. That weekly check-ins are a coping mechanism. That a high NPS score doesn't mean you're safe. I believed some of those things earlier in my career, and the evidence changed my mind.

Free extract

Chapter 1: Happy customers aren't loyal customers

I had a customer who loved us.

They loved their CSM. They loved the product. Every NPS survey we sent came back 9 or 10. They referred two other companies to us. At the quarterly business review, the VP of Marketing said they couldn't imagine running without us.

Six months later, they churned.

The reason wasn't a product failure or a service failure. The company got acquired. The new parent organization had a different vendor already. The decision wasn't made at the VP level. It was made at the CFO level in a country where we had zero relationships. All the goodwill we'd built with the team on the ground didn't translate upward. The economic buyer had no connection to us at all.

That experience clarified something I'd been circling around for years: happiness and loyalty are not the same thing.

A customer can like your product, respect your team, and still leave. Happiness is about experience. Loyalty is about outcomes, switching costs, and how deep the relationship goes into the organization. The CS industry has spent years conflating these two things. We optimize for CSAT scores and NPS scores and renewal surveys. We train CSMs to "make customers happy." We celebrate strong relationships. None of that is wrong exactly. But it misses what actually drives retention.

What drives retention is simpler and harder than happiness: does the customer believe they'd be worse off without you?

Not better with you. Worse without you. That's a different question. It requires a different kind of CS motion.

When a customer can answer yes to that question, they renew. Not because they like you. Not because the relationship is warm. Because the cost of leaving is real and the benefit of staying is provable. They've achieved something with your product they couldn't have achieved without it, and they know it.

This is the gap between a service mindset and an outcome mindset.

A service mindset says: respond quickly, be helpful, build rapport, make people feel cared for. An outcome mindset says: understand what the customer is trying to accomplish, measure progress toward that goal, and connect every interaction to whether they're actually getting there.

Both matter. Service matters. Responsiveness matters. Relationships matter. But if your entire CS strategy is built on making people feel good, you'll lose customers you thought were completely safe, and you won't understand why.

Here's a test you can run right now. For your five most important accounts, can you write down in one sentence the specific business outcome each of them has achieved with your product this year? Not features they're using. Not your NPS score with them. An actual business result they can point to.

If you can't write those sentences, you're operating with a happiness lens, not an outcome lens. The customer might not notice the difference yet. But they'll notice at renewal.

That's roughly half of chapter 1. The rest of it covers the practical shift: what to track, what to open a check-in with, and what to put on the last slide of a QBR.