Most software projects fail before anyone writes code
Because nobody agreed precisely enough what was being built. So every engagement starts with a paid Discovery Sprint, which scopes what gets built and how. If you go ahead, the fee comes off the project.
Founder-led discovery call
Two weeks, £4,500.
Understanding what actually happens.
Turning that into something you can build from.
What you own after two weeks
All of it is yours whether you build with us or not. If you take it to another developer, it will work for them too. We would rather lose the build than have you commit to something nobody scoped properly.
See what one looks likeProject Build and Production Build
The price is fixed before anything starts, and it is built to the specification you already have.
Work is delivered in milestones. At each one you get something you can actually use and judge, not a progress percentage. You see it, you tell us what is wrong, we fix it before we move on. The last milestone is not the first time you find out what we built.
When something needs to change
It always does. Requirements shift, a regulator moves, someone spots a better way halfway through.
Every change is written down, with what it costs and what it does to the timeline, and nothing is implemented until you have said yes. That is not bureaucracy. It is so the fixed price stays meaningful and so nobody discovers a bill at the end that they did not agree to.
When the build is done you get the running system, the source code, the deployment setup, and documentation written for whoever maintains it next, which may not be us.
We do not build things that only we can look after. If you want to take it in-house or hand it to another supplier, you should be able to.
Care Plan
Capacity Retainer
Tell us what is not working.
Thirty minutes, no deck. Tell us what is not working and we will tell you whether we are the right people to build it.
Founder-led discovery call