Every SaaS company loses revenue to failed payments. Most treat it as a billing operations detail — something Stripe's default retry logic handles well enough. At the single-company level, that might be true: the dollar amounts feel small, the recovery rate feels adequate. At the portfolio level, the math changes entirely. A 10-company portfolio with average involuntary churn rates leaves $14K–$22K per month on the table — recoverable revenue that nobody is watching because each company treats it as someone else's rounding error.
$14K+
Monthly recoverable revenue (10-company portfolio)
9–12%
Annual MRR lost to involuntary churn
30–70%
Recovery rate with optimized dunning
The portfolio failed payment problem
Failed payments are the largest source of involuntary churn in SaaS. Across the industry, 9–12% of annual MRR is lost to payment failures that eventually cascade into subscription cancellation. For a single company at $500K MRR, that's $45K–$60K per year in preventable revenue loss. Meaningful, but manageable.
At the portfolio level, multiply that by company count. A 10-company portfolio with an aggregate $5M MRR loses $450K–$600K annually to involuntary churn. Even a modest improvement — recovering 40% of those failures instead of the default 15–25% — recaptures $90K–$150K per year. That's found money, not growth investment.
The portfolio problem isn't that individual companies don't know about failed payments. It's that nobody is watching the aggregate. The PE ops team sees quarterly revenue numbers. The company's billing team sees individual payment failures. The gap between them — the portfolio-level recovery opportunity — sits in nobody's dashboard.
Involuntary Churn Rate
Revenue lost to payment failures, expired cards, and billing errors — distinct from customer-initiated cancellations.
Why individual company dunning isn't enough
Most portfolio companies handle dunning one of three ways: they use Stripe's default retry schedule, they've configured basic dunning emails through their billing provider, or they don't do anything and let failed subscriptions lapse after the retry window closes. None of these approaches are optimized.
Stripe's default retry logic attempts 4 retries over approximately 3 weeks. The schedule is the same for a $29/mo subscription and a $5,000/mo enterprise contract. The dunning emails, if enabled, are generic. There's no escalation based on customer value, no pre-dunning for cards approaching expiration, and no cross-referencing of payment method health signals.
The result is a baseline recovery rate of 15–25%. Companies that invest in optimized dunning — smart retry timing, escalating email sequences, card update prompts, and pre-dunning — achieve 40–70% recovery rates. The gap between default and optimized is 15–45 percentage points of recoverable revenue.
| Recovery approach | Typical recovery rate | Setup effort | Maintenance |
|---|---|---|---|
| Stripe defaults only | 15–25% | None | None |
| Basic dunning emails | 25–35% | 2–4 hours | Quarterly review |
| Optimized retry + dunning | 40–55% | 1–2 days | Monthly tuning |
| Full recovery stack | 55–70% | 1–2 weeks | Ongoing optimization |
The portfolio amplifier is that most companies are stuck at the first or second level. In a typical 10-company portfolio, 2–3 companies have optimized their dunning stack. The remaining 7–8 are running Stripe defaults. The revenue gap between what they recover and what they could recover compounds across every company, every month.
Systematic recovery at portfolio scale
Portfolio-level payment recovery requires a structural approach, not per-company optimization projects. The portfolio operator needs three things: visibility into failed payment rates across every company, benchmarks to identify which companies are underperforming on recovery, and a standardized recovery framework that each company can implement.
Visibility comes from the billing data. Every failed payment in Stripe is an event with a timestamp, amount, failure reason (insufficient funds, card expired, processor declined), and subscription ID. Aggregating these events across companies produces the portfolio's involuntary churn profile: which companies are losing the most, which failure reasons dominate, and how the numbers trend over time.
The failure reason distribution matters because it determines the intervention. Expired cards are preventable with pre-dunning (notify the customer before the card expires). Insufficient funds respond to retry timing optimization (Tuesdays outperform Sundays by 15–20% on retry success rates). Processor declines sometimes resolve with payment method diversification. Each category has a different recovery playbook, and a portfolio operator who can see the distribution can prescribe the right one.
Benchmarking recovery rates across companies
Cross-company benchmarking is where portfolio-level recovery becomes actionable. When the portfolio operator can see that Company A recovers 62% of failed payments and Company B recovers 18%, the conversation is specific: what is Company A doing that Company B isn't? The answer is usually one of three things: a dedicated dunning email sequence, pre-expiration card update prompts, or a third-party recovery tool.
The benchmark also normalizes for company-specific factors. Enterprise SaaS companies with annual contracts and payment via invoice have structurally different failure profiles than SMB companies with monthly credit card billing. Comparing recovery rates within cohorts (similar ACV, similar billing model) produces more actionable insights than raw cross-portfolio comparison.
The economics of portfolio-level payment recovery
The financial case for portfolio-level recovery is straightforward. Take a 10-company portfolio with $5M aggregate MRR. Industry data shows 9–12% of MRR is at risk from involuntary churn annually. That's $450K–$600K per year. The portfolio's average recovery rate, assuming a mix of default and partially optimized dunning, is approximately 25%.
Moving the portfolio's average recovery rate from 25% to 50% — achievable with systematic optimization across all companies — recovers an additional $112K–$150K per year. Moving to 60% recovers $157K–$210K. These numbers flow directly to retained revenue with no customer acquisition cost, no sales cycle, and no incremental product development.
The unit economics are compelling. The revenue recovered is recurring — a customer whose payment is recovered stays on the subscription and continues generating MRR. The LTV of a recovered customer is the same as any retained customer, minus the brief interruption. At median SaaS LTV:CAC ratios, the lifetime value of the recovered revenue is 3–5x the annual dollar amount recovered.
For PE firms calculating portfolio value, the multiple impact is significant. An additional $150K in annual retained revenue at a 10x revenue multiple adds $1.5M in portfolio value. That's from an operational improvement that requires no new product development, no additional headcount, and no changes to go-to-market strategy.
Monthly Recurring Revenue
Predictable monthly revenue from active subscriptions, normalized from all billing intervals.
From company-by-company fixes to portfolio-level recovery monitoring
The shift from individual company dunning to portfolio-level recovery monitoring requires two capabilities: cross-company visibility into payment failure data, and standardized recovery rate benchmarks that make underperformance visible.
North Metric computes involuntary churn metrics daily from each company's Stripe data: failed payment rate, recovery rate, failure reason distribution, and the dollar value of unrecovered revenue. The portfolio view shows these metrics side by side across every company, making it immediately clear which companies are recovering well and which are leaving revenue on the table.
The monthly recovery opportunity — the gap between current recovery rates and achievable rates — is computed per company and aggregated at the portfolio level. When the portfolio operator can see that Company F's 18% recovery rate represents $4,200/mo in recoverable revenue, the conversation with that company's team has a specific dollar figure attached. That specificity converts an abstract "you should improve your dunning" into a concrete "here's $50K/year you're leaving on the table."