How to Size Debt in a SaaS LBO: ARR-Based Lending Explained

Run a standard leveraged buyout debt sizing exercise on a growth-stage SaaS company and something breaks almost immediately: the EBITDA is thin, sometimes close to break-even, but the business is clearly valuable, growing fast, and highly cash-generative on a unit-economics basis once it matures. A textbook 5.0-5.5x EBITDA leverage multiple produces a debt number that's almost irrelevant to how the deal actually gets financed. This article walks through how sponsors and lenders actually size debt for a SaaS leveraged buyout, why ARR-based lending exists, and how to structure an interview answer that shows you understand the difference.

Why a Standard EBITDA Leverage Test Breaks Down for SaaS

A conventional leveraged buyout debt capacity test starts with a leverage multiple applied to EBITDA — the mechanics are the same ones covered in a standard debt capacity walkthrough: take the lender's maximum total leverage guideline (say, 5.5x), multiply it by trailing EBITDA, and that's roughly the debt ceiling. For a mature, EBITDA-generative business, this works reasonably well.

Why Growth-Mode SaaS Defeats the Test

It works poorly for SaaS companies still in growth mode, for one structural reason: SaaS businesses that are prioritizing growth deliberately keep EBITDA margins thin by reinvesting heavily in sales, marketing, and R&D. A company with $50.0m of annual recurring revenue (ARR) and a 15.0% (0.15) EBITDA margin only has $7.5m of EBITDA to lever against. At a 5.5x guideline, that's a debt ceiling of about $41.3m — against a purchase price that, if priced on a typical SaaS revenue multiple of 6.0x ARR, would be $300.0m. Debt would fund barely 14% of the deal, which is a very different capital structure from the 50-70% leverage typical of an industrial buyout.

What Is ARR-Based (Recurring Revenue) Lending?

To solve this mismatch, a category of lenders has emerged that underwrites debt directly against annual recurring revenue rather than EBITDA. These recurring-revenue credit facilities are built on the insight that a SaaS company's ARR — particularly ARR backed by strong net revenue retention and low gross churn — is a highly predictable, contractually recurring cash flow stream, even when it hasn't yet converted into GAAP profitability.

What the ARR Lender Underwrites Instead

Rather than asking "how many times EBITDA can we lend," an ARR-based lender asks "what advance rate against ARR reflects the durability of this revenue base." Advance rates typically run in the 30-45% (0.30-0.45) range of ARR for high-quality recurring revenue businesses, though the exact rate depends heavily on gross margin, churn, and customer concentration. Covenants are usually structured around retention and churn thresholds — a minimum net revenue retention level, a maximum gross churn rate — rather than the leverage ratios that dominate traditional credit agreements.

The Three Debt Capacity Tests That Actually Matter

In practice, a SaaS buyout debt package gets stress-tested against three separate constraints, and the smallest one usually wins — the same "binding constraint" logic that shows up in any multi-covenant debt capacity analysis:

• EBITDA-based leverage test: Maximum Total Leverage × EBITDA. This tends to produce the lowest ceiling for growth-stage SaaS, precisely because EBITDA is thin.
• Interest coverage test: (EBITDA / Minimum Interest Coverage Ratio) / Cost of Debt. This caps debt at the level where interest expense alone doesn't consume too large a share of EBITDA — and it frequently binds even tighter than the headline leverage guideline.
• ARR-based facility: Advance Rate × ARR. This can produce a materially higher ceiling than the EBITDA-based tests, because it's underwriting the revenue base directly rather than current profitability.

The effective debt capacity for the deal is generally the binding (lowest) result across whichever tests the lender group actually applies — sponsors don't get to simply pick the most favorable number.

Worked Example: Sizing Debt for a $50.0m ARR SaaS Target

Consider a target with $50.0m of ARR, $7.5m of EBITDA (a 15.0% (0.15) margin), a lender leverage guideline of 5.5x EBITDA, a minimum interest coverage ratio of 3.0x, and a 7.0% (0.07) cost of debt.

Which Test Binds, and Why

