Essay 01 · The Thesis · 12 min read

The AI-native practice belongs to whoever has the least legacy to defend.

A directory now tracks a few dozen firms rebuilt around AI. That number is going to look tiny very soon - and it will not stay confined to private practice.

Before you read on

This is the thinking behind how we build. For what we actually build and what it costs, see Services.

6

Primitives that describe every legal organisation

2

Tracks - AI-Native Transformation or AI Adoption

7

Markers of an AI-native practice

4–8

Weeks per transformation, on average

There is a quiet assumption running through every conversation about AI and law: that the organisations best positioned to go AI-native are the biggest ones - the ones with budget, an innovation team, a Chief Innovation Officer, a line item for "legal technology." It is backwards.

The practices actually rebuilding themselves around AI are not BigLaw. They are solo lawyers, independent shops, and lean in-house teams doing fixed-fee or fixed-scope work with automated intake and same-day turnaround, quietly profitable or quietly efficient, quietly growing their capacity without growing their headcount. Two years ago the category barely had a name.

The fixed sequence, both tracks

01

Name

Each of the six components the method tracks gets translated into how this specific organisation actually talks about its own work, then written down. Where something is missing gets marked, not criticised.

02

Systematise

Templates, playbooks, role charts, deadline structure. Built so the organisation would keep running cleanly even if every AI tool vanished tomorrow.

03

Automate

Only now do agents deploy - on the primitives already named and systematised, inside MatterOS, LexOS, a custom build, or market software.

Why the largest institutions structurally cannot

BigLaw's entire economic model runs on leverage: partners at the top, a pyramid of associates underneath doing the billable hours that make the partnership profitable. The associate is not just labour. The associate is the product's margin. Large in-house departments and government legal functions have their own version of the same structure - layered sign-off chains, procurement cycles, and headcount models built for a world where legal work scaled with lawyers, not with systems.

Now look at what AI actually automates first: document review, first-draft contracts, research memos, due diligence summaries. That is not a random list. It is, almost exactly, the list of things junior lawyers and paralegals spend most of their time doing. Every hour AI removes from that stack is not efficiency from a leverage institution's perspective. It is revenue - or headcount justification - that the existing model has no way to recapture.

A managing partner who fully automates the associate layer is not modernising the firm; they are dismantling the machine that pays for the building.

This is not a willpower problem, and it is not a technology problem. It is structural - and a partnership of three hundred people whose personal income depends on the current model does not vote against its own equity. A government legal department bound by procurement rules cannot decide on a Tuesday to rebuild its intake process. Both produce the same outcome: pilots, committees, and press releases. Motion without movement.

Why independent firms and lean teams structurally can

A solo lawyer, a five-person shop, or a small in-house function has no pyramid to protect. There is no leverage model extracting margin from junior hours, because there often are no junior hours. The constraint has never been headcount politics. It is time - a handful of people, and more work than the hours can hold.

That flips the entire incentive structure. Where automated hours threaten a leverage model's revenue, they expand a lean team's capacity directly: another matter taken on without hiring, an evening returned, a practice or department that scales without its people scaling their exhaustion alongside it. Identical technology, opposite economics.

Independent practices and lean legal teams hold three quieter advantages, rarely named:

  • Decision speed. A solo lawyer, or a general counsel with real authority, can decide to publish fixed pricing - or fix a broken intake process - on a Tuesday and have it live Wednesday. No committee, no pilot, no change-management consultant.
  • Nothing to unlearn. No twenty years of custom configuration, no support staff trained on the old workflow. The absence of legacy infrastructure, long treated as a disadvantage, is now the edge: there is nothing to migrate, nothing to sunset, no sunk cost voting against the rebuild.
  • Proximity to the work. Independent firms and lean in-house teams sit closest to the actual matters - the exact vantage point most punished by hourly billing's uncertainty or by manual triage, and most rewarded by a fixed price and a fast turnaround.

What "AI-native" actually means

The label gets thrown around loosely, so precision matters. The cleanest way to define an AI-native practice is not by the technology it runs but by what its clients or stakeholders experience, because the operating model becomes visible there first. Seven characteristics recur:

  1. 01Pricing or budgeting is transparent, not open-ended.
  2. 02Intake is automated end-to-end.
  3. 03The organisation meets clients and stakeholders where they already are.
  4. 04AI runs first, on every matter, systematically.
  5. 05The organisation gets measurably better over time.
  6. 06Turnaround is fast - often same-day.
  7. 07Technical capability sits inside the organisation.

