Getting started
One contract type. One week. On your own contracts.
No law firm can make a responsible decision on demo data. The pilot exists so the firm sees on its own real files what AI contract review delivers — and what it does not.
Why a pilot, and not a demo?
Shown on a template contract, every tool looks convincing. But the firm’s question is not whether it works somewhere — it is whether it works on their contracts, to their expectations. That can only be settled on the firm’s own material, which is why we start with a pilot rather than a demo.
A demo measures the vendor. A pilot measures the product.
A demo on sample data shows what the vendor was good at picking. A pilot shows what the system does on the firm’s actual files.
Accuracy on its own is an empty word.
“Accurate” means something only against a specific contract type and specific expectations. So the measuring happens on the firm’s own contracts, against the firm’s own standard positions.
Without a playbook every output is generic.
The firm’s standard positions are captured during the pilot. Without them even the best system can only produce an abstract list of risks — the kind a lawyer has to overrule anyway.
How it runs
Five steps, nothing left to guess.
The sequence is always this one. What differs from firm to firm is the contract type and what goes into the playbook.
We pick the contract type
The one the firm reviews most often — typically an NDA or a service agreement. One type, not three: that is the only way the result stays comparable.
We capture the firm’s standard positions
With an experienced colleague we go through what the firm expects in that contract type and what it will not accept. That becomes the simple playbook the system measures contracts against.
The system processes the firm’s own contracts
Not sample files: the firm’s real, already-closed matters — throughout in the private EU environment or on the firm’s own server, with no external AI API.
The firm measures accuracy on its own files
The firm sees what was extracted, what was flagged as risk, what was missed — and which flag should have read differently. The yardstick is the firm’s professional judgement, not a number from us.
We decide together whether it goes further
At the end of the pilot the result decides: rollout, another round on the same contract type, or a no. All three are legitimate outcomes.
During the pilot the same six steps run as in production — and here too, the last one is the lawyer’s. The full workflow →
The outcome
What the firm gets
What stays with the firm at the end of the pilot is usable material rather than a presentation — and it stays even if the answer turns out to be no.
- Processed contracts drawn from the firm’s own material — not demo examples.
- A configured playbook: the firm’s standard positions in writing, in reusable form.
- A risk-flagging sample for the chosen contract type, with deviations and missing clauses.
- Accuracy feedback: what the system got right and where it was wrong, by the firm’s own judgement.
- A pricing and edition proposal: which edition suits the firm, and on what terms.
Commercial terms are agreed up front
The pilot’s scope, duration and fee are agreed in writing before anything starts — no invoice after the fact, and no automatic roll-over into production. At the end of the pilot the firm decides, not the contract.
Pricing and editions →The other side
What the firm has to bring
Not much — but this much cannot be worked around. Better to know it now than to discover it in week two.
One contract type
One, not three. The one that eats the most review time — that is where a change, if there is one, shows up soonest.
A handful of real contracts
A small set of actual, already-closed files that the firm has the necessary consent to use. Sample documents will not produce a result worth judging.
About two hours of a senior colleague’s time
That is what it takes to state and record the standard positions. It is the pilot’s most important input — and the firm keeps the result of it afterwards.
The pilot runs on the same private infrastructure.
The pilot is not an exception to the rule: it works in the same private EU environment as the production system — with no external AI API, or entirely on the firm’s own server. The data processing agreement is signed before the first document arrives. Audit trail and data export apply during the pilot too.
Which contract type should we start with?
Tell us which one eats the most review time in your firm, and we will put together the pilot around it — terms included, up front.