Workflow, copilot or CLM
Three things are being sold to legal teams under names that overlap, and the confusion is expensive. It costs a team a licence it does not need, or a year spent expecting one kind of tool to do another kind of job. This page is my attempt to draw the line plainly. I sell one of the three, so read it with that in mind.
A copilot answers
You ask it something, it produces text, and you decide what to do with the text. The best of them are very good, they are getting better quickly, and Harvey, CoCounsel, Lexis+ with Protégé, Legora and vLex Vincent are the names most often in the room.
A copilot is the right answer when the bottleneck is a lawyer facing a blank page or an unfamiliar area. It is the wrong answer when the bottleneck is that nobody knows who owns the request.
A CLM holds contracts
It stores agreements, moves them through approval and tells you what you signed. Ironclad, DocuSign CLM, Icertis, Agiloft, Sirion, Juro and LinkSquares are the field.
A CLM is the right answer when your problem is contracts as a portfolio: renewals, obligations, and where the signed version is. It is the wrong answer when your problem is the queue of everything that is not a contract.
A workflow carries the file
It is the path a matter takes, drawn as named stages, each with an owner, a clock, a mandate for whatever software touches it, and a record. That is what LEXSAS designs.
It is the right answer when the problem is not the drafting and not the storage, but the handover: who decided, on what basis, and can you show it later. It is the wrong answer when what you need is a database or a better draft, and I will say so on the scoping call.
The comparison
| Aspect | Copilot or assistant | Contract lifecycle system | Designed workflow (LEXSAS) |
|---|---|---|---|
| What it is | A tool that answers and drafts on request | A system of record for agreements | The path a matter takes, drawn as named stages |
| What it holds | A session and, increasingly, a workspace | Contracts, their metadata and their approvals | The file, the mandate, the record |
| Unit of work | A prompt or a task | A contract | A matter, from arrival to close |
| Who holds the mandate | Whoever is using it that session | The approval chain, over the contract | The agent, in writing, agreed before the run |
| Who signs | Whoever chooses to use the output | Whoever the approval chain names | A reviewer named before the pilot starts |
| What it leaves behind | The output, and whatever logging the vendor provides | The contract and its approval trail | A record of what ran, on which sources, under which mandate, and who signed |
| Bought or designed | Licensed per seat | Licensed per organisation | Designed with the team and left with the team |
| Where LEXSAS sits | Beside it. The workflow can call it, and the gate sits after it | On top of it. The workflow uses it as the contract’s home | This is what LEXSAS designs |
| What it will not do | Own the queue, or keep a record you can defend | Cover the matters that are not contracts | Draft better than a good assistant, or store contracts better than a CLM |
Every claim in that table is one I can defend about the workflows I design. The claims about copilots and contract systems describe what those categories are for, not a test of any particular product. LEXSAS resells none of them and claims no certified connector to any of them.
Why a team ends up with all three
In practice most in-house teams already have a copilot and a contract system, and what they are missing is the path between them. The assistant produces a draft, the contract system stores the signed version, and nobody can say who decided the thing in the middle.
A designed workflow is the part that carries the file from one to the other, and it is the part that is still hand-built almost everywhere.
The honest failure mode
A workflow is a designed thing, which means it has to be maintained. Every model change, prompt edit and connector upgrade has to pass a gate, and someone has to own that.
Teams who want a licence and no upkeep should buy a licence. I say this before a pilot rather than after it, and I have watched enough enthusiasm run out at the maintenance stage to keep saying it.
Next: the eight workflows, or the operating standard if you want the method before the menu. The words used here are defined in the glossary. Get in touch