A failed card rarely looks dramatic at first. It usually sits in the background until the next renewal fails, then the churn report starts to lean the wrong way.
When I use Baremetrics pre-dunning emails, I try to catch that moment before it becomes a billing problem. The goal is simple, I want customers to update their card while the fix still feels easy.
For SaaS billing and retention teams, that small shift matters. It protects MRR, cuts involuntary churn, and keeps support from chasing preventable failures. I use a calm sequence, plain copy, and clear timing, then I watch the numbers to see if it earns its keep.
Why I start before the card fails
I treat pre-dunning and dunning as two different jobs. Pre-dunning prevents the failure, while dunning cleans up after it. That split matters because the tone changes once a charge has already failed, and customer patience changes with it. I like the contrast described in this pre-dunning vs dunning comparison, because it keeps the workflow honest.
Baremetrics Recover supports reminder emails before a card expires, and that is where I begin. The common starting point is a reminder 30 days before expiration, followed by another one about 7 days before. That gives customers enough time to act without making the note feel stale or pushy. For a clearer primer on the idea behind this timing, I also keep an eye on what pre-dunning means.
A failed payment is a broken door after the fact. Pre-dunning puts the sign in the hall before anyone reaches it.
I want the customer to solve the problem before the charge date, because that is when the fix feels natural.
When I do still get a failed charge, I switch into recovery mode and use best practices for SaaS dunning sequences. That keeps the prevention work separate from the rescue work.
How I set up the sequence in Baremetrics
I keep the setup simple. In Baremetrics Recover, I build the sequence around card expiration, then I match each reminder to a clear action. The point is not to write a long campaign. The point is to help someone update their card in under a minute.
I start with a small timing map.
| Reminder timing | What I say | What I want |
|---|---|---|
| 30 days before expiration | The card will expire soon | Early update |
| 7 days before expiration | Last reminder before renewal | Fast action |
| After failure | Move into dunning | Recovery |
This is where I think about the customer’s calendar. A 30-day reminder gives room for travel, approvals, or a card reissue. A 7-day reminder catches the people who ignored the first note or missed it in a busy week. The timing also lines up with common dunning email timing guidance, which is useful when I want to sanity-check my own cadence.
My setup steps usually look like this:
- I filter for active subscriptions that still matter. I do not want expired trials, canceled plans, or already-recovered accounts inside the sequence.
- I send the first reminder well before renewal or card expiration. That message stays short and calm.
- I send the second reminder closer to the date. This one is still polite, but it is more direct.
- I link to the billing update path with as few clicks as possible. If the customer has to hunt for the fix, the email loses half its value.
For subject lines, I keep the language plain. “Your card expires soon” works. So does “Update your billing details” or “Keep your plan active.” I want the email to sound like a useful heads-up, not a collection notice.
I also keep the body copy tight. One short line about the issue, one line about the fix, and one clear button are enough. Anything more starts to read like a lecture, and people tune that out fast.
Segmentation keeps the reminders useful
I never send the same reminder to every customer. A $29 monthly account and a large annual plan should not get the same tone. The first needs a short nudge. The second may need a bit more context, because more people inside the account care about the outcome.
Plan value is the first filter I use. After that, I look at billing history and customer type. If an account has failed before, I treat it with more care. If the customer is self-serve, I keep the message direct. If a team account has several users attached, I make the path to the update page obvious and easy.
This is also where I keep billing noise under control. I do not want to email a customer who already fixed their card, paused the account, or moved to a different plan. That kind of mistake damages trust faster than a failed payment does.
When I need a deeper recovery layer for the accounts that still slip through, I keep failed payment recovery strategies close at hand. Pre-dunning reduces the number of fires. Recovery handles the ones that still start.
Segmentation also helps with tone. Smaller accounts usually respond best to short, practical language. Larger accounts often need a slightly more formal note, especially when finance teams, admins, and end users all touch the same subscription. I keep the message respectful either way, because billing emails are part of the product experience.
What I measure after launch
Once the sequence is live, I stop guessing and start watching the numbers. I care less about how clever the copy sounds and more about whether the reminders keep money from slipping away.
| Metric | What it tells me | What I want to see |
|---|---|---|
| Recovered MRR | Revenue saved before or after failure | Move up |
| Card updates before renewal | Whether customers act in time | More updates |
| Involuntary churn | How many losses come from billing, not choice | Move down |
| Email opens and clicks | Whether the message earns attention | Steady lift |
| Support tickets about billing | Whether the flow is confusing | Fewer tickets |
I read these numbers together. If opens are strong but updates stay flat, the subject line may be fine, but the payment update page may be weak. If updates rise but support tickets also rise, the message may be too vague. If both fall, I know I need to rework the offer, the timing, or the segmentation.
I also compare the results against the rest of my billing system. When I use optimizing your subscription recovery process, I can see whether the pre-dunning step is doing real work or just adding another layer of email. The best sequences feel quiet. They prevent a problem before it gets loud.
Conclusion
When I use Baremetrics pre-dunning emails well, I stop treating card expiration like a surprise. I give customers a clear heads-up, keep the copy simple, and make the fix easy to find.
The strongest setups are the ones that stay calm. They use the right timing, the right segments, and the right metrics, so I can protect revenue without making billing feel heavy. That is the real win, fewer failed charges and a cleaner path to renewal.
