What I build
Three sizes, depending on where you are.
Start at the smallest thing that is genuinely useful. Each size is a real answer, not a step on a ladder you are expected to climb, and each one ends with something written down that you keep.
The three sizes
An agent, a workflow, or a system.
The difference is how much authority the thing holds and how many steps it reaches across, not how impressive it sounds.
- 01
An agent
One assistant doing one job for a team, inside the licensing you already hold. The smallest thing that is genuinely useful, and the fastest way to find out whether an idea survives contact with real work.
- 02
A workflow
An agent plus the connected steps and approvals around it. Work moves through the systems that already hold it, a person approves what matters, and the record of what happened is written as it goes.
- 03
An agentic system
Multiple agents with real authority inside real boundaries, built in your own subscription. Each has its own identity, its own bounds and its own audit trail, and the whole thing stays answerable to a person.
The method
Discover, design, build, deploy.
Four steps, each producing something you can read. Discovery that produces a slide deck and nothing else is discovery theatre.
- 01
Discover
Where the load actually sits: the workflows, the systems of record, the people. An idea that does not make a person more capable is parked, in writing, with the reason.
- 02
Design
A build specification with scope, constraints, architecture decisions and an out-of-scope list. Agentic builds carry a governance sheet before any code: each agent's role, authority, bounds and hand-back conditions.
- 03
Build
Fixed scope, tasks sized in days, a decision record for every significant choice. You can read exactly what was decided and why, months later, without asking me.
- 04
Deploy
Into your tenancy with checklists as state: environment, secrets, rollback. A ship record notes what went live and what it costs to run.
What you get
Written down, and yours.
Whatever the size, the same four artefacts arrive with it.
A build specification
Scope, constraints, the architecture decisions and an explicit out-of-scope list. Written before the build, so the thing being agreed to is a document rather than a conversation somebody half remembers.
A governance sheet
For anything agentic: each agent's role, the authority it holds, the bounds on that authority and the conditions under which it hands back to a person. Readable without being a technologist.
Decision records
Every significant choice, with the reasoning and the alternatives that were rejected. Months later you can read why something is the way it is without asking me.
A ship record
What went live, when, and what it costs to run. The running cost is a number rather than a surprise at the end of the first quarter.
Prices are not published here. The size and the shape of the work vary enough that a number on a page would be either meaningless or misleading, and it is a short conversation to give you a real one.
- Two decades of enterprise Microsoft delivery
- Federal government, civil construction, property and development
- You own the tenancy and the data
- Data resident in Australia
- A human always in command