LegalFabSeries A
The layer beneath the firm’s applications
DocumentsMattersLedgerClients CounterpartiesRelationshipsExperienceEvery judgement, over decades
And yet — it cannot answer a question about itself.
What a firm owns

Every law firm owns almost everything it needs to know about itself.And yet ask it a question that crosses those things — a real questionabout itself — and in most cases it cannot answer.

Rented — the understanding
ExperienceClient relationshipsDocument search Financial truthRisk position
each assembled inside a system the firm licenses
Owned — the raw material
DocumentsMattersLedgerCorrespondence Everything the firm has ever done
Why

Not because the information is missing.Because the understanding of it does not belong to the firm.The firm owns the raw material. It rents the understanding.

Conflictssees conflicts
CRMsees contacts
Experiencesees matters
DMSsees documents
Financesees the ledger
Each vendor assembled the world it could see
And the boundary of the product
became the boundary of the intelligence.
And it was rational

For thirty years that was rational. The problem was genuinely hard,so firms bought applications that each assembled one part of the truth.Each vendor assembled the world it could see.

One agent · one task
DMS→Practice mgmt→Finance→ CRM→Email→Outside world
Who governs that agent?
Why now

Then firms started deploying agents that perform work.And the moment an agent performs real work, it stops livinginside one application.

The document vendor cannotit does not own finance
The finance vendor cannotit does not own the documents
The CRM vendor cannotit does not own the matter system
The model provider cannotit does not know the firm’s rules
Nobody owns the whole path.
So nobody owns the governance of it.
The gap

Which creates a problem the industry has not solved.

You cannot govern
what you have not resolved.
The reason

You cannot enforce a wall around a client who exists as six identitiesacross six systems. The enforcement layer everyone now needssits on a resolution layer nobody built.

REL. PARTNERFOR_CLIENTADVERSE_TOHAS_DOCPRACTICEBILLEDMeridianJ. WhitfieldCFL-48213M&ANorthgateEng. letterWIP £48k
One client, resolved across the estate — with the relationships that no single system holds.
What we build

So we resolve the firm. Not documents about the client —the client, the partner, the matter, the adverse party, the bill,and the relationships between them that no single system holds.

ENTITLEMENT REFUSED · NOT TRAVERSABLE One resolved firm SOURCED · GOVERNED · REPRODUCIBLE EVERY TRAVERSAL LOGGED COMPOSE ↓↑ OBSERVE & REPLAY Agentic StudioPLAIN LANGUAGE · NO CODECONFLICTS · COMPLIANCE · PRICINGBUILT BY THE FIRM GATE · PROPOSE, THEN DISPOSE Resolved entitiesGoverned accessLineage & replayContinuous monitoringConflicts & intake READS · GOVERNED WRITE-BACK ① NOTHING ENTERS UNENTITLED   ② NOTHING ACTS UNGATED DMS ACLCRM ACLPMS ACLREGISTRY ACLFINANCE ACLCONSOLIDATED MODELINHERITED ACLs ARE THE FLOORSTRICTER, NEVER LOOSER The estate,resolved in place.Every system stays where it is.CONNECT, DON’T COPYRESOLVE IN PLACE · NO RAW EGRESS
Governed

Resolved in place. Every system stays where it is.Inherited permissions are the floor and can only be made stricter.Nothing enters the graph unentitled, and nothing acts on it ungated.

14 May
NetDocuments
Legal Context Graph
six days
20 May
iManage
Context Fabric
Two incumbent vendors. One week. The same conclusion.
The market agrees

And the market is arriving at the same conclusion.

