SaaS Debt Covenants Explained: What You're Actually Agreeing to When You Borrow Against ARR

What Are Covenants and Why Do ARR Lenders Require Them?

A covenant is a contractual promise made by a borrower to a lender. In ARR loan agreements, covenants are the lender's ongoing protection mechanism — they define the operational boundaries within which the borrower must operate for the life of the loan. Violating a covenant is a default event, even if you are current on all payments.

This is the fundamental misunderstanding that trips up McKinney founders who have only dealt with traditional bank loans or credit cards. With conventional credit, you default by missing a payment. With ARR loans, you can default while paying on time — if your ARR drops below the minimum threshold, your churn rate exceeds the cap, or you take an action prohibited by an operational covenant.

Covenants in ARR loans divide into two categories. First, financial covenants — quantitative limits on metrics like minimum ARR, minimum MRR, maximum churn rate, and minimum cash balance. These are tested on a regular schedule (monthly or quarterly) and produce a bright-line compliance determination. Second, operational covenants — behavioral restrictions on actions like taking on additional debt, making material acquisitions, or triggering a change of control. These are event-triggered rather than regularly tested.

The legal foundation for ARR loan covenants in Texas is UCC Article 9, which governs secured transactions. When an ARR lender takes a security interest in your recurring revenue stream, they file a UCC-1 financing statement that creates a public record of that security interest. A covenant breach that escalates to default gives the lender the right to enforce against that collateral under UCC Article 9 enforcement provisions. Understanding the full Intel Hub covenant framework — not just the headline terms — is essential before signing.

For the underlying underwriting context that produces these covenants, see our ARR loan underwriting criteria guide.

Financial Covenant 1 — Minimum ARR: The Most Commonly Breached Term

The minimum ARR covenant is present in virtually every ARR loan agreement. It requires the borrower to maintain ARR at or above a specified floor — typically set at 80–90% of ARR at loan closing. If your ARR at closing was $1,000,000, a 90% minimum ARR covenant sets the floor at $900,000. Fall below that floor and you are in breach.

Why is this covenant breached more often than founders expect? Three reasons:

1. Concentration risk crystallizes: A single large customer churns, and ARR drops by 15–25% in one event — exceeding the covenant buffer in a single month.
2. Seasonal renewal lumpiness: B2B SaaS with heavy Q4 renewals can see ARR dip materially in Q1 as the cycle restarts, breaching a point-in-time covenant even when the annual trajectory is healthy.
3. Covenant set at closing peak: Founders often close ARR loans after strong growth quarters. If closing ARR is at a seasonal high, the covenant floor is also at a seasonal high — creating artificial tightness.

The cure period process: when a minimum ARR breach is detected (typically through monthly reporting), the lender issues a breach notice. The borrower then has 15–30 days (the cure period, as negotiated) to restore ARR to the minimum level — by signing new contracts, renewing churned customers, or negotiating a covenant waiver. If the breach is not cured within the cure period, the lender can declare a technical default.

How to Negotiate More Headroom

Three tactics that consistently expand minimum ARR covenant headroom during term sheet negotiation:

• Anchor the floor to 75–80% of closing ARR, not 90%. This is the most direct negotiation — simply request a lower floor. Lenders set initial terms at 90% because most founders don't push back. A well-qualified borrower can routinely achieve a 75–80% floor with minimal friction.
• Negotiate trailing-average measurement. As noted above, trailing-3-month average ARR measurements eliminate the seasonal breach risk that point-in-time measurements create.
• Include a cure period of 30 days minimum. Standard fintech ARR lender agreements include 15-day cure periods. Request 30. This doubles your operational runway to respond to a breach without triggering default acceleration.

Financial Covenant 2 — Churn Rate Caps and Minimum MRR

Beyond the minimum ARR floor, many ARR loan agreements include a monthly churn rate cap — typically set at 3% maximum monthly churn, measured as a net new customer churn rate (not gross churn). The distinction matters: net churn measures ARR lost from departing customers minus ARR recovered from win-backs in the same period. Gross churn measures only the outflow.

The churn rate covenant typically tests net churn on a trailing-3-month basis to avoid penalizing an operator for a single month's outlier. If your trailing-3-month average monthly churn exceeds 3%, you are in breach regardless of whether your ARR covenant is technically satisfied — because elevated churn signals deteriorating collateral durability that the lender's model is not comfortable with.

How Expansion Revenue Interacts with Churn Covenants

This is a nuance that many founders miss: some ARR loan agreements define churn covenants in terms of net MRR change rather than gross logo churn. Under this structure, expansion revenue from existing customers directly offsets churn for covenant purposes. A month in which you lose $10,000 in churned MRR but gain $15,000 in expansion MRR has net positive MRR change — no covenant breach regardless of the logo churn figure.

The practical implication: operators with strong expansion revenue engines (high NRR) should negotiate churn covenants that incorporate expansion — net MRR change or net revenue retention metrics — rather than gross logo churn metrics. This structurally reduces the probability of a churn covenant breach while preserving the lender's economic protection.

For the mechanics of how churn affects your qualifying ARR base, see our churn-adjusted ARR guide.

Financial Covenant 3 — Minimum Cash and Liquidity Requirements

Most institutional ARR loan facilities (above $1M) include a minimum cash covenant — a floor on the cash balance in your primary operating account. The typical threshold is 3 months of debt service: principal repayment plus interest payments. For a $2M facility at 12% annually with 24-month amortization, monthly debt service is approximately $93,000. A 3-month minimum cash covenant requires maintaining at least $279,000 in liquid cash at all times.

