SaaS Contract Red Flags: What to Check Before You Sign

The clause that costs you money is rarely the price on page one. It's the auto-renewal window, the "pricing subject to change at renewal" line, and the seat ratchet buried in section fourteen — none of which show up until you're already locked in. A checklist for reading a SaaS contract like someone who plans to leave it someday.

Why the sticker price isn't the risk

Most SaaS buying decisions get made on a spreadsheet comparing per-seat price across two or three vendors. That comparison is real, but it's answering the wrong question. The terms that actually determine what a tool costs you over three years — how hard it is to leave, whether your price is protected, whether you can shrink your seat count when usage drops — live in the contract, not the pricing page. Our hidden-costs framework covers what a bad exit costs after the fact. This one is about catching the terms that create that bad exit before you've signed anything.

The clauses worth reading twice

Five terms show up across most SaaS contracts in some form. None of them are unusual or necessarily unfair on their own — but each one shifts risk toward the vendor in a way that's easy to miss when you're focused on the price line.

  • Auto-renewal with a long notice window. Many contracts renew automatically for a full new term unless you cancel a set number of days before the renewal date. Sixty and ninety-day windows are common; some enterprise agreements now specify 180 days. Miss the window and you're often locked in for the full next term, not a short grace period.
  • Renewal into a new multi-year term. The more punishing version of the above: some contracts don't auto-renew into a one-year extension, they auto-renew into a new term matching the original commitment. Miss the notice window on a three-year deal and the next term is three years too.
  • "Pricing subject to change at renewal." This language effectively voids whatever discount you negotiated at signing. Without a stated cap, a renewal-year price increase can land anywhere.
  • Seat ratchets. A clause that lets your seat count grow automatically as usage grows, but doesn't let it shrink back down at renewal — so a usage spike becomes a permanent cost floor even after the spike passes.
  • Vague data-export rights. "Export available on request" is not the same as a contractual right to a usable export format within a defined window after termination. The first is a courtesy; the second is enforceable.
Buyer-friendly ask Common default Increasingly common Some enterprise deals 30 days 60 days 90 days 180 days
The wider the notice window, the more of the calendar year you have to actively remember to act on someone else's clause.

Auto-renewal: the clause that turns a decision into a deadline

Auto-renewal isn't inherently predatory — vendors have a legitimate interest in not losing customers to inattention. The problem is asymmetry: a 90-day notice window with no reciprocal notice obligation on the vendor's side means the buyer carries all the risk of a missed date, and the vendor carries none. A more balanced version of the same clause requires the vendor to send a renewal reminder — by email, not certified mail, and confirmed in writing — at least 60 days out, with cancellation permitted electronically rather than requiring a signed letter.

Push for a 30-day notice window where you can get it. Where you can't, the fallback is procedural, not contractual: put every renewal date on a calendar with a reminder set well before the notice deadline, and review the clause again before that date rather than assuming it hasn't changed.

What actually gets negotiated out

None of these clauses are fixed. Procurement teams that review contracts — with outside counsel or an internal legal function — before signing report meaningfully lower total costs over the contract's life, largely by catching pricing-reset language and negotiating caps on renewal-year increases before they're locked in rather than discovering them at renewal. The leverage is highest at signing, when the vendor still wants the deal, and lowest at renewal, when switching has its own cost and the vendor knows it — see our renewal negotiation guide for how to claw some of that leverage back before the clock runs out.

12–18% Estimated cost avoided over a two-year period by mid-market buyers who review SaaS contracts with outside counsel before signing, per contract-review industry guides

A pre-signature checklist

  1. Find the renewal clause first, before comparing price. Note the notice window, whether it renews into the same term length, and whether the vendor owes you a reminder.
  2. Look for a price-increase cap. "Then-current rates" with no ceiling is a blank check; a stated cap — often 3–7% annually — is a negotiated one.
  3. Check whether seat counts can go down, not just up, at renewal.
  4. Get the export format in writing, not just the right to request one — and check whether it's usable in a competing tool without significant rework.
  5. Confirm termination-for-convenience terms, not just termination-for-cause. The difference determines whether you can leave a bad relationship or only a breached one.

Bottom line

A SaaS contract's price is the easiest number to compare and the least predictive of what you'll actually pay. The clauses that determine real cost — notice windows, renewal pricing, seat ratchets, export rights — are negotiable at signing and expensive to discover later. Read them in that order.

Already signed, and wondering what leaving would actually cost right now? Our calculator prices out a switch including the labor and overlap most estimates skip.
Open the switching cost calculator
Sources: Contract-review guidance synthesized from SaaS contracting and procurement guides published by Genie AI, Varisource, and POCsheet (2026); general figures on negotiation outcomes are as commonly cited in procurement industry guidance and are directional, not a controlled study.

This is a practical framework, not legal advice. Contract terms and applicable law vary by jurisdiction and vendor; have an actual SaaS contract reviewed by qualified counsel before signing.