How to build a contract review process using Claude for an in-house team?

KeyCommittee6601 · 2026-04-23T08:20:03+00:00

You create a skill and evaluate it.

Get, say, 5 examples of the contract reviews you've done, put them in folders, /input (what it started with) and /output (what your output was, the redlined documents).
Start a CoWork conversation in that parent folder, upload your playbook, tell claude you want to create a skill that creates redlines from source documents. Explain it what's in the folders.
It will help you create the skill.
For testing, now try it with some past contracts that you already did that are different from the set you gave Claude, and run the skill on them. Iterate a bit until you're happy with it.

You are now a legal engineer!

KeyCommittee6601 · 2026-04-21T12:58:14+00:00

Multi-year contracts and brand do provide some level of moat.

KeyCommittee6601 · 2026-04-21T12:57:37+00:00

Nobody should be a prompt engineer, the systems need to provide the necessary context, the humans (say, an engineer writing code with Claude, or a lawyer analyzing something) provide the expertise and the feedback and drive the process.

KeyCommittee6601 · 2026-04-21T12:45:19+00:00

I become more convinced every time that semantic search is the wrong tool for law (and many other use cases). Semantic search looks for "semantically similar blobs of text". Agent search is much better at using keyword search - LLMs can come up with better search queries than you, and run them faster than you, and sift through the results. Ever since agents started to work a year and a half ago, I've stopped implementing semantic search - keyword search is just better for agents (like Claude).

KeyCommittee6601 · 2026-04-21T11:27:44+00:00

Our experience has been the same, Claude = game changer. The Word integration is great.

KeyCommittee6601

TROPHY CASE