Playbooks
Build Your First Legal AI Agent in an Afternoon (No Code Required)
Build a legal AI agent in one afternoon without code: pick NDA triage, write a one-page playbook, set up a Claude Project, add verification and test on ten documents.
On this page
You can build a working legal AI agent in one afternoon with nothing more than a Claude Project or a custom GPT: pick one bounded task such as NDA triage, write a one-page playbook, paste a set of instructions, add a verification step and test it on ten real documents. The afternoon below does exactly that, with the instruction text and the scoring sheet included.
What you are building, in honest terms
Anthropic's engineering team drew the line in December 2024 and it still holds: "Workflows are systems where LLMs and tools are orchestrated through predefined code paths. Agents ... are systems where LLMs dynamically direct their own processes and tool usage" (Anthropic, 19 Dec 2024). By that definition, what you finish this afternoon is a workflow with one decision point: the model reads an NDA, applies your playbook, rates the document green, yellow or red, and hands you a draft. It does not send emails or browse. That is the right place to start. Gartner's rule from June 2025 says why: use agents "when decisions are needed, automation for routine workflows and assistants for simple retrieval" (Gartner, 25 Jun 2025).
| Stage | What it does | What you need | This afternoon? |
|---|---|---|---|
| Assistant | Answers a question about a document you paste | A chat window | You already have it |
| Bounded agent (this page) | Reads any NDA, applies your playbook, rates it, explains the rating, drafts the reply | A Claude Project or custom GPT, a one-page playbook, ten test documents | Yes |
| Wired agent | Triggers itself from an inbox or folder, writes results into a tracker, pauses for approval | n8n, Zapier or Make plus everything above | Optional, a second afternoon |
Vendors now call almost every feature an agent, so the vocabulary matters; the guide to what AI agents are covers the anatomy. What follows is the practical version, with the clock running.
13:00 — Pick a task that can fail safely
Most projects that die at this stage were chosen for impressiveness rather than testability. Use five filters:
- Bounded. One document type, one jurisdiction, one question. "Review our contracts" fails; "rate inbound NDAs against our playbook" passes.
- Frequent. You see the task weekly, so ten test documents are lying around and the time saved is real.
- Gradable in minutes. An associate can mark the output right or wrong in five minutes without redoing the job.
- Cheap to get wrong. A bad answer costs a correction before anything leaves the building, not a filing.
- Already written down. You have positions, even if they currently live in a partner's head.
NDA triage passes all five. Legal research fails the third and fourth: its failure mode is a plausible citation that does not exist, and Damien Charlotin's database counted 2,041 court decisions involving hallucinated material by 14 September 2026, 811 of them involving lawyers. A wrong NDA rating is visible on reading; a fake case is visible only after a KeyCite.
The reason to insist on gradability comes from Harvey's Legal Agent Benchmark. In Harvey's initial run on 26 May 2026 the best model, Claude Opus 4.7, passed every rubric criterion on only 7.1% of long-horizon legal tasks, at roughly $50.90 and 22 minutes per task (Harvey, May 2026); the aggregator leaderboard on 18 September 2026 puts Claude Fable 5 at 13.3%, while criterion-level pass rates sit around 83–88%. An agent will usually get most of a task right and occasionally miss one thing, and the one thing can be governing law. Your task has to be one where "mostly right, then checked" is still worth having. The NDA review at scale workflow shows the checked version across a hundred documents.
13:30 — Write the one-page playbook
The playbook is the one part no vendor can write for you. Keep it to a page: ten to twelve rows, each with a position, a fallback and an escalation trigger. Write positions as positive statements ("term of confidentiality: three years from disclosure") rather than prohibitions; guides on legal prompting consistently find that positive examples outperform "don't" lists (LegalFly, 17 Sep 2026). The table below is a starting point for an NDA received by a software company; change every row to your own positions before use.
| Playbook point | Our position | Acceptable fallback | Escalate to a lawyer if |
|---|---|---|---|
| Direction | Mutual | One-way in our favour | One-way against us |
| Governing law and courts | England and Wales, English courts | Any EU member state, or New York | Any other jurisdiction, or arbitration |
| Definition of confidential information | Marked or identified as confidential within 30 days | All non-public information disclosed for the purpose | Includes information already known or independently developed |
| Term of confidentiality | 3 years from disclosure | 5 years; trade secrets indefinite | Indefinite for everything |
| Residuals | No residuals clause | Limited to unaided memory, no licence to IP | Residuals clause grants a licence or excludes trade secrets |
| Non-solicitation | None | 6 months, employees met under the NDA only | Longer than 6 months, or covers customers |
| Return or destruction | Return or destroy on request; one archival copy allowed | Certify destruction within 30 days | Officer's certificate required, or no archival copy |
| Remedies | Injunctive relief available to both parties | Injunctive relief for discloser only | Liquidated damages or an indemnity |
Every row needs an escalation trigger, because the trigger is what turns a classifier into something you can trust near the inbox: the agent's job on a RED document is to stop and tell you, not to negotiate. The RED, YELLOW and GREEN vocabulary is the one Anthropic's /commercial-legal:review skill uses in the open-source Claude for Legal repository, so a playbook in this shape ports to that plugin later. And keep it short: firms that struggle with retrieval usually find the problem is a fragmented knowledge base rather than the model, producing "plausible but partial answers" (Inside Practice, Jan 2026). One page the model reads in full beats forty it samples. The contract playbook glossary entry and the playbook-driven contract review playbook go deeper on positions and fallbacks.
14:30 — Set up the Project and paste the instructions
Pick the surface first, because the surface decides the data terms. As of September 2026, Claude Team ($25 per standard seat, five-seat minimum), Enterprise and the API are never used for training; consumer Free, Pro and Max accounts must opt out under Settings > Privacy, or chats can be retained for five years. ChatGPT Business ($25 per seat) and Enterprise do not train by default; Free, Plus and Pro accounts train unless you switch off "Improve the model for everyone" under Data Controls (OpenAI data controls FAQ). The confidentiality checklist covers every vendor. For the afternoon itself, follow the rule Clifford Chance senior associate Jamie Tso set for his own prototypes: never upload client data, use synthetic documents (Tso, 6 Jan 2026).
Then:
- Create a Claude Project called "NDA triage v1", or a custom GPT with the same name; the custom GPT walkthrough covers the ChatGPT side.
- Upload the playbook as a file named
nda-playbook-v1.md, so positions can change later without touching the instructions. - Paste the instruction text below into the Project instructions.
- Choose the model. On Claude Team or Max that is Opus 5, whose first-turn NDA redlines Anthropic claims are "nearly double" those of Opus 4.8 (a vendor claim, July 2026). Sonnet 5, the default on Pro, is adequate for triage.
ROLE
You are a commercial contracts associate at [Firm]. You review non-disclosure
agreements received from counterparties on behalf of [Client], a [B2B software
company incorporated in England and Wales]. You apply the attached NDA Playbook
(nda-playbook-v1.md) and nothing else.
SOURCES
Use only (a) the NDA uploaded in this conversation and (b) the attached playbook.
Do not rely on general knowledge of "market" terms. If the playbook is silent on
a point, say so.
TASK
For each NDA uploaded:
1. Identify the parties, the direction (mutual or one-way), the governing law
and the term.
2. Work through every row of the playbook in order. For each row, quote the
clause in the NDA that deals with the point (verbatim, with clause number),
then rate it GREEN (matches our position), YELLOW (within the fallback) or
RED (outside the fallback, or an escalation trigger is met).
3. Give the document one overall rating: GREEN if every row is GREEN; YELLOW if
any row is YELLOW and none is RED; RED if any row is RED.
4. For GREEN and YELLOW documents, draft a short reply to the counterparty
proposing the fallback wording where needed. For RED documents, draft an
internal note to the supervising lawyer instead, listing the escalation
triggers met.
CONSTRAINTS
- Quote only text that appears in the uploaded NDA. If you cannot find a clause
on a playbook point, write "GAP: no clause found" in the quote column and rate
the row YELLOW.
- Never invent clause numbers, defined terms or party names.
- Do not cite case law or statutes. If a legal proposition needs authority,
write [verify] after it.
- A row is GREEN only if you have quoted the clause that satisfies it. Nothing is
GREEN by default.
- Do not send, file or store anything. Every output is a draft for review by a
qualified lawyer.
- Maximum 700 words for the table and 150 words for the reply or note.
OUTPUT FORMAT
1. Header line: Counterparty | Direction | Governing law | Term | OVERALL RATING
2. Table with columns: Playbook point | Clause quoted (verbatim, with number) |
Rating | Why (one sentence) | Proposed wording (YELLOW rows only)
3. "Escalation triggers met:" followed by a list, or "None".
4. The draft reply or internal note.
5. One line, "Things a lawyer should check before sending:", with up to three
items.
Two design decisions deserve a word. The [verify] tag is borrowed from Anthropic's legal plugins, which tag any citation not checked against a connected research tool the same way. The "GAP" rule exists because models mark things green by default when they cannot find a clause; forcing a written gap turns silence into a yellow flag. Projects hold static uploaded context in one workspace; if the team later wants the same behaviour to fire whenever anyone mentions an NDA, the instructions move into a Claude Skill, a folder with a SKILL.md file that works across Claude.ai, Claude Code and the API (Layer 3 Labs, updated 7 Sep 2026). The Claude Projects setup guide covers the mechanics.
15:15 — Verify, then run ten documents
Assemble ten redacted NDAs before testing: four you would rate green, three yellow, three red, and make one a trap, such as a residuals clause buried under a heading called "Exceptions" or a governing-law change hidden in the notices clause. Include one scanned PDF; Claude reads scans by vision and practitioners report it is more likely to say "illegible" than to invent a number, but for real use run a proper OCR pass first (CounselPro, 2026). Rate all ten yourself before the agent sees them and write the ratings down; the test compares against a fixed answer, not against how persuasive the table looks.
| Criterion | Pass condition | Threshold across 10 documents |
|---|---|---|
| Overall rating | Matches your own rating | 10 of 10 |
| Quotations | Every quoted passage appears verbatim in the NDA | Zero fabrications |
| Escalation triggers | Every trigger present in the document was flagged | 100% |
| Coverage | Nothing you found is missing from the table | At most one miss in total |
| Trap document | The hidden clause was found and rated RED | Must pass |
| GAP handling | Silent points marked GAP, not GREEN | Must pass |
| Draft reply or note | Usable with under five minutes of editing | 8 of 10 |
| Time | Under three minutes per document including your read | Average |
Score the whole sheet per document, not the average across criteria. Harvey's benchmark makes the case: criterion-level pass rates in the eighties coexisted with an all-criteria pass rate in single digits, and one practitioner's analysis argued the all-pass figure "should probably be considered marginal at best" as a predictor of real performance (r/legaltech, 2026). Both readings agree on the practical point: a document that is right on nine rows and wrong on governing law is a wrong document. Harvey also found that verify-and-revise behaviour added 1.5 points and drafting without review cost 1.2, which is why the instruction text ends with the "things a lawyer should check" line.
Decision rule: ten of ten on rating with zero fabricated quotations means the agent goes into use with every output reviewed. Eight or nine means the playbook wording is ambiguous somewhere; fix the row, not the prompt, and rerun. Below eight means the task is not as bounded as it looked. Keep the ten documents and the sheet as the regression test for every model change; models changed three times over the summer of 2026, with Opus 5 on 24 July, Fable 5.1 on 1 September and GPT-6 Astra on 4 September.
16:30 — Optional: wire it so it runs without you
Everything so far is a Project you open by hand. The second afternoon connects it to a trigger, which is where the word "agent" starts to earn its keep. In n8n, Make or Zapier the pattern is four nodes: a trigger (an inbox rule or a watched folder), a call to the model with the same instructions, a step that writes the header line into a tracker, and an approval node that halts the flow until a named lawyer clicks. The n8n for law firms guide covers setup.
Small firms supply the best argument for the second afternoon. A three-lawyer German employment and tenancy firm runs self-hosted n8n with a local model on a German server for EUR 20–30 a month: mail sorting fell from two hours a day to forty minutes, and the firm reclaimed six to seven hours a week with zero deadline-relevant items missed over six months (Lyron AI case study, spring 2026). It needed a § 43e BRAO contract with the host and an Art. 28 GDPR processing agreement. A Zapier and DocuSign intake stack described in April 2026 costs about $210 a month and cut document assembly from 45–60 minutes to 8–12 (Automation Atlas).
Four rules for the wired version, each learned the hard way by someone else in 2026:
- The gate lives outside the prompt. Zenity's PleaseFix research, presented at Black Hat on 5 August 2026, hijacked five browser agents through emails and calendar invites and concluded: "The fix isn't to keep asking the AI to behave. It's to put hard limits around the agent that the agent cannot override" (Dark Reading). An approval node in n8n is a hard limit; a sentence in the instructions is a request.
- No write or delete access to matter folders. In February 2026 a venture capitalist let Claude Cowork "organise" a desktop, approved the deletion of temporary files, and lost fifteen years of family photos to an
rm -rf(Futurism, Feb 2026). Read access to an intake folder, write access to a tracker, nothing else. - Copy the vendors' confirmation pattern. Harvey's Agent Builder agents "flag moments requiring user confirmation before proceeding"; Lexis's Legal Intelligence Engine "presents an executable plan for user approval" before it runs. Your RED route should behave the same way.
- Own the files. Relay.app closed to paying customers on 14 September 2026, and OpenAI's Agent Builder shuts on 30 November 2026. Keep the playbook and instructions as plain text you can paste into whatever survives.
The agent security guide covers prompt injection and the OWASP agentic top ten in more depth.
What to do this week
- Monday: choose the task with the five filters, and pull ten closed-matter documents for redaction.
- Tuesday: write the one-page playbook and have the partner who owns the positions sign off on the escalation column.
- Wednesday afternoon: build, paste, test, score.
- Thursday: show the scoring sheet, not the agent, to the sceptic in the room. Ten rows of numbers persuade better than a demo.
- Friday: decide whether it becomes a six-week pilot with a second user, or whether the playbook needs another draft.
Module 4 of the AI Lab for Lawyers course builds this agent live in the browser and then wires it into n8n, Make and Zapier, step by step. If you would rather start from a pre-built version, Anthropic's Claude for Legal plugins ship a commercial-legal review skill in the same RED, YELLOW and GREEN shape, after a ten-to-twenty-minute cold-start interview that writes your practice profile. Either way, the playbook and the ten test documents are yours, and they are the part that matters.
Frequently asked questions
Do I need to know how to code to build a legal AI agent?
No. The version described here uses a Claude Project or a custom GPT, a one-page playbook written in plain English and an instruction text you paste in. Wiring the agent to an inbox with n8n, Make or Zapier is also drag-and-drop. Coding becomes relevant only when you want custom integrations or a self-hosted model, and even then most lawyers now prototype with a coding agent rather than writing code.
Is a Claude Project or custom GPT really an AI agent?
By Anthropic's definition it is a workflow with one decision point rather than a fully autonomous agent, because the steps are fixed and the model only decides the rating and the draft. That is deliberate. It becomes agent-like when you connect a trigger, a tracker and an approval gate in an automation tool. Starting with the bounded version is how you find out whether the playbook works before anything runs unattended.
Can I test the agent on real client NDAs?
Only on a tier that does not train on your data and only if your engagement terms and professional rules allow it. Claude Team, Enterprise and API usage are not used for training, nor are ChatGPT Business and Enterprise; consumer tiers require an opt-out. For the first afternoon the simpler answer is to redact ten NDAs from closed matters or use synthetic documents, which removes the question entirely.
How much does it cost to build and run a legal AI agent?
The afternoon version costs a subscription you probably already have: Claude Pro at $20 a month or Team at $25 per seat with a five-seat minimum, or ChatGPT Business at $25 per seat, all as of September 2026. A wired version adds an automation tool; one three-lawyer German firm runs self-hosted n8n with a local model for EUR 20 to 30 a month, and a Zapier and DocuSign intake stack has been costed at about $210 a month.
Put this into practice
AI Lab for Lawyers: a live, hands-on course for practising lawyers
4 live sessions (8 hours), recordings included, taught by Dr. Niklas Schmidt of Wolf Theiss. Rated 4.7/5 from 381 ratings; alumni from Norton Rose Fulbright, Paul Hastings, Pillsbury and Taylor Wessing.
Related reading
Use Cases
NDA Review at Scale with AI Agents: A Complete Workflow
AI NDA review at scale works when an agent applies a ten-position playbook, routes exceptions to a named lawyer and logs every concession. Prompt and metrics.
12 min read
Playbooks
Set Up Claude Projects for a Matter: Instructions, Files and Memory
Set up a Claude Project for a legal matter in 30 minutes: sample instruction text, which files to upload, Skills, memory, Team sharing and three prompt flows.
10 min read
Tools
n8n for Law Firms: Building Legal Automations Without Code
n8n is a self-hostable workflow builder with AI nodes. A German firm runs intake and deadlines on it for €20–30 a month; three law-firm workflows, node by node.
9 min read
Guides
What Are AI Agents? A Practical Guide for Lawyers
AI agents for lawyers explained in plain terms: a model plus tools, a loop and a goal. How legal agents review NDAs, where they fail and what to expect in 2026.
10 min read
Playbooks
Automate Contract Review with a Playbook: Positions, Fallbacks and Escalations
A contract review playbook an AI agent can apply: ten sample rows, encoding for Claude, Spellbook and Word's Legal Agent, plus a 20-contract calibration method.
12 min read
Guides
Agent Security for Lawyers: Prompt Injection, Data Leaks and Guardrails
AI agent security for law firms: prompt injection via hostile documents, the Grok Build and Cowork incidents, and the allowlists and gates that contain them.
11 min read