Short answer. The venture debt covenants that matter most are the minimum-cash (liquidity) covenant, any performance-to-plan or minimum-ARR test, and the reporting obligations. The subjective defaults decide the rest: the Material Adverse Change clause, the funding MAC, and investor abandonment all let a lender freeze your next tranche, so read those three first.
Most founders read the rate first. The breach hides somewhere else. A Series B SaaS company draws the first half of a venture debt facility and counts on the second tranche to fund the next two quarters. Revenue softens for one bad month, and the lender, citing a clause buried in the loan agreement, declines to advance the rest. No payment was missed and nothing in the model broke, yet the company lost money it had already built its plan around. That is the most expensive venture debt mistake founders make, and it lives in the covenants, not the rate.
What is the one covenant mistake that actually sinks founders?
The named mistake is drawing venture debt in tranches while ignoring the funding MAC, a Material Adverse Change clause attached specifically to the lender's obligation to advance future capital. Kruze Consulting calls it the lender's "get out of jail free card," often hidden in the fine print, letting the lender withhold the next draw if it decides a material adverse change has occurred. The trigger language is broad enough to capture changes in your business or in the broader market. Those factors sit outside your control.
Founders fixate on the headline rate and the warrant coverage, and this clause gets a single read. If your model assumes tranche two arrives on schedule, you are betting the company on a lender's discretion. The defense is harder to negotiate than to state: remove the funding MAC, narrow it to objective triggers, or draw the full amount upfront. Treat every tranche you have not yet drawn as money you might not get.
Which financial covenants should a SaaS founder scrutinize first?
Venture debt carries far fewer financial covenants than a bank line. Lenders underwrite to the strength of your VC backers rather than to recurring revenue or hard assets, so many deals carry no maintenance financial covenants at all, or only one or two, according to RBCx. When one appears, it is almost always one of three.
- Minimum cash (minimum liquidity). The most common maintenance covenant in SaaS venture debt, sized as a multiple of net burn or of debt outstanding, often three to six months of net burn per RBCx. A company burning $250k a month at the top of that range would carry roughly a $1.5M cushion. Size your facility against that floor rather than borrowing the maximum on offer, because the same logic that sets your draw against recurring revenue sets the cash you must keep parked.
- Performance-to-plan. A growth covenant for pre-profit companies with high enterprise value. It requires you to hit a stated percentage of your forecasted fiscal-year plan, often 85% of the FY plan. Negotiate the plan you can clear, not the plan you hope for: an aggressive FY forecast submitted to win a bigger facility raises the bar you must beat every quarter, and the lender holds you to the number you signed.
- Minimum revenue / minimum ARR. A fixed MRR or ARR milestone tied to your plan by a target date, more common once a repeatable motion exists. Anchor the test to bookings or net-new ARR you have high confidence in, and ask for a step structure rather than a single cliff. A revenue-based facility flexes with revenue. A hard ARR covenant does not, so the milestone you accept needs real headroom.
Breaching any one of these is a technical default, and that gives the lender the right to accelerate, that is, to demand the full balance immediately. You want headroom you control.
How do you do the covenant headroom math?
Model your distance to the threshold every month, and set an internal "yellow flag" above the contractual line, a common rule of thumb being about 120% of the covenant threshold, the convention re:cap recommends. The point is to see the breach a full quarter out. Here is the math for a company burning $250k a month against a $1.5M minimum-cash floor.
| Month | Cash on hand | Net burn | Min-cash covenant | Yellow flag (internal) | Status |
|---|---|---|---|---|---|
| Month 0 | $2.30M | $0.25M | $1.50M | $1.85M | OK |
| Month 1 | $2.05M | $0.25M | $1.50M | $1.85M | OK |
| Month 2 | $1.80M | $0.25M | $1.50M | $1.85M | Yellow flag tripped |
| Month 3 | $1.55M | $0.25M | $1.50M | $1.85M | One month from breach |
The internal flag fires two months before the actual covenant does. That window is when you cut burn, pull forward a raise, or open the lender conversation while you still have leverage. This distance-to-threshold model is the one report worth re-running monthly.
How do affirmative and negative covenants differ, and which bind hardest?
Term sheets split covenants into affirmative and negative, a split Mercury's term-sheet breakdown sets out clearly. Affirmative covenants are obligations to act: deliver financials, keep insurance current, notify the lender of material changes. A standard reporting package runs to company-prepared monthly financials, audited annual statements, monthly compliance certificates, annual projections, and board materials. Watch the compliance certificate, because a late one is itself a default. Negative covenants are prohibitions, and they are the ones that quietly constrain strategy. The patterns to watch:
- Indebtedness caps. A restriction on additional debt, which can block a future facility or an equipment line.
- Negative pledge on IP. A covenant that, in Arc's words, prevents startups from pledging their intellectual property to another party while the loan is outstanding, which matters if you later want to raise against it.
- Change-of-control and asset-sale limits. Restrictions on ownership changes, asset sales, dividends, and M&A without lender consent.
The affirmative reporting load is administrative friction. The negative covenants shape what you are allowed to do for the life of the loan, so read them as if you will need every one of those actions, because eventually you might.
What can you actually negotiate, and why do lenders impose any of this?
Covenant calculations often run on custom lender-defined formulas, not GAAP, so do not assume a standard definition protects you. Negotiate the cushions in writing: a materiality threshold so a small shortfall is not an automatic breach, and cure periods of roughly 15 to 30 days so a one-month dip is fixable. The subjective defaults need the hardest push. A standard MAC, per Orrick, has three prongs: a material impairment of the lender's lien or the value of the collateral, a material adverse change in the borrower's business, operations, or financial condition, and a material impairment of the borrower's ability to repay when due. Whether any of those has occurred is largely in the eye of the lender, who rarely accelerates on a MAC alone but uses it as a hammer to force a workout. Orrick recommends preferring an investor abandonment clause over a MAC, because abandonment turns on facts within your investors' control. Typical language has the lender determine "in its good faith judgment that it is the clear intention of borrower's investors to not continue to fund borrower in the amounts and timeframe to the extent necessary to enable borrower to satisfy the obligations owed to the lender as they become due and payable." The test turns on the lender's good-faith judgment, not its sole discretion, which is why it is less subjective than a MAC. Push to narrow the MAC and accept that test instead.
Lenders impose covenants for one reason: they are underwriting your unit economics, not your assets. A facility priced against clean economics is easier to covenant against than one priced against blended burn. Treat CAC as a capital expenditure, the EBITCAC view, and the numbers a lender tests stop being a black box. Founders building a fully non-dilutive financing stack with the CVF fund get there by knowing what lenders check before they fund. Do that and the funding MAC stops being the clause that strands half your capital: you see your numbers the way the lender does and negotiate the trigger before you sign.
FAQ: venture debt covenants
Can a venture loan default even if I never miss a payment? Yes. A MAC clause can classify a loan as in default and trigger accelerated repayment even though you have made every payment on time. A default can occur independent of payment status.
What happens the moment a covenant is breached? A breach is a technical default. The lender can accelerate the full balance and freeze further funding. It can also seize pledged collateral. Lenders usually use the breach as leverage for a restructuring, but the leverage sits with them.
Is it normal for a venture debt deal to have no financial covenants? It can be. Many deals carry no maintenance financial covenants, or only one or two, because the loan is underwritten to your VC backers. A lighter covenant package shifts the cost elsewhere, usually into the warrant coverage.
How short a cure period is too short? Aim for 15 to 30 days. Anything shorter leaves no room to fix a reporting miss or a one-month cash dip. Pair the cure period with the monthly headroom check and most breaches never reach the lender's desk.
