What it actually means
The word minimum refers to scope.
Not quality.
Founders hear “minimum viable product” and think it means a rough draft, a half-finished app, or a landing page with a signup form. It is none of those things. An MVP is a real product — built with real code, handling real data, used by real people. You are building fewer features, not building features badly.
A real, working product
Not a wireframe. Not a prototype. Not a pitch deck with screenshots. An MVP is functional software — deployed, live, and handling real user data from day one.
One core problem, solved properly
A good MVP solves one problem exceptionally well. Not three problems adequately. Not five problems superficially. The narrower the focus, the clearer the signal.
Built to validate a hypothesis
The purpose of an MVP is to test a belief: that users have a specific problem, and that your product solves it. Everything else — features, polish, scale — comes after you have evidence.
Production-grade code you build on
The MVP you launch should be the foundation you scale. Not throwaway work. Not something you tear down and rewrite in three months. At Wall & Fifth we build MVPs in Next.js, React, TypeScript, and PostgreSQL.
What an MVP is not
Clarity here saves founders
months of wasted time.
Most of the confusion around minimum viable products comes from conflating them with things that are not MVPs. Getting this distinction right before you start building is worth more than any feature list.
01
Not a prototype
A prototype is a clickable design with no real functionality. You cannot acquire users with a prototype. You cannot generate revenue. An MVP is functional software.
02
Not a proof of concept
A proof of concept tests whether something is technically feasible. An MVP tests whether something is commercially viable. Different question, different output.
03
Not a beta
A beta is a near-complete product being tested before public launch. An MVP is deliberately incomplete — built with only the features required to test the core value proposition.
04
Not a landing page
A landing page can validate interest. It cannot validate whether people will actually use and pay for a product. Those are fundamentally different things.
The business case
Why building an MVP matters.
The alternative to building an MVP is building the full product upfront. That means 6 to 18 months of development, £80,000 to £300,000 in spend, and a massive bet that your assumptions about the market are correct.
Most assumptions are wrong. Not because the founder is wrong about the problem — usually the problem is real — but because the founder is wrong about the solution. The feature they thought was critical turns out to be irrelevant. The user flow they imagined turns out to be confusing. The pricing model they planned turns out to not match how people want to buy.
An MVP lets you discover all of this in 8 weeks and £16,000 rather than 12 months and £150,000. For most startups that is the difference between surviving and running out of money.
MVP types
Types of minimum viable product.
The right type depends entirely on the product. Each targets different users, different problems, and different validation questions.
We also build SaaS MVPs with subscription billing and user management, and marketplace MVPs with two-sided matching, payments, and trust systems. Read our web app vs mobile app comparison for a deeper breakdown.
Scoping
How to scope a minimum viable product.
Scoping is where most MVPs fail. The tendency is always to add more — one more feature, one more user type, one more integration. Every addition pushes the launch date further and the budget higher without meaningfully improving validation.
- Define the hypothesis — what are you testing, who is the user, what does success look like?
- Map the critical path — the shortest sequence of actions a user takes to get value from the product
- Cut everything else — admin panels, analytics, email notifications, secondary user types can all wait
- Define launch criteria — what needs to be true for you to put this in front of real users?
We cover the full methodology in our MVP development process guide and the feature decisions in what features to include in your MVP.
Common pitfalls
Where founders go wrong.
The same mistakes repeat across nearly every first-time MVP build. We cover these in depth on our MVP mistakes page, but the short version:
- Building too much — the MVP grows to 40 features and takes 6 months. It is no longer minimum.
- Building too little — a landing page or prototype cannot validate whether people will use and pay for the product.
- Choosing the wrong tech — no-code works for some MVPs, but most serious products need custom code from the start.
- No success metrics — launching without defining what success looks like means no way to know if the MVP worked.
- Ignoring the commercial model — an MVP that users love but cannot generate revenue is not viable.
Read our tech stack guide for the technology decisions and our MVP cost guide for a realistic breakdown of what to budget.
Post-launch
What happens after your MVP launches.
An MVP is not the end — it is the beginning. After launch, you are looking for signal: are users signing up? Are they completing the core workflow? Are they coming back? Are they paying?
If the signal is strong, you invest further — adding features, expanding to new user types, scaling infrastructure. If the signal is weak, you have learned something valuable at a fraction of the cost of building the full product. Either way, the MVP has done its job.
Most of our clients come back for ongoing development after the initial 8-week build. The MVP gives them the foundation and the evidence they need to invest further — or to pivot before they have spent too much.
FAQ
Questions people usually have before the next step feels obvious.
What does minimum viable product mean?
A minimum viable product is the simplest version of a product that can be released to real users. It includes only the core functionality needed to solve the primary problem and validate the idea. Everything else is stripped away until after launch.
What is the difference between an MVP and a prototype?
A prototype is a design mockup — clickable screens with no real functionality. An MVP is a real, working product with real code, real data, and real users. Prototypes test whether the interface makes sense. MVPs test whether the business makes sense.
How much does a minimum viable product cost?
At Wall & Fifth, our MVP Build starts at £16,000 for a complete product delivered in 8 weeks. The Extensive MVP Build is £30,000 for more complex products with multiple user types and integrations. Both are fixed-price.
How long does it take to build a minimum viable product?
A well-scoped MVP typically takes 6 to 12 weeks. At Wall & Fifth, we deliver in 8 weeks — that includes scoping, design, development, testing, and launch. Anything under 4 weeks is usually a prototype, not an MVP.
Is an MVP just a bad version of the final product?
No. A good MVP is not low quality — it is low scope. The code should be production-grade. The interface should be clear and functional. What makes it minimum is that you have deliberately chosen to build fewer features, not that you have built those features badly.
Related pages
Ready to build
Turn your idea into a
minimum viable product.
Tell us what you are building. We will help you define the minimum scope that validates the idea — and give you a fixed price to build it.