Today
The driver wants to talk to a lawyer before he calls his insurance. He calls (718) 395-1818 at 11:14 PM. The call goes to whoever is on after-hours, or to voicemail. Notes get retyped Monday. By then he has already called two more firms.
Claude is the kind of AI you can use today. It reads the files your team already has, drafts in your voice, and summarizes long things fast. Below are four short stories of how it shows up in a normal week, plus one tool for every laptop and a note on custom software. Three minutes to read.
The AI in the news (Lemonade chatbots, big "AI lawyer" demos) is built for huge companies over years. That's not what this note is about.
What's useful for your firm is simpler. Claude (made by Anthropic) reads emails, files, and records, then drafts replies and summaries in your voice. Your associates and paralegals do less retyping. You buy it directly from Anthropic. Your firm has its own account, its own files, its own bills. No middleman SaaS sitting between you and the model.
Other firms like yours report 20-30% of each person's day back for real client work. Across the team that adds up fast.
AI helps in two places. Before someone signs: a Saturday-night call in Russian gets a Russian answer in 90 seconds. After they sign: faster drafting, faster records review, faster replies in any language. Lead-gen brings the calls in. AI helps you not lose them between intake and demand.
The driver wants to talk to a lawyer before he calls his insurance. He calls (718) 395-1818 at 11:14 PM. The call goes to whoever is on after-hours, or to voicemail. Notes get retyped Monday. By then he has already called two more firms.
The same call gets picked up live, in his language. A short greeting in your firm's voice: "Kari Law. Press 1 for English, 2 for Russian, 3 for Spanish, 4 for Georgian." The agent continues in the language he picks. It asks for the basics: when and where it happened, injuries, treatment so far, the other driver, the insurance. In 90 seconds he gets a text back in two languages: "Got it. We'll call you Monday at 9. If anything changes overnight or you go to the ER, just reply here." Same for web forms. By 9 AM Monday, your intake team has a clean queue, sorted, ready to assign.
The first hour after the accident is covered, in his language. The associate on weekend rotation no longer takes notes by hand at 11 PM. Setup is one phone number that routes to the agent after hours, the greeting recorded once, and a week of fine-tuning the questions and the tone.
An associate spends most of the afternoon on a soft-tissue auto demand. Generic legal-AI templates sound nothing like your firm, so they rewrite eighty percent of every paragraph. Then you read it, mark it up, send it back. The case sits another day before it ships.
An agent learns your firm's style from your past demands and from your edits. It reads the case file (intake summary, medical bills, ER and discharge notes, IME, adjuster emails) and writes a first draft in your voice. NY-PI specific. Real case facts woven in. Correct citations. Standard exhibits attached. The associate edits the opening, the injury narrative, and the close. Thirty minutes instead of half a day.
Demands ship the week the file matures, not three weeks later. Junior associates spend their time on the parts that build judgment, not on filling in templates. The agent keeps learning from your edits, so the first draft gets better every month.
A client texts your firm in Russian at 7 PM, asking about her case. The associate on the case is drafting a complaint and only speaks English. The bilingual paralegal who would normally answer in Russian has gone home. The reply either waits until morning or comes back in slow English. Same with Spanish and Georgian. Your multilingual service depends on who happens to be at their desk.
The text comes in to whoever is handling the case. Their screen shows three things at once: the original message, an English summary of what she's asking, and a draft reply in your firm's voice in Russian, ready to edit. They change one phrase, hit send. She gets a fluent Russian reply within five minutes. Same for Spanish, same for Georgian. The complaint they were drafting stays open the whole time.
Multilingual replies stop being a tax on your billable hours. Anyone on the team can hold a fluent conversation in any of your three languages, fast. Word-of-mouth in the Bukharian and Russian-speaking communities adds up: you become the firm that actually replies in the language they texted in.
A medical records bundle lands the week before a deposition. ER intake, hospital discharge, twelve weeks of PT notes, the MRI, the IME. Seventy or eighty pages. The paralegal does a first pass that takes most of an afternoon. The associate reads all of it. You review the prep notes. The same bundle gets read three times.
The paralegal drops the bundle into Claude on their laptop: "Summarize injuries, treatment timeline, gaps in care, anything the IME doctor downplayed, anything that hurts our case." Five bullets in 30 seconds. The paralegal checks the bullets against the records in 20 minutes. The associate then reads the actual records only at the pages the bullets flagged. The deep reading still happens, where it matters. The eighty-page page-flip doesn't.
Pre-depo prep takes a lot fewer total person-hours. Settlement-stage review goes faster. When an adjuster calls about a specific date in the records, whoever picks up has the answer right then, instead of "let me get back to you." No SaaS reseller in the middle: it's a direct Anthropic account, your records on Anthropic's runtime under their published terms, your bills.
Separate from the four agents above. The Claude Team plan from Anthropic (around $30 per seat per month, annual) gives every person on your team a desktop assistant they can interrupt anytime, plus a shared workspace and admin controls. Useful in a normal day:
Standalone. Doesn't depend on the four agents above. You can roll it out next week and let actual usage shape the bigger builds.
This is a different category from the four agents above. Not an AI sitting in someone's day, but a small piece of software made for the way your office runs.
What used to be a six-month, six-figure project is now a three-to-four-week build. Claude does the heavy coding next to me. Your firm owns the code and the data. An agile firm is the right size for this: big enough that the build pays back fast, small enough to skip a six-month rollout.
Three example seeds, just to make the category concrete:
The real build is whichever piece of your work the closest off-the-shelf tool gets to 80% of and stops.
Claude Team on every laptop (Section 06), plus the records summarization piece (Story four). Both run on machines and files your team already has. Neither changes anything customer-facing without your approval. Neither depends on the bigger build. The safest starting line, and a good way to see what the team uses in practice.
If something here resonates, or it's already covered, or it's just not your pain, I'd love to hear. One-word answers are fine: resonates / already doing / not my pain / didn't get it.