Second Brain

Article

Conversation

The Claude-Native Law Firm

A few months ago, the night before a client’s acquisition was set to close, the buyer’s counsel sent a letter demanding that several key deal terms be restructured. New escrow conditions. Expanded indemnification carve-outs. A revised set of closing deliverables. The implicit threat: accept these changes or we walk. It was 7 PM.

I uploaded the purchase agreement, the disclosure schedules, and the demand letter to Claude. Within minutes, Claude mapped every proposed change against the existing deal terms and found what the buyer’s lawyers apparently hadn’t noticed: two of their proposed carve-outs directly contradicted representations they had already confirmed in the disclosure schedules, and a third would have created an internal conflict with the fundamental reps section that would have actually weakened the buyer’s own post-closing protections. Their aggressive last-minute play had holes in it.

As the negotiation continued through the evening with emails going back and forth, I fed each new communication to Claude. It tracked how every proposed concession interacted with provisions across the agreement, flagged where accepting one change would create exposure in another section, and helped me build a response that conceded the points worth conceding and held firm on the ones that mattered. By 11 PM we had a clean set of counter-positions, each grounded in specific cross-references to the buyer’s own language. The deal closed the next morning on terms my client was happy with.

A team of three associates at a mid-size firm would have needed until morning to produce that analysis. I had the core of it in under two hours.

I run a two-person boutique law firm. We handle startup formation, venture capital transactions, and regulatory work. We compete against firms with hundreds and sometimes thousands of lawyers. We are not supposed to be able to do this. But the past year has made something clear: a small firm built around AI doesn’t just keep up with larger competitors. It moves faster, produces more thorough work product, and operates at a cost structure that would have been impossible 18 months ago.

The tool I’ve built my practice around is Claude, made by Anthropic. This piece is an explanation of how I actually use it, every day, for real legal work. Not the theory. The workflow.

The market is full of specialized legal AI products. Harvey, Spellbook, CoCounsel, Luminance. They all share a thesis: lawyers need AI built specifically for legal work. I’ve evaluated most of them. For a small firm practitioner, a well-configured general-purpose AI is better. It’s not close.

The specialized products are wrappers built on top of the same foundation models that power the general-purpose tools. Their marketing pitch sounds compelling: we’ll customize the AI to your firm’s playbook, train it on your templates, build workflows around your brief bank or clause library. Some of them do this reasonably well. But the pitch contains a fundamental misunderstanding of where the value actually lives.

A template library is not a competitive advantage. Every competent firm in your practice area has roughly the same templates. The NDA, the stock purchase agreement, the employment offer letter. These are commodity inputs. The thing that differentiates a great lawyer from a mediocre one was never the template. It was what the lawyer did with the template: how they spotted the issue the other side buried in Section 14(c), how they knew which indemnification fight was worth having and which to concede, how they structured the advice email so the client actually understood the risk. That is judgment. And judgment doesn’t live at the firm level. It lives at the level of the individual professional.

When legal AI companies talk about customizing AI to a firm’s playbook, they are solving a problem that barely matters and ignoring the one that does. The real leverage comes not from which template the AI starts with, but from the instructions that tell it how to think about the work: what to look for, what to flag, how to weigh competing considerations, what format to deliver the output in, what tone to use with the client. Those instructions encode an individual lawyer’s judgment, not a firm’s template library. And that is exactly what Claude’s skill system is built to do.

I’ve created custom instruction files, called “skills,” that encode my analytical frameworks, my preferred formats, my voice, and my judgment about how specific types of legal work should be done. When I upload a contract for review, Claude doesn’t apply a generic framework. It doesn’t even apply my firm’s framework. It applies my framework, the one I’ve developed over a decade of practice, automatically. The difference between a firm playbook and an individual lawyer’s encoded judgment is the difference between giving someone a recipe and teaching them how to cook.

There’s a more fundamental issue, and it’s the one that will matter most to anyone who has spent their career inside Microsoft Word. Claude is a frontier AI model that has been heavily optimized for writing code. That may sound irrelevant to legal practice until you realize what it means: Claude can write code, on the fly, to directly manipulate the applications lawyers already use.

Think about what this means concretely. Every lawyer reading this has lost hours to Word formatting. Paragraph numbering that breaks when you paste from another document. Styles that refuse to cooperate. Track changes that corrupt across versions. Cross-references that go stale. Bluebook citation formatting that requires manual attention on every single period and comma. These are not legal problems. They are software problems. And Claude solves software problems by writing software. When I tell Claude to apply tracked changes to a contract, it doesn’t use a plugin or a macro. It opens the .docx file at the XML level and writes the exact markup that Microsoft Word expects, attributed to my name, preserving every formatting detail. When I tell it to standardize the citation format in a brief, it writes code to parse and reformat every citation in seconds. The result is indistinguishable from expert manual work, delivered in a fraction of the time.

This is the capability gap that no specialized legal AI product can match. They give you a chatbot that talks about documents. Claude is a system that can reach inside those documents and change them. It is the difference between an associate who can tell you what’s wrong with a contract and an associate who can also fix it, format it, produce the redline, and draft the cover email, all without you opening a single application. General-purpose AI advances faster than any vertical product can keep up with. When you’re on the frontier model, every new capability ships to you on day one. When you’re on a wrapper, you’re waiting for someone else’s engineering team to decide what to build next.

I’m describing my own practice here, which is transactional. But nothing about the architecture is practice-specific. A litigator would build skills for deposition preparation, motion drafting, case law synthesis, and discovery review. A tax lawyer would build skills for entity structuring, opinion letter frameworks, and regulatory monitoring. A family lawyer would build skills for asset tracing and custody analysis. The approach is the same: take a powerful general model, teach it your practice, and let it compound your judgment. The content is yours.

Claude’s desktop app has three modes. Learning when to use each one was the single most important step in making this work.

Chat is the conversational interface. I talk to Claude the way I’d talk to a fast, knowledgeable associate sitting across the table. This is where I go for analyzing a legal issue, brainstorming negotiation strategy, getting a first take on a contract provision, or drafting something from scratch. I stay in control of every step. Most lawyers who have used ChatGPT or similar tools have only experienced this mode.

Cowork is the autonomous mode, and it’s the one that changes everything. I point Claude at a folder on my computer, give it a task, and it goes and does it. It reads files, creates new ones, edits existing documents, and makes its own decisions about how to get from A to B. When I have a 40-page agreement that needs a full redline, or a stack of closing documents that need to be generated from a term sheet, I hand it to Cowork and let it work. This is the mode most lawyers haven’t tried. It’s the one that will change their practice the most.

Code is the development mode. Full terminal access. Most lawyers don’t need it daily. But I have a condition that makes it hard to read long documents, so I used Code to build a command-line tool that converts legal documents into spoken audio. It handles the entire pipeline: parsing Word docs and PDFs, converting legal formatting like “Section 4.2(b)(iii)” into natural speech, expanding abbreviations, chunking the text, sending it to an AI voice API, and assembling the final audio file. I listen to contracts on my commute now. Claude built the whole thing.

This is where the leverage becomes something I wouldn’t have believed two years ago.

Anthropic published a guide on building custom “skills” for Claude: structured instruction files that teach it how to behave in a specific context. Not a prompt you type every time. A persistent set of instructions that fires automatically when the situation calls for it. Instead of reading the guide cover to cover, I uploaded it to Claude and asked a better question: based on the hundreds of conversations we’ve had together, spanning contract drafting, client emails, document editing, legal research, and policy writing, what are the skills that would have the greatest impact on my practice?