Definition
An MVP (minimum viable product) is the smallest version of a product that delivers real value to real customers and lets you learn whether the idea works before investing heavily. The concept was popularised by Eric Ries in The Lean Startup. An MVP is not a prototype or a demo; customers actually use it, and often pay for it. Its purpose is to test the riskiest assumptions, usually whether anyone wants the product and will pay, with the least effort.
In a company, an MVP is how you launch a new product, enter a new market or test a new feature without a year of development. You pick the core problem, build only what solves it, launch to a small group and measure behaviour: sign-ups, usage, retention, payment. What you learn decides whether to invest, pivot or stop. An MVP applied well protects budgets, because expensive features are built only after demand is proven.
AI coding tools and no-code platforms have made an MVP something a small team can ship in days, so the constraint is no longer building but choosing what to test and finding customers to test it with. The misconception is that MVP means a poor-quality product. It means a narrow product done well enough that the feedback is about the idea, not the bugs. Minimal in scope, viable in quality.
In practice
Before building a full analytics module, a SaaS company shipped an MVP: a weekly email report with 3 metrics for 30 customers. Open rates and requests for more told the team exactly which dashboards to build next, and which to skip.
Why it matters
The MVP is the cheapest way to find out whether customers want what you plan to build. In my companies, every new product starts as one, because the market's answer is worth more than any internal opinion.
Frequently asked questions
- What is the difference between an MVP and a prototype?
- A prototype demonstrates an idea, often with fake data or no working backend, and is used internally or for feedback sessions. An MVP is a real product that customers use for real, even if it is narrow. The prototype tests understanding; the MVP tests demand and behaviour.
- How long should it take to build an MVP?
- Weeks, not months. With modern tools, a focused team can often ship a usable MVP in 2 to 8 weeks. If it takes longer, the scope is probably too broad. Cut features until only the core problem is solved, then launch and learn.