- contact@insightcontractsai.com
InsightContracts reads the counterparty’s draft, PDF or Word, into its clauses and quotes each one with its page and line. It compares every clause with your playbook’s preferred and fallback positions, finds the missing DPA, the exhibit nobody attached and the assignment clause that contradicts the master agreement, and proposes the playbook’s own fallback language as the redline. Then it stops, and a lawyer decides.

Most of a contract review is preparation: finding the liability clause in someone else’s numbering, checking it against the playbook, noticing that the DPA the agreement mentions isn’t attached, and retyping the company’s fallback wording into a redline. The judgement, which is the part only a lawyer can do, gets whatever time is left. And after signing, the notice deadline and the supplier’s annual report live in a PDF nobody reopens.
Every draft read from the top, every clause compared with a playbook that lives in a separate document, every revised draft compared by eye with the last one.
A services agreement where the supplier will handle personal data and no Data Processing Addendum exists anywhere. An exhibit referenced on page 2 and never attached. A clause that quietly overrides its master agreement.
An auto-renewal can only be stopped before its notice deadline, often months before the end date. Missing it buys another term. So does forgetting the certificate the supplier owes every year.
One matter for every contract request. Seven agents prepare each stage. A lawyer accepts, rejects or asks about what they prepared, and makes every decision that matters.
A matter opens from the business’s request or an uploaded draft. The reader finds twelve clause types, each quoted with its page and line, plus the exhibits referenced and attached and the signature blocks.
Each clause is compared with the playbook: preferred, fallback, deviation, walk-away or missing. Cross-document checks catch a missing DPA, a missing exhibit and an assignment clause that conflicts with the parent.
A redline is the playbook’s fallback language, verbatim, held until a lawyer sends it. Each new draft is read, reviewed and compared with the last, clause by clause and word by word.
Ten approval controls in Rules Studio block or refer the matter to the General Counsel. The approver is never the submitter, and the decision record keeps every control’s outcome.
The executed copy joins the repository. Obligations are tracked with an owner and a due date, and every auto-renewal’s notice deadline is on the renewals calendar.
From the fictional demo company, Calderbrook Systems, Inc.: a US$1.14 million master services agreement on the supplier’s paper, matter CTR-2026-000001 with Ilvermoor Logistics Inc. The supplier’s second draft moved on two clauses. The comparison shows what moved, and the review shows what didn’t.


The playbook and the US$250,000 threshold in the demo are illustrative, not legal advice. The matter, worked end to end
Clause-by-clause comparison with the playbook is half the review. The other half is reading the draft against the rest of the contract family: the DPA, the exhibits and the master agreement it sits under.
The request says the supplier will process personal data. The draft has no data protection clause, no DPA is attached, none is on the matter and none is signed under a parent agreement.
The order form lets a party assign it without consent. The master agreement it sits under, CB-MSA-0042, requires prior written consent and prevails only where the order form doesn’t expressly override it.


Each agent does one stage and stops at a prepared decision: a review summary to use, redlines to apply, a request to hold for sending, a submission to make. A lawyer accepts, rejects or asks. Every answer goes on the record, and how often lawyers agree is how an agent earns more autonomy, up to a ceiling of L2 (ask first).

Every executed copy is read the same way as a draft. The repository holds the key terms with page and line, the renewals calendar counts back from the end of term to the notice deadline, and the obligations tracker lists who owes what by when, quoted from the clause.


The questions a General Counsel is asked are simple. InsightContracts keeps the evidence for each answer on the matter, as it was when the decision was made.
The decision record: who submitted, who approved, the draft and version, every control’s outcome, and each deviation’s position and resolution.
The approver is never the person who submitted. Uncapped liability, governing law outside the playbook and high-value matters go to the General Counsel.
The renewals calendar shows every notice deadline, which windows are closing and which have passed, with the clause it came from.
Every agent step, what it prepared, who answered and how, and the agreement rate that decides whether it earns more autonomy.
A Python API, a React app and PostgreSQL, designed to run in your own cloud account against your own systems. No clause, position or redline on a matter is something a model made up.
Every clause is quoted with its page and line, the same in the PDF, the Word file and the text layer. A clause the reader can’t find is reported missing, never filled in.
Preferred, fallback and walk-away positions, severity and approver are rows you maintain. The redline is your fallback wording, verbatim.
What blocks approval and what goes to the General Counsel are controls you can read, test against a real matter and publish.
InsightContracts prepares and records. It doesn’t give legal advice, and nothing reaches a counterparty without a person sending it.