A few weeks ago I argued that once you hire an AI legal agent, you will never log into a CLM again. The contract was always the record, and the database was a workaround for human reading speed. An agent that can read the contracts directly makes the copy unnecessary.
The obvious follow-up is fair. Fine, the agent can read. But reading was never the hard part. Most of the debate about AI contract management is still about reading. The real question is what happens next.
The CLM stops at the alert
Picture the best possible CLM. Every field filled, every amendment linked, every date correct. In January it sends you an alert: seven vendor contracts expire this year.
Now what?
Someone opens each contract to check how it ends. Does it renew automatically, or lapse? How much notice is needed, and by when? Does the notices clause require registered post to an address the vendor left two years ago? Is an extension a simple letter, or an amendment signed by two directors? Has someone in procurement already agreed something by email?
Then someone drafts the letters, routes them for approval, gets them signed, sends them in the right form, and types the new dates back into the CLM. That is where the data-entry problem starts again.
The database told you something you needed to know. Everything that actually protected the company happened outside it, by hand. That may explain why the leak never closed. World Commerce & Contracting and Deloitte put average contract value erosion at around 8.6%, while nearly 80% of companies had invested in contracting software in the previous five years. The value was rarely lost in not knowing. It was lost in not doing: the notice never sent, the price review never triggered, the obligation nobody performed.
What we actually want from an agent
In agentic AI, the point is not a better answer. It is a colleague who acts. That comes down to two things.
The first is proactiveness. You should be able to ask “which contracts expire this year?” and get the right answer. But a good colleague doesn’t wait to be asked. A good junior lawyer comes to you in October and says: three vendor contracts renew automatically in January unless we give notice by 30 November, here is what each one costs us, do you want to keep them?
The second is execution. You reply in one line: “Extend A, B and C. Hold E and F.” And the work gets done, properly.
Why “properly” is the hard part
That one line hides a surprising amount of law.
“Extend A” might mean doing nothing at all, because A renews automatically. “Extend B” might need a signed amendment, because B has a fixed term and no renewal right. “Extend C” might mean exercising an option in writing, within a window that closes months before C actually expires.
“Hold E and F” is the dangerous one. If E renews automatically, waiting is not neutral. Waiting is a decision to renew. To genuinely hold E, someone has to tell the vendor in time that you will not renew, in the form the contract requires, and then reopen the conversation. If F rolls on month to month after expiry, holding it may need nothing yet, or it may need a termination notice whose notice period runs into next year.
None of this sits in a field called “expiry date”. It sits in the renewal clause, the notices clause, the amendment clause, the signing authority, and sometimes in an email thread from last spring. Where the contract is silent, it sits in the law: in some jurisdictions, simply carrying on after expiry can extend the contract.
This is the part the system of record was never built for. A field captures the standard case. The risk lives in the exceptions: the negotiated renewal mechanism, the unusual notice requirement, the option that must be exercised early. A database built on fields is blindest exactly where the stakes are highest.
An agent that reads the actual contract, against the actual law, can handle “Hold E and F” correctly. An agent that reads a table cannot.
Why the agent can’t live inside the CLM
The CLM vendors have noticed. Their answer to the AI wave has been to add an assistant inside their own app.
For the person doing the work, that is one more assistant. They already have Claude, ChatGPT or Gemini open. Now there is another one, living in one system, knowing only what that system holds, reachable only after another login.
Look again at “Extend A, B and C. Hold E and F.” Carrying it out touches email, the signing tool, procurement, finance and the vendor. Very little of it happens inside the CLM. An assistant confined to the CLM can find the contract. It cannot run the process around it.
The agent that handles your contracts has to be independent of the place they are stored. It goes where the work goes: it reads the contract wherever it sits, writes the notice, routes it for approval, gets it signed and sends it.
The record writes itself
Structured data still has a place. If you ask about four thousand contracts at once, it makes sense for the agent to keep an index rather than reread everything. Renewal deadlines still need watching without anyone asking.
The difference is who maintains it, and why. The index is derived from the contracts and can be rebuilt from them at any time. Nobody types it. And because the agent is the one sending the letter declining renewal and filing the signed extension, the history writes itself as the work happens: who decided, what was sent, when, and on what basis.
The record stops being a chore people do before the work. It becomes evidence that the work was done.
For fifteen years, the system of record was the place you went to find out what you had. The question now is whether the thing that knows your contracts can also act on them, within rules your lawyers set, with a human deciding wherever judgement is needed.
The test
So here is a simple test for any contract tool, old or new. Don’t ask it which contracts expire this year. Every tool can answer that now.
Tell it: “Extend A, B and C. Hold E and F.” Then check what actually happened.
That is the test we build Arna for. Your lawyers instruct her once: how renewals are handled, who approves, who signs. Then anyone in the company can ask her, and she runs the process start to finish, every step on the record.