The incumbent · top-downApplications firstApplicationsIntakeConflictsTermsWallsComplianceThe existing estateEliteAderantiManageSalesforceDBsEmailShared data · integrations · orchestrationGovernance sits inside each application — nothing enforces across the estateThe firm converges on the suiteCapability arrives as the next applicationReach stops at the edge of the suitenot reachedUnify by expanding the suiteLegalFab · bottom-upEstate firstApplicationsConflictsBDPricingDeliveryCompliance…The existing estateEliteAderantiManageSalesforceDBsEmailAgentic Utilities — capability on the shared layerAgentic Studio — agents inherit that governanceGovernance layer — walls, permissions, lineage, auditKnowledge Fabric — resolve entities in placeDiscover and catalogue the estateUnify beneath the suite
Both columns hold the same applications and the same estate. Only the starting end differs.
The difference

But an application vendor unifies by expanding the application.We do not require the firm to converge on us. We converge on the firm.

$5.74bn
Feb 2025
$3.3bn
today
Down 42%And still growing. 142 clients still pay more than $1m a year. A healthy incumbent can grow while the market changes its mind about which layer is valuable.
That is what repricing looks like.
The economics

You can already see it in the capital markets.

Kirkland & Ellis · build
$500mover three to four years
180+AI engineers and data scientists
250attorneys involved
Palantirat the centre of it
LegalFab · buy
We productised the foundation.
Kirkland can spend half a billion dollars building one.
Almost nobody else can.
Build or buy

And in what the largest customers are doing about it themselves.

A licensed application
Its own data model
Its own store, and a migration
Its own permissions and audit
Its own search
Its own integrations
Its own interface
Configuration to approximate this firm
The judgement that does the work
Eight layers. The firm needs one
A utility on a resolved estate
Its own data model
Its own store, and a migration
Its own permissions and audit
Its own search
Its own integrations
Its own interface
Configuration to approximate this firm
The judgement that does the work
One layer. The other seven are the substrate
Why building changes

Because once the foundation exists, the economics of software reverse.Seven of the eight layers already exist. What remains is the judgement.

01LandOne high-value workflow
02ResolveThe foundation gets built
03ExpandThe next one is weeks
04EmbedGovernance moves in
05TravelCapability, not data
06CompoundThe next firm starts further along
One workflow in. An operating layer out.
How it compounds

Which turns wedge, moat and flywheel into one chain,where each link is the reason the next one exists.

1
2
3
4
5
6
7
8
9
10
11
12
15
20
30
40
50
The reference setEach won partly on the ones before it
Ten firms have built on the foundation. The eleventh does not start from zero.
The first ten

Legal is concentrated and referential. Every firm that adoptslowers the risk for the next. But for us the first ten are not ten contracts —they are the reference set for an architectural decision.

Firm sizeSmall15%Large45%Massive40%Product depthAgentic utility35%Full end-to-end65%Practice typeNiche25%Full service55%Consulting20%GeographyLocal20%Regional35%International45%Route to marketDirect40%Via partner35%Managed service25%
Seven engagements, chosen so that no structural axis is unvalidated before scale.
Chosen, not collected

Which is why the seven are what they are. Different sizes,different practice types, different geographies, different routes to market.

LAYER 3 · UTILITIESLAYER 2 · AGENTIC STUDIOLAYER 1 · KNOWLEDGE FABRICSOURCE SYSTEMS · IN PLACEPractice MgmtDMSFinanceCRMRegistriesOSINTresolve in place → one governed knowledge stateLawyer gateclearancefee-earnerConflictsIntakeMatterComplianceBD IntelPricingMatter MgmtResourcing+ yoursDISCOVER · RESOLVEGROUNDENRICH · GOVERNEDCOMPOSE · RUNevery matterenriches the Fabric
What already exists

And we are not standing here with a diagram asking you to financethe experiment. Foundation, execution layer, applications.Built, certified, and in production.

For the first time, a firm can own not only its data
— but what its data means.
The market has started moving toward it.
The incumbents have started moving toward it.
The largest firms have started building versions of it themselves.
And we already have it running.

The assistant is the visible part. The strategic asset is underneath it.

Move the pointer for controls · space to play
00:00