The bugs that taught us something.
Screenshots prove someone can arrange boxes. Diagnoses prove judgement. These are real documented investigations from our own builds, including the one where we broke it ourselves.
Tracking & attribution
The pixel that wasn't firing
Our own store's conversion tracking looked healthy and was silently broken. Finding out why changed how we build tracking for everyone.
100%
of purchases recovered into reporting
Inherited codebases
The code below the return statement
Five templates where every edit we made was being thrown away, and nothing told us.
5
templates silently discarding edits
Operations & safety
The incident and the guard rail
We destroyed a WordPress install over SSH. Here's the post-mortem, and the script that makes it impossible to repeat.
0
repeat incidents since the guard shipped
Why we publish these
Every agency has incidents and dead ends. Most just never tell you. We write ours up: what happened, what we assumed wrongly, what shipped so it can't repeat. Each story ends with a “what we'd do differently” section, because a partner who can't name their own mistakes will eventually hide one of yours.
Recognise one of these on your own site? Tell us what you're seeing and we'll tell you what's actually going on, before you owe us anything.
Book the free call →Pick a time that suits you
Thirty minutes, no pitch, and an honest answer at the end of it. The calendar is already showing your timezone.
Loading the live calendar…
Real availability, already in your timezone.
Rather write first? Send an enquiry instead.