Partner with the frontier.
Freshfields deployed Anthropic’s Claude firm-wide in April 2026 and co-develops with the lab,24 while hedging with a parallel Google deployment. The bet: go to the source and help shape the product.
July 2026
A field guide for in-house lawyers buying legal AI — or having it bought for them.
Most advice about legal AI assumes you are choosing a tool. You probably aren’t. AI is arriving in your legal team through half a dozen doors at once, and most of them were opened by someone else: IT, the contract lifecycle management vendor, your panel firms, the rest of the business. This is a field guide to governing the stack instead of discovering it.
The short version
Most advice about legal AI assumes you are choosing a tool. You probably aren’t. The buying decision isn’t “which product.” It’s three questions, in order:
The answer to the third question is almost never a product. It’s your own knowledge; organised. Every product is an engine. Nobody sells the fuel.
00 — the six doors, already open
Here is how AI shows up in an in-house legal team in 2026.
IT rolls out Microsoft Copilot across the business, often thinly deployed, and legal gets it whether it wanted it or not. The contract platform announces AI features at renewal, priced into the uplift, with no procurement decision for legal. Three panel firms arrive with three different AI portals, each hoping its platform becomes your platform, or at least makes you symbiotic with it. Some may even white-label you an AI product of their own.
Other departments run their own AI projects, some already making calls with legal consequences. Two of your lawyers are quietly using personal ChatGPT accounts; in Thomson Reuters’ 2026 Future of Professionals survey, roughly a third of professionals admitted using AI tools their organisation hasn’t approved.1 And somewhere in the budget cycle, someone asks whether you should buy Harvey or Legora, which you cannot afford on your existing budget.
That is six doors, five pricing models, and one deliberate decision. The stack assembles itself. The question is whether you govern it or discover it.
The strange part: in-house counsel are the most powerful buyers in this market and the least powerful buyers in their own building. In Litera’s Spring 2026 survey, 51% of law firm respondents said a client had directly influenced an AI investment decision in the past year; only 15% said their AI investment was entirely internally driven.2 Meanwhile, your own AI stack may have been chosen by an IT committee you have never met. You dictate to the firms you buy from, and you get dictated to by the business.
There is a reason for the squeeze. In-house legal is a service provider at the heart of the business, which is exactly why so many of these decisions are not legal’s. Law firms sit above you, keen to show off their AI. Business units press in from every side, expecting legal to keep up. In the middle sits a legal team whose own stack may be the least deliberately assembled of anyone’s. And trust inside legal is thin: in Factor’s 2026 survey, 83% of lawyers had access to AI tools but only 22% reported high trust in them.27
This is how I would try and untie the knot: understand the products, understand your constraints, and then, most importantly, understand your needs. Skip to the third part if you only read one thing.
Part 1
Start by watching the big firms. They publish their moves, the press covers them, and they can afford to try everything. Their AI strategies have split three ways.
Freshfields deployed Anthropic’s Claude firm-wide in April 2026 and co-develops with the lab,24 while hedging with a parallel Google deployment. The bet: go to the source and help shape the product.
Harvey, Legora, CoCounsel. Just about every major firm has bought one, usually alongside another strand; Slaughter and May’s Harvey adoption in April 2026 was one announcement in a stream of them.25 The bet: pay the premium, get the workflow, accept the lock-in.
Kirkland & Ellis is building on Palantir’s data architecture, starting with its thousand-lawyer funds practice (June 2026).26 DIY, if doing it with Palantir counts. The bet: the durable asset is the firm’s own structured data, not anyone’s app.
Sit with that. The best-resourced legal buyers in the world looked at the same market and split three ways, with many running more than one strand at once. There is no consensus play; the closest thing is hedging. Treat anyone selling you certainty accordingly.
The same three strategies exist in-house, at smaller scale. But in-house is the harder problem. A firm decides once, for itself. You have a stake in your firms’ decisions as well as your own, and their choices land on your desk as portals, workspaces and AI-drafted work. And you face doors no law firm has to worry about, so your map needs more rows.
The market looks chaotic because vendors describe themselves by what they’d like to be. Ignore the marketing and every AI product or initiative that touches an in-house team comes through one of six doors.
The frontier models, bought direct: Claude, ChatGPT, Gemini, in their enterprise forms. This door got serious for lawyers in 2026. Anthropic shipped Claude for Word in April 2026 and Claude for Legal on 12 May 202634; OpenAI was reported in May 2026 to be planning a “Codex for Legal.”5 (Perplexity launched a lawyer-facing product on 24 June 2026 as well,6 but it belongs with the vendors, not here: buy it and you hold a Perplexity subscription, not a frontier-model relationship. See Rubric 2, question 1.) Buying at the source means the fewest layers between you and the intelligence, and the most assembly. The do-it-yourself path is this door with less paperwork.
Purpose-built legal AI: Harvey, Legora, Thomson Reuters’ CoCounsel, and in-house entrants like Wordsmith.7 You pay a premium for legal workflow, integrations, and someone accountable when it breaks. One myth to puncture early: the platforms’ favourite pitch is that they are the only safe way for lawyers to use AI. Check your enterprise agreements before believing it. No-training defaults and the usual certifications usually already sit in the contracts IT signed with the source and copilot providers. Safety is table stakes, not a platform exclusive. Reported list pricing at the premium end runs to four figures per seat per month, with seat minimums, before discounts.8 These vendors court in-house teams hard because an in-house win markets the product to every firm on your panel.2
Microsoft 365 Copilot and its equivalents. Not legal products, but they arrive with enterprise weight and often without legal’s buy-in (you may even have approved it as “safe”, which is not the same as choosing it). The twist: the forced door keeps filling with legal-grade material, because Microsoft is playing every side at once. It put Harvey inside Copilot (4 March 2026).9 It has been adding Anthropic’s Claude models since September 2025.10 And on 30 April 2026 it shipped its own Legal Agent in Word, US-only at launch, built by a team hired out of legal AI vendor Robin AI.11 If IT locked you in a room, check the room. The walls have doors in them now.
The AI features sprouting in products you already run: the contract lifecycle (CLM) system, the document management system (DMS), e-billing, matter management. iManage and NetDocuments are building AI into the DMS itself.12 This door never faces a buying decision; it arrives with the renewal, priced in. It is the easiest door to walk through by accident. One split matters more than any demo: some bolt-ons can connect to the rest of your tools; many just sit in their own box.
The door most maps miss, because it doesn’t look like procurement: your firms’ platforms reaching you through the engagement itself. Portal seats, shared workspaces, AI-drafted deliverables. Work across several firms and several platforms are coming at you, a buffet you never ordered. Each firm hopes its platform becomes the surface you work on together. Convenient, and also how your instructions, positions and matter history end up inside someone else’s product. It needs a house rule, not a default yes (more in Part 2).
Procurement’s contracting tool, finance’s forecasting models, HR’s screening systems: all sprouting AI, none of it bought by legal, some of it making calls with legal consequences. Legal sits in the middle of everyone else’s workflows, so other people’s AI creates your work and your risk. This door appears on no vendor’s market map.
One property cuts across the map: connectivity. The Model Context Protocol (MCP), an open standard from Anthropic (late 2024), lets AI products call each other’s tools and data.13 Harvey runs it in both directions: other tools can call Harvey, and since December 2025 Harvey can reach out to your other systems.13 iManage has announced support.12 Some platforms have none. Connectivity decides whether the doors add up to a stack or a pile of silos. Treat it as a buying question, not a technical footnote.
| Door | What it really is | Examples (July 2026) | How it usually arrives | How the meter runs | If it dies or you leave |
|---|---|---|---|---|---|
| 1. The Source | Frontier model, bought direct | Claude Enterprise / Claude for Legal, ChatGPT Enterprise, Gemini | You choose it (or build on it) | Per seat, cheap relative to Type 2; usage-based via API | Model is replaceable; whatever you built survives if you kept it portable |
| 2. Legal platform | Legal workflow wrapped around frontier models | Harvey, Legora, CoCounsel, Wordsmith | Legal procurement | Premium per seat; consumption pricing arriving (see Part 2) | Your playbooks, agents and vault structures may not export; ask before you build there |
| 3. Enterprise copilot | General-purpose AI across the company’s Microsoft or Google environment | M365 Copilot, Gemini for Workspace | IT decides; legal inherits | Bundled per seat on the enterprise agreement | It won’t vanish, but the features and models inside it churn |
| 4. Legaltech AI bolt-on | AI features embedded in tools you already own; some connected, some in their own box | CLM AI modules, iManage / NetDocuments AI, e-billing AI | The renewal cycle | Priced into the uplift; rarely itemised | The host product survives; the AI layer is hostage to the vendor’s roadmap |
| 5. Your firms’ AI | Panel firms’ platforms reaching you through the engagement | Portal seats, shared workspaces, AI-drafted deliverables | With the next matter; with the pitch | Folded into the fees | Your playbooks and instructions inside a firm’s platform are the hardest copy to get back |
| 6. The business’s AI | Other departments’ AI making legal-adjacent calls | Procurement contract bots, finance models, HR screening | Nobody tells legal | Someone else’s budget | The risk stays with you even though the tool was never yours |
Connectivity (MCP / open APIs) is a property of the doors, not a seventh door. Test for it with Question 3 below.
When a vendor demo refuses to fit the map, ask these four questions. The answers place it.
| Question | What the answer tells you |
|---|---|
| 1. Who holds the model relationship? You directly → Type 1. A legal vendor → Type 2. Your IT department → Type 3. The product company you already pay → Type 4. Your panel firm → Type 5. Another part of the business → Type 6. | Who captures the margin, and who you depend on when models change |
| 2. Where does your knowledge end up, and can you walk away with it? Ask for the export mechanism in writing, not the roadmap. | Your real switching cost in two years |
| 3. Can it connect? Does it speak MCP (or open APIs), in either direction? | Whether it will join your stack or fragment it |
| 4. How does the meter run: seat, consumption, or bundled into a renewal? | What your bill does when usage takes off (see Part 2) |
Two complications. First, the types are collapsing into each other: the labs are moving up into legal product (Anthropic now sells Door 1 and, since May 2026, something close to Door 24), the copilots are absorbing legal agents, and the incumbents are bolting AI on. That is what the four questions are for. Second, the industry’s own leaders say the categories are unstable. Harvey’s CEO, 12 May 2026: “long term we would end up competing with the model companies.”14 Legora’s CEO: models are “necessary … but insufficient on their own.”15 OpenAI’s president, in a post reported on 22 May 2026: “the model alone is no longer the product.”16 When both sides of the table agree the ground is moving, get ready for earthquakes.
Part 2
Product knowledge is useless until you face three constraints: who holds the authority (and the budget), how pricing is shifting, and the fact that products die.
Start with an uncomfortable question: who actually controls your team’s AI decisions? There are three real answers, each with a different menu.
| Your situation | Your realistic menu | Your levers |
|---|---|---|
| A. Legal owns the budget and the IT relationship | The full map. Run a real Type 1 vs Type 2 evaluation; use connectivity (Rubric 2, Q3) as the tiebreaker | Everything below, plus vendor selection itself |
| B. Legal has budget, but IT owns the platforms | Buy legal-specific tools at the edges (Type 2 for defined workloads); require MCP/API openness so they work with what IT runs rather than against it | Procurement terms; integration requirements; a seat at IT’s steering table |
| C. No budget; Copilot was mandated | The guerrilla position: use what’s already licensed (the copilots now carry frontier models and legal agents91011); build the Part 3 knowledge layer with time and discipline | The contract levers (engagement letters, panel terms, instructions to firms), which cost nothing and nobody can take away |
Row C looks like defeat and isn’t. A mandated Copilot is a constraint, not a verdict: the licensed tools are a free way to learn, and the models inside them are real. Used bare, though, they disappoint. In the first published blind-judged benchmark of its kind (April 2026, run by the vendor Ivo, so read it with that in mind), a frontier model out of the box scored 3.50 out of 10 on contract review. The purpose-built tool scored 4.52; a senior lawyer 4.56. Nobody aces this test, but the ordering is the point.17 The setup wasn’t even-handed: the purpose-built tool came configured for the task; the frontier model came bare. But the asymmetry is the finding. The gap was what the model was given to work with, not the model. Raw model access is not capability. The playbook you feed it is the capability.
One constraint sits across every row: the buffet. Instruct several firms and several platforms will come at you through door 5, each convenient, each moving a little more of your knowledge into someone else’s product. You cannot adopt them all, and deciding matter-by-matter under deadline pressure means the firms decide for you. Set the rule once, for every firm: which portals you will work in, whether your playbooks may go into a firm’s platform, and what firms must tell you about AI-produced work.
I’ve written a longer piece on this shift: The Tokenomics of Legal AI.
For two years legal AI was priced like software: per seat, per year, predictable. That era is ending. On 23 June 2026 Legora moved its flagship tier to consumption pricing, in its own words “from hours billed and seats licensed, to outcomes delivered.”18 Expect others to follow, because the vendors’ own costs run on consumption. Harvey’s founders said in May 2026 that their token throughput (tokens are the units AI work is metered in) had grown twelvefold in five months, and that the company is not currently profitable.19
Consumption pricing cuts both ways. In your favour: cost becomes legible per matter, which a seat licence never showed you. Against you: volatility. Agentic workflows, where the AI takes many steps on its own, multiply consumption in ways nobody can forecast, including the vendor.
Remember margin stacking too. The further from the source you buy, the more layers of markup the same computation passes through: model, then platform, then embedded product, each taking a cut. That is not an argument for always buying at the source; the markup buys real things (workflow, security, someone to sue). It is an argument for knowing how many layers you are paying for, and asking each what it adds.
Two moves follow. First, settle AI cost allocation in your engagement letters and panel terms now, while it is cheap to raise: is AI the firm’s overhead or a disbursement, and if a disbursement, at cost or marked up? One sentence today avoids an argument in 2027. Second, ask every vendor Rubric 2’s fourth question and get per-matter cost visibility written into the contract.
Legal tech products fail, get acquired, or get abandoned. ROSS Intelligence, a respected legal research startup, shut down in 2020 while defending copyright litigation that is still running; the appeal was argued on 11 June 2026.20 Its customers were pointed at three competitors and left to manage the move. Even the safest names get repriced overnight: on 3 February 2026, after Anthropic shipped a legal plug-in, Thomson Reuters shares fell 16% in a day.21 If the market cannot price these products with confidence, neither can you.
You cannot pick survivors, but the risk isn’t uniform. Then do the one thing that makes tool death survivable anywhere on it: keep the knowledge outside the tool.
from Constraint 3 — on planning for products that die
You cannot pick survivors, but the risk isn’t uniform. Thin products that wrap a frontier model in a chat window are the most exposed. Deep workflow platforms are defensible but expensive to run.19 Products anchored to systems of record (your DMS, your CLM, the law reports) are the most insulated, because the data holds even where the AI is mediocre. Rate every product in your stack on that spectrum. Then do the one thing that makes tool death survivable anywhere on it: keep the knowledge outside the tool.
Before the needs, name the failure mode, because it’s the default. Nobody decides it; then it accretes.
The contracts team pilots the CLM vendor’s AI module. Disputes standardises on Copilot, because IT switched it on. One lawyer builds a brilliant personal workflow in a paid ChatGPT account. Two firms’ portal seats arrive with the next two big matters. Procurement renews the DMS with the AI uplift because the discount expired Friday, and procurement’s own contract tool starts suggesting fallback positions nobody in legal has seen.
Eighteen months later: six tools, four pricing models, no shared playbooks. Each product has been learning your team’s precedents and positions inside its own walls, in formats none of them will hand back. The CLM knows your contract positions, the portal knows your instructions, the chat histories know everything else. Three lawyers do the same task three different ways at three different costs. Everyone has become the champion of a different product, which is another way of saying the AI deployment is not managed at all. And when the board asks what legal’s AI position is, the honest answer is: we have six, and they’ve never met.
The cost is bigger than duplicated spend. Whatever makes your team valuable (the positions you take, the way you paper a deal, what you learned the hard way on the last dispute) is exactly what these products absorb as your lawyers use them. If you don’t own your knowledge management, you are giving it away: chopped into a thousand pieces and handed to every vendor, firm and business unit with a prompt box. Nobody would photocopy the precedent bank and post it to six suppliers. An unmanaged AI deployment does the equivalent every day, without anyone deciding to.
None of the individual decisions was wrong. The absence of a decision was wrong. That is what a team AI strategy is for, and it is why the strategy has to start from needs, not products.
Part 3 — the part that actually matters
Run the logic from the work, not the demo. Most in-house AI needs reduce to seven. Six map onto the doors cleanly. One maps to nothing on the market, and that one is the point. (The types below are the six doors from Part 1: source, legal platform, enterprise copilot, legaltech bolt-on, your firms’ AI, the business’s AI.)
| The need | What actually meets it | Types that fit | What it depends on | The trap |
|---|---|---|---|---|
| High-volume repeatable work (NDAs, standard procurement contracts) | Consistent application of your positions at speed | Type 4 (CLM AI) or Type 2 | A written playbook of your positions; the tool applies it, it doesn’t invent it | Buying the tool before writing the playbook; then it applies someone else’s defaults |
| Advice and drafting (memos, board papers, correspondence) | A strong drafting model plus your precedents and house style | Type 1 or 3, fed with your knowledge | Your precedent bank; a verification habit | This is your least-checked output. Litigation has opposing counsel as quality control; a board memo has no one |
| Legal research | Grounded, citable authority in your jurisdiction | Type 2, or research-specific products | Jurisdiction coverage; citation verification | General models are weakest exactly here; the cases where courts have sanctioned lawyers over AI are overwhelmingly citation failures |
| Knowing what you know (precedents, positions, matter histories) | Structured, searchable, owned knowledge | No type solves this for you | You. This is the input to every other row | Believing a vendor’s “vault” or “memory” feature is your KM strategy. It’s theirs |
| Managing external counsel | Leverage: panel terms, cost visibility, quality expectations | Contract levers plus your firms’ portals (Type 5), used deliberately | Knowing what AI-era work should cost and how fast it should arrive | Demanding “show us your AI ROI”: you will get a number, not the truth. Specify outcomes instead |
| Governing the business’s AI (procurement bots, finance models, HR screening) | Visibility and review gates where other teams’ AI touches legal risk | Type 6 is the object of governance, not a tool you buy | A map of where AI decisions with legal consequences happen | Assuming silence is safety; door 6 never announces itself |
| One-off automation (a review sprint, a data-room triage) | Short-lived, task-shaped tooling | Type 1 plus the connector property | A named owner who checks the output | Letting the prototype quietly become infrastructure with no owner |
Now read the fourth column. The tools supply almost none of it. The rows keep asking for what only you can bring: your positions, your precedents, your matter histories, a named owner. No product ships with any of it; the benchmark result in Part 2 is that gap, measured. The model is the engine. Your knowledge is the fuel. Everyone is selling engines.
Related: why I keep my own knowledge base as flat, portable files — Flat Markdown.
The strategic core is unglamorous: get your filing system in order, and make it readable by the various tools. Keep the master copy of your team’s knowledge in plain, portable formats you own. Ordinary files, ordinary folders, readable by anything; in practice, Word documents and plain-text files in storage the team controls. Not inside Harvey’s vault, Legora’s playbooks, the CLM’s clause library, or Copilot’s memory. Those are working copies, rebuilt from the master whenever you like.
Three reasons, all downstream of Parts 1 and 2:
The same playbook file improves Copilot on Monday, the panel firm’s platform on Tuesday, and a Type 1 experiment on Friday. Locked into one product, it improves one product.
If a vendor dies, triples its price at renewal, or gets acquired, a team with an external knowledge layer re-points at a new tool in weeks. A team whose knowledge lives inside the product is hostage. Renewal negotiations feel very different when the vendor knows you can leave.
This is also the answer to the authority problem in Part 2. A row-C team, no budget and a mandated Copilot, can build the knowledge layer with nothing but discipline, and it converts into leverage the moment budget arrives. It is the only AI investment available at every authority level, including none.
If the chaos scenario is the default, the alternative must be light enough to use.
One owner. A named person accountable for the team’s AI position. Not a committee, and it can be a fraction of one person’s role.
One map. Rubric 1, filled in for your team: all six doors, including the ones you didn’t open and the shadow use you suspect. You can’t govern what you haven’t listed.
One knowledge layer. One master copy: portable, owned, per above. Start with the ten documents your team reinvents most often.
One contract position. Standard AI clauses in engagement letters and panel terms: cost allocation, disclosure expectations, knowledge portability from your vendors. In-house teams are already reshaping firm behaviour this way222; use the leverage. In Australia the natural moment is the next panel refresh, when the terms are open anyway.
One review rhythm. Quarterly, not annually. Pricing models, product capabilities and the vendor map all moved materially inside single quarters in the first half of 2026318.
That’s the strategy. It contains no product name. The products are Part 1; they slot into a strategy shaped by Parts 2 and 3, never the reverse.
the asset that was never on the price list
The teams that come out of this era ahead won’t be the ones that picked the winning vendor. Nobody reliably can: the vendors disagree about which layer survives141516, and so do the big firms242526. The winners will be the ones who understood the products well enough to label them, faced their constraints, and knew their needs well enough to notice that the most important asset was never on any vendor’s price list.
You have more leverage than you think. The firms are already taking direction from clients like you22223. The vendors want your logo. And the knowledge layer, the thing that makes every product on the map work at all, is already sitting in your team’s documents and heads, waiting to be structured by the one party with no incentive to lock you in: you.
Drafted with AI on a research base I curate and verify by hand — the same discipline this article recommends. Product facts dated as at 5 July 2026; check anything load-bearing before you rely on it, which is also the advice in the article.
dated as at 5 July 2026