Four systems, four different reasons they were hard.

Context, constraints, architecture, outcome. Client names are withheld where I am under agreement; everything else is as it was built.

01US healthcare providerArchitect

A contact centre with no data centre

Cloud-native contact centre for a US healthcare provider, architected from an empty AWS account: routing, self-service, agent desktop, and the boundary that keeps patient data out of the parts that should never see it.

Amazon ConnectAmazon LexAWS Lambda.NET CoreReact

Read the case study

02ConfidentialArchitect

Campaigns that decide in milliseconds

A real-time campaign engine: evaluate a customer against every live campaign, decide, and answer before the page finishes rendering.

.NET CoreEvent streamingDistributed cacheReact

Read the case study

03ConfidentialFrontend architect

The front door to identity

Registration, authentication, and self-service built on ForgeRock — a Next.js front end driving a journey engine that was never designed to be pretty.

Next.jsTypeScriptForgeRockOIDC

Read the case study

04Authority PartnersLead

Tooling that writes the boring half

LLM-backed developer tooling for code generation, tests and documentation — plus the company-wide rollout that got engineers actually using it, and the working method I now build my own products with.

LLM APIsAgent orchestration.NETTypeScriptAzure

Read the case study