In partnership with
Hey {{first_name | CS Pro}},
The customer that churned on you last quarter? They're going to churn on you again.
Not the same logo, but the same situation, the same warning signs, the same renewal call where you felt it slipping and told yourself it would be fine.
It keeps happening because nobody looks at why it happened the first time. This week's episode fixes that, with a churn retro that changes how your team works…
But first, today’s sponsor
↓
Turn AI into Your Income Engine
Ready to transform artificial intelligence from a buzzword into your personal revenue generator?
HubSpot’s groundbreaking guide "200+ AI-Powered Income Ideas" is your gateway to financial innovation in the digital age.
Inside you'll discover:
A curated collection of 200+ profitable opportunities spanning content creation, e-commerce, gaming, and emerging digital markets—each vetted for real-world potential
Step-by-step implementation guides designed for beginners, making AI accessible regardless of your technical background
Cutting-edge strategies aligned with current market trends, ensuring your ventures stay ahead of the curve
Download your guide today and unlock a future where artificial intelligence powers your success. Your next income stream is waiting.
Churn isn't the problem. Learning nothing from it is.
Losing a customer is painful, but losing a customer and learning zero from it is a choice you are making.
And the timing matters. We are living through the era where retention is the growth strategy. The median annual logo churn for B2B SaaS sits around 3.5%, which sounds tiny until you run it against your own book. A company under 3% annual churn with net revenue retention above 110% can command 8-12x ARR. One at 8% or more trades at 3-5x or worse. Same product, same revenue, but a leaky book versus a healthy one can triple what the company is worth.
Think about how obsessed the world is with reviews. Spotify Wrapped every December, athletes watching the tape the morning after a game even when they won. And then there's us in CS, where we lose a six figure account, write one word in a drop-down field, and move on. 🙈
That gap is the entire opportunity.
The mistakes that make a retro useless
I have made every one of these myself, so no judgment here.
You treat churn as an event instead of a signal. You obsess over the cancellation call, but that's the last frame in a very long movie. The real story happened months earlier, when the exec stopped showing up or usage flattened.
You write down the single drop-down reason. "Budget" is not a reason, it's a symptom. When a customer says it's too expensive, they're almost always telling you the value was never obvious enough to justify the price.
You do the retro alone inside your CS bubble. Churn is company-wide, and if the only people in the room are CSMs, you'll keep blaming CS when the root cause often sits in another department.
You turn it into a blame game, so everyone protects themselves instead of telling the truth. Or worst of all, you land on insights with no action. Everyone nods, the meeting ends, and not one playbook gets updated.
The Churn Retro Loop
Every stage starts with R so you remember it when you're tired and tempted to type "budget" and move on.
Reconstruct the timeline. Rebuild the whole account month by month, from signing to kickoff to the day they left. You're building a flight recorder, and nine times out of ten the warning signs were screaming months before renewal.
Root cause. Use the five whys. Start at "too expensive" and keep asking why until you get from "budget" to something real, like "we have no process for re-onboarding when a champion leaves." One is an excuse, the other you can actually solve.
Recognize the pattern. Tag every churn with a type: onboarding failure, value gap, relationship failure, product gap, bad fit, sponsor change, or involuntary. When you look up after a quarter and 60% is tagged relationship failure, that's not one sad account, that's a flashing sign your team has a multi-threading problem.
Rewrite the playbook. Every retro ends with one concrete change, with an owner and a date. A trigger when your main contact goes quiet for 30 days. A mandatory QBR question on business outcomes. Insight without an owner is just a wish.
Recur. Run it monthly, on the calendar like payroll. At the start of each one, before you look at new losses, check whether last month's rewrites got built and whether the same tags are dropping.
The hardest part was knowing I could have seen all of it coming if I had done the work at the front end. That was the quarter that changed how I operate. I never started another one without the audit, the segmentation, the forecast, and the plays. My numbers improved, but honestly so did my confidence. A pilot does not take off without a flight plan, and neither should you.
This week's challenge
Run one churn retro. Just one. You don't need permission or a meeting. Pick one account from the last 90 days and walk it through the loop yourself: reconstruct the timeline, do the five whys out loud on paper, tag the type, and write down one change with an owner and a date. It'll take 45 minutes and teach you more than the last five churn reports you skimmed.
Because a renewal is a sale, and every churn is a lesson if you're brave enough to study it.
Have a listen to the full episode on Spotify, Apple Podcasts, or YouTube, and let me know what you think.
I hope you enjoyed this week’s newsletter.
If you have any questions or suggestions, please feel free to contact us.
Cheers to your CS success,
Anika
