MVP — Minimum Viable Product
An MVP is the simplest version of a product that allows a startup to test its core value hypothesis with real users and gather validated learning.
What Is an MVP?
A Minimum Viable Product (MVP) is the most stripped-down version of a product that still delivers enough value for early adopters to use it — and enough instrumentation for the team to learn from that usage.
The concept was popularized by Eric Ries in The Lean Startup and builds on Steve Blank’s customer development methodology. The central insight is simple: you don’t know what customers want until they tell you with their behavior, not just their words.
Why It Matters
Building a full-featured product before validating demand is one of the most common — and costly — startup mistakes. An MVP lets you:
- Test your core assumption cheaply and quickly
- Collect real behavioral data instead of relying on surveys
- Iterate based on evidence, not intuition
- Preserve runway for when you find what actually works
What an MVP Is NOT
- A buggy, half-finished product you’re embarrassed to show
- A prototype or mockup (though those can be part of the process)
- The smallest thing you can build in a weekend
- An excuse to ship something broken
An MVP must solve a real problem well enough that someone chooses to use it over doing nothing.
Types of MVPs
| Type | Description | Best For |
|---|---|---|
| Landing Page | Describe the product, measure sign-ups | Early demand validation |
| Concierge | Manually deliver the service before automating | Service/marketplace ideas |
| Wizard of Oz | Fake automation behind the scenes | AI/automation products |
| Piecemeal | Assemble with existing tools (Zapier, Airtable) | Workflow products |
| Single Feature | Ship only the one core feature | Software products |
The MVP Spectrum
Think of MVP not as a fixed point but as a spectrum:
Smoke Test → Prototype → MVP → MMP → Full Product- Smoke Test: Does anyone want this? (landing page, waitlist)
- Prototype: Can it be built? (mockup, demo)
- MVP: Will they use it? (bare-bones working product)
- MMP (Minimum Marketable Product): Will they pay for it and tell others?
Common Mistakes
- Building too much — perfectionism kills MVPs. Ship when you’re embarrassed.
- Wrong success metric — define what “validated” means before you build.
- Wrong audience — launch to your ideal early adopter, not everyone.
- No feedback loop — an MVP without a mechanism to learn from users is just a bad product.
Key Takeaway
The goal of an MVP is not to build a product — it’s to learn as fast as possible whether you’re solving a real problem for real people. Speed of learning beats speed of building.