Here, the interest coverage test binds at $35.7m — below the $41.3m implied by the leverage guideline. This is a common pattern in thinner-margin SaaS deals, and it's exactly the kind of calculation walked through step by step in the case on sizing a SaaS LBO around ARR and NRR, which extends this exact example through to the sponsor's equity check and the return under two different retention scenarios.

Notice what didn't appear in this particular worked example: an ARR-based facility. In practice, a sponsor sizing this deal would also solicit terms from a recurring-revenue lender and compare that offer against the traditional EBITDA-based tests — but the EBITDA and coverage tests remain essential because they represent what a conventional senior lender will actually underwrite, and many capital structures blend a smaller traditional tranche with a recurring-revenue tranche rather than relying on ARR-based debt alone.

Why the Exit Multiple Matters More Than the Debt Structure in a SaaS LBO

Once the debt capacity and the resulting sources and uses of the deal are set, the more important question for a SaaS buyout's return is what happens to the exit multiple — not the leverage. Because the entry price is set on a revenue multiple (6.0x ARR, in this example, against $7.5m of EBITDA — implying a roughly 40x EBITDA multiple), the sponsor's return is dominated by whether ARR keeps growing and whether the market is still willing to pay a similar multiple for that ARR at exit.

How This Differs From an Industrials Buyout

This is a meaningful departure from a traditional industrial leveraged buyout, where debt paydown and margin expansion typically do a large share of the work in driving multiple of money and IRR. In a revenue-multiple-driven SaaS deal, a sponsor can hold debt completely flat over the entire hold period and still generate a strong return purely from ARR compounding — or lose money entirely if growth stalls and the exit multiple compresses, even with the debt structure untouched.

How Net Revenue Retention Feeds Into Both the Debt and the Exit Multiple

Net revenue retention (NRR) is the single input that connects the debt sizing conversation to the exit multiple conversation. On the debt side, strong NRR and low churn are exactly what makes a lender comfortable extending an ARR-based facility at a higher advance rate — the more predictable the revenue, the more a lender is willing to lend against it. On the exit side, NRR anchors how much ARR growth the sponsor can reasonably underwrite, and by extension what exit multiple the business can command.

Sensitivity of the Base Case to NRR

A base case built on 115% (1.15) NRR compounding ARR at 15% (0.15) a year for five years produces a very different outcome from a downside case where NRR erodes to 100% (1.00) and ARR growth stalls entirely. Modeling both scenarios — and showing how the exit multiple should reasonably compress alongside a retention slip, rather than holding it artificially constant — is exactly the kind of sensitivity analysis that separates a strong candidate's answer from a mechanical one that only plugs numbers into a single formula.

How Advance Rates and Covenants Vary With SaaS Quality

Not every SaaS company gets the same terms from a recurring-revenue lender, and understanding what moves the advance rate is worth knowing even beyond the headline 30-45% (0.30-0.45) range. Lenders typically look at four things when setting the advance rate and the covenant package: net revenue retention, gross churn, gross margin, and customer concentration. A business with 120%+ (1.20+) NRR, sub-5% (0.05) gross churn, 80%+ (0.80+) gross margin, and no single customer above 5% (0.05) of ARR sits at the favorable end of that range and can typically negotiate lighter covenants. A business with weaker retention, higher churn, or concentrated revenue in a handful of large accounts will see a lower advance rate, tighter covenants tied to minimum NRR and maximum churn thresholds, and often a higher spread on the facility to compensate the lender for the added risk.

Why Cohort Data Drives the Advance Rate

This is also why cohort-level data matters so much in the underwriting process, not just the blended company-wide NRR figure. A lender examining a target with 110% (1.10) blended NRR wants to know whether that number is stable across cohorts or whether it's propped up by one unusually strong customer segment while newer cohorts are trending down — the latter pattern would justify tighter terms even though the headline number looks fine.

Blended Capital Structures: Combining Senior Debt With a Recurring-Revenue Tranche

