Oscar Klink · CTO  ·  25 June 2026

Why AI on top of chaos is still chaos

AI makes disorganised contracts faster to search. It doesn't fix the underlying data problems.

Most legal and operations teams are not ignoring AI. They are using it. Copilot summarises documents, ChatGPT drafts first versions, and a growing number of tools promise to surface risk from contracts in seconds. The technology is genuinely useful, and the teams adopting it are making a reasonable decision.

The problem is not the AI. The problem is what the AI is working with.

And to be clear about what that means in practice: if you had no CLM before, you still have no CLM. AI does not give you control over who can commit the company to a contract. It does not give you a renewal calendar you can trust. It does not enforce approval workflows, standardise your templates, or tell you what obligations you are currently on the hook for. It just lets you do all of that, wrong, faster.

The invisible gap in every AI-first contract workflow

When a company runs AI on top of a shared drive, an email inbox, and a collection of Word documents, it gets faster access to the same fragmented information it had before. The AI can read the document. It cannot tell you which version is current, whether the approval process was followed, or what obligations are now overdue across your portfolio.

Missed auto-renewals, unchecked liability caps, and compliance requirements do not disappear because you can draft agreements more quickly. These are structural contract management challenges, not speed problems. And structural problems require structural solutions.

According to the World Commerce and Contracting Association, poor contract management costs organisations an average of 9 percent of annual revenue. That figure does not decrease when AI is added to a disorganised repository. It decreases when the underlying data model is fixed.

AI is only as good as the structure underneath it

Think of it this way. A powerful search engine works because the web is indexed. The same technology applied to an unindexed archive returns noise. Contract AI is no different. Natural language queries, risk flags, and obligation summaries all depend on structured, validated metadata to produce reliable results.

If your contracts live in folders without consistent tagging, if approval history exists only in email threads, and if there is no single source of truth for what is signed and active, then your AI tools are pattern-matching against incomplete data. The output looks plausible. It is not trustworthy.

This is not a criticism of AI. It is a description of the prerequisite. You cannot fix data quality downstream, and contract data is no exception.

What CLM actually provides

A CLM platform solves a different category of problem than AI does, and that category is the one that keeps legal and ops teams up at night.

When contracts are created through structured workflows with enforced templates and approval logic, every agreement arrives in the archive with clean, consistent metadata. When that metadata is validated at the point of entry, reporting on obligations, renewal dates, and financial exposure becomes reliable rather than approximate. When permissions and audit trails are embedded in the process, you can demonstrate compliance rather than reconstruct it.

This structured layer is what gives AI something real to work with. Natural language filters, automated risk flags, and obligation tracking all perform significantly better when the underlying data has been governed from the start.

The decision is not either/or

No one is suggesting that legal teams choose between AI and CLM. The point is sequencing. Deploying AI on top of unstructured contracts is understandable. It is also a way of deferring the harder problem.

The organisations that will get the most from AI in their contract processes are those that invest first in the data infrastructure underneath it. That means consistent contract templates, governed workflows, structured metadata, and a searchable archive where every document has a clear status and owner. Ultimately, a contract is not a document, it is a strategic asset, and treating it as one is what makes AI genuinely useful rather than superficially impressive.

Once that foundation exists, AI tools can do what they are genuinely good at: surfacing patterns, accelerating review, and reducing the manual burden on legal teams who are already stretched thin.

The question worth asking is not whether your AI tool is powerful enough. It is whether the contracts underneath it are structured enough for the AI to be trusted.

Free tier available. No card required. Generally available 31 August 2026.