You're running a micro-SaaS. Maybe you have 50 customers. Maybe 500. You're probably the only person working on it, or one of two or three.
You have a hundred things competing for your attention: features to build, bugs to fix, customers to support, marketing to do. "Optimize dunning" is somewhere near the bottom of the list, sandwiched between "redesign the pricing page" and "finally set up proper monitoring."
That's reasonable. At small scale, every failed payment feels manageable. You might even be handling them manually right now, checking Stripe every few days and sending personal emails to customers whose payments bounced.
But there's a point where this stops working and starts costing you real money. This guide is about knowing where that point is, what to do before you reach it, and what to do after.
Stage 1: Under 20 Customers (Do the Minimum)
At this stage, you might see 1-2 failed payments per month. That's not a dunning problem. That's a personal email.
What to do
Enable Stripe's built-in retries. Go to Settings > Billing > Subscriptions and emails in your Stripe Dashboard. Configure automatic retries. Stripe's default is 3 retries over 3-4 weeks. Leave it on. This alone recovers 15-25% of failures with zero effort from you.
Turn on Stripe's dunning emails. In the same settings area, Stripe can send basic payment failure emails to customers. These emails are generic and Stripe-branded, not your-branded. But they work, and at this stage, "works" is all you need.
Personally follow up on high-value failures. If your $99/month customer's payment fails and Stripe's automatic email doesn't resolve it, send a personal email from your actual email address. At this scale, personal outreach is both feasible and effective. A direct email from the founder recovers far more than any automated sequence.
What not to do
Don't spend a week building a custom dunning system. Don't sign up for a dunning tool. Don't A/B test email subject lines. Your time is worth more than the $100-200/month in failed payments at this stage. Build your product.
Stage 2: 20-100 Customers (Stripe's Tools + Light Automation)
Now you're seeing 3-8 failed payments per month. At $50-100 average revenue per customer, that's $150-800 in monthly revenue at risk. Not catastrophic, but not nothing.
What to do
Upgrade your Stripe retry settings. Instead of the default schedule, customize your retry timing based on what you've observed. If most of your failures are insufficient_funds, retrying on the 1st and 15th (common paydays) performs better than fixed intervals.
You can configure a smart retry schedule in Stripe:
- First retry: 2 days after failure
- Second retry: 5 days after failure
- Third retry: 10 days after failure
Write your own dunning email. Replace Stripe's generic email with one that matches your brand and voice. Stripe lets you customize the payment failure email template. Make it specific: include your product name, the customer's name, the amount, and a direct link to update their card.
Here's a simple template:
Subject: Your [Product] payment didn't go through
Hi [Name],
Your $[amount] payment for [Product] didn't process. This
usually happens when a card expires or a bank flags something.
You can update your card here: [Stripe-hosted link]
Takes about 30 seconds. Once updated, we'll retry automatically.
If you have questions, just reply to this email.
[Your name]
[Product]
Set up a Stripe webhook for payment failures. If you're technical (and as a micro-SaaS founder, you probably are), set up a webhook listener for the invoice.payment_failed event. This gives you real-time visibility into failures and lets you trigger custom logic, like a Slack notification so you know immediately when a payment fails.
At this stage, a Slack notification might be all you need. You see the alert, glance at it, and decide if manual follow-up is warranted.
The break-even calculation
Should you pay for a dunning tool at this stage? Run the numbers:
Monthly failed payments: 5
Average revenue per customer: $75
Monthly revenue at risk: $375
Current recovery rate (Stripe defaults): 20% = $75 recovered
Expected recovery with dunning tool: 65% = $244 recovered
Additional monthly recovery: $169
Cost of dunning tool: $30-50/month
Net benefit: $119-139/month
If the math works, great. If the net benefit is marginal relative to your time, Stripe's built-in tools plus occasional manual follow-up is a perfectly valid approach at this scale.
Stage 3: 100-500 Customers (Time to Systematize)
This is the tipping point. You're seeing 10-50 failed payments per month. Manual follow-up is eating 2-4 hours of your week. Some failures are slipping through because you're busy. The revenue impact is $500-3,750 per month, or $6,000-45,000 annually.
At this point, the cost of not having a dedicated dunning system exceeds the cost of setting one up.
What to do
Set up a proper dunning sequence. You need at least 3-4 automated emails, spaced over 7-14 days, with escalating urgency. Here's the simple sequence that covers 90% of cases:
Email 1 (Day 0): The Heads-Up
Subject: Quick fix needed for your [Product] subscription
Hi [Name],
Your $[amount] payment for [Product] didn't go through.
This usually happens when a card expires or a bank flags
the charge. Quick fix:
[Update Payment Method]
Once updated, we'll retry automatically. Your account
is safe in the meantime.
[Your name]
Email 2 (Day 3): The Reminder
Subject: Still need your updated card for [Product]
Hi [Name],
Just following up. Your $[amount] payment for [Product]
still hasn't gone through.
If you've been meaning to update your card but haven't
gotten to it, here's the link: [Update Payment Method]
Your account is active for now, but we'll need to pause
it if we can't process payment by [date].
[Your name]
Email 3 (Day 7): The Deadline
Subject: Your [Product] account will be paused on [date]
Hi [Name],
We've tried to process your $[amount] payment a few times
now without success.
Your [Product] account will be paused on [date] unless
payment is updated.
[Update Payment Method]
If you'd like to cancel instead, you can do that here:
[Cancel Link]. No hard feelings.
[Your name]
Email 4 (Day 10): The Last Chance
Subject: Last day for your [Product] account
Hi [Name],
Your [Product] account will be paused tomorrow due to
the unpaid invoice of $[amount].
All your data will be preserved for 30 days. You can
reactivate anytime by updating your payment.
Last chance to update: [Update Payment Method]
[Your name]
This four-email sequence, sent over 10 days, recovers 55-65% of failed payments. That's roughly 3x what Stripe's built-in retries achieve alone.
Add SMS (optional but effective)
If you collect phone numbers, adding 1-2 SMS messages to your sequence bumps recovery rates by 15-20%. A simple text on Day 2 and Day 8 fills the gaps between emails.
Pre-authenticated links matter
The single most impactful thing in your dunning sequence isn't the copy. It's the link. A pre-authenticated payment update link (no login required) converts 2-3x better than "log in and navigate to billing."
Stripe Billing offers a customer portal where customers can update their payment method. You can generate session URLs that go directly to the payment update form. Use those.
Stage 4: 500+ Customers (Full Dunning System)
At this scale, you're seeing 50+ failed payments per month. The revenue at risk is $3,750+ monthly. This is no longer a side concern. It's a core business operation.
What changes at scale
Volume makes manual follow-up impossible. You can't personally email 50 customers per month. Even if you could, the opportunity cost of your time makes it irrational.
Patterns emerge. With enough data, you'll see patterns: certain card types fail more often, certain geographies have higher failure rates, certain times of month are worse. A dedicated dunning system lets you act on these patterns.
Multi-channel becomes essential. Email alone caps out around 50-60% recovery. Adding SMS pushes you to 65-75%. At scale, that 10-15% difference represents thousands of dollars monthly.
Analytics drive optimization. Which email in your sequence converts the most? What's the optimal delay between messages? Are certain subject lines outperforming others? You need data to answer these questions, and you need enough volume for that data to be meaningful.
What to do
Deploy a dedicated dunning tool. At 500+ customers, the ROI is clear. A dunning tool that costs $50-100/month will typically recover 10-30x its cost in additional revenue.
Implement pre-dunning. Monitor card expiration dates and reach out to customers before their cards expire. This is the highest-ROI dunning activity, with 80-90% success rates versus 60-70% for post-failure recovery.
Segment your dunning. Not all customers are equal. A $299/month customer deserves a different (more attentive, more personal) recovery path than a $19/month customer. At minimum, create two tiers of dunning intensity.
Track your metrics. Recovery rate, time to recovery, recovery rate by sequence step, recovery rate by failure type. Review monthly and optimize.
The Cost-Benefit Decision Framework
Not sure where you fall? Use this quick framework:
| Monthly Failed Payments | Monthly Revenue at Risk | Recommended Approach | Expected ROI of Dunning Tool |
|---|---|---|---|
| 1-5 | Under $300 | Stripe defaults + manual | Not worth it yet |
| 5-15 | $300-1,000 | Custom Stripe emails + webhook alerts | Marginal, evaluate |
| 15-50 | $1,000-3,750 | Dedicated dunning tool | 5-15x |
| 50+ | $3,750+ | Full dunning system + SMS + pre-dunning | 10-30x |
The tipping point for most micro-SaaS businesses is around 10-15 failed payments per month. Below that, the time and cost of setting up dedicated dunning outweighs the benefit. Above that, every month without proper dunning is money left on the table.
Common Mistakes Micro-SaaS Founders Make
Over-engineering early
Don't build a custom dunning pipeline with Kafka, Redis queues, and a custom email renderer when you have 30 customers. Stripe's built-in tools plus a well-written email template handle 80% of the job at this scale.
Under-investing later
The opposite mistake. You hit 200 customers and you're still manually checking Stripe once a week. Payments are failing and you're not catching them for days. This is the point where a simple dunning tool pays for itself many times over.
Ignoring it entirely
"My churn is 5%, that's normal for SaaS." Sure, but 1-2% of that might be involuntary churn from failed payments. That's recoverable revenue you're writing off. Even at small scale, awareness matters.
Using aggressive language
You're a one-person SaaS sending dunning emails. Your customer is a human who likes your product. "URGENT: PAYMENT FAILURE" is never the right tone. "Hey, your card didn't go through, here's a quick fix" is.
Key Takeaways
- Match your approach to your stage. Stripe defaults work fine at 20 customers. At 200 customers, you need more.
- The tipping point is 10-15 failed payments per month. That's when a dedicated dunning system starts making financial sense.
- The simple 4-email sequence works. Friendly, escalating, with pre-authenticated links. This handles 90% of recovery scenarios.
- Don't build, buy. Unless dunning infrastructure is your core product, spend your engineering time on features your customers pay for.
- Pre-authenticated links are the biggest lever. Removing the login step doubles recovery rates regardless of your scale.
Rekko is built for this exact problem. Connect your Stripe account, set up a sequence, and start recovering failed payments in minutes. No complex configuration. No engineering work. Just automated recovery that works from day one.
Start your free trial and spend your time building product, not chasing payments.