Term · Web & development
MVP (minimum viable product)
An MVP — minimum viable product — is the smallest version of a product that real users can use to get real value, built to answer a key business question: will people use it, and will they pay for it? It is a learning tool as much as a product.
[ 01 ]
Explained
What makes it "minimum"
Only the features needed for the core scenario — the one task that delivers the product's value from start to finish. Secondary features, extra roles, advanced settings and nice-to-have integrations wait until evidence shows they are needed.
What makes it "viable"
- Users can complete the core task without help.
- It works reliably — bugs would distort what you learn.
- It is secure and handles data properly.
- It measures what matters: usage, retention, payment.
Common misunderstandings
- An MVP is not a prototype. A prototype simulates the product; an MVP is a working product with real users.
- An MVP is not low quality. It has fewer features, built properly.
- An MVP is not the final foundation-free version. Data model, security and architecture should allow growth.
Example
A booking service for clinics might launch with online booking, reminders and a simple admin panel for one clinic type — without reports, loyalty features or integrations — to test whether clinics use it and pay for it.
See MVP development and defining MVP scope.
[ 02 ]
FAQ
Frequently asked questions
How long does an MVP take to build?
It depends on the core scenario. The aim is to launch while the question is still worth asking, which usually means weeks to a few months.
What happens after the MVP?
The product is extended, changed or stopped, based on what users do. All three are valid outcomes.