Minimum viable product (MVP)
In short. A minimum viable product is the simplest version of a product or service that real customers can use and pay for, built to test whether a genuine need exists. It contains only the features required to learn something useful, so a business can find out what works before spending heavily.
Last checked against its sources on 10 October 2026. How we write these.
The point of an MVP is learning, not polish. Instead of building everything you can imagine, you build the smallest thing that lets a real customer try the core promise and tell you, through their behaviour, whether it is worth having.
An MVP does not have to be software. A baker testing a subscription box might take twelve orders by message, bake by hand and deliver on a Saturday. A consultant might sell one fixed-scope workshop before designing a whole programme. The test is whether customers part with time or money.
The common mistake is treating minimum as an excuse for poor quality. The product should do one job properly. Another mistake is building for months before any customer sees it. A useful rule is to decide in advance what result would count as success, such as ten paying customers or three repeat orders, so that the result is read honestly rather than bent to fit hopes.
Once the MVP has taught you something, you improve it, change direction or stop, having spent a fraction of what a full launch would have cost.
Questions people ask
Does an MVP have to be a finished product?
No. It can be a manual service, a simple page or a single feature, provided real customers can use it. What matters is that it produces honest evidence about demand.
How is an MVP different from a prototype?
A prototype usually demonstrates how something might work and may never be used by customers. An MVP is released to real users so that you can measure whether they value it.
Sources
- The Lean Startup: Principles checked 10 October 2026