Projects
Case studies
Each case study explains the situation, the constraints and the approach we took. We include only outcomes a client has confirmed and agreed to publish.
Status
Case studies are published only with client permission.
Our first case studies are being written.
We only publish work we can describe accurately and with our clients' permission. Until then, we're happy to talk through how we'd approach a problem like yours.
Discuss your projectCase file · template
The same eight questions, every time.
A consistent structure makes case studies easier to compare, and harder to pad with claims that can't be checked.
- 01
Context
Who the client is (anonymised where needed) and why the work mattered.
- 02
Problem
What wasn't working, described in the client's terms.
- 03
Constraints
Systems, timelines, budgets, security or people that shaped the options.
- 04
Approach
How we ran discovery and decided what to build.
- 05
Solution
What was built, and how it fits into existing systems.
- 06
Technology choices
The tools we used, and why they suited this situation.
- 07
Verified outcomes
only client-confirmedOnly results the client has confirmed. Left out rather than estimated.
- 08
Lessons learned
What we'd repeat, and what we'd do differently next time.
No published case studies yet
Want to talk through a problem like yours?
Tell us about the situation. We'll explain how we'd approach it.
What happens next
- 1
We read your message and reply, often with a few questions.
- 2
If it looks like a fit, we suggest a call to understand the context.
- 3
We follow up with how we'd approach it.
