Richard.

Desemax · Engineering case studies

Four pieces of work, written the way an engineer would want to read them.

Each one names the decisions that mattered, what they cost, and what was measured. Clients are withheld. Each comes as a full PDF and a one-page summary.

01 Case study · Real-time voice AI

A voice AI platform in production. One engineer.

An AI assistant answering phone calls, WhatsApp and web chat, live in sixteen production deployments. The architecture, and the four decisions that mattered.

Real-time voice · LLM · TypeScript · Laravel
Headline figure
16 deployments
phone, WhatsApp, web chat · 8 regions
Full case study (PDF) One-page summary (PDF)
02 Case study · Query performance

928 queries per page, down to 36.

Profiling and fixing the back office of an energy retailer: page loads from 22.3 seconds to 2.7, with the method that found them.

Laravel · Filament · Performance · Profiling
Headline figure
22.3 s 2.7 s
page load · 928 36 queries
Full case study (PDF) One-page summary (PDF)
03 Case study · Regulated integration

Built against a mock. Proven against the national system.

A live eligibility check against SII, Italy's national energy-market system, finished and tested four months before access arrived. Part of wider, ongoing SII work.

Laravel · REST · mTLS · JWT
Headline figure
369 ms median
49 real calls · ~300 tests · 4 months blocked
Full case study (PDF) One-page summary (PDF)
04 Method · Legacy rebuild

Rebuild against the live system, not the source.

How I verify a legacy rebuild before anyone relies on it: side by side, screen by screen, every divergence numbered, security findings included.

Legacy · Laravel · Parity audit · Security
What it is
A method
parity audit, screen by screen, against production
Full method (PDF) One-page summary (PDF)

Have a system like one of these?

One email. I reply with questions, not a quote.

Let's have a chatSee more client work