Score the risk in an enterprise AI contract across data use, pricing, and exit. The three decisive clauses and the moves.
Enterprise AI contracts are new enough that the standard paper favors the vendor. Three clauses decide most of the risk: how your data may be used, how price can rise, and how cleanly you can exit. Score them before you sign.
Score the risk first, then fix the clauses.
Quick answer
Three clauses decide most enterprise AI contract risk: how your data may be used, how price can rise, and how cleanly you can exit. Example: unclear data use, open ended pricing, and weak exit scores 100 of 100, high risk. See Anthropic commercial terms and Anthropic documentation.
AI contract clause risk scorer
Three clauses decide most enterprise AI contract risk: how your data may be used, how price can rise, and how cleanly you can exit.
The contract should bar training on your data and define retention and isolation. Ambiguity here is the highest risk.
Open ended price increases and usage repricing are common. A cap and clear unit pricing control the exposure.
Weak termination, data return, and portability terms lock you in. Define them before signing.
Certifications, residency, and incident terms should match your obligations, not the vendor default.
Indemnity and acceptable use terms shift risk. Read them against how you will actually use the model.
| Clause | Risk if weak | Buyer side move |
|---|---|---|
| Data use | Training on your data | Bar training, define retention |
| Pricing | Open ended increases | Cap and fix unit pricing |
| Exit | Lock in | Define return and portability |
The standard advice is to accept the vendor paper to move fast in a new market. We disagree. The standard AI contract favors the vendor on exactly the clauses that matter, and speed now becomes lock in later. The buyer side move is to fix data use, pricing, and exit before signing, even under time pressure, because these three clauses decide the contract more than the rate.
Most Claude business cases over claim the saving. They assume Opus everywhere, ignore caching, and price Bedrock as if it were free routing. Model the real mix first, then the number survives the CFO.
It weighs the three clauses that decide most enterprise AI contract risk: how your data may be used, how price can rise, and how cleanly you can exit.
Data use. Ambiguity on training, retention, and isolation of your data is the most consequential gap in a standard AI contract.
Negotiate a cap on increases and clear, fixed unit pricing rather than accepting open ended repricing tied to usage or model changes.
No. It is a directional buyer side prioritization. Have counsel review the contract; the scorer points them at the three clauses that matter most.
Yes. It is free and runs in your browser. No payment and no account required.
No. It is buyer side data. Build the position internally and negotiate on your modeled number.
It is directional, calibrated to the patterns we see across enterprise AI engagements. Published rates and your contract govern the final number.
We model the position, benchmark against our deal database, and sit at the table for the negotiation. We are independent and buyer side.
The cost model is the anchor. Walk into the Claude Enterprise conversation with a number you trust and the seller reshapes its offer around you.
Independent buyer side advisory on GenAI spend: Claude Enterprise seats, API token cost, prompt caching, Bedrock routing, and vendor lock in. Model first, then negotiate.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying GenAI contracts. No vendor influence. No reseller margin.
Independent buyer side advisory. No vendor influence. No reseller margin. We sit on your side of the table when you negotiate with Anthropic and the GenAI vendors.
Monthly. One email. Zero noise.
The moves we use across Claude, ChatGPT, Gemini, and Copilot deals, from the buyer side practice. Talk to us before you commit.
Independent buyer side advisory. No obligation.
