What Is an MVP? Definition and Examples
A minimum viable product is the smallest version of a product that lets you learn whether customers want it. It is a learning tool first and a product second, which is why so many first versions are too big.
What is an MVP?
A minimum viable product (MVP) is the simplest version of a product that real customers can use, built to test whether they want it before you invest more. Eric Ries defined it as the version that collects the most validated learning about customers with the least effort. Frank Robinson coined the term in 2001, and Steve Blank and Ries popularized it (Wikipedia’s minimum viable product entry).
How is an MVP different from a prototype or proof of concept?
An MVP is used by real customers to do a real job. A prototype shows how something might look or work, a proof of concept shows something is technically possible, and a minimum lovable product aims to delight from the first release. The table shows what each one proves.
| What it proves | Who uses it | Typical form | |
|---|---|---|---|
| Proof of concept | It can be built | Your team | Technical test, often thrown away |
| Prototype | People understand the idea | Test users, investors | Clickable design, no real data |
| MVP | Customers use it and come back | Real early customers | Working product with one core flow |
| Pilot | It works in one customer’s setting | One or a few customers | MVP deployed with support |
| Minimum lovable product (MLP) | Customers enjoy it, not only use it | Early customers | A smaller scope, finished with more care |
What does ‘minimum’ and ‘viable’ mean in practice?
‘Minimum’ means you remove everything the customer doesn’t need to reach the main result. ‘Viable’ means what is left actually works, is reliable enough to trust, and solves the problem. Founders usually get ‘minimum’ wrong by adding features, and ‘viable’ wrong by shipping something that breaks. What to include in an MVP covers how to draw the line.
What isn’t an MVP?
An MVP isn’t a cheap, rushed version of your full roadmap, a demo built only to impress investors, or a beta that never ends. It is also not always software. Some of the best first tests are a landing page, a manual service or a person doing the work behind the scenes, as types of MVP explains.
- Not version 1.0 of the full roadmap.
- Not a demo with fake data.
- Not an excuse for poor quality on the core flow.
- Not a one-off: it starts a learning cycle.
An MVP is an experiment, not a launch.
Judge it by what you learned and how fast, not by how complete it looks.
Where should a founder start?
Start with the riskiest assumption: usually whether a specific customer has the problem badly enough to change how they work. Then pick the cheapest test that answers it. If you are still looking for the right customer, read what to build before product-market fit. When you’re ready to budget, see how much an MVP costs.
Frequently asked questions
What does MVP stand for?
Minimum viable product: the simplest version of a product that real customers can use, built to learn whether they want it.
Who invented the MVP concept?
Frank Robinson coined the term in 2001. Steve Blank and Eric Ries made it popular through customer development and the Lean Startup.
What is the difference between an MVP and a prototype?
A prototype shows how an idea might look or work. An MVP is used by real customers to do a real job.
Is an MVP the same as a beta?
Not quite. A beta tests a product that is mostly finished. An MVP tests whether the product should exist in its current form.
What is a minimum lovable product?
A smaller scope delivered with more polish, so early customers enjoy it rather than only tolerate it.
Does an MVP have to be software?
No. A landing page, a manual service or a person working behind the scenes can test demand before you build.
How minimal should an MVP be?
Minimal enough to ship quickly, but the core flow must work reliably or you won’t learn anything useful.
Sources & further reading
Figures and rules change. These sources let you verify the current information directly. Hours, rates and timelines on this page are planning assumptions, not quotes.