Law Systems
Claude
The owner's walkthrough

Claude for law firm owners.Every feature worth using in 2026.

Every Claude for lawyers video is for the person doing the drafting. This one is for the person who owns the firm. Each feature on screen, and the exact point where Claude stops.

Scroll
Part 01 Setup

Set it up like a firm.

01 Seats and projects

One project per matter type.

  • Team or Enterprise seat. No training on your chats, admin sees usage.
  • One Project per matter type: intake, records, billing.
  • The instructions file is the trick. Four of mine on screen.
Claude
Projects
Personal injury intake12 chats
Medical records31 chats
Client updates58 chats
Billing review9 chats
Project instructions
02 Claude for Legal

Twelve plugins. Two run matters.

  • Free, open source, a minute to install.
  • Ten draft for one practice area. The in-house four: skip.
  • Install Litigation Legal. Legal Clinic is a maybe.
  • None write into Clio or Filevine yet.
0practice-area plugins
0named workflow agents
0connectors
Commercial Legalvendor agreements, NDAsif your practice Corporate LegalM&A diligence, closingsif your practice Employment Legalhire and termination reviewif your practice Privacy LegalDPAs, DSARs, PIAsin-house, skip Product Legallaunch and claims reviewin-house, skip Regulatory Legalreg feed, policy diffsin-house, skip AI Governance LegalAI use-case triagein-house, skip IP Legalclearance, takedownsif your practice Litigation Legalintake, status, holds, deadlinesinstall Law Studentbriefing, outlines, bar prepskip Legal Clinicintake, deadlines (built for clinics)maybe Legal Builder Hubcommunity skills, trust checkthe store
InstallIf it is your practiceSkipAnthropic, May 12, 2026
03 Connectors

It reads your case system. It does not run it.

  • Connect Clio or Filevine. Ask the owner questions.
  • Reads matters, documents, tasks, calendar, billing. Only when asked.
  • Write-back is limited. Check on screen what actually lands.
NetDocuments
Westlaw
Readsmatters · contacts · documents · tasks · calendar · billing
Writes backlimited, verify on screen
Anthropic · vendor listings
Part 02 The work

The work, by hand.

04 Records

300 pages of records. A chronology with page cites.

  • Drop the PDF in. Dated chronology, page cites.
  • 100 pages per read, so split bigger files first.
  • First pass on every new file. A paralegal spot-checks three cites.
1 to 100
101 to 200
201 to 300
300 pagessplit into three reads of 100
↓
Mar 14, 2024ER visit, Memorial Hermannp. 12
Mar 21, 2024MRI, lumbar spinep. 48
Apr 2, 2024Orthopedic consultp. 131
May 9, 2024Physical therapy dischargep. 262
100 pages per PDF readsupport.claude.com
05 Call to case note

Paste the transcript. Get the note and two tasks.

  • Paste the transcript. Ask for the note and the follow-ups.
  • The one thing we automate end to end. Here it is by hand.
Call transcript
Intake call · 14 min
→
Case note

Maria Alvarez, rear-end collision

Treating with Dr. Patel, two visits so far. Adjuster has the claim number. Client wants updates by text.

Request records from Dr. PatelFri, Jun 6
Call adjuster on PIP statusMon, Jun 9
06 Morning brief

What is overdue across these 20 matters?

  • Export from Filevine, drop it in, ask. It works once.
  • Run it daily in a chat thread and by week three it forgets.
  • One-off audits: yes. The daily check needs a job that remembers yesterday.
#morning-briefDay 1
FV
Filevine exportDay 1 · 20 matters

overdue_matters_0602.csv

Claude

3 overdue: Alvarez (records request, 6 days), Chen (demand letter, 2 days), Ortiz (medical bills, 9 days).

FV
Filevine exportDay 7

overdue_matters_0609.csv

Claude

2 overdue. Alvarez cleared. Chen demand letter still out, Ortiz bills still open.

FV
Filevine exportDay 14

overdue_matters_0616.csv

Claude

Looks on track. Chen handled.

FV
Filevine exportDay 21

overdue_matters_0623.csv

Claude

Nothing overdue.

Done?Or just not updated?
Part 03 The stop line

Where Claude stops.

07 Where Claude stops

Claude reads and writes text. Code does the rest.

  • No memory of state. No schedule. No approval gate.
  • It writes into a chat, not the case system.
  • Code does that part.
