There is a tax on your SaaS revenue that nobody sends you a bill for. It does not show up in your analytics. Your customers do not complain about it. But it quietly drains 5-10% of your monthly recurring revenue, every single month.
It is called involuntary churn -- and it happens when payments fail.
What Is Involuntary Churn?
When people talk about churn, they usually mean customers who cancel. They are unhappy, they found a competitor, they do not need you anymore. That is voluntary churn, and yes, it is important to reduce.
But there is a second kind: involuntary churn. These are customers who want to keep paying you, but their charge fails. The reasons are mundane:
- Their credit card expired
- Their bank flagged the transaction
- Insufficient funds at the exact moment you charged them
- Network errors between your payment processor and their bank
The customer did not do anything wrong. They probably do not even know it happened. But their subscription is now at risk.
The Scale of the Problem
Industry data consistently shows:
- 5-10% of recurring charges fail on the first attempt
- 1.5-3% of monthly revenue is permanently lost to involuntary churn
- For a SaaS doing $50K MRR, that is $750-$1,500/month in preventable revenue loss
Over a year, that adds up to $9,000-$18,000. For a bootstrapped SaaS, that is the difference between hiring your first employee or not.
Why Stripe Smart Retries Are Not Enough
If you use Stripe, you probably know about Smart Retries. Stripe uses machine learning to determine the optimal time to retry a failed charge. It works reasonably well.
But Smart Retries only handle the retry timing. They do not:
- Email your customer to let them know their card was declined
- Alert customers when their card is about to expire (before the failure)
- Send win-back emails to customers who cancel after repeated failures
- Show you analytics on your recovery rates and at-risk revenue
A complete dunning strategy adds a communication layer on top of retry logic. The two work together: Stripe retries the charge at the optimal moment, while your dunning system ensures the customer knows to update their payment method.
The ROI of Dunning
Smart dunning emails recover 30-70% of failed payments. Here is what that looks like in practice:
| MRR | Monthly Failures (7%) | Recovered (50%) | Annual Recovery |
|---|---|---|---|
| $10K | $700 | $350 | $4,200 |
| $30K | $2,100 | $1,050 | $12,600 |
| $50K | $3,500 | $1,750 | $21,000 |
| $100K | $7,000 | $3,500 | $42,000 |
At a $19/month cost for a dunning tool, the ROI ranges from 18x to 184x. It is one of the highest-ROI tools a SaaS founder can invest in.
See Your Own Numbers
I built a free, interactive calculator that lets you plug in your MRR and see exactly how much you are losing to failed payments:
It is entirely client-side -- no data is collected, no signup required. Adjust the sliders for your failure rate and expected recovery rate, and see the impact on your bottom line.
What You Can Do About It
Three levels of effort, from easiest to most comprehensive:
Level 1: Know your number. Check your Stripe dashboard for your actual payment failure rate. Go to Payments > Failed. Most founders have never looked at this.
Level 2: Set up basic dunning. At minimum, make sure failed payment customers get an email with a link to update their card. Even a simple automated email recovers some revenue.
Level 3: Use a dedicated tool. Purpose-built dunning tools like Rebill ($19/mo), Churn Buster ($249/mo), or Stunning ($99/mo) automate multi-step email sequences, expiring card alerts, and recovery analytics.
The math on this is too good to ignore. Even at conservative estimates, most SaaS companies are leaving thousands of dollars a year on the table by not addressing failed payments.
Start by checking your numbers. The calculator is free -- the insight might be worth thousands.
Top comments (0)