The review running in your cloud, with redlines in Word.
Supplier liability is capped at fees paid in the prior 3 months 12 months, except for breaches of the data protection clause, which are not capped.
AI contract review
Each contract is checked against your playbook, with every deviation flagged and redlines tracked in Word.
Two years, renews yearly unless either side gives 60 days notice.
Net 45 from the invoice date, in US dollars.
Supplier processes customer data only on written instructions.
Supplier liability is capped at fees paid in the prior 3 months.
Either side may end it for material breach after 30 days to cure.
The laws of the State of Delaware.
Supplier liability is capped at fees paid in the prior 3 months 12 months, except for breaches of the data protection clause, which are not capped.
Lawyers read each one in full to find the few clauses that matter, and a missing clause still slips through because nobody checked it against the playbook.
of yearly revenue is lost to poor contracting, on average.
Sourcecfo.com
of legal professionals spend 3 hours or more reviewing one contract.
Sourceinfo.abovethelaw.com
Every contract is read against your playbook before a lawyer opens it.
| What changes | Without it | With it |
|---|---|---|
| Review time | Days per contract. | Hours, with the first pass done. |
| Consistency | Each lawyer reviews their own way. | Every contract against one playbook. |
| Missing clauses | Found after signing. | Flagged before review. |
What changes for your teams. We pick the tools to fit the systems you already run.
Two years, renews yearly unless either side gives 60 days notice.
Net 45 from the invoice date, in US dollars.
Supplier processes customer data only on written instructions.
Supplier liability is capped at fees paid in the prior 3 months.
Either side may end it for material breach after 30 days to cure.
The laws of the State of Delaware.
Supplier liability is capped at fees paid in the prior 3 months 12 months, except for breaches of the data protection clause, which are not capped.
Two years, renews yearly unless either side gives 60 days notice.
Net 45 from the invoice date, in US dollars.
Supplier processes customer data only on written instructions.
Supplier liability is capped at fees paid in the prior 3 months.
Either side may end it for material breach after 30 days to cure.
The laws of the State of Delaware.
Supplier liability is capped at fees paid in the prior 3 months 12 months, except for breaches of the data protection clause, which are not capped.
Illustrative figures, not a client result. Your own baseline is taken in the first week.
Another company built the same kind of system and wrote publicly about how it went.
What they learned
Checking each playbook rule against a long contract works when one search finds the clause and a second check confirms it.
In a pilot, bi-directional search caught 88.1% of relevant paragraphs.
You own the config, the tests and the runbooks, so you can swap any part later.
Supplier liability is capped at fees paid in the prior 3 months 12 months, except for breaches of the data protection clause, which are not capped.
Two years, renews yearly unless either side gives 60 days notice.
Net 45 from the invoice date, in US dollars.
Supplier processes customer data only on written instructions.
Supplier liability is capped at fees paid in the prior 3 months.
Either side may end it for material breach after 30 days to cure.
The laws of the State of Delaware.
Typical building blocks: A YAML playbook; Docling parsing; retrieve-then-verify on the Claude Agent SDK; a missing-clause check; tracked changes through a Word add-in; CUAD and matter evals.
Alternatives: Spellbook, LegalOn, Harvey, Ironclad.
The work happens in your cloud, with the people who will own it.
Contracts checked against your playbook.
About 5 weeks. You get a price range before the call and one fixed number after it. That number is the invoice.
We pick the one that fits the systems you already run. You own the config, the tests and the runbooks, so you can swap any part later. Most often a YAML playbook, Docling parsing and the Claude Agent SDK, with a Word add-in for redlines; Spellbook, LegalOn, Harvey or Ironclad when buying beats building.
No. It does the first pass and suggests redlines. A lawyer accepts or rejects every change.
Each playbook rule says what must be there. When no clause matches a rule, the contract is flagged.
Standard ones you sign often, such as NDAs, order forms and supplier agreements.
They stay in your cloud. Parsing, review and the logs run in your account.
Contracts checked against your playbook. You own the config, the tests and the runbooks.