An Industry BriefingLEGAL & COMPLIANCE

Moat.
Speed.
Allocation.

The platform moat that survives 2028 is being chosen this year.

This briefing tells you which platform moats survive 2028 in legal and compliance as AI rewrites build economics. Read it before your R&D allocation locks for the decade.

GRAIL 2026 10-page briefing
Read more ↓
GRAIL industry briefing on AI in legal and compliance for CPTOs.
Get the briefing

The 10-page briefing. Worth 20 minutes.

One email. One PDF. Worth twenty minutes of your week.

Check your inbox. Your briefing is on its way.

We send it once. Work emails only.

Monday 9:15, management committee pre-read. The Thomson Reuters renewal is on the managing partner's desk. Fourteen months until the contract lapses. Protégé upgrade bundled. Harvey's enterprise team emailed Friday about a new data-rights clause in the Q2 refresh. The senior partner who ran the firm's largest M&A book for fifteen years retires in Q4. His methodology sits in three conference-room conversations and an iManage folder.

You are not running one technology function. You are running two, and only one is on your committee scorecard. One funds what you already run: Thomson Reuters, iManage, Kira, Harvey licences. The other funds what has to exist by 2028: data rights you have not renegotiated, a model-agnostic memory store you have not built, methodology-IP walking out the door with every partner retirement.

The moat that matters in 2028 is not above the model layer. It is underneath it, in the methodology your partners carry and your closed-matter files encode.

This is the question your managing partner is about to ask. The briefing below is what you want in your hand before the next renewal.

Capital Allocation. Build Velocity. Product Defensibility.

Three questions every legal CTO and CPO is tracking. The third is the crux. The first two are how you earn the right to answer it.

01 · R&D Capital Allocation

Is our technology budget one instrument or two?

One funds the existing stack at lower cost. The other builds the methodology-IP moat that survives Harvey, Protégé, and partner retirements. On one renewal cycle the first wins every quarter. On one scorecard the second does not exist.

The CTO who walks in with one budget runs the same programme every peer firm is running.
02 · Build Velocity

Is our review discipline holding on Harvey output, or are we shipping drafts we have not actually read?

Harvey adoption at seventy percent. Cycle time flat. Partners edit first-pass AI drafts for ten minutes and sign. Citations unverified. Mannheimer Swartling spent four years on the foundation that lets Legora ship cleanly.

Buy what the tool layer can carry. Own the review bar that makes it safe to ship.
03 · Product Defensibility

What does our firm do that a Harvey plus a good paralegal cannot copy?

Your drafting edge commoditises every eighteen months when the next foundation model rolls. Your closed-matter corpus, your partner methodology, and your data-rights clauses compound. The methodology that priced your senior partner's last three deals sits in his head and a folder named after him.

The moat sits underneath the model layer. The window to encode it is eighteen months.
Inside the briefing

What you get when you download

An 11-page report for CTOs, CPOs, and Heads of Innovation at mid-size European law firms and compliance advisory practices. Designed to be read in one sitting before your next management committee.

Inside the Briefing · Chapter 1

Your industry, your technology function, and why they are one problem

What is happening to mid-size legal and compliance: AI-natives absorbing the drafting layer, reference platforms absorbing their own layer, corporate clients going in-house on Spellbook. What is happening inside your function: Harvey adoption up, cycle time flat, the KM graph organised for human search not agent consumption, and the committee AI-strategy ownership question. And the intersection: same force, three altitudes, one problem.

The vocabulary to name the shift before the Thomson Reuters renewal lands on the committee desk.
Inside the Briefing · Chapter 2

Four moves across build engine, platform and data, product thesis, and R&D bench

Redesign review discipline on Harvey-generated output with eval harnesses and stakes-tiered sign-off. Build the methodology moat underneath the model layer through data-rights redlines, a closed-matter corpus memory store, and an integration depth graph. Stand one fixed-fee practice line on protected P&L. Rebuild the junior pipeline around legal-engineer hybrids.

One concrete move per sub-function, starting this quarter.
Inside the Briefing · Chapter 3

Five questions for your next management committee

Is your technology budget one instrument or two, and what is the kill criterion on each? Name the AI-native platform in your practice area. How many months to reconstruct the methodology behind the last three major matters if your senior partner retires? Where did the freed hours from Harvey adoption go? Is your Thomson Reuters redline for data rights and audit logs written?

Where your technology and legal leadership cannot agree, that is the hour on the agenda.