What Is a Minimum Viable Product (MVP)? Definition, Examples & How to Build One
The term minimum viable product (MVP) was popularized by Eric Ries in The Lean Startup, and it is one of the most misunderstood ideas in startups. An MVP is not a buggy, half-finished product. It is the smallest thing you can build to learn whether people want what you are making, without wasting months on features nobody asked for.
Get the MVP right and you save your runway. Get it wrong (either by shipping too much or by shipping something that does not actually solve the problem) and you burn time and money proving nothing.
What "minimum" and "viable" really mean
Both words carry weight:
- Minimum: The fewest features required to deliver the core value. Everything that is not essential to that core gets cut, delayed, or faked.
- Viable: It must genuinely work well enough that real users get value and give you honest feedback. A broken product teaches you nothing except that it is broken.
The tension between the two is the whole point. Too minimal and it is not viable; too viable and it is no longer minimal. The sweet spot is the smallest build that still lets someone reach a real outcome.
MVP vs prototype vs proof of concept
These three get confused constantly:
- Proof of concept (PoC): Answers "can this be built?" Usually internal and technical.
- Prototype: A clickable or visual model of the experience. Answers "how should it look and feel?" Not usually functional under the hood.
- MVP: A real, usable product in the hands of customers. Answers "do people want this and will they use it?"
You do not always need all three. If your risk is technical, start with a PoC. If your risk is demand (which it usually is), skip straight to a lean MVP or even a demand test on a landing page.
Famous MVP examples
- Dropbox: Released a 3-minute demo video instead of a finished product. Waitlist sign-ups went from 5,000 to 75,000 overnight, proving demand before the hard engineering.
- Airbnb: The founders photographed and rented air mattresses in their own apartment on a bare-bones website to prove strangers would pay to stay.
- Zappos: The founder photographed shoes in local stores and only bought them when someone ordered online, testing whether people would buy footwear on the internet at all.
- Buffer: Launched with a landing page describing the product and pricing. Only after people clicked "Plans and Pricing" did the founder build the app.
Notice the pattern: each MVP tested the riskiest assumption for the least effort, and often without building the full product at all.
How to build an MVP in 5 steps
1. Identify the one core problem
An MVP solves a single problem well, not five problems poorly. Name the one job your first users are hiring the product to do.
2. Map the critical path
Trace the shortest sequence of steps a user takes to get value: sign up, do the one key action, receive the outcome. That path is your MVP. Everything off it is a candidate to cut.
3. Ruthlessly cut features
List every feature you imagine, then ask of each: "Can a user get the core value without this?" If yes, it is not in the MVP. Settings pages, integrations, and admin dashboards can almost always wait.
4. Pick the lightest build that works
Consider, in order of effort:
- Concierge MVP: Deliver the outcome manually behind the scenes. Great for services.
- No-code MVP: Assemble it from existing tools before writing custom code.
- Single-feature app: A narrow, well-built product that does one thing.
5. Ship it and measure behavior
Put it in front of real users and watch what they do. The key MVP metric is not sign-ups but retention: do people come back and use it again? Return usage is the clearest signal that you built something valuable.
What to measure
Vanity metrics (page views, total sign-ups) feel good but mislead. Track instead:
- Activation: What share of users reach the core value the first time?
- Retention: Do they return in week two, week three?
- Willingness to pay: Will they upgrade, pre-order, or refer others?
If retention is flat, more features will not save you. Return to idea validation and rethink the problem or the audience.
Common MVP mistakes
- Building too much. The most common failure. If you are not slightly embarrassed by the first version, you shipped too late.
- Confusing an MVP with a cheap product. Minimum in scope, not in quality of the core experience.
- Skipping validation. Build the MVP after you have demand signal, not as your first demand test.
- Ignoring the metric that matters. Retention beats sign-ups every time.
From MVP to real business
An MVP that shows strong retention has earned real investment. Document what you learned in a lean business plan, then expand along the critical path your users already value. If you are still deciding what to build, our guides on validating a startup idea and AI business ideas will help you choose.
AIdea Hub takes you from idea to a scoped MVP with AI-guided steps, so you build the smallest right thing instead of the biggest wrong one. Start building your MVP today.
Frequently asked questions
What is considered a minimum viable product?+
A minimum viable product (MVP) is the simplest version of a product that still delivers real value to early users and lets you learn from their behavior with the least effort. "Minimum" means you strip away every feature that is not essential to the core value. "Viable" means it must actually solve the problem well enough that people will use it and give feedback.
How do you create an MVP?+
Create an MVP in five steps: (1) identify the single core problem your product solves, (2) map the one critical path a user takes to get value, (3) list features and cut everything not on that path, (4) build the smallest working version, sometimes even a manual or "concierge" version, and (5) put it in front of real users and measure whether they come back. The goal is learning, not perfection.
What is an MVP with an example?+
Dropbox is a classic MVP example. Before building the complex file-syncing engine, the founder released a short demo video showing how it would work. Sign-ups jumped from 5,000 to 75,000 overnight, validating demand before heavy engineering. Airbnb is another: the founders rented air mattresses in their own apartment and built a basic site to prove people would pay to stay in a stranger's home.
What's the difference between an MVP and a PoC?+
A proof of concept (PoC) tests whether something is technically possible and is usually internal, answering "can we build this?" An MVP is a real, usable product released to customers to test whether people want it and will use it, answering "should we build this?" A PoC validates feasibility; an MVP validates desirability and the market. A prototype sits between them as a clickable model of the experience.
How much does it cost to build an MVP?+
An MVP can cost anywhere from almost nothing to tens of thousands of dollars. A no-code or concierge MVP, where you deliver the service manually, can be built in days for the cost of your time. A custom-coded MVP typically ranges from a few thousand to around $30,000 depending on scope. The point of an MVP is to spend as little as possible to answer your riskiest question.
Keep reading
Put this into practice
AIdea Hub guides you from idea to launch with AI at every step: validation, market research, planning, and go-to-market.
Start an idea