How does SaveMRR connect to Stripe?

You create a restricted API key in your Stripe dashboard and paste it into SaveMRR. Read-only access — SaveMRR cannot charge anyone, modify subscriptions, or touch your money. You can revoke the key in 2 clicks from Stripe anytime. No OAuth, no Stripe Connect, works in every country Stripe supports.

Will Cancel Shield break my existing cancel flow?

No. It's a single line of JavaScript you add to your app. When a customer clicks cancel, the widget pops up with an exit survey and a smart offer. If they accept, SaveMRR applies the discount or pause in Stripe. If you remove the script, your cancel flow goes back to exactly what it was. Zero risk.

How does SaveMRR login tracking work?

On the Growth plan, you drop a tiny JS snippet into your app (like an analytics script). It pings SaveMRR when a user logs in — no personal data, no tracking cookies. If someone hasn't logged in for 14 days, Churn Radar flags them as at-risk and auto-sends a check-in email. Most founders catch 3-5 at-risk customers per week they would have never noticed.

Does SaveMRR work with Paddle or LemonSqueezy?

Stripe only right now. That covers 96% of indie SaaS founders. Paddle and LemonSqueezy support is planned for later this year.

How much does SaveMRR cost?

Free plan: full Revenue Autopsy scan, no card needed. Starter: $19/mo (early bird, regular $49/mo) with Cancel Shield, Revenue Rescue, Churn Radar, daily digest. Growth: $49/mo (early bird, regular $99/mo) with everything in Starter plus Win-Back Autopilot, custom SMTP, JS login tracking, unlimited Stripe accounts, Slack alerts, custom branding. No percentage cuts — flat monthly fee. Early bird pricing locks in forever for the first 100 users.

Can I use SaveMRR on multiple SaaS products?

On the Growth plan, you can connect unlimited Stripe accounts from one dashboard with labels for each product. Perfect for portfolio founders running 3-8 micro-SaaS products. On the Starter plan, it's one Stripe account per SaveMRR account.

Can Revenue Rescue emails come from my own domain?

Yes. On the Growth plan, plug in your SMTP credentials and all recovery emails send from you@yourdomain.com — plain text, no 'sent via SaveMRR' footer. Looks like you personally wrote it.

How long before I see results with SaveMRR?

Revenue Autopsy shows your data in 60 seconds — you'll know exactly what you're losing before you even pay. Cancel Shield saves its first customer the moment someone tries to cancel. Revenue Rescue catches the next failed payment. Most founders see their first save within the first week.

What is SaveMRR and how does it reduce SaaS churn?

SaveMRR is a churn reduction platform for SaaS founders using Stripe. It provides 5 automated retention engines: Revenue Autopsy (free diagnostic), Cancel Shield (smart cancel flow with 42% save rate), Revenue Rescue (failed payment recovery with 55% recovery rate), Silent Churn Radar (pre-cancel detection using Stripe signals and login tracking), and Win-Back Autopilot (12% win-back rate). The average SaaS loses 5-12% of MRR monthly — SaveMRR can recover up to 40% of that. Setup takes 3 minutes via Stripe API key paste. Starts at $19/mo with no percentage cuts.

How does SaveMRR compare to Churnkey, Raaft, and other churn tools?

SaveMRR provides cancel flows, payment recovery, churn prediction, login tracking, and win-back campaigns — all for $19/mo with 3-minute setup. Churnkey starts at $250+/mo and requires a sales call. Raaft is $15-300/mo for cancel flows only — no payment recovery, no churn detection. Stunning is $100+/mo for dunning only. Churnfree is $49-199/mo for basic cancel offers. SaveMRR is the only tool that covers all 5 churn types in one product at indie-founder pricing. Some competitors also take 3-5% of recovered revenue on top of monthly fees — SaveMRR charges zero percentage.

Does Stripe Have Dunning? Yes, But Here's What It Misses

