Work
No case studies yet.
We would rather show you an empty page than a fabricated one. A case study goes up when a client has agreed to the number in it, in writing.
If you want references before you commit to anything, ask on the discovery call. We will arrange them directly, which is more useful to you than a logo grid anyway.
What each one will contain
The same four parts, every time.
01
Context
The business, the process, and what it cost to run before we touched it.
02
Constraint
The thing that made it hard — a deadline, a site, a regulator, a legacy system that could not be switched off.
03
What we built
Specifics. Which services, which stack, which hardware, and the decisions we would defend.
04
Measured outcome
One number, its source, and the period it was measured over. Signed off by the client before publication.
Pending sign-off
What is waiting on a client’s permission.
WORK-01
Automation
A named client or an agreed anonymisation, the process before and after, and one measured number with a source.
WORK-02
Hardware + AI
An install we can describe: what was specified, what it runs, what it replaced. Site photography only with written permission.
WORK-03
Software build
The constraint that shaped the build, and a before-and-after figure the client will stand behind publicly.
Next step
Judge us on the call instead.
Bring the process you most want to fix. Forty-five minutes, and you leave with a written summary of what we heard and what we would do — regardless of what happens next.