The method
One person. One agent. Bounded authority. Full audit. Then multiply.
I do not automate processes. I amplify roles. The unit of transformation is a single person and a single agent, inside a policy envelope, on rails the organisation owns. Prove one, then multiply.
The turn
Transformation starts with someone
Enterprise AI fails at the process and succeeds at the person. Processes do not adopt AI. People do. So transformation does not start with a system. It starts with someone.
I find the person carrying the load, make their work verifiable, and only then delegate part of it to an agent that stays inside their authority.
The formula
Transformation = Σ ( Role × Agent )
Every amplified role is one unit: a person, and an agent scoped to a slice of what that person does, inside a policy envelope, on rails the organisation owns. Add the units up and you get transformation you can audit, not a platform you have to trust on faith. The first role I am building as a product is the community manager: The Amplified Community Manager, the first of the Amplified Role family.
Eight rules that decide what I will and will not build.
The doctrine
- Processes do not adopt AI. People do. Put the agent inside the role.
- Make work verifiable, then delegate it.
- Amplify the person. Instrument the workflow. Recompose from evidence.
- Automation takes tasks. People take command.
- Authority is delegated, bounded, auditable and role-scoped, or it is not delegated.
- Delete artefacts. Never digitise them.
- Bold outcomes require conservative scaffolding.
- Protect persons, not positions.
The climb
An agent earns autonomy. It does not start with it.
Every workflow moves up a ladder, and only when its verification arrives.
- 01
ASSIST
The agent prepares and suggests. The person does the work, and every suggestion is checkable against it.
- 02
AGENT IN THE LOOP
The agent carries the task. The person approves what matters before anything leaves the room.
- 03
ARTEFACT DELETED
The intermediate artefact goes. The agent works from the system of record, and the record writes itself.
- 04
DOMAIN AUTONOMOUS
Inside one bounded domain, the agent acts under its delegated authority, with the hand-back conditions written first.
- 05
THE CAPTAIN
The person commands a set of agents across domains. Judgement stays human; the grind does not.
A workflow ascends the moment its verification arrives. Never before.
The measure
The measure of every build
There is one test I apply to everything I ship. Did this make the person more capable? If the answer is no, it is parked, in writing, with the reason.
See where this fits your team.
Tell me where the week goes and I will tell you honestly whether this is worth building. If it is not, that is a useful answer too.