Short answer: yes, Stripe has dunning. It retries failed payments automatically and can send basic dunning emails. Long answer: Stripe's dunning is a starting point, not a solution. It recovers about 30-40% of failed payments and leaves the rest on the table. Here's exactly what Stripe provides, what it doesn't, and how to fill the gap.

Stripe's built-in dunning features

Stripe has two dunning features:

1. Smart Retries

When a payment fails, Stripe automatically retries it. Smart Retries uses machine learning to pick the optimal retry time based on factors like card type, day of week, and time of day. This is enabled by default and actually works reasonably well for transient failures (temporary declines, insufficient funds that resolve).

Stripe retries up to 4-8 times over approximately 3-4 weeks (the exact schedule varies). After that, the invoice is marked as uncollectible and the subscription status depends on your settings — it might cancel, pause, or stay active.

2. Failed payment emails

Stripe can send automated emails when a payment fails. To enable this:

Go to your Stripe Dashboard
Settings → Subscriptions and emails
Under "Manage failed payments," enable email notifications
You can customize the reply-to address and add your logo

That's it. One email template. Stripe sends it when the first payment fails, and optionally sends reminders. The email comes from Stripe (not your domain), uses Stripe's HTML template, and you have minimal control over the content, timing, or sequence.

What Stripe's dunning misses

Here's where Stripe's dunning falls short for SaaS founders:

No multi-email sequence — Stripe sends one email (or maybe a couple reminders with the same content). There's no escalation. No "friendly reminder" → "here's what you'll lose" → "final notice" progression. Research shows the second and third emails recover an additional 20-30% beyond the first.
No custom SMTP — Emails come from Stripe's domain or a generic noreply. Your customer sees an email from Stripe, not from you. This hurts open rates (customers don't recognize the sender) and deliverability (Stripe's shared sending reputation).
No plain-text option — Stripe sends HTML emails with templates. Plain-text emails have 40-60% higher open rates for transactional/dunning purposes because they feel personal and land in Primary instead of Promotions.
No pre-dunning — Stripe doesn't proactively alert you when a customer's card is about to expire or when spending patterns suggest a decline is coming. By the time the payment fails, you're already behind.
No analytics — Stripe shows failed payments in the dashboard, but doesn't aggregate recovery rates, email open rates, or show you which customers are in active dunning sequences.

How to improve Stripe's dunning

You have three options:

Option 1: Build your own

Listen for invoice.payment_failed webhooks, write an email sequence system, handle retry logic, track recovery. This works but takes 40-60 hours to build properly, plus ongoing maintenance. If you're already stretched thin as a solo founder, this is a poor use of your time.

Option 2: Use a dedicated dunning tool

Tools like Stunning ($99/mo), Gravy (custom + revenue %) focus exclusively on dunning. They do it well but only solve one churn type. You'd still need separate tools for cancel flows, churn detection, and win-back.

Option 3: Use an all-in-one retention tool

SaveMRR's Revenue Rescue handles dunning as one of 5 engines. You get the multi-email recovery sequence plus cancel flows, churn detection, win-back campaigns, and a free revenue diagnostic — all for $19/mo. The dunning is less customizable than Stunning's, but for most indie SaaS founders, the default sequence recovers 55% of failed payments without any tweaking.

Quick setup: Stripe dunning settings

Regardless of whether you use a third-party tool, make sure your Stripe dunning settings are configured:

Smart Retries — Enabled by default. Don't disable it.
Failed payment emails — Enable in Settings → Subscriptions and emails. Set reply-to to your support email.
Subscription behavior on final failure — Set to "Cancel subscription" (not "Leave as past due"). This gives you a clean signal to trigger win-back campaigns.
Customer portal — Enable Stripe's customer portal so dunning emails can link to a card update page.

These are table stakes. After configuring Stripe's built-in options, layer SaveMRR on top for the multi-email sequence, custom SMTP, pre-dunning alerts, and the four other retention engines that Stripe doesn't touch.