MVP development
The smallest complete version that proves the idea with real users.
- Engagement
- Fixed-scope build, one small team, weekly releases
- Typical timeline
- 6–8 weeks
- Starts with
- The one sentence you want the market to prove or disprove for you.
Eighteen months of building before a customer sees anything is the most expensive way to find out you were wrong. The useful question is not how much fits into six weeks, it is which single thing, once shipped, tells you whether to keep going.
Validated learning in weeks rather than a year of building.
What we build
Concrete artefacts, handed over and documented.
One user journey working end to end for real people, with real data and a real payment if money is part of the test
A written list of everything we deliberately did not build, so the gaps are decisions on record
Measurement for the one question the release exists to answer, agreed before the first line of code
A short note on which parts are throwaway and which are worth keeping if the answer comes back yes
What changes
Evidence from paying or nearly-paying users inside two months
The case for further investment is argued from behaviour rather than from a deck
If the idea does not hold, you found out for the price of six weeks
How it runs
01Cut
We agree the question and remove every feature that does not help answer it. This is the week that saves the most money.
02Build in the open
A weekly release to a link you can send a customer, so you are using it while changes are still cheap.
03Read the result
Real usage against the number we set in week one, and a recommendation: continue, change direction or stop.
Chosen per project. Named here so you can see the shape of it.
- Next.js
- Supabase
- Vercel
- PostHog
Questions we get asked
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.