How Much Revenue Are You Losing to Failed Payments?

The silent revenue leak

Ask a SaaS founder their churn rate and they'll give you a number — usually voluntary churn. Customers who actively canceled.

Ask them about involuntary churn — revenue lost because a payment failed and was never recovered — and you'll get a blank stare. Most companies don't track it separately. Some don't track it at all.

Involuntary churn accounts for 20-40% of all SaaS churn, depending on the study. For a company doing $100K MRR with 5% monthly churn, that's $1,000-$2,000/month disappearing because of expired cards, insufficient funds, and bank processing errors. Not because anyone decided to leave.

Why default retry logic fails

Stripe and other payment processors have built-in retry logic. The problem: it's generic. Stripe's Smart Retries optimize for the overall platform, not for your specific customer base.

Default retry schedules typically attempt 3-4 retries over 7-14 days with fixed intervals. This misses several critical patterns:

Payday alignment: B2B invoices to small companies often fail on the 28th-31st of the month and succeed on the 1st-3rd. Generic retries don't account for this.

Bank processing windows: Some banks reject charges during overnight batch processing (11 PM - 6 AM). Retrying at 2 AM is wasted.

Card update lag: When a customer gets a new card, there's a 3-7 day window before the new card number propagates through network token updates. Retrying daily during this window just generates more declines.

The math: what you're actually losing

Here's a framework to estimate your involuntary churn cost:

Pull your last 12 months of failed invoices from Stripe. Count how many were eventually recovered (paid after retry) vs. permanently lost (subscription canceled due to non-payment).

For most SaaS companies, the breakdown looks like this:

60-70% of failed invoices are recovered automatically by Stripe's built-in retries. 15-25% could be recovered with smarter retry timing + customer notification, but aren't. 10-15% are permanently lost — the customer's payment method is truly dead and they never update it.

That middle bucket — the 15-25% that could be recovered — is pure upside. On $100K MRR, that's $750-$1,250/month in recoverable revenue that most companies leave on the table.

Smart recovery: what works

Effective involuntary churn recovery combines three tactics:

Intelligent retry timing: Instead of fixed intervals, retry based on patterns that work for your specific customer segments. Retry small business customers on the 1st and 15th (common payroll dates). Retry enterprise customers during business hours on weekdays. Avoid retrying during bank batch windows.

Pre-dunning emails: Don't wait for the payment to fail. Stripe exposes card expiration dates. Send a card update email 14 days before expiration, then 7 days, then 3 days. Recovery rates are 3-5x higher when the customer updates their card before the charge fails.

Escalation sequences: If retries and the first dunning email don't work, escalate. A second email from a real person (not noreply@) with a direct card update link recovers another 10-15% of otherwise-lost revenue.

Measuring your recovery rate

The metric that matters is net recovery rate: of all invoices that failed on first attempt, what percentage were eventually paid?

Best-in-class SaaS companies recover 85-95% of failed invoices. The median is 65-75%. If you're below 70%, there's significant revenue sitting uncollected.

ChurnBurner automates this entire flow — smart retry timing based on your customer patterns, pre-expiration card update emails, and multi-step dunning sequences. It connects to your Stripe account and starts recovering revenue from the first failed payment.

The ROI math is straightforward: if you're doing $50K+ MRR, recovering even 5% more of failed payments pays for ChurnBurner's Pro plan several times over.