The line that separates AI-native from AI-augmented is systematic versus incidental. An organisation where lawyers occasionally paste a document into a chatbot when they remember to is not AI-native, no matter how many licences it bought. An organisation where every matter, every time, gets an automated first pass before a human ever touches it - reviewed, corrected, and taken responsibility for - is running a different operating model entirely.

Not every organisation can make the full trip

Here is the part most essays on this subject skip. A three-hundred-partner firm, a regulated government legal function, or a decades-old in-house department carrying real institutional constraints usually cannot rebuild itself into the picture above, in full, on any realistic timeline. That is not a failure of ambition. It is the same structural reality this essay opened with, just applied honestly. Pretending otherwise is how AI-transformation engagements turn into slideware.

That does not mean the underlying method stops applying to firms of any size. It means the destination differs. A practice with no legacy pyramid to protect can rebuild pricing, intake, and delivery from zero and reach full AI-nativity. A larger or more constrained organisation can still name its primitives, systematise the ones it controls, and install AI as a systematic - not incidental - layer inside its existing structure. adnah calls the first path AI-Native Transformation and the second AI Adoption. Both start from the same audit. Both run the same sequence - name, then systematise, then automate. They differ only in how far the rebuild can honestly go, and we say which one applies to you before any work begins, not after.

AI-Native Transformation

Who it's for
Solo practices, independent firms, lean in-house teams, legal aid organisations - anyone with no legacy pyramid to protect.
What happens
Pricing, intake, and delivery are rebuilt from zero. Full AI-nativity is a realistic, honest destination.
Typical timeline
Typically four to eight weeks.

AI Adoption

Who it's for
Large firms, in-house departments, and government legal functions carrying real sign-off chains, procurement cycles, or partnership economics.
What happens
The same six primitives, named and systematised, installed as a systematic layer inside the structure that already exists.
Typical timeline
Typically six to ten weeks, given approval cycles.

Quick self-check

Does one person, or a small group with real authority, control your pricing and intake - and could they change either this week without a committee? If yes, you are likely AI-Native Transformation territory. If a change like that would need sign-off, procurement, or a vote, you are likely AI Adoption territory. Either way, the AI Readiness Audit gives you a scored answer in two minutes.

The wave is not staying confined to private practice

Right now the category numbers a few dozen tracked firms. It will not stay a few dozen, and the reason is a pattern that repeats every time a services industry meets a genuine infrastructure shift: a founding cohort proves the model works, the model gets documented, and the constraint on growth stops being invention and becomes adoption. Most of the firms actually doing this today are bootstrapped, not venture-funded - an operating model, unlike capital, is replicable by anyone willing to install it.

The same operating model - systematic first-pass AI, measured improvement, transparent economics - maps directly onto in-house legal departments drowning in contract volume, onto government legal functions with fixed budgets and unfixed demand, onto legal aid organisations that have always had more need than capacity. Everywhere legal work is done under resource constraint, which is everywhere, the model applies. Some of these organisations will reach full AI-nativity. Most will run AI Adoption instead. Both are the actual opportunity - not "can a lawyer use ChatGPT," but what a rebuilt operating model looks like for this specific organisation, and how much of it can honestly be installed.

Where adnah fits

We are not a software vendor. We do not sell dashboards. We are a studio that builds the operating model above into legal organisations of every size - solo practices, small and mid-sized firms, larger firms ready to run AI Adoption honestly, in-house legal departments, and government legal functions - piece by piece, in the specific order the sequence requires.

The sequence is fixed: name the primitives, systematise them, then automate. Most of the profession is currently running that sequence backwards, which is how you get expensive chaos at higher speed. Our job is to run it forward, with you, in weeks rather than years - typically four to eight, occasionally up to ten for a larger or more constrained organisation. Read the full process on how a transformation actually runs.

You cannot bolt AI onto chaos and get anything but faster chaos.

The old assumption was that AI-native belonged to whoever had the biggest budget. The actual answer is the opposite: it belongs to whoever has the least legacy structure to defend - and everyone else can still be transformed, honestly, within the structure they actually have. Right now, one of those two is you.

Next step

See the six primitives, one at a time.

Book a call