← All services
03 / 06 · Function brief

Legal.

Keep the alpha. Rent only the capability.

Position

A no-training clause solves privacy, not competition. Rent capability; never rent the layer that holds your judgment.

The business case

Keep the alpha. Rent only the capability.

Legal AI is good enough now that the interesting question moved. It is no longer whether to adopt, it is what you hand over on the way in. Three moves:

01
Name the alpha, then fence it

Your positions, your fallbacks, your precedent, and the reasoning that produced them. That is the asset a vendor cannot sell you and a rival cannot buy. It stays on compute you control, by architecture rather than by clause.

02
Build the ontology before the tooling

Matter types, clause taxonomy, party roles, risk severity, escalation thresholds, written once, versioned, and readable. These are the deterministic levers: they bind every model, every vendor, and every replacement for both, and they survive the tool that is fashionable this year.

03
Own the harness, rent the model

A routing gateway with a hard floor: privileged work sealed to local inference, anonymised lanes for the hard non-privileged minority, citations verified character by character, every call in an append-only log. Harvey, Legora, and the frontier labs plug in behind it, and can be swapped out on a Tuesday.

The operating model

The harness is yours.
The models are rented.

Your perimeter · EU-resident
Counsel in command
01
Intake
02
Classify
03
Route
04
Draft & review
05
Attest & log
Your legal ontology · matter types & clausesPrivileged corpus · retrieval on local computeHard tier floor · privileged work cannot route outAn audit trail your GC can sign
The sovereignty line
↓ Only what may leave

Public-law research and bounded, anonymised drafting. The classifier decides, not the person in a hurry, and a privileged matter is refused rather than warned about.

↑ Work product back

Reviewed by counsel, logged against the matter, citations verified character by character before anyone relies on a word of it.

Interchangeable suppliers, behind your line
HarveyvendorLegoravendorClaudefrontierMistralfrontierOpen weightslocal

The point is not that vendors are bad. It is that they should be replaceable. When the ontology, the routing rules, and the log belong to you, a supplier is a supplier, and your GC can still tell a court exactly where every privileged document went.

The signal

What's actually
shipping.

Harvey reached an $11B valuation with customers running more than 25,000 custom agents that, in its words, “run workflows from start to finish.”

Harvey

European-built Legora (Stockholm) raised to a reported $5.6B valuation as “the AI operating system for the legal industry”, agents running end-to-end legal workflows.

Legora

OpenAI's Hebbia case study is titled, plainly, “Automating 90% of finance and legal work with agents.”

OpenAI

The LegalQuants community maintains an open-source engine and assistant that run against models you choose, seal privileged matters to local inference by architecture, and verify every citation character by character.

LegalQuants
Engagement scope

Legal AI works, so the question has moved. It is no longer whether to adopt, but what a legal department gives away when it does. We help General Counsel and Legal Ops separate the capability that can safely be rented from the judgment that cannot, then build the two things that keep them in control of both: a legal ontology of their own, and a harness that decides where every matter is allowed to run.

  • 01Name the alpha: the matter types, positions, and playbooks that never leave
  • 02Your legal ontology: matter types, clause taxonomy, party roles, severity, escalation
  • 03The harness: routing with a hard floor, verified citations, an append-only log
  • 04Privileged retrieval in-house, on local compute and open-weight models
  • 05Vendor and frontier due diligence, with an exit that actually works
Where the software lives

The same stack, pointed at an in-house team's work.

A legal department runs a privacy programme, an AI register, a vendor file, and a negotiation queue, and every one of them is a place where your positions get encoded. We build and operate these as todo.law: self-hostable, deterministic by default, with the Donna assistant only where you switch it on. Read the code, run it on your own infrastructure, or have us run it for you.

DPO CentralAI SentinelVendorWatchDealroomDonna · LQ.AI
Open todo.law

Open source (AGPL for the practice apps, Apache-2.0 for the assistant). Read the code before you trust it, run it yourself, or have us run it.

Working session

Bring us one
legal
workload.

In one 90-minute working session we map it across the frontier-sovereign axis, cost, risk, and strategic value. Then we tell you what we'd do.

Request this research

Working-session request