Why do lenders require this? The minimum cash covenant ensures that the borrower has sufficient liquidity to meet debt obligations even if ARR temporarily contracts. It prevents the scenario where a company draws its entire facility, deploys all capital into growth, and then has no cash buffer when a major customer churns and ARR dips below the minimum ARR covenant simultaneously.

Modeling your required cash buffer before closing is a critical pre-signing step. The formula: Minimum Cash = Monthly Debt Service × Covenant Buffer Months (typically 3). This amount must be excluded from your operational deployment plan — it is not free cash flow to invest in growth.

Fintech ARR platforms (Pipe, Capchase) often do not include formal minimum cash covenants for facilities under $500K, relying instead on the ARR covenant as the primary credit protection mechanism. Institutional private credit funds almost universally include minimum cash covenants for facilities above $1M.

Operational Covenant — Equity Raise Restrictions: The Clause That Surprises Founders

The equity raise restriction is the operational covenant that most consistently catches McKinney founders off guard. It does not prohibit equity raises — in most cases — but it creates reporting obligations and sometimes more consequential restrictions around what happens to equity proceeds.

The typical structure across institutional ARR loan agreements:

• Notification requirement: Borrower must notify lender within 5–10 business days of closing any equity round exceeding a specified threshold (typically $500K). This is administrative, not restrictive.
• Change of control provision: If an equity transaction results in a change of control — a new majority shareholder or a merger — the lender may require immediate loan repayment or consent to the new ownership structure. This applies to acquisition scenarios, not standard venture rounds.
• Right of first refusal on refinancing: Some institutional lenders include an ROFR clause: if the borrower uses equity proceeds to retire the debt facility early, the lender has the right to match any competing refinancing term. This is effectively a prepayment restriction dressed as an ROFR.
• Additional debt restriction: Many ARR loan agreements include a covenant against taking on additional senior debt without lender consent. Equity raises are not restricted by this clause — but convertible notes (which are debt instruments) often are.

The "permitted equity issuances" definition in your loan agreement defines exactly which equity transactions are pre-approved and which require lender consent. Standard venture equity rounds (Series A, Series B, SAFE agreements) are typically pre-approved in well-drafted agreements. Unusual structures — participating preferred with liquidation preferences that subordinate the lender's position — may require individual consent.

Covenant Breach: What Actually Happens After You Trip a Covenant

Understanding the breach-to-default escalation path gives McKinney operators critical visibility into the real consequences of covenant violations — and the time they have to respond before consequences become severe.

The escalation sequence in most ARR loan agreements:

1. Covenant measurement event: Monthly or quarterly reporting date. The borrower submits compliance certificates (financial statements, ARR schedules) to the lender.
2. Breach detection: Lender's credit team reviews submissions and identifies a metric below the covenant threshold. The lender issues a formal breach notice in writing.
3. Cure period begins: The cure period clock starts from the breach notice date (not the measurement date). Standard cure periods: 15 days (fintech lenders), 30 days (institutional private credit). The borrower has this window to restore the metric to compliance or negotiate a waiver.
4. Waiver negotiation: If the breach cannot be cured operationally within the cure period, the borrower can request a covenant waiver. Lenders frequently grant first waivers to otherwise performing borrowers — the lender does not want to accelerate a loan being repaid on time. However, waivers often come with additional conditions (tighter future covenants, reporting frequency increases, or a waiver fee).
5. Technical default: If the cure period expires without cure or waiver, the lender can declare a technical default. At technical default, the lender can accelerate the loan — demanding immediate repayment of the outstanding principal balance.
6. UCC Article 9 enforcement: If acceleration occurs and the borrower cannot repay immediately, the lender enforces their UCC Article 9 security interest against the ARR collateral — which may include directing customers to pay the lender directly or assigning the ARR contracts to a successor operator.

The key practical point: proactive communication with your lender before a covenant breach is detected — not after — is the most effective way to prevent escalation. Lenders who are informed that a major customer is at risk and a metric may dip below threshold in the next 30 days are far more receptive to a pre-negotiated waiver than lenders who discover a breach in a compliance certificate. Access the Capital Access Protocol for guidance on lender relationship management best practices.

Under Texas Finance Code Chapter 306, lenders must follow specific notice and cure procedures before enforcing against secured collateral. Texas-based ARR lenders are subject to these state-level procedural requirements in addition to the contractual cure periods in their loan agreements.

Negotiating Covenant Headroom: Three Proven Tactics

Covenant negotiation is a legitimate and expected part of the ARR loan closing process. Lenders set initial covenant terms conservatively — they expect pushback from sophisticated borrowers. McKinney operators who treat covenant terms as fixed and non-negotiable leave material headroom on the table.

The three tactics with the highest return in covenant negotiations:

1. Change point-in-time measurement to trailing-3-month average. This single change eliminates the seasonal breach risk that accounts for a significant portion of technical defaults in SaaS ARR lending. It costs the lender nothing in credit risk and dramatically improves the borrower's operating flexibility.
2. Require lender consent before acceleration. Automatic acceleration upon technical default is the most dangerous clause in an ARR loan agreement. Requiring lender consent to accelerate — rather than automatic acceleration — preserves a negotiating window after default declaration. Most institutional private credit funds will accept this modification. Some fintech lenders will not.
3. Include a 15–20% ARR cushion below current levels in the covenant floor. If your ARR at closing is $1M and you negotiate a 78% minimum ARR floor, your covenant threshold is $780,000. A single large customer churning (say, $150K ARR) drops you to $850,000 — still above the floor. Without the cushion, the same event creates an immediate breach.

For additional context on how covenant terms interact with your facility size and advance rate, see our ARR loan sizing guide and ARR to cash flow liquidity framework.