You are about to sign a contract for a product that will not be the same product in six months, using a template written for software that shipped twice a year and changed when you accepted an upgrade.

Nothing in this lesson is legal advice. It is the commercial shape to hand to the person who does give it, because your legal team will draft what you ask for and they are not going to know to ask for these on their own.

The change that breached nothing

Composite from a few archive-scale evaluations: a media and publishing group, automated content classification and rights checking across a large back catalogue.

They deployed, then spent about three months tuning their thresholds until the review queue was a size two editors could handle. Good outcome, sensibly done.

Then an update on the provider side changed how the underlying model behaved. Nothing broke. Illustratively, precision moved a few points one way and recall a few points the other, which is the sort of change that is invisible in aggregate and very visible in a queue. Their carefully tuned thresholds were now set for a system that no longer existed.

They found out roughly six weeks later, when an editor mentioned the queue felt heavier. No term of the contract had been breached. No term of the contract covered it. Their own vendor had not been told in advance either.

Five terms worth asking for

Notice of material change to the underlying model. Vendors resist the word material, and fairly, because it is vague. Offer a test instead of an adjective: any change of model family or version, plus anything they announce publicly as a behavior change, plus anything they themselves detect as moving output distribution.

Deprecation notice with a floor. How long you get before a version you depend on is withdrawn. Ask for a stated number of months. Ask separately for the right to remain on a prior version during a validation window, which is worth a great deal in regulated work and very little elsewhere, so do not spend negotiating capital on it if you do not need it.

A benchmark written into the agreement. Almost nobody does this and it is the most useful of the five. Agree a small set of your own held-out cases and an acceptance threshold at signature. Re-run it quarterly. If the result falls below the threshold, you have a defined remedy, even if the only remedy you can win is a termination right.

Without it, the sentence available to you in month eight is that it seems worse than it used to be, which is an opinion, and you will be having an argument rather than exercising a right.

Your data out of training, in terms that survive a product change. Most vendors will give you this readily. What varies is whether it covers the derived artifacts from the previous lesson, and whether it binds their providers as well as them.

What happens if their provider relationship ends. Many vendors in this category are built on capability they license. Ask what happens if that arrangement changes, whether they can serve you on an alternative, and how long that would take. The answer tells you how much of the product is actually theirs, which is useful well beyond the contract.

What you will actually get

Not all five. Possibly two. So rank them before you walk in, because the order in which you concede is decided in the room otherwise, and in the room the unfamiliar clause always goes first.

For most buyers the benchmark and the deprecation notice are worth more than the price concession you would trade to keep them. Procurement will not see it that way, because a discount appears in the savings number and a benchmark clause appears nowhere. That is a reporting artifact rather than a judgment, and it is worth naming out loud before the negotiation rather than after.

One tactical note. Ask for these early, in the first commercial conversation, framed as how we work rather than as demands. A clause introduced in week two is a requirement. The same clause introduced in week nine, after the shortlist is public and your sponsor has told the board, is a problem you are creating for a deal everyone now expects to close.

The list you already have

If you have been keeping the running list from your reference calls, the answers to what would you put in the contract if you were signing again, this is where it earns its keep.

Those answers tend to be narrow and specific in a way that generic templates are not. A named support contact. A cap on the annual uplift. The right to add users mid-term at the original rate. Notice on a change to how consumption is counted. Every one of them came from somebody who learned it at their own expense, and there is no cheaper source of contract language anywhere in this process.

One thing to do differently

Put a benchmark in the contract. Twenty of your own cases, an agreed threshold, re-run quarterly, with a stated consequence if it fails.

It takes an afternoon to assemble and it converts the most likely failure in this category, quiet degradation that nobody can prove, from a disagreement into a clause.