Dunning Flow Design Template for Product Managers

A healthy SaaS dunning flow recovers 65-80% of failed payments. If you are below 50%, your retry timing or notification sequence likely has gaps. The biggest single improvement comes from enabling your payment provider's smart retry feature, which optimizes retry timing based on network-level data. After that, focus on reducing friction in the payment update experience.

No. Immediate suspension frustrates customers and increases voluntary churn on top of the involuntary churn you are trying to prevent. A 7-14 day grace period gives retries time to work and gives customers time to update their card. During the grace period, maintain full access with clear messaging about the payment issue. Use the [RICE framework](/frameworks/rice-framework) to prioritize which degradation steps to implement first.

3-5 attempts over 7 days is the industry standard. Beyond 5 attempts, the incremental recovery rate drops below 2%. Space retries 1-3 days apart. If your payment provider offers smart retries (Stripe, Recurly, Braintree), enable them. They use network-level signals to pick the optimal retry time, which outperforms fixed schedules by 20-30%.

The first 1-2 emails should come from your product or billing system (transactional, clear, action-oriented). The final email should come from a real person (founder, CSM, or head of customer success) with a personal tone. This escalation pattern signals increasing urgency without starting aggressive.

Annual failures are high-stakes: the charge is large, and a lost annual subscriber is 12 months of revenue gone. Offer a quarterly payment option as a recovery path. If the customer cannot pay annually, four quarterly payments recover more revenue than cancellation. Extend the grace period to 21 days for annual plans. CSM outreach is mandatory for annual accounts, regardless of revenue tier. ---