Enterprise AI contracts do not behave like enterprise SaaS. The pricing is usage-based, the training-data and IP exposures are new, the underlying model can be deprecated mid-term, and the contract framework is still being written in real time. This pillar walks through the four dimensions that matter most, the clauses most legal teams miss, and the structural protections that should be in place before signature.
Enterprise AI contracts — OpenAI, Anthropic, Google Vertex, Microsoft Copilot, AWS Bedrock, plus the rapidly expanding tier of vertical AI products — do not behave like SaaS. The pricing is usage-based rather than per-seat. The training data and customer data clauses carry obligations no traditional software contract did. The vendor's underlying model can be deprecated in months. And the contract framework is still being written in real time, which means many enterprise terms that are routine for SaaS — price protection, audit clauses, IP indemnity, exit rights — are absent or worded in ways that favour the vendor heavily.
In our experience across 340+ engagements, AI contracts signed in 2024–2025 without specialist review are now generating renegotiation cycles 12–18 months in. The patterns we see most often: unprotected token-pricing exposure, weak IP indemnity, ambiguous data-use clauses, and absent model-deprecation protection. The AI Vendor Contract Red Flags paper goes through each one in detail. Each is also a recurring theme in the vendor audit defense matters we handle.
Our team reviews the structural clauses before signature — when changes are still on the table.
Token-based pricing creates a cost exposure pattern unfamiliar to most procurement teams. Unlike per-seat SaaS, where cost scales with predictable headcount, AI cost scales with prompt complexity, output length, model selection, and integration depth — each of which can change without a procurement approval gate. The result: enterprises that piloted at $50K/month find themselves at $400K/month within six months once production integrations land, with no contractual mechanism to slow it down.
All the major AI vendors offer committed-use discounts — discounts of 20–50% in exchange for monthly or annual usage commitments. The trap is committing before production usage is baselined. We have seen enterprises commit to 12-month usage levels that turned out to be 3x actual usage by month four, with no contractual true-down. The defence is a 60-to-90-day production baseline before any meaningful commitment, and a negotiated quarterly true-down right of 15–25% on committed volume.
Vendors release new model versions on accelerating cadences. The contract typically pegs the discounted rate to a specific model family; newer, more expensive models are quoted separately. The customer's developers will migrate to the new model the day it ships because the output is better; the procurement team will discover the migration in the next invoice. The clause to negotiate is a "successor model" entitlement — automatic access at the same effective price to newer models in the contracted family.
Most enterprise AI usage is mediated through orchestration layers — Retrieval-Augmented Generation, vector databases, agent frameworks — that amplify token consumption. A single user query at the interface can generate dozens of model calls under the hood. Buyers who size based on user query volume understate token consumption by 5–20x. The discipline is to baseline token consumption per business workflow, not per user.
The clause-level review framework for OpenAI, Anthropic, Vertex, Bedrock and the vertical AI tier.
AI vendor contracts carry obligations and exposures that traditional software contracts do not. The legal review needs to cover dimensions an enterprise legal team may not have benchmarks for.
By default, many AI vendors retain the right to use customer prompts and outputs for model improvement unless an enterprise tier explicitly excludes it. The exclusion must be on-the-record, written into the contract, and apply to all sub-processors. "Zero data retention" terms are negotiable in most enterprise AI contracts but rarely offered without explicit ask.
Most enterprise AI MSAs assign output IP to the customer, but the wording varies. Some grant a perpetual licence; some assign full ownership. Some include carve-outs for "model improvements" derived from customer interactions. The clause should be unambiguous: customer owns the output, the vendor has no rights to output IP, no exception.
AI-generated output can infringe third-party copyright, trademark or patent rights. Vendor IP indemnities range from broad ("we cover any third-party IP claim arising from output use") to narrow ("only model output, only with commercial use, with claim notice within 30 days") to absent. At enterprise scale, the indemnity should cover commercial use, the cap should be at least 12 months of fees, and the obligations should mirror customer obligations under other technology contracts.
For regulated industries and EU customers, AI processing of customer data triggers GDPR, sectoral regulations, and increasingly explicit AI Act requirements. Contract clauses on data residency, sub-processor locations, and cross-border transfer mechanisms (SCCs, BCRs, adequacy decisions) need to align with the customer's compliance posture.
Our consultants benchmark AI contract terms against the broader market. The clauses that look standard often aren't.
A unique AI contract risk: the model version your application was built on can be deprecated within the term. The vendor's accelerated release cadence and the rapid pace of underlying research mean that 2-year-old models are routinely retired. Customer applications that fine-tuned, optimised prompts, or built guardrails against a specific model behaviour face a forced migration with no contractual recourse.
The negotiable clause is a model-availability commitment — minimum support window for any model used in production. 12 months is reasonable; 24 months is achievable at enterprise scale. The vendor's standard position is 6 months, sometimes less. Without the clause, every model upgrade becomes an unpriced migration project for the buyer.
When migration is unavoidable, contractually obliging the vendor to provide migration support — prompt translation guidance, A/B testing tools, fine-tuning credits on the new model — reduces the buyer-side engineering cost. This is standard in cloud migrations and should be standard in AI model deprecations.
The specific clauses, edition mix and rollout sequencing for Microsoft's AI suite.
Three actions before signing a meaningful AI commitment. First, baseline current production token consumption against the proposed commit; assume the baseline is 1.5–2x what the team expects. Second, list every contract clause the AI vendor has provided and benchmark each against the standard market position. Third, negotiate the structural clauses — model availability, training-data exclusion, IP indemnity, true-down rights — before the unit price.
Our team benchmarks AI contracts across the major vendors. We work for buyers, not for OpenAI, Anthropic, Google, Microsoft or AWS.
Weekly compliance intelligence for IT leaders.