What Is a Minimum Viable Product (MVP)? Definition, Types and Examples
What a minimum viable product is, how it differs from a prototype, the main types with real examples, and how to build one without overbuilding.
By Suren, Founder & Growth Strategist at Gufy · Published · Last updated
A minimum viable product (MVP) is the smallest version of a product that lets you learn whether real customers want it. It is not a cheap or unfinished product. It is a test: the least you can build to find out if your most important assumption is true.
The term was coined by Frank Robinson in 2001 and made popular by Eric Ries in The Lean Startup, where the idea is to learn as much as possible about customers for the least effort.
What an MVP is for
- Testing demand before you spend heavily. Many products fail because nobody wanted them, not because they were badly built.
- Focusing on the core outcome. One thing that matters to one kind of customer.
- Getting evidence. Real use and real payment tell you, and any investors, more than a plan does.
- Learning what to build next. What people do with a first version is a better guide than what they say they want.
MVP, prototype or proof of concept?
These are often confused. They answer different questions.
| Type | Question it answers | Who uses it | Example |
|---|---|---|---|
| Proof of concept | Can this be built? | Your own team | A rough technical test |
| Prototype | How should it work? | Test users, in a session | Clickable screens |
| MVP | Do people want it, and will they pay? | Real customers | A working first version, or a manual service |
Seven types of MVP
An MVP does not have to be software. Choose the cheapest type that will test your biggest assumption.
| Type | What it is | Good for testing |
|---|---|---|
| Landing page | A page describing the product with a sign-up or pre-order | Whether people want the outcome |
| Demo video | A short video showing how it would work | Interest in something hard to explain |
| Concierge | You deliver the service by hand to a few customers | Whether the outcome is worth paying for |
| "Wizard of Oz" | Looks automated to the customer, with a person doing the work behind it | Demand, before building the technology |
| Single feature | One function, built properly | Whether the core job matters enough |
| Pre-order | Customers pay before the product exists | Willingness to pay |
| Piecemeal | Existing tools joined together to deliver the result | Whether the whole workflow is useful |
Real examples
Dropbox tested demand with a short video showing the product working, before the full product was available. Sign-ups to the waiting list rose sharply, which told the founders people wanted it.
Zappos began with photographs of shoes taken in local shops. When someone ordered, the founder bought the pair and posted it. That tested whether people would buy shoes online without building a warehouse.
Buffer started as a simple landing page describing the product, with a pricing page behind the sign-up button. Clicks on a paid plan showed willingness to pay before the product existed.
Airbnb started when the founders rented air mattresses in their own apartment to people attending a conference. That first test showed strangers would pay to stay in someone's home.
Instagram grew out of a check-in app called Burbn. Its founders saw that photo sharing was the part people used, and cut the product back to that.
In each case the first version tested one question, cheaply.
How to build an MVP
1. Write down the riskiest assumption
Usually it is one of these: people have this problem, they will pay to solve it, or they will switch from what they use now. Your MVP exists to test that one thing.
2. Choose one customer and one outcome
Talk to at least five potential customers who do not know you. Find the outcome they care about most, in their words. The SaaS Idea Validation Playbook covers how to run those conversations.
3. Pick the cheapest type that tests it
If a landing page with a real offer answers the question, do not build an app. Building a full product is one of the most expensive ways to test an idea.
4. Cut the feature list
List everything you think the product needs. Keep only what is required to deliver the one outcome. Everything else waits. That outcome is the product's aha moment, and the MVP is the shortest path to it.
5. Put it in front of real customers
A small number is enough. Start with people from your conversations.
6. Measure what they do
| Signal | What it tells you |
|---|---|
| People pay or commit | The problem is worth solving |
| They reach the first useful moment | The product delivers |
| They come back unprompted | The need is recurring |
| They tell someone else | It solves something they care about |
7. Decide
Go ahead and build more, change the customer or the scope, or stop. All three are useful outcomes.
Building an MVP without code
You may not need a developer for the first version.
- Landing pages: Webflow, Carrd, Unbounce
- Apps: Bubble, Adalo, Glide
- Automation: Zapier, Make
- Design and mock-ups: Figma, Canva
- Forms and feedback: Typeform, Google Forms
Check current plans and prices before you commit, as they change.
Once people are using it, how to tell if you have product-market fit is the next question.
Common mistakes
- Building too much. If the first version takes many months, it is not minimal.
- Treating "minimum" as an excuse for something that does not work. It still has to deliver the one outcome.
- Testing with friends. They are kind, not accurate.
- Counting sign-ups as proof. A sign-up is interest. A payment is demand.
- Not deciding in advance what success looks like. Then any result can be read as encouraging.
Common questions
What is a minimum viable product in simple terms?
It is the smallest version of a product that lets you learn whether real customers want it. It does one thing well enough for someone to use, and it exists to test an assumption, not to impress anyone.
What is the difference between an MVP and a prototype?
A prototype shows how something would work and is used to test the design. An MVP is used by real customers to test whether they want it and will pay. A prototype can be a set of clickable screens. An MVP has to deliver the actual outcome, even if a person does the work behind the scenes.
How long should it take to build an MVP?
Weeks, not many months. If the first version is taking longer than that, it is probably doing too much. Cut it back to the one outcome your first customers care about most.
Does an MVP have to be software?
No. A landing page with a real offer, a demo video, or a service you deliver by hand can all be an MVP. What matters is that it tests whether people want the outcome, with the least effort on your side.
Where Gufy fits
Gufy does not build products. We help founders test demand and plan the launch: audience research, messaging, landing pages, tracking and the first acquisition tests. See go-to-market strategy and growth workshops.