The renewal trap: 5 contract clauses you should refuse to sign

You don''t read your software contracts. Almost nobody does. Your legal team reviews them on the way in, finance reviews them on the way out, and the people who use the tool every day never see them. The result is a stack of contracts you signed years ago, on terms nobody now remembers, that quietly cost more every year. Here are five clauses that show up in most of them, and what to do about each.

Clause 1: auto-renewal with short notice

The most common is some variant of: this agreement renews automatically for additional one-year terms unless either party provides written notice of non-renewal at least 60 days before the end of the current term. The number after "at least" varies (30, 60, 90, sometimes 120). The mechanism is the same. Miss the window, and the renewal fires. The vendor doesn''t have to remind you.

What to do. Before signing, push for either a longer notice window for the buyer (30 days, ideally), or a clean opt-in renewal (vendor must email you 90 days before end of term, you must affirmatively renew). If you can''t move the vendor, log the renewal date in a calendar that fires at notice-minus-30 days. Cubbie does this automatically off the registry.

Clause 2: price escalator without cap

Some contracts include language like: subscription fees may be increased by up to the change in CPI plus 5 percent at each renewal. CPI plus 5 sounds modest. Compounded over five years it''s a 35 percent real cost increase. Other versions skip the CPI floor and just say "annual price increase of 7 percent" or "list price at time of renewal," which is even worse because list price typically rises faster than the price you negotiated initially.

What to do. Push for either a flat cap (3 to 5 percent annual increase, no CPI tie) or a multi-year price lock (3-year flat). Vendors will often agree to one or the other if you ask. If neither moves, get the cap in writing. "List price at time of renewal" is a trap.

Clause 3: limited data export

Look for language about what happens to your data on termination. The good version is something like: customer may export all data in a structured, machine-readable format at any time during the term and for 90 days after termination. The bad version is: vendor will provide reasonable assistance with data export upon request. "Reasonable assistance" usually means CSV exports of the surface schema, no associations, no historical events, no API access, charged hourly. Once you''re a former customer, "reasonable assistance" becomes whatever the vendor wants it to mean.

What to do. Push for explicit, structured export (JSON or CSV with documented schema, full history, all records, including soft-deleted), available via API for the term and for 90 days after, no charge. If the vendor refuses, the export language tells you something about how the rest of the relationship will go.

Clause 4: unilateral terms changes

The phrase to watch for is something like: vendor may modify these terms at any time by posting an updated version on its website, with continued use constituting acceptance. This converts your fixed contract into a variable one. The vendor can change pricing, SLAs, data handling, IP terms, anything, and your only recourse is to stop using the product.

What to do. Either remove this clause, or carve out the parts that matter to you (pricing and material terms locked for the term, only operational details modifiable). For high-value contracts, the carve-out is non-negotiable from your side. For low-value contracts, fine to leave it in but log the inbound link the vendor uses for terms updates and check it quarterly.

Clause 5: limitation of liability with carve-outs that don''t carve

The standard structure is a cap on liability (often 12 months of fees), with carve-outs for indemnification, confidentiality breach, willful misconduct, and gross negligence. Read the carve-outs carefully. Some vendors structure them so the carve-outs apply only to one party (the buyer). Others tie them to specific notice procedures that are easy to fail. Others have caps inside the carve-outs (so confidentiality breach has a cap of 24 months of fees, not unlimited).

What to do. Confirm the carve-outs apply to both parties symmetrically. Confirm the carve-outs don''t have their own caps. Confirm the notice procedure for triggering a carve-out is realistic. If you''re a buyer signing for high-sensitivity data, this clause matters more than the headline liability cap.

The pattern

Each of these clauses survives because nobody reads them at the moment they matter. Vendors aren''t being malicious. They''re using the standard legal scaffolding, and the standard scaffolding has gotten cheaper for vendors over the last decade. The scaffolding only changes when buyers refuse to sign it.

A 90-minute review of your top five contracts will surface most of these. A red-line of the next five renewal documents will save you 5 to 15 percent of your software spend. Most procurement teams that get systematic about this find out they could have been doing it years ago.