Written product plan
What the software has to do, for whom, and in what order. In plain language your team can read.
Blueprint
We work through the problem, the people who live with it and the constraints around it. You get a plan you can act on and a fixed price for the first block of the build. The fee contributes to that build. If you stop there, you still have the plan.
Book a 30-minute call (opens in a new tab)What you get
What the software has to do, for whom, and in what order. In plain language your team can read.
The thinnest complete path first. Enough detail that the build can start on Monday.
Reviewed by our CTO: data model, hosting, sign-in, integrations and the reasons behind each call.
What each block delivers, roughly when, and exactly what the first one costs.
Working prototype, production for your business, or sellable product. Agreed before anyone writes code.
If we think you shouldn't build this, or shouldn't build it with us, we will say so in the plan.
How the week runs
Sit with the owners and the people doing the work. What is slow, what is wrong, what is trusted.
Walk the real process end to end. Sketch the system around it, not the other way round.
Data, integrations, security and hosting, with our CTO. Decide what we must get right first.
Play the plan back, agree the first block, and give you the fixed price and the go/no-go.
If you go ahead
Run by the person who wrote the plan. The Blueprint fee contributes to the first block. Block one follows the shape on the How we work page: build, two-week live review, build, sign-off.
How we workIf you don't
Take it to another team, build it in-house, or sit on it. The plan is written to be usable by anyone, and we will happily answer questions about it.
Book 30 minutes with Kevin. We'll tell you straight.