AI transformation
Hierarchy is a routing protocol. Yours is the bottleneck.
A leader holds 3 to 8 people in their head. That limit is why you have layers, and every layer costs you a day. We do not bolt a copilot onto the chart. We replace what the layers do.
The argument
The Roman army sized a unit around what one commander could hold. The railroads drew the same shape on paper. Every company since has inherited it, because until now nothing else could route the information.
A model can. Once your own work is machine-readable, the context a manager relayed is held continuously and handed to whoever needs it. The layers that existed to carry it stop earning their latency.
The argument above follows Jack Dorsey and Roelof Botha, “From Hierarchy to Intelligence” (March 2026). We practise it; we did not originate it.
What is left is the edge: the people who touch reality, make the calls a model should not, and feed back what it cannot yet see.
What we build
-
Diagnostic
We name your hard-won understanding — the thing competitors cannot buy or copy — and measure whether it is deepening or flat. If nothing qualifies, we say so and recommend against the rest.
-
Company world model
Your decisions, code, designs, plans and blockers become one continuously updated picture of what is being built, what is stuck and what is working. This is the information your management layer carries today.
-
Capability map
We separate the atomic things your business can do from the products you ship. A capability has reliability and compliance targets, no interface, and no roadmap of its own.
-
Intelligence layer
The composer recognises a moment in a customer's reality and assembles capabilities into a response before they ask. Every composition it cannot complete is a named gap — and that list replaces your roadmap.
-
Edge re-org
You normalise to 3 roles: individual contributors who own a layer, Directly Responsible Individuals who own a problem, and player-coaches who own craft and people. The permanent middle layer retires.
Why it compounds
A copilot makes each person faster once. The gain lands, then stops. It leaves the chart, the layers and the latency exactly where they were.
A model that reads your own operations gets better every day you run it. The signal feeds the model, the model routes the work, the work produces more signal. That is the only part of this that compounds.
What we refuse
- Engagements framed as headcount reduction. If the goal is cost, we are not the firm. Cutting people from a hierarchy leaves you a smaller hierarchy.
- Copilot rollouts with no world model underneath. That is a productivity purchase. It improves the existing structure slightly and changes nothing about how work is routed.
- A re-org before the model exists. Remove a management layer while information still routes through people and you break the company.
Products
We run what we recommend. Each product below is a working business built on the model we sell — capabilities composed for a customer moment, not a roadmap.
Start here
Four weeks to an honest answer.
The diagnostic ends in a written answer, a map of where your information routes through people, and a measured latency for 3 real decisions. If the answer is that nothing here is hard-won, we tell you and we stop.