The practice — arc, method and credentials

The practice

I build software end to end — data, services, agents, interface, deployment.

For a decade that meant client and agency delivery: high-traffic sites for tourism operators, an international airport, a botanical garden. The work was rarely about the platform underneath it. It was scheduled synchronisation against a CRM, two flight feeds at different cadences resolved into one board.

Then products of my own — an assistant that turned scattered notes into structured projects, a purchase-decision tool built on live research instead of access to anyone's bank account. Then agents, which is where the work has been going since.

Agentic systemsAn orchestratorhanding work tospecialists,contexts keptnarrow, destructiveactions guardrailedaway from themodel.Product and platformProducts of my own— an assistant thatstructuresscattered notes, apurchase-decisiontool built on liveresearch, agentsthat draft insidethe WordPresseditor.Client deliveryOver a decade ofhigh-trafficplatforms: tourismoperators, aninternationalairport, abotanical garden.

One thing recurs across all of it. Narrow the context, split the concerns: an orchestrator handing work to specialists rather than one agent holding every tool, a content agent kept apart from the agent that chooses the interface, destructive actions kept away from the model entirely. The guardrails live in the code around the model rather than in the prompt inside it: what an agent cannot reach, it cannot get wrong.

Credentials