Selected work
Difficult systems, understood in context.
Each engagement begins with the organisation and the constraint. Technology follows from that understanding.
The night World Sailing took back its digital estate
Every website, API and member record lived in a supplier’s cloud account — until a five-week rebuild and a single two-hour window brought it all home.
Four new platforms, one 2008 database, and no big bang
An ERP holding 8.9 million stock movements since 2006 was still working perfectly — and quietly capping everything the business could do next. Replacing it was unthinkable. So we built around it instead.
Seven websites, eleven people, one error in 3,500 orders
Behind a £2m footwear retailer sat an operating system built from inside the business — repricing thousands of products daily, forecasting two years ahead and running a warehouse that hardly ever made a mistake.
50,000 members, 18 championships and no simple entry form
A championship entry looks like a form. In reality, it is a live decision about identity, membership, eligibility, consent and payment — made across countries, organisations and changing rules.
Three groups, fourteen questions, and a rulebook that runs itself
An Olympic sport's eligibility regulations became a versioned, executable ruleset — deciding the clear cases instantly and saving the review commission for the arguments only humans can settle.
Securing a public API without changing a line of its code
A live public data API needed keys, rate limits and per-consumer metering. The legacy application behind it could not safely change — so authentication moved to the network edge in front of it.
Tell us what is becoming difficult.
You do not need to arrive with a technical specification. A description of the organisation, the problem and what is currently preventing progress is enough to begin.