Claude
Reads the file
Writes the note
Drafts the update
Answers the question
</>Code
Keeps state
Runs on a schedule
Waits for approval
Writes back
08 The rules line

ABA Formal Opinion 512, in three words.

  • The bar’s first opinion on generative AI, July 2024.
  • Know what the tool does, where client data goes, get informed consent.
  • Verify citations. Bill real time. Supervise staff.
  • Open the data settings. Read them out loud.
CompetenceKnow what the tool does and does not do. Check every citation before it leaves the firm.
ConfidentialityKnow where client data goes. Training off, retention set, read the data settings.
Informed consentBefore client information goes into a tool that learns from it, ask the client first.
Also in the opinion: supervise how staff use it · bill the time actually spent · tell the client when AI use matters
Data settingsread it on screen
Part 04 The scorecard

Task by task. Where Claude is strong, where it stops.

Six tasks a firm runsScore = how much of the task Claude does on its own, out of 5. Our read, November 2026
01
IntakeReads the call, cannot make one.
0/5
Claude does

Writes the intake note from a transcript or web form. Qualifies against your script when you give it the script.

Claude stops

Cannot answer the phone, call back, text, or remember yesterday's lead. No schedule.

What gets built

Instant callback, a text and email cadence, the unsigned-retainer chaser.

02
Case workStrong on one file, blind to the caseload.
0/5
Claude does

Chronology from records, 100 pages per read. Case note plus tasks from a call. A summary of any matter you hand it.

Claude stops

Does not check every open file every morning. No memory between sessions. Cannot tell done from not updated. Write-back to Clio or Filevine is limited.

What gets built

The morning check per person, and verified write-back.

03
AdminDrafts well, moves data badly.
0/5
Claude does

Fills your own templates from a questionnaire. Drafts letters and forms.

Claude stops

Retyping between HubSpot and Filevine still needs a person or code. Nothing runs on its own.

What gets built

One database with two-way sync. A one-time migration.

04
Client updatesWrites them, never sends them.
0/5
Claude does

A plain-words update from one status line.

Claude stops

Nothing goes out on its own. No reminders, no document chase, no record of what was sent.

What gets built

Stage updates written once and sent on every change. The document chase, with a call task at the end.

05
BillingReads the ledger, cannot close the gap.
0/5
Claude does

Reads Clio billing through the connector. Explains an invoice. Drafts a reminder.

Claude stops

No weekly reconciliation of hours worked vs invoiced vs paid. No collections cadence. No approval gate on anything touching money.

What gets built

Billing reconciliation every week. Collections chasing.

06
Research and draftingBest in class, still needs the lawyer.
0/5
Claude does

Research, first drafts, redlines, the Claude for Legal plugins.

Claude stops

Leading legal research tools hallucinated 17% to 33% of the time, so every line gets checked. ABA Formal Opinion 512 applies.

Stanford RegLab, 2024ABA Formal Opinion 512
What gets built

Nothing. This stays with the lawyer.

Part 05 Set it up

Eight steps. Thirty minutes.

1
Get a Team or Enterprise seat, not a personal plan.5 minutes. Commercial plans do not train on your chats by default; the admin sees usage.
2
Create one Project per matter type: intake, records, client updates, billing review.5 minutes. Different work, different rules.
3
Paste the instructions file into every project. The four lines on screen are the minimum.10 minutes. Add a line every time something goes wrong.
4
Install Litigation Legal and the one drafting plugin for your practice. Skip the in-house ones.Free. 10 to 20 minutes of setup interview per plugin, done once.
5
Connect Clio or Filevine. Open one matter and ask what is stuck on it.5 minutes. It reads the case system, it does not run it.
6
Open the data settings. Training off, retention set, read them out loud.2 minutes. ABA Formal Opinion 512: competence, confidentiality, informed consent.
7
Run the three jobs by hand once: records to chronology, call to case note, Filevine export to overdue list.One file each. This is what Claude does well on its own.
8
</>
Write down what has to run on a schedule, remember state, wait for approval, or write back into the case system.That list is what Claude cannot do alone. Code does that part.
Done for you

Want us to install
the part where Claude stops?

Claude reads and writes the text. We build the part that keeps state, runs on a schedule, waits for your approval and writes back into Clio or Filevine.

See how it works →