Case Studies
The thinking behind the delivery.
Illustrative engagement patterns — anonymised composites of how we approach hard delivery problems, written for people who appreciate depth. Named, client-attributed studies will follow as engagements complete.
The architecture wasn’t the problem. The decisions were.
Hundreds of capable people agreed on architecture diagrams while quietly disagreeing on ownership. A multi-year commerce transformation that turned out to be a decision-architecture problem, not a technology-selection one.
Conceptual composite · AI engineering & knowledgeThe demo worked. Production couldn’t trust it.
The demonstrations were impressive. Then production asked what the system could see, what it could do, and whether anyone could prove what happened. The model was never the constraint — trust was.
Anonymised · Transformation programmeThe pilot nobody could stop
It was successful enough to continue but never successful enough to justify scale — and nobody wanted to stop it. How a pilot drifted into a programme without a deliberate decision at any transition, and the evidence gates that broke the spell.
Anonymised · Enterprise transformationEverybody owned the outcome. Nobody owned the boundary.
Every team optimised its own platform successfully — yet customer issues kept appearing at the seams between them. The architecture looked coherent on slides; the ownership model between the boxes did not exist.
Conceptual composite · AI engineeringThe team bought better models. The results barely changed.
Every model upgrade promised better reasoning, larger context, stronger coding. Generated output went up; accepted output didn’t. The improvement, when it came, was in the environment around the model — not the model.
Anonymised · Knowledge & contextThe transformation had data everywhere and knowledge nowhere.
Documents, wikis, spreadsheets, tickets, emails — information existed everywhere, yet people kept asking the same questions. The problem was never storage. It was trust: which information deserved it.
Illustrative pattern · CommerceRe-platforming a complex buying experience
An illustrative engagement pattern: moving a high-traffic buying journey to a composable, headless architecture without a big-bang cutover.
Application Modernisation · Engineering softwareFrom a server per customer to one elastic platform
A legacy single-tenant monolith — a dedicated, always-on server for every customer — modernised into an elastic, multi-tenant cloud platform. New-customer setup fell from ~4–5 days to 1–2 hours, and run-time infrastructure dropped by roughly 85–90%.