TTM ARR Covenants: When Churn Triggers a Technical Default

The covenant defines ARR as your annualized recurring revenue run rate as of the testing date, typically excluding one-time fees, services revenue, and other non-recurring items, and it's tested monthly or quarterly against a minimum threshold that may step up over time as the loan matures. The definition of what counts as recurring revenue, and how multi-year prepaid contracts get annualized, is negotiated at closing and matters enormously later, so read it as carefully as the threshold number itself.

A single large customer's non-renewal, timed right before a testing date, can drop trailing ARR below a threshold even if new bookings that quarter were strong and the underlying business is healthy. This is exactly why lenders call it a technical default: it's a breach of the covenant's letter, triggered by measurement mechanics and timing, not necessarily a sign the company itself is failing.

That distinction matters in the conversation that follows a miss. A lender who sees strong new bookings alongside the churned account is in a very different negotiating position than one looking at broad-based, ongoing losses across the customer base, and it's worth making that contrast explicit rather than assuming the number speaks for itself.

Many venture debt agreements include an equity cure right, letting an investor inject additional capital that gets added to the ARR calculation, or used to pay down debt, to retroactively fix a covenant breach within a set window after the testing date. This is a term worth negotiating hard for at closing, before you need it, since a lender has far more room to refuse or limit it once you're already asking to use it during an actual breach.

If your investors are willing to backstop a miss this way, get the mechanics, including how many times you can use it over the loan's life, written into the credit agreement from day one.

Build a rolling forecast of your trailing twelve month ARR that updates as contracts renew, churn, or get signed, rather than only calculating the actual number at each testing date. A forecast that flags a likely miss two or three months out gives you time to have a conversation with the lender, explore an equity cure, or push for new bookings before the covenant is actually breached, instead of discovering the problem the same week the compliance certificate is due.

Call the lender before the testing date, not after. Come with the same kind of forecast and honest explanation that any covenant conversation needs, showing what drove the miss and what the trend looks like from here. Lenders who hear about a likely breach in advance, with a real plan attached, are far more willing to work through an amendment, a waiver, or an equity cure than lenders who learn about it only when the compliance certificate lands in their inbox already showing a breach.

Bring your investors into the conversation at the same time you tell the lender, not after, especially if an equity cure is even a possibility. A cure that has to be arranged and funded within a short window after the testing date isn't something you want to be negotiating with your own board for the first time while the clock is already running.

When a miss looks likely, work through these steps:

1. Update your rolling trailing twelve month ARR forecast to show how far below the threshold you expect to land and which contracts drive the gap.
2. Call the lender before the testing date, not after, bringing the forecast and an honest explanation of what caused the miss.
3. Show the lender what the trend looks like from here, including new bookings and renewals that offset the lost revenue.
4. Tell your investors early if an equity cure right exists, so they have time to decide whether to use it.
5. Check the credit agreement for the cure window and for any cap on how many times a cure can be used.