Churn preventionfor usage-based SaaS.
See whose usage is fading in Stripe Meters or PostHog, ranked by money at risk.
In usage-based SaaS, churn often starts without a cancel.
Usage fades, spend falls, and the subscription can stay active with nothing billed. Usage-based churn is that loss of metered revenue. Reducing it means spotting the fall against each customer’s own baseline in Stripe Meters and acting while they still use the product.
Spend falls beforeanyone cancels.
For pay-per-use and AI products, the bill shrinks first. There is no seat cut or cancel date to warn you.
Fading, thenstopped using.
Usage-only customers don’t cancel first. They fade, then stop. Each stage has its own label, and the move comes while they’re fading.
Moves that fitpay-per-use.
This is customer retention software written for how usage customers pay. Approve each move, or set rules with limits.
Usage revenue, countedthe same everywhere.
Usage MRR is the average of a customer’s last 3 metered invoice amounts, or fewer when the history is shorter.
That one figure feeds money at risk, the ranking, the free churn report and Kept MRR.
The customer page labels it “average of last 3 invoices”. The free churn report reads billing only; usage signals from Meters or PostHog start with the trial.
At launch, usage accounts get three usage metrics.
Usage revenue, idle customer rate and usage-based NRR. Mark known quiet months in your profile, and a drop inside one shows “Seasonal?” without raising risk on its own.
Kept MRR counts usage customers kept by a move at what they pay now.
Tied to invoices, and never Stripe’s own recoveries. A comparison group of at-risk customers left alone shows what changed: read how we measure money kept.
Free shows who.Paid keeps them.
Questions aboutusage-based churn.
A usage-only customer counts as churned when usage stays at zero for whole billing periods while the subscription is still active, with the reason "stopped using". Before that, they show as fading, and a check-in can still go out.