What is a Minimum Viable Product (MVP)?
A minimum viable product is the smallest version of a product that delivers real value to real users and produces evidence about whether the idea works. It is a learning instrument, not a cut-down version one — the point is answering the riskiest assumption with the least build.
Understanding Minimum Viable Product (MVP)
The word doing the work is viable. A prototype demonstrates; an MVP is used, by people who chose to use it, in circumstances where it can fail. That is what makes the evidence meaningful, and it is why an MVP still needs working auth, a sane data model and a path that does not break — those are not polish, they are preconditions for anyone using it at all.
Scoping starts from the riskiest assumption rather than the feature list. If the risk is that nobody wants the thing, the MVP should test demand and can fake almost all the mechanics. If the risk is technical feasibility, the MVP should be a thin slice of the hard part with barely any interface. Building a small version of everything tests nothing in particular.
The most expensive MVP mistake is shipping something so rough it fails for reasons unrelated to the hypothesis. If users leave because onboarding was confusing, you have learned nothing about the actual idea and burned the audience you needed to learn from.
Key points
- Smallest build that produces real evidence, not a smaller product
- Scoped from the riskiest assumption, not from a feature list
- Still requires working auth, a sound data model and a reliable path
- Typically eight to twelve weeks for a genuine product MVP
- A failure caused by roughness teaches nothing about the idea
Where this gets oversold
MVP is routinely used to justify shipping something broken. Minimum applies to scope, not to quality within that scope — narrow the surface, then build the narrow thing properly.
Related terms
Minimum Viable Product (MVP) — related questions
How long does it take to build an MVP?
Eight to twelve weeks is typical for a product MVP with real authentication, a sound data model and a reliable core flow. Shorter timelines are achievable by narrowing scope further, not by lowering the quality of what ships.
What should an MVP include?
Only what is needed to test the riskiest assumption, plus the infrastructure required for real use — working auth, a data model you will not have to rewrite, and one core flow that does not break. Everything else waits.
Need help with minimum viable product (mvp)?
From MVP to scale: dashboards, onboarding and billing flows that turn sign-ups into paying customers. If you are weighing whether this applies to your situation, we will give you a straight answer before there is any proposal involved.