In practice, many SaaS buyouts don't rely on a single financing source. Sponsors frequently combine a smaller traditional senior term loan — sized off the EBITDA and interest coverage tests described above — with a separate recurring-revenue tranche or an ARR-based revolver that provides additional liquidity for working capital and growth investment. This blended approach lets the sponsor access the lower cost of capital available on the traditional tranche while still tapping the larger capacity that an ARR-based lender might offer, without having a single lender group underwrite the entire capital structure against one methodology.

The Cost of a Blended Structure

The tradeoff is complexity: blended structures typically involve more intercreditor negotiation, since the traditional senior lender and the recurring-revenue lender need to agree on relative priority, covenant thresholds, and what happens if NRR or churn breaches an agreed level. For interview purposes, it's enough to recognize that this blending exists and to be able to explain why a sponsor might prefer it over relying on a single facility type — you're unlikely to be asked to structure the intercreditor agreement itself.

How Comparable Company Analysis Sets the Entry and Exit Multiple Assumptions

Neither the entry EV/ARR multiple nor the assumed exit multiple is arbitrary — both come from a comparable company analysis built around a peer set of similarly-positioned SaaS businesses, adjusted for growth rate, NRR, gross margin, and scale. This is worth stating explicitly in an interview answer, because it shows you understand that the 6.0x-type multiple used in a worked example isn't a number pulled from thin air — it's meant to represent where the market is currently pricing companies with a comparable growth and retention profile.

This also explains why the exit multiple assumption should move with the NRR assumption rather than staying fixed: if NRR erodes over the hold period, the company no longer resembles the same peer set it was benchmarked against at entry, and a comparable company analysis run at exit would likely point to a lower multiple, all else equal. Treating the exit multiple as static regardless of how the retention profile evolves is effectively assuming the company stays in the same peer group no matter what happens to its underlying metrics — an assumption most interviewers will push back on if you don't address it yourself.

How to Structure Your Answer in an Interview

When asked to walk through a SaaS LBO, or specifically to size debt and set exit assumptions for a recurring-revenue target, a strong answer typically follows this sequence:

• Flag upfront that a pure EBITDA leverage test will likely understate debt capacity for a thin-margin, high-growth SaaS target.
• Run the EBITDA leverage test and the interest coverage test, and identify which one binds.
• Mention that an ARR-based recurring-revenue facility is a realistic financing alternative, and explain the underwriting logic (NRR, gross churn, advance rate against ARR) even if you don't have exact terms to model.
• Note that the entry valuation is likely set on a revenue multiple, not an EBITDA multiple, and that this shifts the return drivers away from leverage and toward growth and exit multiple assumptions.
• Tie NRR explicitly to both the debt capacity story and the exit multiple assumption, rather than treating it as a single unexplained input.

This kind of structured, sequenced answer demonstrates the same disciplined approach used in a paper LBO, where being explicit about what you're approximating and why matters just as much as getting the arithmetic right.

Common Mistakes to Avoid

• Applying a generic 5.0-6.0x EBITDA leverage assumption to a SaaS target without acknowledging that EBITDA margins are often deliberately thin at this stage.
• Forgetting to check the interest coverage covenant, and assuming the headline leverage multiple is automatically achievable — as shown above, coverage frequently binds tighter.
• Treating the exit multiple as fixed regardless of how the retention profile evolves over the hold period.
• Focusing the entire answer on the capital structure while ignoring that growth and multiple assumptions are the dominant driver of returns in a revenue-multiple-priced deal.
• Not distinguishing between what a traditional senior lender will underwrite versus what a specialized ARR-based lender might offer — real capital structures often blend both.

Conclusion

Sizing debt for a SaaS leveraged buyout isn't a matter of swapping one leverage multiple for another — it requires running multiple debt capacity tests, understanding why a recurring-revenue credit facility exists in the first place, and recognizing that the debt structure is often a secondary driver of returns compared to ARR growth and the exit multiple. For a full worked example that carries this logic through to a multiple of money calculation under two different retention scenarios, see the case on SaaS and recurring revenue LBOs. Jetzt üben.