Should You Ever Agree to a Termination-for-Convenience Clause?

Procurement just sent back your redline with one line added: either party may terminate this agreement for convenience with 30 days' written notice. Your instinct is to fight it, because it turns a signed annual contract into a month-to-month bet against your own forecast. Don't fight it on principle. Run three questions first, because the right answer depends entirely on the deal in front of you, not on the clause itself.

Here's the test, the guardrails to propose instead of a flat refusal, and what actually happens to your revenue forecast once one of these clauses gets signed.

What you're actually giving up

A termination-for-convenience clause lets either side, though in practice it's almost always the customer, exit the contract without cause and without penalty, on notice. Roughly 85% of enterprise SaaS agreements now include one, and 60 days has become the most common notice period in negotiated deals, versus 30 days in standardized paper. That's not a fringe ask anymore. It's closer to a market default, which changes how you should think about resisting it.

What you lose isn't the contract value on paper, since you were never guaranteed to keep an unhappy customer for the full term anyway. What you lose is the ability to treat that ARR as committed when you're making hiring plans, board forecasts, or a fundraise deck. A logo that can leave with 60 days' notice is a logo you should be modeling as month-to-month revenue, whatever the contract says the term length is.

The three-question test

Run these in order. Each one narrows what you should actually be negotiating for.

1. Does this single account represent more than 15% of your ARR? If yes, a termination-for-convenience clause is a concentration risk, not a boilerplate term, and deserves real pushback or real pricing. If the account is under 5% of ARR, the clause barely moves your forecast risk and isn't worth burning negotiation capital on.
2. Do you have more than 12 months of runway without this account's revenue? If your runway assumes this contract renews and you have under a year of cash without it, treat the clause as a solvency question, not a legal one, and either get a longer notice period or a cancellation fee that buys you a real replacement-revenue runway.
3. Can you price the risk instead of refusing it? A minimum-term floor (no termination in the first 6 months), a wind-down fee equal to one to three months of fees, or a longer notice window all convert an open-ended risk into a bounded, plannable one. Most procurement teams will accept one of these three in exchange for keeping the clause on their side.

If the answer to all three points toward high risk, an over-concentrated account, thin runway, and no room to price around it, that's the deal worth walking from or restructuring entirely, not just redlining.

What to propose instead of a flat no

Refusing the clause outright is the weakest move at the table, since 85% market adoption means most enterprise legal teams will simply hold firm and you'll have spent your leverage on a term you were likely to lose anyway. Three fallback structures resolve it without a standoff:

• A minimum committed term (often 6 months) before the termination right activates, so at minimum the ramp-up cost of onboarding the account is recovered.
• A wind-down or transition-assistance fee, typically one to three months of fees, payable on early termination, framed as covering offboarding support rather than as a penalty.
• A longer notice window, 90 days instead of 30 or 60, which doesn't reduce the risk of losing the account but gives you enough runway to replace the revenue or adjust headcount before it hits.

Happy to include a termination-for-convenience right, standard in most enterprise agreements at this point. To keep both sides protected, we'd propose a 90-day notice period and a minimum initial term of six months before it applies. That gives your team flexibility if priorities shift, and gives us enough runway to plan around it responsibly.

That framing works because it doesn't contest the customer's right to the clause, which you'll likely lose that argument anyway, it just negotiates the shape of it.

How this actually changes your forecast

Once a meaningful share of your ARR sits under termination-for-convenience terms, stop reporting it as committed annual revenue internally. Split your forecast into two lines: contractually locked revenue (accounts with no convenience clause, or past their minimum term with no notice given) and at-risk renewal revenue (everything terminable on notice). Board decks and hiring plans should size against the locked line, not the blended total. It's a more conservative number, but it's the one that doesn't blow up your runway math if a single logo exits with 60 days' warning.

What to do this week

1. Pull your current enterprise contracts and flag which ones already carry a termination-for-convenience right, then check what percentage of ARR that represents.
2. Draft your three fallback positions now, minimum term, wind-down fee, notice window, so you're proposing them in the first draft instead of reacting to a redline under deadline pressure.
3. Split your revenue forecast into locked versus at-risk lines before your next board meeting, so the number you're planning against already reflects which accounts can leave on short notice.

Frequently asked questions

How common is a termination-for-convenience clause in enterprise SaaS deals?

Around 85% of enterprise SaaS agreements now include one, almost always as a right for the customer rather than the vendor. Treat it as a near-default term to plan for, not an unusual ask to fight on principle.

What's a reasonable notice period to counter with?

60 days is the common middle ground in negotiated enterprise deals; 90 days is a reasonable ask if the account represents a meaningful share of your revenue and you need runway to replace it.

Should you charge a fee for early termination?

Yes, when the account is large enough to matter. Frame it as a wind-down or transition-assistance fee, typically one to three months of fees, rather than a penalty, which procurement teams accept far more easily.

Does a termination-for-convenience clause mean the deal isn't worth closing?

No. Most enterprise deals now include one and still get modeled and closed successfully. The clause changes how you forecast the revenue, not whether the deal is worth signing.

It's the same underlying discipline behind negotiating auto-renewal terms: you don't win by refusing the clause the market has already standardized on. You win by naming your fallback position before the redline forces you into one.

If you want a second read on a specific clause before you sign it, that's a contract review question we help early-stage SaaS founders work through.