You’re being offered a price in one of three shapes. The shape will do more to determine what you pay over three years than the number attached to it, and it’s the part most evaluations spend the least time on.

What each shape does to you

	Per seat	Consumption	Outcome
You pay for	People with access	Volume used	Results delivered
Budgets	Cleanly	Badly	Unpredictably
Bad incentive it creates	Restrict who gets access	Discourage use	Argue about definitions
Who carries the variance	The vendor	You	Contested
Right when	Value is per person and adoption will be broad	Usage is concentrated in a few heavy users	The outcome is already measured in a system you both trust

The row worth sitting with is the third one. Every pricing shape creates an incentive that works against the reason you bought the thing.

Per-seat pricing makes every additional user a cost, so organizations ration access, and a tool that only the enthusiasts can reach never changes how the work is done. Consumption pricing makes every use a cost, so managers tell their teams to be thoughtful about it, which is a polite instruction to use it less. Outcome pricing makes the definition of the outcome the thing worth arguing about, and you will argue about it, in month seven, with someone whose commission depends on the answer.

You can’t escape this. You can pick which version of it you’d rather manage.

Paying for a curve that didn’t happen

Composite from a few regulated-documentation evaluations: a pharmaceutical company, medical writing and regulatory submissions, a few hundred people in scope across two sites.

What they signed was the shape most of these contracts settle into: a platform fee, plus consumption, with a committed annual minimum in exchange for a better unit rate. Illustratively, the commitment was set at roughly the volume they expected in month nine of year one, extended across the year.

They reached about forty percent of that in year one. They paid for all of it.

The commitment wasn’t a trick and the vendor had given real value for it. The error was upstream: the adoption forecast came from pilot volunteers, who had used the tool enthusiastically for ten weeks, and the curve was drawn as though four hundred medical writers would behave like the thirty who’d signed up.

Adoption in a large regulated function is slow for reasons that have nothing to do with the software. Validation, standard operating procedures, someone has to update a template, a therapeutic area lead is on leave. None of that was in the model.

The clauses that make a commitment survivable

Committed minimums are not inherently bad. They’re how you get a decent unit rate, and refusing all commitment usually means paying a premium for flexibility you may not need. Four terms make them liveable:

• Rollover of unused commitment into the following period. The most commonly granted of the four and the most commonly not requested.
• A ceiling on unit price, not only a floor on volume. If you’re guaranteeing their revenue, they can guarantee your rate.
• A re-baseline right at twelve months, resetting the commitment to actual usage. Harder to get, worth asking for, and the reaction tells you how confident they are in your adoption.
• Protection against changes underneath. If your consumption is measured in units the vendor defines, and the definition changes because the technology changed, your effective price moves without anyone renegotiating.

That fourth one is specific to this category and it’s newer than most procurement templates. Consumption units in AI products are not stable objects. A change in how the product processes a request can change your unit count materially, in either direction, without a single term of the contract being amended.

The thing almost nobody negotiates

Ask what happens to your price when their costs fall.

In a category where the underlying cost per unit of capability has been falling consistently, a three-year fixed price is a bet you’re making against the trend, and you’re making it silently. An annual benchmark review, or a clause that passes through some share of a reduction in underlying cost, is unusual but not absurd to ask for.

Most vendors will decline. The way they decline is informative. A vendor who explains that their own input costs are contracted and can’t be passed through is telling you something specific and probably true. A vendor who treats the question as inappropriate is telling you how the renewal conversation will go.

Which to insist on

If the value is genuinely per person and you intend broad rollout, per seat is usually right, and negotiate the right to add users mid-term at the original rate. That last clause is cheap to get at signature and expensive to get later.

If usage will be concentrated in a small group doing heavy work, consumption is right, because per-seat pricing across a large population to serve twenty real users is how you end up with an unflattering cost per active user in the benefits review.

Outcome pricing is right when the outcome is already being measured, by a system you both already trust, that neither party controls. In practice that condition holds rarely. When someone offers it and the condition doesn’t hold, what’s being offered is a future dispute with a discount attached.

One thing to do differently

Model whatever shape you’re offered at three adoption levels: the rate your pilot volunteers achieved, half of your plan, and double it.

The first is the fantasy, the second is the likely case, the third is what happens if it works better than expected, which is a scenario people rarely cost and which has bankrupted more than one committed-volume contract from the other direction. Sign the shape that’s survivable in all three.