Hospitals do rounds before a crisis, not after one. Subscription billing mostly does the opposite: all of its energy, tooling, and worry concentrates on the days after a payment fails, while the week before the renewal — when a meaningful share of failures are already visible and preventable — passes without a single scheduled look.
Consider what is knowable seven days before a charge. The card on file has an expiry month, and expiry is the most predictable event in the entire billing file. The account updater may already hold a replacement credential issued when the subscriber's bank reissued their card. The subscriber's last renewal may have failed once and healed, which marks the account as fragile. None of this requires prediction. It requires a list, reviewed on a cadence — rounds.
Pre-dunning is the name for working that list. Its moves are deliberately unglamorous. A courteous note before renewal to subscribers whose cards expire this month, carrying a secure update link and no alarm. A quiet check that updater coverage is actually flowing, not merely enabled. A flag on accounts whose details changed elsewhere in the stack. Each move is cheap, each is timed while the subscriber still feels like a customer rather than a debtor, and each converts a future failure — with its retries, its anxious emails, its churn risk — into a non-event.
None of these moves asks the subscriber for anything unusual, and that restraint is the point: the ask is small, early, and obviously in their interest.
The objection is usually that pre-renewal messages train subscribers to ignore billing mail. The evidence of the queue suggests the opposite: a short, specific, genuinely useful note — your card ending in this number expires before your next renewal — is the best-opened message most subscription businesses ever send, precisely because it arrives as service rather than collection.
A practical explainer of pre-dunning and the quiet week before a renewal sets out the full routine: which signals to pull, how far ahead to pull them, and how to keep the messages welcome rather than wearying.
The rounds themselves need a fixed shape or they dissolve into good intentions. A workable cadence pulls the signal list twice: once about a week out, when there is still time for a replacement card to arrive or an updater record to settle, and once two days out, as a final sweep for anything the first pass missed. The list itself stays short enough to read in one sitting — cards expiring before the renewal date, credentials replaced upstream since the last charge, accounts that failed once and healed, and payment methods flagged by the processor as at risk. Each entry gets one of three dispositions: contact now, watch silently, or clear. What rounds must never become is a second dunning sequence pointed earlier; the messages stay rare, specific, and visibly about the subscriber's convenience, because the entire advantage of acting before a failure is that trust has not yet been spent.
The deeper shift is accounting. Teams that run rounds start reporting a new number alongside recovery rate: failures prevented, estimated from the cards updated before their renewal date. It is a humbler metric than recovered revenue, because nobody can photograph a crisis that did not happen. But month over month it is the number that compounds — every prevented failure is a subscriber who never entered the queue, never read a dunning email, and never had a reason to reconsider the subscription at all. Recovery will always be necessary. The week before is where it gets smaller.
Published by Swipe Again — failed payment recovery at a flat $179/mo.
Top comments (0)