You have decided to build. We take it from there.
Scope, design, engineering and launch for a product that does not exist yet. One team, one thread of accountability, code your next engineer can read.
This is for you if
- The decision is made and the budget is real.
- You need design and engineering, not one without the other.
- There is a first version that has to be right, not a prototype to throw away.
- Nobody internally has the capacity to own delivery end to end.
And it is not, if
If you are still testing whether anyone wants this, a build is the expensive way to find out. Say so and we will tell you what would answer the question faster, even when that is not us.
What you actually receive
A written scope before any code
What ships, what it has to do, what is explicitly out. You approve it, and it is what we are held to.
Design that survives contact with engineering
Interface design done by the people who then build it, so nothing is drawn that cannot ship.
A preview environment from week one
A URL you can open and click through. You review the product, not a status report.
The release, and the keys to it
Repository, deployment setup, environment config and a walkthrough. You own all of it.
How the engagement runs
We scope first, as a paid piece of work in its own right, because a quote written before anyone has looked at the problem is a guess. Once the scope is agreed you get a fixed shape for the release and a schedule we hold ourselves to. Build runs in the open against a preview environment.
What does a project cost?
We do not publish a number, because a quote written before anyone has looked at your problem is a guess dressed up as a price. We scope first, as a small paid piece of work, and that produces a fixed shape and a real figure. If the scope shows the project is not worth doing, you have spent a fraction of a build to find that out.
How long will it take?
Ask us after the scope, not before. Anyone quoting a duration off a first call is quoting a hope. What we can tell you up front is the shape: releases land continuously against a preview environment you can open, so you are never waiting months to see whether it is going the right way.
Do you work fixed price or time and materials?
Both, depending on what the work actually is. A defined release with an agreed scope can be fixed. Ongoing engineering against a moving roadmap cannot honestly be, and anyone who fixes it is pricing in the risk and charging you for it. We will tell you which one your project is.
We are early and pre-funding. Are we too small?
Possibly, and we will say so. If you are still testing whether anyone wants this, a full build is an expensive way to find out. Tell us where you are and we will tell you what would answer the question faster, even when the answer is not us.
Can you work with our existing team and codebase?
Yes, and most of our work is exactly that. We have joined codebases whose original authors had left and worked alongside in-house teams who needed a discipline they did not have, usually mobile or front end. We read before we rewrite.
Start the conversation
Tell us what you need to ship. You will get a straight answer on whether this is the right engagement for it.
The others
- Fractional CTOSenior technical leadership without the full-time hire.
- Connected productsThe software that turns working hardware into a product a customer can use.
- Modernise existing softwareReplace what holds the roadmap back while the rest keeps running.
- Ongoing engineeringA senior team on your roadmap, release after release.