AI contract review

First-pass review, done before legal opens it.

Each contract is checked against your playbook, with every deviation flagged and redlines tracked in Word.

About 5 weeks
to live on real traffic
Founder-led
no handoff to juniors
Fixed price
agreed before work starts
Master services agreement Supplier draft, version 2, 14 pages Checking against the playbook 1 clause to change
Clauses 6 of 6 checked
Term and renewal Not checked Matches playbook

Two years, renews yearly unless either side gives 60 days notice.

Payment Not checked Matches playbook

Net 45 from the invoice date, in US dollars.

Data protection Not checked Matches playbook

Supplier processes customer data only on written instructions.

Limitation of liability Not checked Outside playbook

Supplier liability is capped at fees paid in the prior 3 months.

Termination Not checked Matches playbook

Either side may end it for material breach after 30 days to cure.

Governing law Not checked Matches playbook

The laws of the State of Delaware.

Playbook Acme supplier terms
Renewal notice of at least 30 days
Payment no sooner than Net 30
Customer data used only on our instructions
Liability cap of at least 12 months of fees
Data breaches are not capped
Suggested edit Limitation of liability
PlaybookCap supplier liability at no less than 12 months of fees. Data breaches are not capped.

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.

LCLegal counsel to approveRejectAccept edit
The problem

Every contract waits for legal, and sales waits with it

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.

Almost 9%

of yearly revenue is lost to poor contracting, on average.

Sourcecfo.com

Half

of legal professionals spend 3 hours or more reviewing one contract.

Sourceinfo.abovethelaw.com

How we fix it

Every contract is read against your playbook before a lawyer opens it.

What changesWithout itWith it
Review timeDays per contract.Hours, with the first pass done.
ConsistencyEach lawyer reviews their own way.Every contract against one playbook.
Missing clausesFound after signing.Flagged before review.
How it works

What we build

What changes for your teams. We pick the tools to fit the systems you already run.

Clauses 6 of 6 checked
Term and renewal Not checked Matches playbook

Two years, renews yearly unless either side gives 60 days notice.

Payment Not checked Matches playbook

Net 45 from the invoice date, in US dollars.

Data protection Not checked Matches playbook

Supplier processes customer data only on written instructions.

Limitation of liability Not checked Outside playbook

Supplier liability is capped at fees paid in the prior 3 months.

Termination Not checked Matches playbook

Either side may end it for material breach after 30 days to cure.

Governing law Not checked Matches playbook

The laws of the State of Delaware.

What changes

Measured against where you started

Example: Acme Inc

What changes at a company like Acme Inc

Illustrative figures, not a client result. Your own baseline is taken in the first week.

MeasureBeforeAfter
Time to first review5 daysSame day
Contracts checked against the playbookSomeEvery one
Lawyer time on a standard contract3 hours45 minutes
Missing clauses caught before signingUnknownEvery tested case

How others built it

Another company built the same kind of system and wrote publicly about how it went.

What you keep

Everything runs in your cloud, and stays yours

You own the config, the tests and the runbooks, so you can swap any part later.

The review running in your cloud, with redlines in Word.

Playbook Acme supplier terms
Renewal notice of at least 30 days
Payment no sooner than Net 30
Customer data used only on our instructions
Liability cap of at least 12 months of fees
Data breaches are not capped
Suggested edit Limitation of liability
PlaybookCap supplier liability at no less than 12 months of fees. Data breaches are not capped.

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.

LCLegal counsel to approveRejectAccept edit

Your playbook as rules your legal team owns.

Clauses 6 of 6 checked
Term and renewal Not checked Matches playbook

Two years, renews yearly unless either side gives 60 days notice.

Payment Not checked Matches playbook

Net 45 from the invoice date, in US dollars.

Data protection Not checked Matches playbook

Supplier processes customer data only on written instructions.

Limitation of liability Not checked Outside playbook

Supplier liability is capped at fees paid in the prior 3 months.

Termination Not checked Matches playbook

Either side may end it for material breach after 30 days to cure.

Governing law Not checked Matches playbook

The laws of the State of Delaware.

  • A test set of past contracts that gates every change.

  • A runbook your legal team owns.

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.

How the weeks run

Live in about 5 weeks

The work happens in your cloud, with the people who will own it.

  1. Week 1Write your playbook as rules with legal and collect past contracts to test on.
  2. Weeks 2 to 4Build the review and the redlines in Word, and tune them against your contracts.
  3. Week 5Open it for the first contract type and hand over the runbook.
  4. After thatRunning on real traffic

    Contracts checked against your playbook.

Before we start

  • Your current playbook or redline notes, in any form.
  • At least 50 past contracts of that type with known issues.
  • A named lawyer who owns the rules, about 3 hours a week.
Fit

Is this the right first build?

It fits when

  • Every contract waits for legal.
  • A missing clause is found after signing.
  • A team on your side will own it after we leave.

It does not fit when

  • You want a hosted tool picked and resold to you.
  • You want a strategy deck in place of working software.
  • Nobody on your side can own it after we leave.

What’s included and what isn’t

Included

  • One contract type, such as NDAs or supplier agreements.
  • One playbook of up to 40 rules.
  • Redlines as tracked changes in Word.
  • A test set of up to 50 past contracts.

Not included

  • Legal advice or negotiation.
  • A second contract type, which is added after the handover.
  • Contract storage and signing.
Fixed quoteOne price, agreed before work starts

About 5 weeks. You get a price range before the call and one fixed number after it. That number is the invoice.

  • If the work takes longer than we planned, we absorb the cost.
  • You pay 50% at the start and 50% at acceptance. Builds of 6 weeks or more pay 40% at the start, 30% at the midpoint and 30% at acceptance.
  • If a build starts within 60 days of your Audit results, the full Audit fee comes off its price.
  • We start three new projects a quarter, so your start date depends on when you book.
Book a demoSee starting prices
FAQ

Questions teams ask before they book

Which tools do you use?

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.

Does it replace our lawyers?

No. It does the first pass and suggests redlines. A lawyer accepts or rejects every change.

How does it find a missing clause?

Each playbook rule says what must be there. When no clause matches a rule, the contract is flagged.

Which contract types fit first?

Standard ones you sign often, such as NDAs, order forms and supplier agreements.

Where do our contracts go?

They stay in your cloud. Parsing, review and the logs run in your account.

AI contract review, running in your cloud in about 5 weeks.

Contracts checked against your playbook. You own the config, the tests and the runbooks.