Expertise Without Permission

Three companies. Two refusals. One AuDHD diagnosis. The prologue — why this book exists.

You don't learn to handle emergencies during emergencies. I built my entire first domain in a simulator — and what came out of it wasn't just expertise. It was the first Office.

A degree earned in 2015 has the same value in 2026. A case archive built in 2015 has ten times the value it had in year one. The permission economy rewards the wrong asset.

Your best person is your biggest risk. The knowledge that makes your team valuable is stored in one place — a human being who can resign, retire, get sick.

What actually leaves when your expert resigns. Not the person. The methodology they never documented, the exception they handled without a record, three years of regulatory interpretation stored only in their head.

Organisations evolved through seven stages. Each was a breakthrough. Each created a limitation. The eighth — Forest Green — solves the one thing none of them could: making capability permanent.

The three-layer architecture of a Permanent Role. What each layer does, why all three are required, and what breaks when you remove any one of them.

Building C is up 12% this month. Without the expert, you do not know if this is a problem, what caused it, or what to do about it. That is not a data problem. That is a knowledge problem.

In 2017, I defined the problem: the cascading replication of competencies. In 2026, we built the machine that solves it. An expert sits down for thirty days. An Office stands up forever.

The step-by-step process of converting fifteen years of expertise into a live Office. What happens in each week, what the pipeline produces, and what the expert reviews.

Software can be cancelled with a click. A brass plate on the wall cannot. Why the physical ecosystem is the moat that makes a Permanent Role genuinely permanent.

Two people. 290,000 lines of code. 289 database tables. One platform. No engineering team. No CTO with a Stanford degree. No seed round. The pattern that became the product.

70% of your specialist's time does not require specialist judgement. The 30% that remains is what you are paying for. Here is how to get more of it.

A GRI certificate did not help. Twelve months manually. Two to three weeks on the platform. The first proof.

The origin of the domain expertise. How a two-person firm acquired enterprise clients — and what 500 buildings taught about compound knowledge.

90 days. Positive ROI from week eight. Then scale with your own data.

Not a disability. Not a superpower. A different operating system — that runs extremely well in specific conditions.

The alternative path from the inside. No degree. No consulting background. AuDHD. And a system that outperforms credentialled practitioners — through architecture, not talent.

The full journey on one page. From a failed experiment in self-management to the infrastructure that makes capability permanent.