Home/ Comparisons/ Law Firm AI Hire vs Commission

Hire an AI developer for your law firm vs commissioning the build.

Hire an AI developer for your law firm when three to six builds are queued and a partner will supervise a nonlawyer technologist. Commission the build when one workflow is stalling. Large firms are advertising these roles at $200,000 to $440,000; a ColabContent commission is a fixed $45,000 to $180,000, code owned at handoff.

For managing partners and firm administrators at 20 to 150 attorney firms who have conceded the budget and are deciding whether it buys a person or a system. The math, the supervision problem, and the cases where hiring is the better call.

ForManaging partners and firm administrators
StanceBoth work. In different firms.
Bottom lineA queue of builds justifies a hire; one stalled workflow does not
CostFree analysis

The economics, in law firm terms.

The price of this hire is public now. Bloomberg Law reported on 2 July 2026 that at least sixteen large firms had more than twenty-five AI strategy and capability roles open at once, advertised between $200,000 and $440,000. Pillsbury posted up to $440,000 for a director of data science and AI engineering; Latham & Watkins listed $295,000 to $400,000 for associate directors in AI governance. The reporting blames the trouble filling them on a candidate pool that has not kept pace with demand.

Those are large-firm numbers and a 45-attorney firm is not paying them. A 2026 recruiter salary guide compiling Built In, Glassdoor and Levels.fyi data puts senior AI engineers at $180,000 to $280,000 in base and tells hiring managers to add fifteen to twenty-five percent for bonus, equity and benefits. We budget the loaded figure at $185,000 to $280,000, the range we use on the general version of this comparison, plus a six-month minimum ramp before the first system lands. A firm bidding at the top of that recruiter guide's senior band should plan higher.

A commissioned build is a fixed $45,000 to $180,000 for one named workflow, with a working prototype on the firm's real data in seven to ten days and production in four to seven weeks. One year of the loaded hire buys roughly one to three finished builds; two years buys three to six. The hire wins on arithmetic only if three to six builds are actually queued.

Firms have the money. The Thomson Reuters Institute and Georgetown Law 2026 Report on the State of the US Legal Market records 13 percent average profit growth in 2025 and talent costs up 8.2 percent over 2024. The constraint is not budget. It is whether the budget should become a permanent salary line.

What else that money buys.

Three other uses of the same money come up in the same partnership meeting.

A lateral hire. The strongest competing claim, and a revenue bet rather than a cost-structure bet. It carries a documented failure rate: research from Decipher Investigative Intelligence, reported by Above the Law in May 2026, puts lateral partner departures at 30 to 38 percent within five years. That does not argue against laterals. It argues the partnership already knows how to price a risky people bet.

A legal operations or practice technology director. For most firms in this band that is the better hire, and usually what the firm means when it says it wants an AI person. Salary.com put the US average for a director of legal operations at $244,992 as of 1 August 2026. That person runs vendor selection, adoption, policy and measurement. They do not build systems.

A commissioned build. A fixed scope against one named constraint, delivered and owned. A legal-ops director and a commission are complements rather than rivals: the director decides where to point the firm and holds adoption, the commission produces the thing being adopted.

The supervision problem no job posting solves.

Every other hire a law firm makes lands under somebody who has done the job. An associate reports to a partner who has run the same motion. A controller reports to an administrator who reads the same ledgers. An AI engineer reports to nobody who has managed engineering.

That is a governance issue before it is a culture one. The hire is a nonlawyer whose work product touches client matters. ABA Formal Opinion 512, issued 29 July 2024, builds on Model Rules 1.1, 1.6 and 5.3, the last of which covers a lawyer's responsibilities regarding nonlawyer assistance. The obligation sits with the lawyers holding managerial authority. It does not transfer to the technologist.

A firm that hires without an answer here inherits four unowned questions: who reviews the code, who decides the architecture, who signs off on the security posture, and who tells the partner group that the thing they asked for is a bad idea. A firm that cannot name a person for each is not ready to hire. It is ready to commission, where scope, acceptance criteria and review gates are written and signed before any code exists.

A commission does not remove the supervisory duty. It makes the duty reviewable, because the data boundary, the model selection and the human checkpoints are named in a document the firm keeps. That is the same paperwork a carrier or a client will ask to see, covered in our guide to bar rules and malpractice.

Where hiring is the right answer for a law firm.

Three to six builds genuinely queued. Not aspirations, a queue. At a firm that usually reads as new-matter intake and conflicts clearance, retrieval over the matter archive before a senior partner retires, billing narrative review, and client reporting. Four systems, four owners, four data boundaries. A firm holding that list in writing should hire.

AI as a position rather than a convenience. Some firms are pushed there by their own clients. Once corporate clients put AI sections in outside counsel RFPs and renewal packets, the answer becomes a capability the firm has to hold and keep current. Standing work wants a standing owner.

A partner who will actually sponsor it. The hire needs administrative rights on the document management system, access across practice groups, and enough standing to override a workflow three partners are fond of. Firms that hire the person and withhold the authority lose them inside eighteen months.

Where commissioning is the right answer.

One named workflow, not a roadmap. "Conflicts clearance takes us two days and we lost two matters this year waiting on it" is a build problem. Hiring a director to solve it is a $250,000 recurring answer to a $90,000 one-time question.

The firm would rather not compete for this candidate. The Bloomberg Law reporting is a warning as much as a benchmark. Sixteen of the largest firms are bidding, and technology companies are bidding against them for the same people. A 60-attorney firm in that auction should expect a long search and a hire who stays recruitable.

