Case studies
Nothing published here yet.
A case study needs a client willing to be named or described, results that were measured rather than estimated, and permission to publish both. Until all three exist, this page stays empty.
Why an empty page rather than a plausible one
It would take about an hour to fill this page with convincing-sounding projects and percentage improvements. Plenty of sites do. The problem is that anyone who has run a project can tell, and a fabricated result is a strange thing to build a working relationship on.
So this page waits. When a project is finished, measured, and the client is happy to have it written up, it will appear here in full — including the parts that were harder than expected.
In the meantime, the service pages describe exactly what gets built and how, and a conversation will tell you more about fit than a case study would.
The format each one will follow
- Context
- The client, the sector and how the business actually runs.
- Challenge
- What was going wrong, described specifically enough to be recognisable.
- Approach
- What was investigated, and why that route was chosen.
- Implementation
- What was built, which systems it touched and what it took to get live.
- Results
- Measured outcomes the client has confirmed and agreed to publish.
- Technologies
- What it was built on, so it can be assessed technically.
Want to talk to the person who would do the work?
A conversation about your situation will tell you more than a case study about somebody else's.