Operate audaciously.
We help the ambitious build the technological.
We help the ambitious build the technological.
01The problem
Not because it was wrong. Because nothing was designed to make it hold. Three failure modes account for almost all of it, and none of them are model problems.
01
A tool in another tab is a tool you have to remember. Remembering is a cost, and it is paid every day by the busiest person in the room.
02
Output nobody will put their name on is output nobody ships. If a partner cannot see where a line came from, they will rewrite it from scratch.
03
The demo has clean inputs and a friendly question. Tuesday has a half-scanned PDF, a client on the phone and a deadline at four.
02The diagnostic
Stated wants for AI are almost always rational in ambition and underspecified in detail. The work of diagnosis is to trace each stated want to the structural need beneath it, and then to the constraint that explains why the need has not already been met.
These four are not alternatives. They are a sequence of maturity, and each depends on the resolution of the one above it.
| Stated want | The real need | The binding constraint | Conversation required |
|---|---|---|---|
| A bot with our context | Accurate answers grounded in our own knowledge | Where does the context live, who maintains it, and how is it kept current | Knowledge audit |
| A bot that takes actions | Automation of real workflows, not just answers | What counts as correct, who owns errors, where the boundaries sit | Process mapping and liability |
| An autonomous agent | Reduced oversight without loss of control | Trust, observability, rollback and escalation paths | Org design and change |
| An AI strategy | Confidence we are not being left behind | No specific problem yet. Fear preceding vision. | Vision before roadmap |
Clients who present with a row-three want are, in practice, almost always a row-one or row-two problem. To start where the client named is to build the roof before the walls.
Clients describe an outcome and assume the path to it is technical. In professional services the binding constraints are almost always organisational.
A large share of demand is row four: no specific problem, a well-founded fear of falling behind, and board pressure to demonstrate capability.
Followed honestly, the most ambitious want does not terminate in a product to be bought. It terminates in a single word, autonomous, and that word is the design brief for an operating system.
The Corporate Brain · Part II
03The idea
Adhesion is not a feature you add at the end. It is the thing you design for from the first hour. We borrowed the word from materials science on purpose: a bond is not the two things it joins, it is a third thing with its own properties that fails in its own particular ways. That third thing is our work.
04What we do
We do not sell a platform and we do not sell a pilot. We sell the sequence that gets a thing into daily use and keeps it there. Each stage has a fixed price and a written output. You can stop after any of them.
01
Two weeks inside the work. A written map of where the hours go, which a machine can carry, and which are judgment you should never automate. 2 weeks, fixed fee.
02
Interfaces, citations, escalation paths and refusals. We specify what the system will decline to answer as carefully as what it will. 3 weeks, fixed fee.
03
Into your stack, against your data, with your security team in the room from week one. One workflow all the way through. 6 to 12 weeks.
04
Training, adoption tracking, and sitting next to people while they use it. This is where the bond forms, and the stage most programmes cut. Ongoing.
05How we work
We will not quote you for a twelve-month programme on the first call, because on the first call neither of us knows enough to make that number honest. We start with two weeks. If the map we hand back is wrong, you have lost two weeks and we have lost a client, which is the correct distribution of that risk.
01
One call. What returns every week and what it costs you.
02
Two weeks inside the work. A written map, whether or not you hire us again.
03
Into your stack, with your security team, one workflow all the way through.
04
We sit beside it while the bond forms. Usually the longest stage.
06The thesis
A brain is not a single faculty. It is many faculties, separated and coordinated. So is a firm that thinks. Everything above is the practice; this is the argument underneath it.
One call, thirty minutes, no deck. If we are not the right people we will say so and point you at who is.
Start a conversation