1
Curious builder0 XP earned · 300 to level 2
0 daysFinish a lesson to begin
Badge collection0 of 6 unlocked
51 small wins to finish your pathNext question →
A law firm wants an AI contract review assistant. Design the solution and your 4-week engagement plan.
30-second answerSay your answer out loud first, then reveal.
Architecture

Key design choices
- Playbook as structured data: the firm's positions per clause type (e.g. "liability cap: ≥ 12 months' fees; fallback: 6 months with carve-outs"). The LLM compares against explicit criteria, which improves consistency and explainability.
- Citations to the exact clause text, and quotes for every issue.
- Missing-clause detection needs a checklist approach, since retrieval alone won't notice what's absent.
- Confidentiality: client documents stay in approved environments; strict access controls per matter; no training on client data.
- Integration: a Word add-in, because lawyers live in Word, plus DMS integration.
4-week plan
| Week | Activities | Deliverable |
|---|---|---|
| 1 | Discovery with partners and associates; pick 1 contract type (e.g. NDAs or MSAs); collect 50 contracts + playbook; security setup | Scope doc, eval set plan |
| 2 | Parsing + clause segmentation; playbook encoding; first classification prompts; SMEs label 30 contracts | Baseline accuracy |
| 3 | Iterate on errors; explanations and fallbacks; Word output; second labelling round | Accuracy report v2 |
| 4 | Pilot with 5 associates on live (non-urgent) matters; measure review time; demo to partners | Results + production plan |
Metrics: issue detection recall (missing issues is the costly error), precision (noise annoys lawyers), review time saved, associate satisfaction.
Related
Little by little, you're building something great.