Skip to main content
Orion Five Engineering
Book a scoping call

10 Jalan Kilang #04-05, Singapore 159410
+65 6100 5505

AI governance

What your AI vendor contract is probably missing

Most AI agreements are recycled SaaS templates. That structure assumes software which does what it is told, performs consistently, and does not learn from your data. None of the three holds.

Terence Kok · 2026-06-21 · 5 min read

A stack of matte white machined plates with one thin red shim inserted between two of them, standing slightly proud of the stack.

The gap in an AI vendor contract usually becomes visible only after something has gone wrong, which is the worst moment to discover that the agreement never contemplated it.

A standard software contract was drafted for a deterministic product. AI systems produce probabilistic outputs, degrade over time with no change to the code, learn from the data you put into them, and raise provenance questions about what they were trained on long before you met them.

Where the template stops short

Assumption in a SaaS templateWhat an AI system actually does
Output is deterministic and reproducibleOutput is probabilistic and may differ across identical inputs
Performance is stable until the code changesPerformance drifts in production with no code change at all
Your data is processed, not absorbedYour data may improve the model, and the contract may be silent on who owns that
Provenance is the vendor's own IP questionTraining-data provenance becomes your exposure once you deploy the output

Clauses worth insisting on

Regulation is still catching up with practice, which means the contract is currently doing work the law has not yet been asked to do. That is an argument for drafting carefully now, not for waiting.

All insights