MishaBook a demo

Aug 14, 2026

Surface MRR Risk and Dunning Status Daily

Subscription health in the morning brief is a daily standup practice that flags active churn risk, failed payment volume, and at-risk cohorts before they compound into revenue leakage.

Why Subscription Health Belongs in Daily Standup

Most DTC operators review subscription health weekly or monthly. By then, a cohort of failed payments has already cascaded into involuntary churn. A single day of payment failures across 50 - 100 subscribers can represent $500 - $2,000 in MRR loss if not caught and dunned immediately.

The morning brief is the moment when operators decide resource allocation for the day. If churn risk is invisible, dunning campaigns don't get prioritized, support doesn't know which customers to reach out to, and product doesn't see the pattern in cancellations. Daily visibility forces daily action.

Subscription health metrics are leading indicators. They move before MRR does. A spike in failed payments predicts churn 3 - 7 days later. A rise in dunning attempts signals customer friction that may trigger cancellations. Catching these signals in the brief prevents the damage.

Core Metrics for the Daily Brief

Three metrics should appear in every morning subscription health review:

  • Failed payment volume (24h): Count of payment attempts that failed in the last 24 hours. Threshold: flag if >5% of daily transaction volume or >$500 MRR at risk.
  • Active dunning campaigns: Number of customers currently in retry logic (typically days 1, 3, 5, 7 post-failure). Threshold: flag if >2% of active subscriber base or >10% growth from prior day.
  • Churn rate (7d rolling): Percentage of subscribers who cancelled in the last 7 days. Threshold: flag if >3% or >20% above 90-day average.

The Daily Checklist

Conduct this review in the first 30 minutes of the operator day, before standup or planning meetings. Use a template to enforce consistency.

  • Pull failed payment count from payment processor (Stripe, Adyen, etc.) for the last 24 hours. Compare to 7-day average.
  • Check dunning queue size and identify which cohorts are in retry (new vs. returning, subscription tier, payment method type).
  • Calculate 7-day churn rate. Compare to 30-day and 90-day rolling rates. Flag if trending up.
  • Identify any single day or cohort spike (e.g., 'all Visa failures on Tuesday' or 'churn spiked in cohort acquired 6 months ago').
  • Assign one owner to each flagged metric: support for dunning outreach, product for churn investigation, finance for MRR forecast adjustment.
  • Document the brief in a shared log (Slack, Google Sheet, or ops tool) so the team sees the pattern over time.

Dunning Status Breakdown

Dunning campaigns are the primary lever for recovering failed payments. The morning brief should surface not just volume, but distribution across retry stages.

Organize dunning queue by retry attempt: Day 1 (first failure), Day 3 (second attempt), Day 5 (third attempt), Day 7 (final attempt before involuntary churn). Each stage has a different recovery rate.

Day 1 recovery rate is typically 40 - 60%. Day 7 recovery rate is 10 - 20%. If Day 1 queue is large, the issue is recent and recoverable. If Day 7 queue is large, customers are already disengaged.

Also segment by payment method. Card failures have higher recovery rates than ACH or bank transfer failures. Flagging method-specific issues allows targeted fixes (e.g., 'Amex is declining 8% of transactions - check processor settings').

MRR Risk Calculation

Convert failed payments and dunning queue into MRR impact so the operator understands the revenue stake.

Formula: (Failed payments in last 24h + Active dunning queue) × Average subscription value = MRR at risk.

Example: 30 failed payments + 80 customers in dunning queue = 110 at-risk subscriptions. If average subscription value is $25/month, MRR at risk = $2,750.

Set a threshold for escalation. If MRR at risk exceeds 2% of total MRR, escalate to leadership. If it exceeds 5%, treat as a crisis and mobilize support and product immediately.

Track this number daily so the team sees whether dunning efforts are working (queue shrinking) or failing (queue growing).

Linking Churn to Dunning Failures

Not all churn is payment failure. But a significant portion is. The morning brief should track the overlap.

Segment churn into two buckets: voluntary (customer-initiated cancellation) and involuntary (failed payment + no recovery). Involuntary churn is preventable; voluntary churn is not.

If involuntary churn is >30% of total churn, the dunning process is failing. Investigate: Are emails being delivered? Are retry attempts happening at the right intervals? Is the payment method being updated by the customer?

If involuntary churn is <10%, dunning is working well. Shift focus to voluntary churn root causes (product, pricing, support).

Escalation Rules and Thresholds

Define clear escalation rules so the morning brief drives action, not just awareness.

  • Yellow flag: Failed payments >10% of daily volume OR dunning queue >3% of subscriber base. Action: support reviews dunning emails and retry logic.
  • Red flag: MRR at risk >2% of total MRR OR churn rate >5% (7-day rolling). Action: escalate to leadership and product.
  • Critical: MRR at risk >5% of total MRR OR involuntary churn >40% of total churn. Action: emergency response - pause other work, mobilize all teams.
  • Document every escalation and the action taken. Review weekly to see if early flags prevented larger problems.

Questions

FAQ

How often should we pull subscription health data?

Daily, in the morning before standup. Most payment processors update failed payment counts in real-time or within 1 - 2 hours. Dunning queue and churn can be pulled from your subscription platform (Subbly, Cratejoy, custom Shopify app) on the same cadence. If data is delayed, pull it the night before and review in the morning.

What if we don't have a dunning system yet?

Build one. Manual dunning (email sequences triggered by payment failure) is the minimum. Most payment processors (Stripe, Adyen) offer built-in retry logic. Enable it immediately. Set retry attempts to 3 - 4 over 7 days with increasing intervals (1 day, 3 days, 5 days, 7 days). Track the queue manually in a spreadsheet until you can automate it.

Should we include dunning metrics in the weekly business review?

Yes, but differently. The morning brief is tactical (today's failures, today's queue). The weekly review is analytical (trends, cohort performance, recovery rates by payment method, ROI of dunning campaigns). The daily brief drives action; the weekly review drives strategy.

How do we know if our dunning process is healthy?

Benchmark: Day 1 recovery rate should be 40 - 60%, Day 3 should be 20 - 40%, Day 7 should be 10 - 20%. If your rates are lower, improve email copy, timing, or retry logic. If involuntary churn is <15% of total churn, dunning is working. If it's >30%, dunning is failing and needs investigation.

Want this on your account?

Thirty minutes. Bring the number that keeps you up.

More from the blog