Ownership matters more than headcount. A commission ends with the firm holding the code, prompts, models, datasets, runbook and integration documentation, inside its own cloud tenant under NDA. No runtime to license, no per-seat fee. That is the same ownership outcome the hire produces, without the payroll line.

Key-person risk. When the internal engineer leaves, the knowledge leaves. When a commission closes, the documentation is the deliverable.

What we have built in law, and what we have not.

Systems built here have handled more than 6,000 live customer calls. The client we can name is Jim Glaser Law, a Massachusetts firm running five channel-specific voice agents across PPC, organic, TV, Meta and LSA, which have taken 3,787 calls across 5,514 minutes and give the firm per-channel attribution on every answered call. Jimmy takes reference calls for us. A prospect who would rather hear the work than read about it can call our own line at (617) 675-9067, which an AI receptionist answers.

A second law firm engagement we are not permitted to name is a platform build rather than a point solution: 13,296 matters, 4,396 clients and 5,684 invoices migrated off the firm's prior system, with the trust ledger reconciling byte-identical against the system it replaced at cutover.

What we do not have is a case study for every practice area, and we would rather say so here than in week three. If a firm's situation favors the hire, we say that on the call.

Side by side

Where the comparison actually matters.

The five dimensions that decide the buy.

Cost shape. The hire is $185,000 to $280,000 fully loaded every year the role exists, against a market bidding $200,000 to $440,000. A commission is a fixed $45,000 to $180,000 in two installments, at build start and at handoff.

Time to a working system. The hire needs a search, a notice period and a six-month ramp. A commission puts a prototype on the firm's real data in seven to ten days and production in four to seven weeks.

Ownership. Both paths end with the firm owning the code, and the hire owns it from day one, which is the honest advantage of the internal route. A commission transfers code, prompts, models, datasets and runbook at handoff.

Supervision. The hire needs a manager the firm does not have, under a duty the partnership cannot delegate. A commission arrives with scope, acceptance criteria and review gates agreed in writing.

Key-person risk. The hire concentrates the firm's AI knowledge in one recruitable person. A commission concentrates it in documentation the firm keeps.

When to hire, when to commission.

Hire if three to six distinct builds are queued rather than one, AI capability is becoming a position the firm competes on, a partner will grant stack access and workflow authority, and the firm can name who reviews the work.

Commission if one or two named workflows are the constraint, the budget runway for a $45,000 to $180,000 fixed fee is real this quarter, owning the code matters, and the firm would rather not carry key-person risk.

Many firms end up with both, in sequence. Commission the first build, then hire once two or three commissions have proved the queue is deep. That order beats hiring first and hoping the queue shows up, an argument we make at length in the case for commissioning before hiring a head of AI.

If the firm already has a legal operations director.

Then the question is narrower and better posed. The director already owns adoption, policy and measurement, so what is missing is build capacity, not ownership. The usual boundary: the director keeps the recurring work and the vendor relationships, and builds with deadlines get scoped out and handed back as owned code.

That also answers the supervision problem cleanly. A named person inside the firm is accountable, and the specification they hold is what an outside team is measured against. Our guide to vetting an AI consultant covers what to ask first.

Extended questions

The questions partners ask after the first one.

Should a law firm hire an AI engineer or commission the build?

Hire when the firm has three to six distinct builds genuinely queued, a partner with the authority to sponsor the work, and a five-year horizon for the role. Commission when one named workflow is the constraint. Most 20 to 150 attorney firms are in the second situation and buy the first, which is where the money goes wrong.

What does hiring an AI developer cost a law firm in the first year?

Budget $185,000 to $280,000 fully loaded in most US markets, or $140,000 to $200,000 for a remote-eligible role, plus recruiting time and a six-month ramp before the first system lands. Large firms are advertising AI leadership roles between $200,000 and $440,000, which sets the market a mid-market firm has to bid into.

Is a legal operations director a better hire than an AI engineer?

For most mid-market firms, yes. Salary.com put the US average for a director of legal operations at $244,992 as of 1 August 2026. That person owns vendor selection, adoption, policy and measurement, which is work the firm has every week. They do not build systems, and pairing one with a commissioned build is the common shape.

Who supervises an AI engineer inside a law firm?

Answer this before posting the role. ABA Formal Opinion 512, issued 29 July 2024, builds on Model Rule 5.3, which covers a lawyer's responsibilities regarding nonlawyer assistance. The duty sits with the lawyers holding managerial authority. If no partner can name who reviews the work, the hire opens a governance gap rather than closing one.

Can a 60-attorney firm compete for this candidate?

It can, but it should know what it is entering. Bloomberg Law reported in July 2026 that at least sixteen large firms had more than twenty-five AI roles open at once, with technology companies bidding for the same people. A mid-market firm in that auction should expect a long search and a hire who stays recruitable.

Does the firm own the code from a commissioned build?

Yes. At handoff the firm receives the code, prompts, models, datasets, runbook and integration documentation, and the system runs inside the firm's own cloud tenant under NDA. There is no proprietary runtime to license and no per-seat fee to renew. That is the same ownership result an internal hire produces, without the payroll line.

What if the firm wants to hire and commission at the same time?

That is a sensible posture and a common one. Keep the internal owner on the work that recurs, meaning adoption, policy, measurement and tuning, and commission the builds that carry a deadline. The boundary worth writing down is which workflows the internal owner keeps and which get scoped out, before either is started.

What should a firm bring to the first call?

Two things. A one-page description of the leading constraint in the firm's own words, naming the workflow and the rough hour or dollar leakage. And a list of the systems involved, meaning the document management system, the practice management system and the integration boundaries. Neither has to be polished.

Get the honest read.

Free 45-minute diagnosis. We will tell you whether your firm favors the hire or the commission, with the math.