Venture debt covenants: the warning signs before a breach

Venture debt covenant breaches rarely start with a missed payment. They start three weeks earlier, in a cash balance that dipped below the floor for a few days, or a growth number that came in soft two months running. By the time your lender's monitoring flags it, you have already lost the ability to get ahead of the conversation.

If you took on venture debt for the runway without giving up equity, the interest rate was never the real risk. The covenants are. Most seed and Series A SaaS loans carry two to four financial covenants, and almost nobody outside the CFO's spreadsheet is tracking them month to month. Here is what to watch, and what to do the moment a number moves the wrong way.

What a venture debt covenant actually is

A covenant is a number in your loan agreement that your business has to stay on the right side of for as long as the debt is outstanding. Break it, and the lender does not need to prove anything else went wrong. The breach itself is the default trigger, even if revenue is fine and the team is shipping on schedule.

Most SaaS venture debt agreements, sized at 20 to 35 percent of your last equity round, carry a small, repeating set of covenant types:

• Minimum liquidity: a cash balance floor, often a flat dollar amount (commonly $500K to $2M) or a multiple of monthly net burn, that has to hold at all times, not just on the day you report it.
• Revenue or MRR growth: a required growth rate, sometimes stepping up each quarter as the loan matures.
• EBITDA or burn cap: a ceiling on how much you can lose in a given period, independent of what you raised the capital to fund.
• Reporting: monthly financials and a KPI package (ARR, MRR, churn or NRR, cash) delivered within a set number of days after month close. Missing that deadline is, on many term sheets, a breach on its own. Warrants are a separate cost stacked on top of all this, and worth negotiating down before you sign, not after.

The reporting covenant is usually the first one founders trip, and not because the business is struggling. The person who negotiated the loan gets busy, the KPI pack slips a week, and nobody realizes the slip itself is the violation.

The four numbers that catch a breach before your lender does

You do not need loan-covenant software or a full-time controller to see a breach coming. Four numbers, checked monthly against your actual term sheet, catch almost every covenant problem before your lender's own monitoring does.

1. Days of buffer above your liquidity floor, not your total balance. A $1.4M balance against a $1M covenant sounds safe until you map the actual low point across the month, after payroll and vendor payments clear. What matters is the lowest the balance touches, not the number on the first of the month.
2. Trailing three-month growth against the covenant rate, not against last year. Loan agreements typically test recent performance on a rolling basis, so one soft month can pull the average below the required line even if your year-over-year number still looks strong.
3. Days between month close and report delivery, tracked like a hard deadline on a calendar, not a task on a list. A term sheet requiring financials within 20 days of month end starts that clock automatically. Miss it by even a few days with no communication and you are technically in breach before anyone has looked at a revenue number.
4. A 10 to 15 point growth deceleration scenario, run against every covenant, not just the liquidity one. If dropping your current growth rate by 10 to 15 points alone would breach a covenant, you are already exposed. You just have not had the unlucky month yet.

What to do the moment a number moves

Call your lender before they call you. A first, disclosed, temporary miss that you raise proactively is almost always resolved with a waiver. The same miss discovered through the lender's own monitoring reads as concealment, and covenants restrict your options at exactly the wrong time, right when you have the least leverage to negotiate.

1. Notify the lender as soon as you see the number trending wrong, not after the covenant is already breached. Lenders regularly grant waivers for a disclosed, temporary shortfall. They are far less flexible once they find it themselves.
2. Get the waiver in writing, with the specific period and terms it covers, not a verbal 'we're fine with this.'
3. Bring a plan, not just a warning. A specific fix, with a number and a date attached, turns a difficult call into a five-minute one.
4. If the miss is going to repeat, ask to reset the covenant level itself instead of requesting a new waiver every month. One renegotiated threshold, done with a documented reason, usually costs less goodwill than three consecutive waiver requests.

A worked example

Say you raised a $10M Series A and took $3M in venture debt at 11 percent, with a covenant requiring a minimum cash balance of $1M and quarterly MRR growth of at least 8 percent. Six months in, a large customer churns and a hire slips a quarter. Trailing MRR growth drops to 5 percent for one quarter while cash dips to $850K on payroll week. Both covenants are breached, on paper, for a matter of days.

A founder who called the lender two weeks earlier, when the growth trend first showed at 6 percent and the cash model first projected the dip, has a very different conversation than a founder whose lender finds both numbers in the monthly report after the fact. The first conversation is a waiver request with a recovery plan attached. The second is a default notice with a cure-period clock already running.

The 30-day move

Pull your actual term sheet this week, not the summary you remember from signing it. List every financial covenant with its exact number, the measurement period (point-in-time or rolling average), and the reporting deadline. Put the deadline on a calendar with an owner's name attached, not a floating task. That one document, checked monthly, is most of what a covenant-compliance tool would do for you anyway.

Frequently asked questions

What happens if you breach a venture debt covenant?

Most agreements give a cure period of 7 to 30 days to fix the issue. If you fix it, or the lender agrees the miss was temporary and immaterial, they typically issue a waiver. If not, they can declare default, which can trigger higher rates, accelerated repayment, or a demand for more collateral.

Can you renegotiate covenants after signing?

Yes, especially with a track record of on-time reporting and transparent communication. Founders can ask for materiality thresholds, longer grace periods, or covenants measured as a rolling average instead of a hard monthly minimum.

How much cash cushion should you keep above the covenant minimum?

Model your actual lowest cash point in the month, not your month-start balance, and keep enough buffer that a single delayed customer payment or vendor timing shift does not put you under the floor.

Do all venture debt loans have financial covenants?

No. Some lenders offer covenant-lite structures that reduce or remove hard financial tests in favor of broader reporting and operating conditions, though these are less common and can carry a higher rate or more warrant coverage in exchange.

What's the difference between a technical default and a full default?

A technical or covenant default happens when you miss a specific term, like a cash minimum or a report deadline, even if payments are current. A payment default means you missed an actual principal or interest payment. Lenders treat these very differently: most technical defaults resolve with a waiver, while payment defaults move much faster toward acceleration.

Venture debt buys runway without dilution, but only if you treat the covenants as seriously as the number you borrowed. If the covenant math never works no matter how you negotiate it, comparing it against revenue-based financing is worth doing before you sign anything, the same way one seed-stage founder did to avoid a down round. The founders who avoid a breach are not the ones with better luck. They are the ones who saw the number moving before their lender's monitoring did.