Your billing system says you have 412 active subscriptions. Last month, 31 of them failed to renew. Most of those customers still use the product, and the ones whose cards expired never told you a thing. How many of the 31 would have renewed if a reminder email had landed before the charge failed?
Subscription renewal emails are the cheapest retention system most subscription businesses never build. They run before the renewal date to keep payment details current, and they pick up the pieces after a failed charge. The engine underneath matters just as much as the messages. Stripe's Smart Retries uses AI signals to time retries, and the email layer decides who gets a reminder and when. The teams that wire this up properly stop losing revenue they never needed to lose.
The scale of the leak is bigger than most operators assume. Baremetrics, which tracks billing data across hundreds of subscription companies, puts the average loss at about 9 percent of monthly recurring revenue to failed payments. Chargebee's glossary, relaying ProfitWell's churn study, says 20 to 40 percent of churn is involuntary, and almost all of it is avoidable. The customers behind those numbers still want the service. The process dropped their payment.
Why subscription renewal emails lapse even when customers are happy
Happy customers lapse every day. Their card expires and the bank sends the replacement to an old address. The account runs low on the day the invoice lands. The bank flags a routine charge as suspicious. None of those reasons reflect how the customer feels about the product, and the subscription dies anyway.
Paddle's research says around 80 percent of payment failures are soft declines, temporary issues like expired cards or network errors. Most of the time the customer would happily pay, the system just could not complete the charge. That distinction matters, because a soft decline is recoverable with a reminder and a retry, while a deliberate cancel needs a completely different message.
The soft decline problem
A soft decline looks identical to a hard one in the billing dashboard. Same failed invoice, same red status. The difference only shows up when you dig into the decline code, and most teams never do. The practical consequence is that a large share of your churn is sitting in a state where one well-timed email fixes it. Chargebee's research arm, relaying ProfitWell's study of churn across subscription businesses, puts that share at 20 to 40 percent of all churn, with almost all of it avoidable. Paddle's own analysis of failed payments and chargebacks points the same way, with failed payments driving 20 to 40 percent of all churn and a further 10 percent of subscription revenue lost before recovery even starts.
The cost compounds quietly. Each lapsed subscription stops producing revenue, and the customer usually does not notice until they go looking for the product. The renewal email sequence exists to catch the lapse at the moment it happens, when one message fixes it.
What a renewal sequence sends, and when it sends it
The sequence does one job. It keeps the payment method current before renewal, then fixes a failed charge if one happens. Stripe's documentation describes the built-in version of both. Stripe sends renewal reminders before a renewal, an expiring-card email one month before the card on file expires, and a failed-payment email after each failed attempt.
Most billing platforms cover part of this out of the box. Stripe's subscription model handles retry logic, dunning and status transitions automatically, so the platform does the bookkeeping while the email layer does the talking. Chargebee's dunning controls retry frequency, reminder emails and final actions, and its Revive product reads 200-plus signals per failed payment to decide the next move. The email side is where most teams add their own layer, because the billing platform's default messages rarely sound like the brand.
Brevo, an email platform that slots into this stack cleanly, builds automations from triggers, conditions, actions and exit rules. The exit rule is the piece most teams forget. It stops a win-back sequence the moment a customer repurchases, so the messages never contradict each other, and Brevo's Shopify marketing automation guide walks through the mechanic.
The 90/30/7/1 cadence before expiry
The cadence we recommend is 90 days, 30 days, 7 days and 1 day before renewal. It is a recommended pattern anchored in timings the platforms already use. Stripe emails customers one month before the card on file expires, and Chargebee's customer Cafeyn sends automated reminders one month before card expiration, an approach the Chargebee case study credits with calming early churn.
- The 90-day email matters only for annual plans. It gives the customer time to switch to a card that will still work in a year, and it catches the "I forgot which card is on file" problem early.
- The 30-day email asks them to confirm the payment method. This is the touch with the strongest precedent, because it matches the expiring-card timing both Stripe and Cafeyn use.
- The 7-day email is a short heads-up that renewal is coming, with a one-click link to check the details.
- The 1-day email sets the expectation that the charge lands tomorrow, so a declined payment does not come as a surprise.
Keep the messages short and the ask single. One email asks for a card update. One confirms the renewal date. One explains what happens next. The same trigger-based approach powers customer anniversary email automation, where the date fires the automation and the exit rule keeps it honest.
The rescue lane when a payment fails
When the charge fails, the rescue lane takes over. Stripe's Smart Retries uses AI signals to time retries, with a recommended default of 8 attempts within 2 weeks, and it never auto-retries hard declines like a lost or stolen card, because those attempts will not succeed. Chargebee's Revive product reports a 53.5 percent recovery rate on retried invoices.
Retry logic and the messages around it
The email cadence inside the rescue lane matters as much as the retry logic. Recurly's dunning cheat sheet calls three to four messages over 28 days a widely accepted practice, and merchants who applied those practices saw a 12 percent revenue lift in the first three months. Each message needs one clear ask, whether that is updating the card, checking the bank or contacting support.
Chargebee's dunning also lets you pause retries until an expected payment date, which is useful when a customer says the money lands Friday. Recurly's churn guide notes there are more than 2,000 reasons a card can be declined, which is why the retry and the message matter more than the diagnosis. The customer does not need to understand the decline code. They need to know what to click.
The payoff shows up in the numbers. Across 119 US B2B SaaS companies tracked by Baremetrics in May 2026, recovery tools brought back USD 1,236,764 in a single month, with a median attempted recovery rate of 12.7 percent and a median ROI of 808 percent. Which of your failed renewals last month would have come back with a reminder and a retry? That is the exact pool of revenue the rescue lane protects.
Recovery analytics closes the loop. Stripe's revenue recovery dashboard tracks failure rate and recovery rate separately, so you can see whether the problem sits in the payment method data or in the rescue lane itself. Recurly's 2026 State of Subscriptions report notes the Software industry reclaimed over USD 155 million through recovery tools in 2025.
The win-back lane for customers who choose to leave
Some customers cancel on purpose, and no renewal email will change that. The sequence should still separate deliberate cancellations from accidental lapses, because the two groups need different messages. A customer who left on purpose needs a win-back sequence that waits a beat and makes a real offer, and the B2B win-back email workflow covers the timing and messages in detail.
The size of the prize justifies the extra lane. Recurly's 2026 State of Subscriptions report found 1 in 4 new sign-ups are returning subscribers, which makes reactivation one of the cheapest acquisition channels a subscription business has, because the customer already knows the product works.
For subscribers who do not respond to the win-back lane either, the play changes again. The email list re-engagement sequence covers the longer game of quiet lists, where the campaign extends past a few emails into a measured re-engagement program.
How to measure renewal rate in one billing cycle
Renewal rate is the percentage of customers who renew at the end of a billing period. Recurly's renewal guide puts good services businesses around 80 percent and sticky software at 90 percent or more, so a healthy benchmark for most SaaS sits above 90.
The two numbers that matter
The measurement itself takes one billing cycle. Take the customers due for renewal in a month, count how many renewed, and divide. Then split the failures by cause, because separating involuntary churn from voluntary churn is the first diagnostic step, and the two demand different fixes. For context, Paddle's analysis puts the average monthly SaaS churn rate around 5 percent, with a good rate at 3 percent or less.
The reason the split matters shows up in the baseline. Recurly's churn guide says 53 percent of total churn is involuntary and payment-led, and Baremetrics found about 9 percent of monthly recurring revenue leaks to failed payments. When the involuntary share is that large, the renewal sequence is the most direct fix available to the retention team.
Here is the calculation that decides whether this is worth doing. Take your monthly recurring revenue and multiply it by 0.09, the average share Baremetrics says leaks to failed payments. That is the pool a renewal sequence can recover each month. Compare it with the tool bill. Brevo's Starter plan starts at AUD 12 per month, its Standard plan, which includes the automation workflows, runs AUD 25 per month, and Paddle bundles revenue recovery into its 5 percent plus 50 cents per transaction fee. When the recovery pool is bigger than the tools, the case writes itself. This is something we do at Supernodes. A two-week pilot covers the audit, the connection and the measurement. Speak with us if it sounds like your Monday morning.
Frequently asked questions
How long does it take to set up a renewal email sequence?
The foundation can be live in two weeks. The Supernodes pilot covers the audit, the connection and the measurement, so the first renewal cycle runs with the sequence already in place.
How many renewal reminder emails should a customer get?
Three to four messages over 28 days is the widely accepted dunning practice Recurly cites. Before expiry, most annual plans cope with four touches at 90, 30, 7 and 1 days, and monthly plans need fewer because the cycle is shorter.
What is a good renewal rate?
Recurly's benchmark puts good services businesses around 80 percent and sticky software at 90 percent or more. For a SaaS product, above 90 percent is the healthy zone.
How much revenue do failed payments really cost?
Baremetrics measured about 9 percent of monthly recurring revenue lost to failed payments across hundreds of businesses, and ProfitWell's churn study, relayed by Chargebee, puts involuntary churn at 20 to 40 percent of all churn.
Do renewal emails annoy customers?
Most of the customers behind a failed payment still want the service. Paddle's data shows around 80 percent of failures are soft declines, temporary problems like an expired card, and a short email that fixes the payment method is usually welcome.
Is a renewal sequence the same as a win-back sequence?
Renewal emails run before the expiry date to protect revenue already earned. Win-back emails run after a lapse or cancellation to win the customer back, with different timing, messages and offers. The win-back workflow guide spells out the difference.