Churn

Churn is the metric founders measure most often and understand least often. There are at least six valid ways to compute it (customer vs. revenue, gross vs. net, contracted vs. realized, monthly vs. quarterly cohort) and the wrong choice will tell you a comforting lie for months. We've watched founders celebrate "1% churn" that was actually 4.2% gross because they were looking at the net number after expansion revenue masked the bleed underneath.

The single most common diagnostic mistake: looking at the aggregate churn rate without segmenting. Aggregate churn is the average of healthy customers and customers actively cancelling — by definition it under-reports the problem on your worst cohort. Almost every "churn mystery" we've helped a founder debug turned out to be one bad segment (a specific plan, a specific acquisition channel, customers from a single campaign) pulling the average down or up. Segmentation is the lever, not aggregate reduction.

Start with what is churn rate, founder definition — it lays out the six definitions and which one to default to at your stage. For actionable reduction tactics, how to reduce customer churn ranks them by effort vs. impact (dunning is almost always the highest-impact, lowest-effort lever — and the one most founders never set up properly). For the rare advanced case where expansion outpaces gross churn, negative churn SaaS shows how to engineer it without faking the numbers.

The hardest part of churn work isn't measurement — it's deciding which cohort to fix first. Indie founders tend to over-invest in saving customers who were unlikely to stick regardless of intervention. Better to spend that energy preventing the next bad signup than rescuing the last bad one. The articles here are organized so you can identify which intervention is worth your week, given what your Stripe data is actually telling you, rather than what a generic best-practices post hopes is true.