Minimum Viable Product (MVP)
A minimum viable product (MVP) is the smallest version of a product that delivers real value to users and lets a team learn from actual use.
The point of an MVP is not to ship less for its own sake, but to reach real users sooner and learn faster. Done well, it cuts scope without cutting the quality of what remains — the corners that matter stay intact.
How it works
Building an MVP starts with the riskiest assumption: the thing that, if wrong, makes the product pointless. The team defines the smallest end-to-end experience that tests it with real users, cuts every feature that does not serve that test, and decides in advance what result would mean "keep going", "change course" or "stop".
Cutting scope is different from cutting quality. What does ship must work, be secure and treat users' data properly, or the test measures the wrong thing.
Example
A marketplace for event venues might launch with one city, venues listed by hand and bookings confirmed by email, instead of a self-serve listing tool and automated payments. If organisers book, the automation is worth building; if they do not, the team has learned that cheaply.
In practice
Before any build starts, write one page: the assumption you are testing, who the first users are, the single core task they must be able to complete, and the result that would count as success, such as a number of paying customers or repeat bookings within a set period. Share it with whoever is building. It becomes the test for every feature request: if a feature does not help that core task or that measurement, it waits for later.
Ask your developer or agency which parts can be manual at first. Payments can be invoiced, matching can be done by a person, onboarding can be a phone call. Manual steps are slower per customer but much cheaper to change while you are still learning. Agree which parts must be solid from day one, usually anything involving security, personal data and money, and which can be rough. Also agree what happens to the code if the MVP succeeds: whether it will be extended or rebuilt, and roughly what each would cost, so a successful test does not surprise you with a rebuild bill.
Why it matters for your business
An MVP protects the budget by spending a fraction of it to find out whether customers want the thing before you pay for the full build. If the answer is no, you have lost weeks rather than a year; if yes, you build the next stage on evidence instead of guesses, moving toward product-market fit. The cost is that early users see rough edges, so be clear with them about what stage they are using. The biggest threat to an MVP is scope creep, where nice-to-have features slip back in. For a simple marketing website the idea rarely applies; it is a tool for new products and services with real uncertainty.
Common mistakes
- Shipping a buggy product and calling it an MVP, then blaming users for not returning.
- Adding features before the first version has told you anything.
- Not deciding up front what result would count as success.
Questions people ask
How long does it take to build an MVP?
It varies with the product, but the aim is weeks to a few months rather than a year. If the plan stretches much longer, the scope probably includes features the first test does not need. Some of the best MVPs take days, because they rely on manual work behind a simple front end rather than full automation.
What is the difference between an MVP and a prototype?
A prototype simulates a product to test an idea or interaction, usually with a handful of people in a session, and nobody relies on it. An MVP is a real, working product that real customers use, sometimes pay for, and return to. A prototype answers whether people understand it; an MVP answers whether they want it.
What happens after an MVP launches?
You measure the results against the success criteria agreed before launch, talk to the people who used it and the people who did not, then decide: keep building, change direction or stop. The next features should come from what users actually did, which then shapes a more reliable product roadmap.