← Blog
Technology ContractsNovember 20265 min read

Your vendors are adding AI features and charging for them. Check what you asked for.

Last updated: November 16, 2026

By Morris Stern · Stern Technology Advisory

The renewal quote arrives and the number is higher. Some of the increase is the usual uplift. Some of it is a line you did not ask for: an assistant, a copilot, an intelligence tier, an add-on with AI somewhere in the name. Sometimes it is not a line at all. It is a new edition, and the old one is no longer offered.

I do not lead with AI, and this piece is not really about it. It is about contracts. The question is not whether the feature is clever. The question is whether you agreed to buy it, what it does with your data, and what it will cost once the vendor stops discounting it.

How it arrives

Embedded AI comes in through four doors, and none of them is a purchase decision.

The renewal. The vendor bundles the feature into the next term's price, or moves you to a higher tier that includes it. The old tier quietly disappears from the price list.

The terms update. A revised service agreement or data addendum arrives by email with an effective date and a line saying continued use means acceptance. The change that matters is usually how your data may be processed, and by whom.

The default switch. The feature appears in the product, turned on, for everyone. Staff start using it before anyone has decided whether they should.

The usage meter. The feature is included, but only up to a number of credits, calls or seats. Past that it bills by use, and nobody on your side is watching the meter.

None of these goes through purchasing approval. That is the problem. A new software purchase of the same size would get a review. A feature that arrives inside an existing contract usually gets none.

Why this is a contract problem

When I wrote a summary of an ERP agreement in one operating role, one of the gaps I named was the line between new development and platform improvement. If the vendor improves the platform, the customer should not pay twice for it. If the customer asks for something new, it is chargeable. The agreement did not draw that line clearly, so every enhancement turned into a negotiation.

Embedded AI sits exactly on that line. The vendor will call it a new capability and price it. You may reasonably see it as the product getting better, which your maintenance fee already pays for. Which one it is should be settled in writing before the renewal, not argued about after the invoice.

The pricing basis matters as much as the price. That ERP was licensed as a share of sales. A supplier-integration vendor I later renegotiated charged per store. In both cases, the way the price was calculated mattered more than the number on the first invoice, because the basis decides how the cost grows. AI features add a new basis, usage, and usage is the hardest one to forecast.

What to ask for in writing

Before you renew any agreement where AI features have appeared, ask the vendor to answer these in the contract or the order form, not in an email from the account manager.

1. Is it on by default? If so, can it be turned off for the whole company, and does turning it off remove anything you already use?

2. What data does it use? Which of your records it reads, where that processing happens, and which other companies process it on the vendor's behalf.

3. Is your data used to train or improve anything? The answer you want is no, by default, with a clause that says so.

4. What does it cost on its own? The price of the feature as a separate line, and the price of the renewal without it.

5. What happens at the next renewal? Introductory pricing ends. Ask for the price for the following term, or a cap on the increase.

6. How is usage counted and capped? If it meters, you want the unit, the included amount, the overage rate and a hard limit that needs your approval to exceed.

7. Who stands behind what it produces? If the feature writes an answer for a customer or changes a record, the contract should say what the vendor is responsible for when it is wrong.

If a vendor cannot answer one of these in writing, you have learned something about the feature.

How to price it out

The goal is not to refuse every AI feature. Some of them are useful. The goal is to buy them on purpose.

Separate the line. Ask for the renewal priced two ways, with the feature and without it. If the vendor will not price it without, ask what you lose by staying on the old edition, and get that in writing too.

Pilot before you commit. Ask for a trial for a named group, with the feature off for everyone else and a decision date before it becomes chargeable. I have run enough pilots to know the first users find the problems. Better they find them before the contract does.

Cap the meter. If it bills by use, put a monthly ceiling in the order form and name who on your side gets the alert.

Trade it. If you do want the feature, it has value to the vendor as well. They want adoption they can report. That is bargaining power on the rest of the renewal, and it only exists before you sign.

Put it on the calendar. Add the feature's own dates to your renewal calendar: trial end, price change, next notice date. A feature that renews on a different date from its parent agreement is a second contract, whatever the paperwork calls it.

The practical takeaway

Pull the last renewal quote and the last terms update from your five largest software vendors. Mark every line or clause that mentions AI, assistants, automation or data use. For each one, write down whether anyone on your side asked for it. Anything nobody asked for gets the seven questions above before its next notice date.

Checking what you pay for that you did not ask for is part of every Technology Spend and Contract Diagnostic. It is usually a short list. It is rarely an empty one.

Continue your research

These links follow the same decision area and connect guidance to implementation paths.


About the author

Morris Stern is a Winnipeg-based technology executive and advisor. He has run the ERP, store systems, integration, and governance decisions these articles describe as the accountable executive.