How to Raise Non-Dilutive Debt When Your SaaS Is Usage-Based
Yes, a usage-based SaaS can raise venture debt or revenue-based financing, but lenders value a dollar of consumption revenue below a dollar of committed subscription ARR, and that gap is widening. Most loan covenants were written for a seat-based world. When your revenue meters by API call, token, or gigabyte, the "recurring" in recurring revenue gets fuzzy, and underwriters price that uncertainty straight into your advance rate. Founders who close clean deals prove their usage revenue is predictable before the lender has to ask.
This is no longer a niche problem. Seat-based pricing fell from 21% to 15% of SaaS companies in a single year while hybrid pricing jumped from 27% to 41%, according to Kyle Poyar's Growth Unhinged research. A majority of finance leaders now run hybrid or usage-based models. The capital stack has not caught up with the billing model, which leaves a real opening for founders who understand how lenders actually read metered revenue.
Why do lenders discount consumption revenue?
Lenders lend against predictability, not against a headline growth rate. A committed subscription contract gives an underwriter a contracted floor: even if the customer stops logging in, the invoice still goes out. Pure consumption revenue has no floor. If usage drops 30% next quarter, so does the cash the loan is repaid from, and the lender carries that risk.
There is a quieter problem too: verification. A covenant that references "ARR" assumes ARR is a clean, auditable number. With metered billing it often is not. Billing-platform research reported by Forbes found that 82% of finance teams still close the month on manual spreadsheets, and only 11.9% said their billing automation matched their current pricing model. If your own team reconciles usage to invoices by hand, an outside lender cannot trust the figure a covenant depends on. That reconciliation gap, not the pricing model itself, is what sinks most usage-based debt deals.
What actually counts in your borrowing base?
Your borrowing base is the slice of revenue a lender will advance against, and usage-based pricing splits that slice into tiers the lender treats very differently. Committed minimums behave like subscription ARR; raw pay-as-you-go revenue barely counts at all.
| Revenue type | How a lender counts it | Effect on borrowing base |
|---|---|---|
| Committed minimums and platform fees | Near full weight, like subscription ARR | Highest advance rate |
| Contracted usage with floors or commits | Partial weight, discounted for variability | Moderate advance |
| Pure pay-as-you-go consumption | Lightly weighted, often trailing-average only | Lowest advance, if any |
| Overage above the commitment | Usually excluded | None |
Revenue-based financing providers typically advance up to roughly 50% of qualifying ARR, per re:cap, but the word "qualifying" does the heavy lifting. The more of your revenue sits in committed minimums rather than raw metering, the larger the base and the cheaper the capital. Our breakdown of how much you can borrow against MRR walks through the advance-rate math.
A quick illustration shows why the mix matters. Take a company running $3M of annualized revenue, split $1.8M in committed minimums and $1.2M in pure consumption. A lender might advance 50% against the committed slice, roughly $900K. For the $1.2M consumption slice, the lender carves out unproven overage, leaving say $900K of reliable trailing usage, then applies a stricter 20% advance rate to that qualifying portion, yielding $180K. That gives a borrowing base near $1.08M. The same $3M treated as clean subscription ARR at 50% would have supported $1.5M. In this example the usage mix quietly removes about a quarter of the available debt, and the only lever that moves it back is converting more consumption into contracted minimums.
How do you set covenants for usage-based SaaS?
The goal is to give the lender a floor without pretending metered revenue is subscription revenue. Three structures do most of the work in 2026 deals:
- Trailing-average revenue tests. Instead of a point-in-time MRR covenant, the lender measures a trailing three- or six-month average, which smooths the natural spikes and dips of metered usage.
- Revenue-floor covenants. You commit to a minimum monthly revenue level; fall below it and the lender gains cure rights or a facility step-down rather than an instant default.
- Committed-minimum carve-outs. The covenant references only the contracted, floor-protected portion of revenue, leaving pure overage as upside the lender never underwrote.
Getting this language right matters more than shaving the headline rate. A rigid point-in-time covenant on volatile usage revenue is exactly how a healthy company trips a technical default. Our guide to venture debt covenants covers the specific clauses to negotiate before you sign.
What should you prepare before approaching a lender?
Expect to spend as much time explaining your billing infrastructure as your growth story. The document that decides most usage-based deals is a usage-to-invoice reconciliation that ties metered events to billed dollars across the trailing twelve months. If a lender can follow the line from raw events to cash collected, the discount on your consumption revenue shrinks fast.
Bring two more things to the table. Show cohort retention measured on consumption rather than logos, because a usage cohort that expands past 100% net revenue retention proves consumption compounds instead of leaking away. Then hand over a revenue bridge that separates committed minimums from variable overage, so the underwriter can size the base without guessing. The frequent mistake is arriving with a cash-basis income statement on a business that carries meaningful deferred and metered revenue; clean that up first, because retrading a term sheet after diligence exposes the gap costs far more than the prep. Strong net revenue retention on your usage cohorts is what turns a discounted base into a fundable one.
ARR-linked facility or venture debt: which fits usage revenue?
For volatile usage revenue, the structure matters as much as the lender. A traditional venture debt term loan repays on a fixed schedule no matter how a given month meters, which is fine when you hold runway and punishing when consumption dips. An ARR-linked or revenue-based facility lets you draw as qualifying revenue grows and ties repayment to performance, so the debt moves the way usage revenue actually moves. Providers such as Lighter Capital position these flexible lines specifically for SaaS revenue that does not sit still. The tradeoff is price: flexible capital carries a higher effective rate. Weigh the two in our comparison of revenue-based financing versus venture debt.
Whichever route you pick, sequence the decision around your runway. If you have twelve months or more of cash, a cheaper fixed term loan against your committed base can work, provided the covenants use trailing averages. If your revenue swings hard month to month, the performance-linked facility protects you from tripping a covenant in a slow quarter, and that protection is often worth the extra cost.
The EBITCAC lens: usage cohorts as a serviceable asset
Here is the reframe that changes the lender conversation. When you acquire a usage-based customer, the acquisition cost buys an asset that meters revenue for years, not a one-time sale. A cohort that expands past 100% net revenue retention throws off a growing, self-funding cash stream, which is precisely the kind of asset that services debt. Treating customer acquisition cost as a capital expenditure rather than a pure operating expense, the core premise of the EBITCAC framework, gives a lender a cleaner way to read your debt capacity even when the top-line ARR number is blurred by metering. The monthly revenue may be variable; the underlying asset base is not.
