how it works
Bespoke AI, distilled from the way your firm already works.
Most lawyers have only used AI in a chat window. We install something better, configured around your documents, your voice, and your standards. Your data stays inside your firm.
quick look / claude reading a matter folder
illustration of the workflow. matter, files and names are invented.
Most lawyers use AI in a chat window. That is the problem.
A chat window is a blank slate every time you open it. You paste in a contract, you write a prompt, you get a generic answer. Nothing about it knows your firm. Nothing about it remembers what you decided last time. Nothing about it follows your standard positions on a tenant rep redline.
The model is capable. The setup is the problem. We fix the setup.
What we actually set up.
Claude Code
runs locally
The official Anthropic app, configured on your machine. Claude reads files where they already sit. Nothing uploads, nothing leaves the firm.
Scoped matter access
filesystem-mcp
Claude sees only the folders you point it at. Client matters, work product, templates. Everything else on the machine stays invisible to the model.
MCP connectors
email · calendar · document systems · servers
The wiring between Claude and the places your firm already works. Each connector is gated: you decide what it can reach, what it may do, and what needs your confirmation first. This is most of the work, and most of what firms get wrong on their own.
Matter structure
one shape, every matter
A consistent place for the facts of a case: parties, posture, key documents, what has happened and when. Claude knows where to look because every matter is laid out the same way.
Dates and deadlines
surfaced, never auto-filed
Dates pulled out of filings and correspondence and gathered in one place, with what they hang off. You confirm before anything reaches a calendar.
Firm memory
carried between matters
What your firm has learned about the bench, opposing counsel, mediators and repeat clients, written down where it can be used again. Year one is useful. Year three is hard to replace.
Skills library
~/.claude/skills/
Markdown files, one per document type or workflow, teaching Claude how your firm handles that work. You can read every line. You own every line.
Workflows and scripts
~/.claude/scripts/
The mechanical work: opening a tracked-changes redline, assembling a Bates-numbered exhibit binder, building a timeline from a folder of email and photographs.
Where everything lives, and what never leaves.
The system has three layers. Each one has a clear boundary. Knowing the boundaries is the whole trust model.
Skills
what it contains
Patterns extracted from your work. Standard positions, tone rules, structural preferences. Markdown files.
what it does not contain
Client names, case facts, dates, dollar amounts, anything specific to a matter.
where it lives
In a folder on your machine. Backed up to a private repository if you want.
Firm knowledge
what it contains
Templates, form documents, your firm's standard agreements, your client intake forms, your engagement letters.
what it does not contain
Live client matter content.
where it lives
In your existing firm document management system. Claude reads it locally.
Client knowledge
what it contains
Active matter files. Lease drafts, deposition transcripts, email threads, client photos, exhibits.
what it does not contain
Anything that should not be there. Same boundaries as your existing matter folders.
where it lives
Where it already lives. Claude reads it locally and never copies it anywhere else.
Client data never leaves the firm. Patterns become Skills. Skills become leverage.
What the first month looks like.
Discovery
- We sit down with your team, in person or remote
- We learn your practice: how matters run, what your clients need, how your corner of the industry actually works
- We find the tasks you repeat, and the ones that cost you the most time
Build
- Skills, connectors and workflows configured around what we found
- Wired into wherever your files already live
- You see the first working pieces on your own material
In practice
- You put it to work on live matters
- We work alongside you and sharpen whatever is not quite right
- Your team learns to run, edit and extend it
Handover
- Everything is yours: readable, portable, documented
- We agree what is worth building next
- Ongoing support begins, if you want it
and then further
Claude Code is not only for drafting.
The same setup that reads your matter folder can build things you would otherwise pay a vendor for. Interactive timelines a client can click through. Exhibit binders assembled and numbered. Dashboards over matters in flight. Images, video and everything else a case accumulates, organised and searchable.
- Interactive case timelines
- Bates-numbered exhibit binders
- Matter dashboards
- Image, video and document libraries
We teach your team to build these, not just receive them. That is what up-levels a practice.