Picture the business side of your firm at full power. A new inquiry is answered and routed the same day, and it reaches the conflicts clerk with every name to search already in the packet. A matter opens complete the first time, with the billing contact, the rate arrangement and the e-billing preference recorded before anyone enters time. Every Monday the firm administrator sees which invoices are overdue, which receipts are unmatched and which clients need a call. Clients hear where their matter stands before they think to ask. A new legal assistant knows what to read, who to sit with and what to own by the end of the first week.
That is what it looks like to 10X what your team can do in a law firm. The intake coordinator, firm administrator and billing coordinator stay the same people. The preparation is done before the work reaches them, and their time goes to the calls only they can make.
The firm already pays for AI. A partner wants to know what it does for the business of the firm. Year-end billing is close, and the 2027 budget needs an AI line that someone can explain at the management meeting. This guide is the plan you take into that meeting: start from the outcome, map the work that crosses roles, land each capability on the person who does it, prove one on real work, then roll it out.
Start from the outcome.
Write the outcome first, in the words the managing partner would use: every inquiry is answered the same day, no matter opens without a billing contact, and the receivables picture is clear every Monday. Then ask which work produces each outcome and who does that work today.
Most of it crosses roles. An inquiry passes from the intake coordinator to the conflicts clerk, the responsible attorney, the firm administrator and the billing coordinator. At every handoff a name, a contact or a preference can drop out. A plan drawn by role puts those handoffs on the page, and they are where AI preparation pays back first.
This is AI capability planning: deciding which capabilities the firm needs, which role each one lands on, and what that person reviews before the work moves on.
Your procedures set the standard.
The firm’s own procedures are the rulebook for every capability in the plan. Your intake form, conflict procedure, matter-opening checklist and billing rules decide what a complete packet contains and what a properly opened matter looks like.
Some of that is written down. Much of it lives with the people who do the work: the intake coordinator who knows which questions a commercial dispute needs, the billing coordinator who knows which clients require e-billing. Where a procedure is documented, we work from it. Where it lives in someone’s head, we walk through recent examples with that person and write it down together. The procedure owner approves it before anything is built.
Map the operating work.
The operating-work map lists the recurring work in intake, finance, client service and people operations: what starts it, which roles touch it, what AI prepares and who decides. Here it is completed for an invented firm.
Illustrative example with invented data. An invented 40-person litigation and employment firm.
| Work | Trigger | Roles involved | What AI prepares | Who decides |
|---|---|---|---|---|
| Intake: inquiry handoff | A web form, call or referral | Intake coordinator, conflicts clerk, responsible attorney | An inquiry packet with the names to search and a missing-items list | The conflicts clerk runs the search; the attorney accepts or declines |
| Intake: matter opening | The attorney accepts the matter | Firm administrator, responsible attorney, billing coordinator | A checklist of required fields, with gaps flagged | The firm administrator opens the matter |
| Finance: receivables exception review | The weekly aging export and the week’s receipts | Billing coordinator, firm administrator | Proposed payment matches, unmatched receipts and exceptions, each with its evidence | The billing coordinator posts payments; the firm administrator decides each exception |
| Finance: overdue-invoice follow-up | Invoices past the firm’s follow-up point | Billing coordinator, responsible attorney | Draft reminders by client, with disputed invoices held back | The attorney approves contact; the billing coordinator sends |
| Finance: weekly receivables summary | Monday, after the exception review | Firm administrator, managing partner | A one-page summary of aging, exceptions and clients to call | The firm administrator and managing partner set the week’s actions |
| Client service: status update | The monthly cycle or a matter milestone | Responsible attorney, legal assistant | A draft update from the matter notes and recent filings supplied | The attorney edits, approves and sends |
| People operations: onboarding plan | An accepted offer and a start date | Firm administrator, supervising attorney | A first-week and first-month plan from the role’s checklist | The supervising attorney adapts the plan and judges progress |
| People operations: feedback preparation | A review cycle or the end of a large matter | Supervising attorney, firm administrator | The supervisor’s own observations, organized against the role’s responsibilities | The supervisor writes and holds the conversation |
Every row ends with a named role making the decision. The law firms page lists more work areas if your firm’s map runs wider than this one.
Intake.
Intake sets up everything after it. The inquiry handoff turns a web form and call notes into a packet the conflicts clerk and attorney can act on, with what is still missing and who needs it. Matter-opening checklist preparation checks the accepted matter against the engagement letter before billing starts. From new inquiry to open matter follows one invented inquiry through all five roles.
Finance.
Finance carries the year-end pressure. Receivables exception review gives the billing coordinator proposed matches and exceptions every week, each with the record behind it, and the firm administrator decides the exceptions. The weekly receivables summary turns that review into one page for the managing partner. Overdue-invoice follow-up preparation drafts the reminders and holds back anything in dispute.
Client service.
Client-status update preparation drafts the update from the matter notes and filings the attorney supplies, and lists what it could not confirm. The attorney decides what the client reads.
People operations.
The employee onboarding plan gives a new legal assistant a first week built from the role’s real responsibilities, shaped by the supervising attorney. Manager feedback preparation organizes a supervisor’s own observations before a review conversation.
What stays with lawyers and staff.
Every capability in this plan prepares work. The decisions stay with the people who hold them today, and the plan says so in writing.
- Conflicts.The conflicts clerk runs the firm’s conflict search, and the responsible attorney resolves any potential conflict under the firm’s procedure. A packet lists the names to search. It never clears anyone.
- Accepting a client.The responsible attorney decides whether the firm takes the matter and on what terms.
- Legal advice.Legal questions go to the responsible lawyer. Drafts for clients carry facts and status, and the attorney decides what is said.
- Deadlines.An attorney calculates and confirms every legal deadline. A workflow lists dates exactly as a document states them and marks them for the attorney.
- Money.The billing coordinator posts payments. Credits and write-offs are issued by the people the firm’s approval rules name.
- Messages and records.A person sends every message and changes every record in the practice-management and billing systems.
- People decisions.Hiring, performance and pay stay with the firm’s supervisors and partners.
- The workspace and the standard.The firm approves which AI workspace may hold client and prospective-client information. The procedure owner agrees the standard each workflow is tested against.
Score the candidates and choose one pilot.
A map shows everything the firm could do. The worksheet picks what it does first. Score each candidate on five criteria from 1 to 3, where 3 always favors a first pilot: it runs often, it causes visible friction, its inputs exist today, a mistake is caught in review before it reaches a client or the books, and a first version needs only files and exports in the workspace the firm already uses.
Illustrative example with invented data. Scores for the same invented firm.
| Candidate workflow | Lead role | Frequency / friction / inputs / consequence / effort | Total of 15 |
|---|---|---|---|
| Inquiry handoff | Intake coordinator | 3 / 3 / 2 / 3 / 3 | 14 |
| Receivables exception review | Billing coordinator | 2 / 3 / 3 / 3 / 3 | 14 |
| Matter-opening checklist preparation | Firm administrator | 2 / 3 / 2 / 2 / 3 | 12 |
| Overdue-invoice follow-up preparation | Billing coordinator | 2 / 2 / 3 / 1 / 3 | 11 |
| Weekly receivables summary | Firm administrator | 2 / 2 / 2 / 3 / 2 | 11 |
| Employee onboarding plan | Firm administrator | 1 / 2 / 2 / 3 / 3 | 11 |
| Manager feedback preparation | Supervising attorney | 1 / 2 / 1 / 3 / 3 | 10 |
| Client-status update preparation | Responsible attorney | 2 / 2 / 1 / 1 / 2 | 8 |
The firm chose the inquiry handoff. It tied with the receivables review, and the tie broke on what happens downstream. A billing contact missed at intake becomes a matter opened without one, then an invoice with nobody to receive it, then an exception in next month’s receivables review. Fixing the packet improves three later steps. The pilot also involves the intake coordinator, the conflicts clerk and the responsible attorney from the first day, which makes it the firm’s project and not one desk’s. Its inputs score 2 because call notes vary with whoever took the call, and agreeing what a complete packet contains is the first thing the pilot settles.
The worksheet makes the alternative a deliberate choice too. If the managing partner’s priority this quarter is year-end collections, the receivables exception review goes first and intake goes second. The meeting picks one on purpose and writes down why.
Client-status updates score lowest because the matter notes are scattered and the draft goes to clients. They move up once matter notes live in one place. Feedback preparation waits for a similar reason: its input is observations supervisors have not yet written down.
The blank worksheet.
Copy this for your own candidates, and fill it in with the people who do the work. They know where the friction is.
Blank worksheet to copy. Contains no data; add your own candidates.
| Candidate workflow | Lead role | Frequency / friction / inputs / consequence / effort | Total of 15 | Notes |
|---|---|---|---|---|
| 1. | _ / _ / _ / _ / _ | |||
| 2. | _ / _ / _ / _ / _ | |||
| 3. | _ / _ / _ / _ / _ | |||
| 4. | _ / _ / _ / _ / _ | |||
| 5. | _ / _ / _ / _ / _ | |||
| 6. | _ / _ / _ / _ / _ |
How to fill in the worksheet
- Candidate workflow. Name the recurring work and its outcome. Ask: what starts it, and what does finished look like?
- Lead role. Ask: whose working day changes, and who will own the pilot?
- Frequency. Ask: how often does this work run across the firm? Score 3 for several times a week, 2 for weekly, 1 for monthly or less.
- Friction. Ask: where does it stall, get chased or get redone? Score 3 when delays and rework show up every week, 2 when they show up most months, 1 when it mostly runs clean.
- Input readiness. Ask: do the inputs exist today as files or exports someone can supply? Score 3 when they do, 2 when they exist but vary with who prepared them, 1 when they are spread across inboxes and memory.
- Consequence of error. Ask: if the prepared work is wrong, where is it caught? Score 3 when a person reviews it before it reaches a client, a court or the books, 2 when that review is the only check, 1 when it leaves the firm soon after.
- Effort. Ask: what does a first version need? Score 3 for files and exports in the AI workspace the firm already uses, 2 when another workflow has to run first, 1 when it needs new connections or changes to the firm’s systems.
- Total and notes. Add the five scores. Note ties, dependencies between candidates and anything the scores cannot see, such as a partner’s priority or the year-end calendar.
Prove one on real work.
We build with invented inquiries. The pilot then runs on the firm’s real ones, in the firm’s own workspace, while we observe without receiving or keeping copies. The intake coordinator does the work. The conflicts clerk and the responsible attorney receive the packets and say whether each one is complete.
Test the awkward case as well as the ordinary one. An inquiry that names a company but not its parent. A caller who gives two spellings of the other party. A web form with no phone number. A request for a practice area the firm does not handle. Agree what the packet should do in each case before the first run, then review the actual output against that expectation. The ordinary case shows the workflow runs. The awkward case shows it is safe to hand on.
Pilot acceptance-test preparation sets up those cases and their expected behavior, and what we test before we call an AI workflow ready explains the record we keep. The procedure owner, here the intake coordinator with the responsible attorney, decides when it is ready. The first 90 days of an AI adoption plan takes it from the chosen pilot to the decision to expand, week by week.
Roll it out, then take the next one.
Once the pilot passes, it becomes how intake runs. The intake coordinator has a short job aid, the conflicts clerk knows what arrives and in what form, and a named owner updates the workflow when the intake form changes. The rollout checklist covers the rest.
Then go back to the worksheet. Matter-opening checklist preparation reads the packet the pilot now produces, and its input score rises once every packet arrives complete. Over a year the map fills in area by area, each capability planned, proven, rolled out and kept current by the roles that use it. That whole cycle is AI capability management.
Your platforms, your pace, your people.
We build every capability in this plan in the AI the firm already uses, whether that is ChatGPT, Claude, Copilot or Gemini. We 10X the ROI of your existing AI spend by putting it to work on the firm’s own procedures, one capability at a time.
The pace is the firm’s: one pilot proven before the next, each step decided at the management meeting. The people stay in charge. The procedure owner sets the standard, the responsible attorney keeps every legal decision, and the firm changes a workflow when its procedures change. We help your organization strategically plan and migrate to AI without losing control of how the work gets done.
What to bring to the management meeting.
Bring the plan on two pages and end with one decision.
- The map.Your firm’s operating work across intake, finance, client service and people operations, with the roles and the decisions filled in.
- The scored worksheet.Every candidate on the map, scored with the people who do the work.
- One proposed pilot.The workflow, its lead role, its reviewers and what finished looks like.
- A question for each person in the room.For the managing partner: is this the outcome the firm wants first? For the finance lead: does the pilot help year-end or wait behind it? For the IT director: which workspace is approved for client and prospective-client information?
- The decision.Approve one pilot, name its owner and set the date to review it.
Bring your draft map or worksheet to a fit call, and we will help you choose the first pilot.