Skip to content
No jargon, no drawn-out phases

How it works.

This page exists to answer the objections before the call, so there's nothing to be nervous about when you book.

01

The discovery call

Thirty minutes. We ask what the work looks like day to day, where it jams, what happens when you're not there, and what you've already tried. We're listening for the ceiling, the one thing your team physically can't do more of. You don't need to prepare anything.

02

The time tracking sheet (optional)

If it helps, we'll share a simple sheet your team can use for a week to show where the hours actually go. It is a tool for the team, not an audit of anyone's day, and it is entirely optional. Plenty of builds happen without it.

03

What a build day produces

One working tool you can use the next morning. For an auction house that was a shared enquiry board replacing an overloaded inbox. Not a mock-up, not a prototype. The real thing, live, with your data in it.

In writing

If a build overruns, that's our problem, not yours.

The price is the quoted number of days. We agree it before we start. If it takes us longer than we said, you pay what we quoted and not a penny more. We'd rather carry that risk than have you watch the clock.

04

Keeping it running

£100 a month covers hosting, fixes and small changes, the tweaks that keep a tool fitting the work as the work shifts. It does not cover a whole new feature or a second tool; those are another build day, quoted the same way. Every quarter we sit down for a review to check it's still earning its keep, and to spot the next ceiling before you hit it.