MVP: what a minimum viable product is and how to build one

The MVP, short for Minimum Viable Product, is the leanest version of a product able to deliver the core value to early users while generating learning at the same time. The idea was popularized by Eric Ries in The Lean Startup: instead of spending months building everything you imagine, you ship the minimum that already solves the problem and watch how real people react.

The goal is not to save for the sake of saving, but to reduce risk. Every extra feature you postpone is a bet you did not yet have to make. In a SaaS, this means launching the essential flow that proves (or breaks) the main hypothesis with the least possible effort.

Building an MVP is a process of hypothesis and testing, not a mere scope cut. A simple playbook usually follows four steps:

• 1. Define the hypothesis. What problem you solve, for whom, and why the current solution is not enough.
• 2. Isolate the core value. The single feature that, if it works, proves it is worth continuing.
• 3. Build the minimum. The smallest version that delivers that value end to end, good enough to be used for real.
• 4. Measure and learn. Put it in front of real users and observe behavior, not just opinion.

Step four is what separates an MVP from a simple prototype. Without measuring what people actually do, you built a demo, not an experiment.

The most common mistake is confusing minimum with poorly made. An MVP is not a broken product or a half-finished version that frustrates whoever tries to use it. The V for viable matters as much as the M for minimum: what you deliver has to work well enough for the user to reach the value and for you to trust what you learned.

It is also not a never-ending project. Some teams use the MVP label to justify months of development without ever showing anything to anyone. If there are no real users interacting and generating learning, it is not an MVP: it is just an incomplete product delaying the moment of truth.

The MVP exists to serve a bigger question: is there a market that wants this? It is the first concrete tool on the journey toward product-market fit. It turns an internal opinion (we think people want X) into market evidence (people use it, pay for it and come back).

One of the most cited reasons startups fail, according to CB Insights research, is building something the market does not want. The MVP attacks exactly that risk. Funds such as Sequoia and a16z stress that validation comes before scale: first prove there is demand, then invest in growing. Behavioral metrics, such as the activation rate, help you read whether early users actually reach the promised value.

An MVP is not a synonym for code. Often the fastest way to test a hypothesis does not involve building the real product. Some classic formats:

• Landing page: a page that describes the offer and measures how many people sign up or try to buy.
• Concierge: the team delivers the service manually, behind the scenes, before automating.
• Wizard of Oz: the user sees something that looks automatic, but people are operating behind it.
• Single-scope product: an app that does one thing, very well.

Large companies were born this way. The most remembered case is a video that demonstrated the idea of file syncing before the product existed, used to measure real interest. What they all share is the same principle: spend the minimum to learn the maximum.

In SaaS, shipping fast and learning from data is a structural advantage: the product lives in the cloud, updates continuously and lets you measure every step the user takes. The MVP fits this logic perfectly, because the cost of putting a version live and observing is low, and the cost of building the wrong thing for years is enormous.

The market only grows: according to Gartner, worldwide spending on SaaS applications is set to approach $300 billion in 2025. In a market that size, arriving early with the right solution is worth more than arriving late with the complete one. Product-led growth models take this logic further: the product itself, starting with the MVP, becomes the acquisition engine, and the activation rate becomes the thermometer that value was delivered.