Churn kills. And your customer success team can't save you.

Infinia · 2026-10-16

Here's the uncomfortable part, before anything else:

If your churn is high, hiring a VP of Customer Success is probably the wrong move.

It feels right. Customers are leaving, so you hire someone whose job is keeping customers. You give them a team, a tool and a dashboard. Six months later, churn is the same, and now you also have a team that writes very good explanations of why.

Subscriptions changed the deal you made with customers

In the old model, you closed a sale and the revenue was yours. If the product disappointed, that was a support problem.

Subscription software ended that. In what Winning by Design calls Revenue Architecture, the close isn't the finish line. It's the first payment on a promise you have to keep every month, every quarter and every year.

So a customer leaving takes more than this month's revenue. It takes every payment they would have made after that. The whole business model depends on future revenue, and churn deletes the future.

That's why churn is not a metric. It's a slow leak in the thing your valuation is built on.

The math founders don't want to do

Take a company at $3M ARR.

At 2% monthly revenue churn, you lose about 21% of your revenue base in a year. That's roughly $645,000 of ARR gone before you count a single new customer.

At 1% monthly, you lose about 11%, or roughly $340,000.

Same company. Same product. One percentage point a month is a difference of about $300,000 a year.

Here is the truth that few talk about:

• Growth gets harder. To grow 50% next year at 2% monthly churn, you need to sell roughly $2.1M of new ARR, not $1.5M. Sales is filling a bucket with a hole in it.
• Valuation shrinks. If investors value you at 6x ARR, that $645K of lost ARR is close to $4M of enterprise value gone in a year.
• The raise gets harder. Net revenue retention is one of the first numbers investors ask for. If existing customers are worth less this year than last, every growth number in your deck gets discounted.
• It compounds. A customer who would have stayed five years at $30K a year is $150K of future revenue. Lose them in year one and you lose all of it.

And here's the scariest part: most founders at $1M to $5M ARR can't tell you why their customers leave. They know the rate. They don't know the reason.

Why customer success can't fix it alone

This is where the strong opinions start.

Customer success sees churn at the very end. By the time someone is in a "save" conversation, the customer decided to leave weeks or months ago. They decided because of something that happened much earlier:

• They were sold the wrong plan, or sold to when they were never a fit. That's a pricing and targeting problem. It shows up in the numbers.
• The product broke a promise. Slow, unreliable, missing the integration they were told was coming. That's a technology problem.
• Nobody noticed the warning signs. Usage dropped, seats shrank, logins stopped. That's a data problem.

Customer success can soften all three. It can't fix any of them. You can't relationship-manage your way out of a product that doesn't do what you sold.

So a CS hire becomes the most expensive way to watch churn happen.

The first line of defense: a CFO and a CTO working together

Here's my position. The first line of defense against churn is a fractional CFO and a fractional CTO working together. Not because they talk to customers. Because they own the two halves of the reason customers leave.

The CFO finds where churn comes from.

• Which cohorts churn, and which plans.
• Whether discounted deals churn faster than full-price ones.
• What each lost customer was worth over their expected lifetime.
• Which accounts are shrinking before they cancel.

The CTO finds why the product didn't hold them.

• Which features the churned customers stopped using, and when.
• Whether reliability or performance dropped for that segment.
• Which promised integrations never shipped.
• Whether the warning signs exist in your data and nobody is looking at them.

Separately, each produces a report. Together, they produce a cause. The CFO says "customers on the mid-tier plan who came through the partner channel churn at three times the average." The CTO says "that's the segment that depends on the integration we deprecated in March." Now you have something you can fix.

Each owns a number. The CFO owns net revenue retention. The CTO owns the product reasons behind it. Neither is billing you for meetings about it.

When you don't need this

• Your churn is low and you know why. If net revenue retention is over 100% and you can explain the losses you do have, keep doing what you're doing.
• You're under $1M ARR. At that stage, churn is usually product-market fit telling you something. Talk to every customer who leaves yourself. You don't need anyone else yet.
• The cause is obvious and single. If customers leave because one feature is missing, you don't need two executives. You need to build the feature.
• You already have a strong finance lead and a strong technical lead who talk to each other. Then the job is covered. Get them in a room once a month with the churn list.

If you're in one of those groups, we'll tell you that, and send you back to your product.

Three questions to answer this week

1. What is your net revenue retention, and is it going up or down?
2. Of the last ten customers who left, what was the actual reason for each one? Not "budget." The real reason.
3. Which customers will leave next quarter, and how do you know?

If you can't answer all three, churn isn't a customer success problem. No one owns the number yet.

And while nobody owns it, your future revenue is leaving one renewal at a time.

If you're at $1M to $5M ARR and churn is the number keeping you up at night, start here: infinia.fun/for-businesses/intake