MVP Build
A live product that real people can sign up to.
- How long6 to 12 weeks
- How we workSprints
What you receive
In 6 to 12 weeks you have a real product live, that real people can sign up to and pay for, engineered in steps you can see.
What will the first version do?
You receiveUp to two core journeys
A small first version reaches the market sooner and teaches you what to build next.
What it is. The two most important things a user can do, from start to finish, chosen with you.
Why it matters. A small first version reaches the market sooner and teaches you what to build next.
Where will people use it?
You receiveA web app, or an app for iPhone and Android
You meet users where they already are, without building for every device at once.
What it is. The product made for the place your users are: in the browser, or as a phone app.
Why it matters. You meet users where they already are, without building for every device at once.
How do we run it day to day?
You receiveAn admin panel
You can run the product yourself without asking a developer for every change.
What it is. A private screen for your team to manage users, content and orders.
Why it matters. You can run the product yourself without asking a developer for every change.
Who can see and do what?
You receiveSign-in and roles
Data stays with the right people from day one, which is far easier than adding it later.
What it is. Secure sign-in, with different permissions for users, staff and admins.
Why it matters. Data stays with the right people from day one, which is far easier than adding it later.
Can people pay us?
You receivePayments, if you need them
You can start earning from launch day.
What it is. Card payments or subscriptions through a trusted provider, with receipts.
Why it matters. You can start earning from launch day.
Will new changes break things?
You receiveAutomated tests
You can keep improving the product quickly without breaking what already works.
What it is. Tests that run on every change and catch mistakes before users do.
Why it matters. You can keep improving the product quickly without breaking what already works.
Where does it live?
You receiveHosting in production
It is ready for real users from the first day.
What it is. The product running on reliable hosting, with backups and a proper web address.
Why it matters. It is ready for real users from the first day.
Are people using it?
You receiveAnalytics
You learn what works from real behaviour, not opinions.
What it is. Measurement of sign-ups and the key steps in each journey, respecting privacy.
Why it matters. You learn what works from real behaviour, not opinions.
Can someone else pick this up?
You receiveDocumentation
You are never tied to one developer.
What it is. Written notes on how the product is engineered, deployed and run.
Why it matters. You are never tied to one developer.
What if something goes wrong after launch?
You receive30 days of support after launch
Launch week is when surprises happen.
What it is. A month of fixes and help after go-live.
Why it matters. Launch week is when surprises happen. You are not left alone with them.
From brief to done
- 1
Week 1
Shape
Agree the journeys, the screens and the plan for each sprint.
- 2
Weeks 2 to 10
Build in sprints
Two-week sprints, each ending with a demo you can try.
- 3
Final sprint
Launch
Tests, hosting and go-live.
- 4
30 days after
Support
Fixes and help while real users arrive.
Is this quote fair, and what is it missing?
Second opinion on a quote. A plain-English read of a quote or plan from another supplier: what is missing, what is unclear and what to ask.
- Send us the quote or plan
- We mark it up and send it back with the questions worth asking
- It is free. There is nothing to pay and nothing to sign.
- The report is yours to keep and share, whatever you decide.
- No sales call unless you ask for one.
Questions people ask
How much does it cost?
We send a written quote after your request: what it covers and what it does not. The tier, scope and timing set the price.
Could I just use AI for this?
AI drafts code and prototypes quickly, and we use it every day. It cannot decide what to build, prove that it is secure, or answer for it when real people rely on it. That is the part you are hiring us for.
Who owns the work?
You do. Code, designs, files and documents are yours, and the quote says so in writing.
Can we change the scope?
Yes. If something needs adding or removing, we agree it in writing before we do it.
What happens after?
Most people go on to Operate and Improve Plan, but there is no obligation. You keep everything we made.