Building apps
What is a minimum viable product (MVP)?
A minimum viable product (MVP) is the smallest version of a product that delivers real value to real users and tests whether the central assumption behind it holds.
New to Bolt? Sign up free.
Technical definition
A minimum viable product is a release containing the smallest feature set sufficient to deliver the product's core value and generate validated learning about a specific hypothesis. Scope is defined by the assumption being tested rather than by a feature checklist.
An MVP differs from a prototype in being usable by real customers in real conditions, and from a proof of concept in testing demand rather than feasibility.
In plain terms
An MVP is the smallest thing you can put in front of customers that is genuinely useful and tells you whether the idea works.
Minimum means fewer features, not lower quality. The one feature it has should work properly.
Why it matters
Most products fail because nobody wanted them, not because they were built badly. An MVP finds that out in weeks rather than after a year of work.
The discipline is in what you leave out. Every feature you add before anyone has used the thing is a bet placed with no information. Cutting scope is not lowering ambition; it is refusing to guess.
AI building changes the calculation in a way most MVP advice has not caught up with. When a working application takes an afternoon, the reason to keep an MVP small stops being cost and becomes clarity. A focused product gets you a clear answer. A product with 12 features gets you a shrug.
So the useful question is no longer what you can afford to build. It is what one thing you need to learn, and what is the smallest product that teaches you that.
