Three quarters of small firms use AI. About a third say it has moved revenue. The gap is not adoption — it is depth. This book shows you how to find the four places a small practice leaks time and money, automate the right one first, keep verification and professional obligations in the design, and decide honestly what happens to the money when the work gets faster.
93 pages, five parts, five appendices — including an AI policy skeleton, a citation verification checklist, and the four-leaks audit worksheet.
AI automation for solo and small law firms — how to turn reclaimed hours into revenue without risking your licence
Adoption is no longer the problem.
Conversion is.
of small firms — and 71% of solos — report using AI in 2026, up from around 19% two years earlier.
say AI has actually moved revenue. Only 4% of small firms and 8% of solos describe their use as extensive.
billed in an eight-hour day at solo and small firms — utilisation of about 37–38%.
not cost or scepticism, is the barrier firms name most often: 27% of solos, 33% of small firms.
Figures as reported in the book from Clio’s Legal Trends work [Clio 2025a, Clio 2026]. The book discusses their provenance and limits, including the vendor’s own interest in the subject.
AI applied to a task in front of you. You initiate it, supervise it, consume the output. Value scales with your attention.
AI applied to a process that recurs. Configured once, fired by a trigger. Value scales with volume — including on the days you are in court, ill, or away.
Most small firms have a great deal of the first and almost none of the second. The revenue gap lives in that asymmetry.
Each leak has a different size in every practice, and one chapter each. The loudest is rarely the largest — the leaks differ in how much noise they make, not in how much they cost.
Prospective clients who contact you and never become clients, because nobody responded fast enough. The thread simply dies.
Firms reply to roughly a third of prospective-client emails. This is the only leak whose repair grows the top line rather than protecting margin.
Documents rebuilt from scratch, or from a scavenged old file, when they should be assembled from a verified template.
For most repeat documents in most practices, between 5 and 20 per cent actually changes between instances. The rest is re-creation.
The plumbing work of moving information between people, documents, email, calendars and systems that do not talk to each other.
The leak most people underestimate: a two-minute task done thirty times a day is an hour, and it does not feel like an hour.
Work you actually performed that never reached an invoice — or reached it in a form the client would not pay.
Realisation below 85%, or more than 5% additional time surfacing when you reconstruct a day, points here.
The book does not tell every firm to automate the same thing. Chapter 2 is an audit you can run on your own practice in about ninety minutes, using your existing records and a spreadsheet. It produces one number per leak, and those four numbers tell you where to start.
The single most common way small firms waste money on automation is buying a solution to a problem they do not have.
Measure, do not estimate. The leak that feels worst is rarely the largest.
Use a real window — the last complete ninety days, not a typical week.
Appendix C reproduces the audit as a worksheet.
The fastest workflow is worthless if the output is wrong. Two chapters are dedicated to not getting hurt: a verification layer that keeps fabricated authority out of your filings, and an ethics spine that maps ABA Formal Opinion 512 and the Model Rules onto every workflow in Part Two.
The book is specific about what should never be automated: representations about the merits, the value of a claim, or whether a limitation period has expired. Automate the conflicts check; never the clearance.
Every citation in anything filed with a court passes all four. Appendix B is the checklist.
Independent testing put hallucination rates at roughly 17% for one leading legal research tool and about 33% for another; a general-purpose model measured near 43%. Retrieval helps substantially. It does not solve it.
Magesh et al., Hallucination-Free?, Journal of Empirical Legal Studies (2025), as reported in Chapter 7.
Under a pure hourly model, every efficiency you build converts into revenue you no longer collect. That is arithmetic, not paradox, and it explains part of the revenue gap even for firms whose adoption was not shallow at all. Chapter 9 works through four coherent responses — and the case for each, honestly.
Fully compliant, no systems to change — and your revenue falls as your tools improve. A defensible waypoint, a poor destination.
Price the predictable work as a product, against post-automation cost. Requires knowing your costs and holding scope.
Fixed for productised components, hourly where the opponent controls the effort. Where most firms that think hard end up.
Decouples revenue from time entirely. Demands the most from the client relationship, and the rules constrain it. Not a starting point.
The worst outcome is drifting between them without choosing. Freed time is not revenue until it is deliberately redeployed — decide before the hours arrive, and write the decision down.
Ninety days: one leak repaired, two safety systems established, one pricing decision made. Less than most firms plan and considerably more than most firms finish.
AI policy, verification protocol, an inventory of every tool already in use. Before any automation.
Document the process as it is, build the smallest useful version, run it in parallel for a week, then cut over.
Re-run the audit on the leak you addressed. Including: how would you know if it silently stopped?
Take your most predictable matter type. Keep it hourly or price it as a product — and record the reasons.
Document it, schedule the monthly checks, update the policy. Only then plan the next ninety days.
Almost every automation project hits a wall around the third week: enthusiasm gone, system half-built and therefore worse than what it replaced, something urgent in the way. Most small-firm automation dies there — from being half-finished rather than from being wrong. The book gives you two defences.
Built to be raided rather than read cover to cover. Read Part One, run the audit, then read the chapter your audit pointed at.
“You do not have a lead generation problem. You almost certainly have a lead response problem, and it is much cheaper to fix.”
“Never let a model be the only place a citation has existed. Asking a chatbot whether its own citation is real is not verification.”
“A firm with one working automation is in a fundamentally better position than a firm with four half-built ones, and the second firm is much more common.”
Frameworks and working papers, not predictions.
Where the book uses a figure it says where the figure came from and how much weight it can bear. Three independent sources do most of the load-bearing work: Clio’s Legal Trends Reports, the Stanford RegLab study in the Journal of Empirical Legal Studies, and the AI Hallucination Cases database maintained at HEC Paris.
Lawyers who run their own practices — solo practitioners and firms small enough that the person reading it also fixes the printer. It assumes you are competent, busy and reasonably sceptical, and that your practice works; you are reading to make it work better.
No. It is about operational automation: processes that recur, configured once and triggered without you. The book’s central distinction is between assistance, which does not compound, and infrastructure, which does.
No. The build estimates in the book assume you are doing the configuration yourself with no prior automation experience — and the book is equally clear that buying those hours from someone else is often the sounder decision.
Appendix D sets out the tool landscape by category, and individual chapters name the categories and representative products. But tools change every quarter; the argument is that workflow design and sequencing matter more than product choice.
Yes — two full chapters plus two appendices. Verification, confidentiality, supervision, written AI policies, citation checking, court standing orders and the application of ABA Formal Opinion 512 to each workflow in Part Two.
No. It is not legal advice and not ethics advice. Your obligations come from the rules of professional conduct in each jurisdiction where you are admitted, your court’s standing orders, and your regulator’s guidance — all of which move faster than any book. Check any workflow against them before adopting it.
The operational material — the leaks, the audit, the sequencing, the pricing analysis — is jurisdiction-neutral. The professional-conduct discussion uses the ABA Model Rules and Opinion 512 as a common vocabulary, and the book is explicit that the Model Rules are a model: outside the U.S., your own regulator governs.
Identify the leak, choose the right automation, protect the professional obligations, and decide deliberately what the reclaimed hours are worth. That is the whole book.
AI automation for solo and small law firms — how to turn reclaimed hours into revenue without risking your licence
Adoption is no longer the problem.
Conversion is.
paymentUrl in site-config.js.