Claude Code is an AI tool from Anthropic that writes, runs, and fixes software based on plain English instructions. For lawyers, that means the dashboards, document checkers, and letter generators your firm rents today can be built in-house in an afternoon, without a developer.
I’m not a programmer. I’ve never taken a computer science class, and if you asked me to explain what a database index is, I’d change the subject.
In the past year I built a live dashboard tracking sign-ups across my 10 law firms, a document review system that reads lemon law case files, a demand letter generator, and a set of intake scoring tools. Lines of code I personally wrote: zero.
The tool that made this possible is Claude Code, and I think it changes the economics of running a law firm more than anything else covered on this site.
What Claude Code actually is
Every AI tool you’ve used so far follows the same pattern: you ask, it answers, you copy the answer somewhere useful. Claude Code breaks that pattern. You give it a goal, and it does the work.
Tell it “build me a tool that takes a folder of repair orders and lists the repair dates in a table,” and it writes the software, runs it, hits an error, reads its own error message, fixes the problem, and runs it again until the table appears. You watch this happen in real time. It feels less like using a program and more like supervising a very fast junior developer who never gets discouraged.
It comes in two forms: a terminal app and a desktop app. The word “terminal” scares lawyers off, which is a shame, because the desktop app is a normal window where you type English sentences. Nobody needs coding knowledge to start. What you need is the thing lawyers already have: a precise description of what you want.
What I built with it
Concrete examples from my own firms, because vague claims about “AI transformation” help nobody.
A KPI dashboard. One web page showing live sign-up counts across all 10 firms, updated from our CRM. Before this, the numbers lived in five systems and a weekly spreadsheet someone had to assemble by hand. I described the layout I wanted, told Claude Code where the data lived, and had a working version the same day.
A document review system. Lemon law cases run on documents: repair orders, purchase contracts, registration, warranty records. The tool reads a case file, checks what’s present against what the case type requires, and flags what’s missing. My document collection team used to do this by eye. Now a human only looks when the tool raises a flag.
A demand letter generator. It pulls case facts into our letter format and produces a draft in our firm’s structure. An attorney still reads and signs every letter. The two hours of assembly are gone.
Intake scoring tools. They read intake notes and score case strength on the factors we care about, so my intake team prioritizes callbacks instead of working the list top to bottom. If intake is your bottleneck, AI intake for law firms covers the bigger picture.
None of these existed as products I could buy in the exact shape I needed. All of them exist now, and I own them outright.
The $2,000 rule
Here’s the rule I give lawyers in my communities: any software you’re paying under $2,000 a month for, that doesn’t quite fit your workflow, is a build candidate.
A business owner I know was quoted $10,000 for dynamic pricing software. He described what he needed to Claude Code and had a working version that afternoon. Not a prototype. The thing he actually uses.
Legal software carries the same markup. Much of what firms rent for $200 to $800 per seat per month is a form on top of a database with some logic in between, priced at what a law firm will tolerate rather than what it costs to make. When the vendor’s tool fits your workflow exactly, pay them, it’s worth it. When you’re contorting your process to fit their screens, that subscription is now optional.
What to build first
Don’t start with your grand vision. Start with one of these:
A case status dashboard. One page, every open matter, current stage, days since last activity. Ugly is fine. Useful beats pretty.
A client intake scorer. Feed it your intake notes format and your criteria for a good case. Get back a score and the reasoning.
A document checklist tool for your practice area. Give it the list of documents each case type needs, point it at a case folder, get back what’s missing. This is my standard recommendation for a first build because it’s finished in one sitting.
A settlement calculator. Encode the math you currently redo in a legal pad every time: your fee structure, costs, lien reductions, net to client.
Each of these is an afternoon project, and each one teaches you how to describe software to an AI, which is the actual skill.
What it costs
Claude Code is included in the same Claude Pro and Max plans that cover regular Claude, $20 to $200 a month. That’s the whole bill.
| Plan | Price | Who it fits |
|---|---|---|
| Claude Pro | $20/month | Your first builds and light daily use |
| Claude Max 5x | $100/month | Regular building, a few tools in production |
| Claude Max 20x | $200/month | Heavy daily use across a firm |
For comparison, a single seat of most legal practice software costs more than the $200 Max plan, and the Max plan builds you unlimited tools that you own. I pay for Max across my firms and it’s the least contested line item in my budget.
The honest caveats
You own the maintenance. When your CRM changes its export format, your dashboard breaks and nobody is coming to fix it except you and Claude Code. In practice the fix is usually one conversation, but it’s your conversation to have.
Start with internal tools. Dashboards, checklists, calculators. Nothing client-facing until you’ve lived with an internal tool for a few months and know how it fails.
Be careful with client data. Build and test on sample or redacted documents. Decide deliberately, later, what confidential material a tool touches, the same way you’d decide for a new hire.
Verify outputs. A generated demand letter gets read by an attorney before it goes anywhere. A missing-document flag gets checked before you email a client about it. The tool does the assembly; you keep the judgment.
How to start this week
Install Claude Code from claude.com/claude-code. The setup takes minutes.
Make a folder with 10 or 15 sample documents from your practice area. Non-confidential ones: blank forms, your templates, documents from closed matters with names redacted.
Then open Claude Code, point it at that folder, and type something like: “Build me a simple tool that checks this folder against a checklist of required documents for a [your case type] case and tells me what’s missing.”
Watch what it does. Then start talking to it. “Make the output a table.” “Add a column for the document date.” “Flag anything older than two years.” Every instruction is a sentence, and every sentence makes the tool more yours.
Once you’ve built one thing, connect Claude to your real systems with MCPs, starting with Clio if that’s your practice management platform. That’s when the tools stop working on sample folders and start working on your firm. Where this fits in the bigger picture is stage five of the roadmap, and most lawyers reach it faster than they expect.
The gap between lawyers who rent software and lawyers who own it is going to be one of the defining gaps of the next decade of law practice. Crossing it costs $20 and an afternoon.