Section 7 of 13: Build
MVP Planner: How to Build a Minimum Viable Product
A minimum viable product plan defines the smallest version of a product that can test whether customers want it, and how to build that version. Business Launchpad's MVP Planner starts with a web research pass, in which a search-enabled model gathers sourced, dated notes on the tools and approaches available, then produces the plan from your brief and Your Customers section: core features ranked must, should or could with an effort rating, a recommended tech stack, build phases with weeks and deliverables, a total timeline, an estimated cost range, a build-versus-buy table, the single biggest technical risk and three to five post-launch success metrics.
No account for the brief. Free accounts build three ideas. Downloads need Founder or an eligible trial.
What you walk away with
Outcomes
A feature list you can say no with
Must, should and could priorities against low, medium and high effort give you a defensible reason to cut features before the first release.
A realistic timeline and cost bracket
Weeks per phase and a cost range in pounds, so a conversation with a developer or agency starts from a shared expectation rather than a guess.
Fewer things built from scratch
The build-versus-buy table names components worth subscribing to rather than coding, with a suggested tool for each.
One risk to de-risk first
The section names the technical thing most likely to derail the build and how to test it early, before money is spent.
Inside the section
What you get
- Core features
- Each with a name, description, priority (must, should, could) and effort (low, medium, high).
- Tech stack
- Frontend, backend, database and hosting recommendations, with key integrations and payments where relevant.
- Build phases
- Named phases with weeks, a description and deliverables, adding up to the total build timeline in weeks.
- Estimated cost range
- A low-to-high figure in pounds for the MVP, and a one-line view on outsourcing versus building in-house.
- Build vs buy
- For each major component: build, buy or subscribe, the reason, and a suggested tool.
- Biggest technical risk
- The one thing most likely to break the plan, and a way to reduce that risk early.
- Success metrics
- Three to five post-launch measures that tell you whether the MVP is working.
Step by step
How it works
- 1
The MVP Planner opens the Build group, after the four market sections, reading your Founder Brief and Your Customers. It starts with a web research pass whose sourced, dated notes feed the writing model. If you completed the founder interview, your answers about the product shape the features.
- 2
Review the feature table. Move anything you disagree with between must, should and could by editing in place.
- 3
Compare the cost range and timeline against your budget. On the Founder plan, regenerate with instructions such as 'no-code only' or 'must launch in six weeks' to see a different plan.
- 4
Take the build-versus-buy table and the biggest technical risk into your first conversation with a developer, agency or technical co-founder.
Who uses it
Use cases
Non-technical founder getting quotes
A founder with no coding background has three agency quotes ranging from £8,000 to £45,000 and no way to compare them. The MVP Planner gives a feature list and phase plan to send to all three, so the quotes answer the same question.
Developer deciding what to skip
A software engineer building a side project keeps adding features. The must/should/could split and the twelve-week timeline give a reason to ship the must-haves first and leave notifications and analytics for phase two.
Hardware idea with a software layer
Someone designing a smart planter uses the section to separate the app from the device. The build-versus-buy table suggests subscribing to an existing IoT platform rather than writing firmware, cutting the first-phase cost.
Free or Founder?
The MVP Planner is one of the thirteen sections free accounts build for up to three ideas, fully editable on screen. The Founder plan (£19 a month or £149 a year) removes the idea limit and includes the MVP plan in the branded business plan PDF inside the downloadable pack.
Frequently asked questions
How do I build an MVP if I cannot code?
Decide what the product must do to test your riskiest assumption, then choose the cheapest way to do that. The MVP Planner helps by ranking features and suggesting where a no-code tool or a subscription replaces custom development. On the Founder plan, regenerate the section with the instruction 'no-code only' and it proposes a stack you can assemble yourself, along with the trade-offs.
How much does an MVP cost in the UK?
It varies enormously: a no-code prototype might cost a few hundred pounds in subscriptions, while a custom app from a UK agency can run from £10,000 to well over £50,000. The section gives a cost range specific to your feature list and stack. Use it as a sanity check against quotes rather than a fixed budget, and remember it excludes marketing and your own time.
What does must, should and could mean?
It is a common prioritisation method. Must features are essential: without them the MVP does not test the idea. Should features add clear value but the product works without them. Could features are nice to have and are the first to cut when time or money runs short. Combined with the effort rating, it shows which high-value, low-effort items to build first.
Is the tech stack recommendation reliable?
It is a sensible default based on the type of product, the integrations you need and the research notes gathered before the section was written, and a good starting point for a conversation with a developer. It is not a substitute for that conversation. If you already have constraints, such as an existing team's skills, regenerate with those as instructions on the Founder plan and the recommendation adapts.
Does the MVP plan connect to the rest of the plan?
Yes. Licences & Insurance builds straight after it and reads what you actually deliver, because handling food, holding personal data or fitting things in someone's home are different regulatory positions from the same one-line idea. The Launch Roadmap reads the phases and timeline, Financial Projections use the cost range in start-up costs, and AI Opportunities reads the tech stack. Change the MVP section after those have built and they are marked out of date; one tap rebuilds them.
Keep reading
Know what to build first
Features, stack, timeline and cost, generated from your free Founder Brief.