Glossary
What Is an MVP (Minimum Viable Product)?
Updated · Team Fonda
Short answer
An MVP, or minimum viable product, is the smallest version of a product that lets you learn whether real customers want it. It does one job for one type of customer, and its purpose is to test your riskiest guess before you spend months building.
Key takeaways
- An MVP is a test, not a small version of your final product.
- Pick the one guess that would sink the business if it were wrong, and build only what tests it.
- Many MVPs need no code: a landing page, a form or a service you deliver by hand can be enough.
- Decide what result counts as a pass before you launch it.
What an MVP means in plain words
Every new business rests on guesses: that a problem exists, that people will pay to fix it, that you can reach them. An MVP is the lowest-cost thing you can put in front of customers to find out whether the most important guess is true. The term became common through the lean startup method, which treats a new business as a series of experiments.
Minimum means you cut every feature that does not help answer the question. Viable means it still solves the problem well enough that someone would use it or pay for it. A product that is small but useless teaches you nothing, because people ignore it for the wrong reason.
How an MVP works
- Write down your riskiest guess. For example: "Dog owners in my city will pay for a walker they book the same day."
- Choose the smallest test. Ask what a customer needs to see or do for you to learn the answer.
- Set a pass mark first. Decide the number of sign-ups or payments that would convince you, before you see results.
- Put it in front of real people. Friends and family are too kind. Use strangers who have the problem.
- Measure and decide. Keep going, change the product or pivot.
| Type of MVP | What you build | What it tests |
|---|---|---|
| Landing page | One page with an offer and a sign-up or pre-order button | Whether people want it enough to act |
| Concierge | You deliver the service by hand to a few customers | Whether the result is worth paying for |
| Wizard of Oz | A simple front end, with you doing the work behind it | Whether people use it the way you expect |
| Single feature | One working feature and nothing else | Whether the core job is done well enough |
A worked example
This is an illustration with made-up numbers. Say you want to build an app that matches dog owners with walkers. The app would take months. The risky guess is whether owners will pay a stranger at short notice.
Your MVP is a one-page site with a booking form, and you match owners to two walkers by text message. You set a pass mark: 10 paid walks in two weeks. You spend $150 on flyers and local posts. Forty owners fill in the form and 12 pay $15 for a walk. You passed, and you also learned that most bookings came for weekday lunchtimes, which tells you what to build first.
Why it matters for a first-time founder
The most expensive mistake a new founder makes is building something nobody wants. An MVP limits that loss to days or weeks. It also protects your runway, because you spend on learning rather than on features.
You meet the MVP after you have validated the idea through customer conversations and before you invest in a full product. In Fonda, the MVP plan is a step in the Launch phase, after the Validate phase has given you a Verdict of go, refine or pivot. For a full walkthrough, read how to build an MVP.
Common mistakes
- Building too much. If it takes many months, it is a first version, not an MVP.
- Skipping the conversations. An MVP tests a solution. You still need customer interviews to confirm the problem.
- No pass mark. Without one, any result can be read as good news.
- Counting compliments. Sign-ups, payments and repeat use are evidence. Kind words are not.
- Treating a weak result as final. One failed test rules out one version, not the whole idea.
Related terms
- Prototype: a model that shows how the product would look or work. It does not need to deliver real value.
- Proof of concept: a check that something can be built at all.
- Product-market fit: the point where a market clearly wants your product. The MVP is an early step toward it.
Frequently asked questions
What is the difference between an MVP and a prototype?
A prototype shows an idea so you can get feedback on it. An MVP is used by real customers to do a real job. You often make a prototype first, then an MVP.
Does an MVP need to be an app or software?
No. A physical product can start as a small handmade batch, and a service can start with three clients. What makes it an MVP is that it tests demand at low cost.
How long should an MVP take to build?
There is no fixed rule. Aim for the shortest time that still tests your guess. If the plan runs to many months, look for a smaller test, such as a landing page or a manual service.
Should you charge for an MVP?
If your guess is about willingness to pay, yes. A payment or a pre-order is much stronger evidence than a free sign-up, even at a low price.