00 / Work

Recent builds, with the numbers

Every case study says what was built, how long it took, what it cost and what changed for the business afterwards. If we can't share the numbers, we don't publish the case study.

01 / Case studies

Websites, tools and custom builds.

01.1 Case study[sector]
[ screenshot of case study 1 ]
Built[what we built]
Timeline[X] weeks
Result[measured outcome]
[ client ][ location ]
01.2 Case study[sector]
[ screenshot of case study 2 ]
Built[what we built]
Timeline[X] weeks
Result[measured outcome]
[ client ][ location ]
01.3 Case study[sector]
[ screenshot of case study 3 ]
Built[what we built]
Timeline[X] weeks
Result[measured outcome]
[ client ][ location ]
01.4 Case study[sector]
[ screenshot of case study 4 ]
Built[what we built]
Timeline[X] weeks
Result[measured outcome]
[ client ][ location ]

02 / What each case study shows

The same 6 facts, every time.

Case study / contentsDCM-CASE
Problem
What was going wrong, in the client's words
Built
What we made and what we left out
Timeline
Spec to launch, in weeks
Price band
Within a range, with the client's permission
Result
A measured change, such as hours saved or enquiries per month
Since
What's happened in the months after launch

Want to talk to a client?

We'll put you in touch with a past client who's had a similar project, once you've had a spec from us. It's the best way to check we do what we say.

Next step

Here's what it does, what it costs and when you'll have it.

Tell us what's slowing the business down. The engineer who'd build it will reply within 2 working days with a rough price range.