AI and automation for law firms
The money in a law firm leaks in three places: intake that answers too slowly, documents that get read manually for the fifth time, and deadlines tracked in someone's head. AI handles all three, but only inside an architecture that respects privilege, which rules out most consumer tools before you start.
Reviewed:
The short answer
Start with intake, not with document analysis. Intake is where a firm loses instructions it already won, the compliance question is easy, and the result shows up in the same month. Document work pays more per hour saved but takes longer to get past a partner.
| Bottleneck | What it costs today | What we build |
|---|---|---|
| Enquiries outside office hours | The caller phones the next firm on the list | A qualifying assistant on web and phone that captures the matter type and books the consultation |
| Conflict checks | A manual search before every new matter | An automated first-pass search across the matter database, flagged for a person to confirm |
| Reading long documents | Chargeable hours spent locating clauses | Retrieval over the firm's own files that returns the clause plus the document it came from |
| Deadline tracking | One diary, one person, one bad week | Dates extracted on filing and written to the calendar with escalating reminders |
| Client status chasing | Interruptions that break deep work | Automatic milestone updates from the matter record |
| Invoicing | Time recorded late and rounded down | Draft invoices assembled from the time entries for review |
Sources: GDPR Art. 28: processors and data processing agreements · GDPR Art. 32: security of processing · reviewed: Jun 27, 2026
Where the money leaks
The enquiry at 19:40
A prospective client with a real matter calls after hours, reaches voicemail, and calls the next firm before yours opens. An assistant that answers, establishes the matter type and jurisdiction, and books a slot converts that enquiry instead of donating it.
The fifth read of the same contract
A clause needs finding across a hundred pages. Retrieval returns the passage with a citation, and the lawyer reads that passage rather than the hundred pages. The lawyer still decides; the system just stops the hunting.
The limitation date nobody wrote down
Extracting dates at the point of filing and pushing them into the calendar with reminders removes the single most expensive failure mode in the practice. This one is worth building even if you build nothing else.
What we will not automate
Advice. Anything that goes to a client as legal opinion gets drafted with a human and signed off by a human. Systems that write advice unsupervised are a professional indemnity problem, not a productivity gain.
What we would build first
Every firm we have talked to opens with document analysis and closes with intake, because intake is where the loss is measurable. A partner can tell you roughly how many enquiries came in last month. Almost nobody can tell you how many of those never got a call back within the hour, and that number is where the fee income went.
The constraint that shapes the build is privilege. Client material cannot be sent to a service that trains on it or stores it outside an agreed region, which rules out the free tiers of most consumer assistants and quietly rules out a few enterprise ones too. What works is a model under a data processing agreement with EU residency, or a model running inside the firm's own infrastructure, plus retrieval over the firm's documents rather than any attempt to train on them. That architecture also happens to be the cheaper one, because nothing gets retrained when the law changes. The five deployments we see pay back fastest are written up in 5 AI automations every law firm needs, and the intake side is the same machinery described in AI chatbots and Voice AI.