NDA and vendor-paper review
First-pass review against your playbook, with the exceptions routed to a lawyer.
The problem
NDAs and vendor paper arrive faster than anyone can read them. They are mostly standard, occasionally not, and the team cannot tell which is which without reading all of them.
How we would run it
STAGE 1
Evidence
A written picture of the current state, with its gaps named.
Pull a sample of recent agreements and the redlines that were actually made. The playbook that matters is the one in the markups, not the one in the folder.
STAGE 2
Baseline
A baseline measurement both sides agree on.
Measure today: how long a first pass takes, how many come back with no changes, and where the queue forms. Test whether the sample is clean enough to evaluate against.
STAGE 3
Design
A design your architecture and risk leads have approved.
Set the clause positions, the fallbacks and the escalation rules. Decide which deviations the assistant may accept silently and which always reach a lawyer — that line is the whole design.
STAGE 4
Ship
Working software or a live process, in production.
Release to one intake channel behind the evaluation set, with the redline and rationale produced for a reviewer rather than applied automatically.
STAGE 5
Prove
A result measured against the baseline, and an instrument you keep.
Report against the baseline: turnaround, share needing correction, and which clause types the assistant is still poor at. Expand only where the evidence supports it.
What you get
- Clause position set and fallbacks, written down
- First-pass review producing a redline plus rationale
- Escalation rules for deviations that must reach a lawyer
- Evaluation set of agreements with known-good answers
What it needs from you
- A sample of executed agreements and their redlines
- The current playbook, in whatever state it is in
- Access to the intake channel the paper arrives through
Where the human stays
Every redline is proposed, not applied. A lawyer accepts or edits before anything is returned to the counterparty, and deviations outside the agreed positions always route to a person.
How we would know it worked
- Turnaround on a first pass, against the baseline
- Share of outputs a reviewer changes
- Deviations caught that the previous process missed
Where it starts
Starts as a sprint
Prompt & Workflow Starter Kit
Ten tested prompts for the work your team actually repeats.
Sprint details →Grows into
AI Build — pilot to production
One use case, built and put into production, with evidence it works.
Program details →Start with one sprint
Two to three weeks, one approver, a deliverable you keep. Tell us the problem and we'll come back within one business day with a scope, a date and a fee.
Scope a sprint →