AI credits at renewal: seats become consumption
September 2, 2026
A per-seat contract has one property finance depends on: the annual cost is known on the day it is signed. AI credits break that property. The seat fee stays, a credit allowance is attached to it, and consumption above the allowance is billed separately. The line item looks the same in the vendor's quote and behaves completely differently in the forecast.
What actually changed
Three things, and they compound. The seat price usually rises to fund the AI capability whether or not it is used. An allowance is granted per seat or per tenant, and it typically does not pool across the year or roll forward. And overage is billed at a rate set by the vendor, not by the market, so the cost of the marginal unit of usage is no longer something the buyer controls.
The questions to ask before signing
- What is one credit, in units the buyer can observe — a request, a document, a generated output — and can the vendor's own reporting show it per user?
- Does the allowance pool across seats and roll over across months, or is unused allowance simply lost?
- What is the overage rate, is it capped, and can it change mid-term?
- Can the vendor change the credit cost of an existing feature during the term, effectively repricing without a price increase?
- Who can incur overage, and can an administrator cap it before it is incurred rather than see it on the invoice?
Model the renewal, not the quote
Take a representative month of the vendor's own usage data and build three cases: current usage, the adoption level the vendor is projecting in the business case, and a case where the feature is genuinely successful. If the third case is unaffordable, the contract is not priced for the outcome both sides say they want, and that is a negotiation point rather than a surprise for the following year.
Where this belongs in the budget
Split the renewal into the committed seat line and a variable consumption line, and forecast them separately. Rolling the whole thing into a single software subscription number is how a formerly predictable line starts producing variances nobody owns. The consumption half belongs to whoever owns adoption of the feature.
The pattern is spreading
This is not one vendor's pricing experiment. Any software category where the vendor pays a model provider has the same incentive to convert a fixed subscription into a metered one. Treat the next several renewals as repricing events by default, and put the credit questions in the standard renewal checklist rather than raising them once, per vendor, under time pressure.