# Minimum Viable Product: What It Is and How to Build One

> Source: [https://botensten.com/articles/what-is-a-minimum-viable-product](https://botensten.com/articles/what-is-a-minimum-viable-product) (canonical)
> Author: Botensten — Botensten, https://botensten.com
> Published: 2026-07-17

## TL;DR

A minimum viable product (MVP) is a version of a product built with only the core features needed to satisfy early users and gather feedback. Coined by Eric Ries in The Lean Startup (2011), it exists to test business assumptions cheaply through the Build-Measure-Learn loop rather than to ship a finished product. A strong MVP can reduce product failure risk by up to 90%, and most cost between $50,000 and $200,000 to build. The goal is to learn fast, then iterate, pivot, or stop.

A minimum viable product is a working product with just enough features to satisfy early customers and generate feedback for the next round of development — a concept Eric Ries popularized in his 2011 book The Lean Startup. The point is learning, not polish. An MVP exists to test a hypothesis, not to impress. Teams that validate demand this way can cut product failure rates by as much as 90%.

## What is a minimum viable product?

A minimum viable product is a working product with just enough features to satisfy early customers and generate feedback for the next round of development. The point is learning, not polish. You ship the smallest thing that tests your riskiest assumption, then you watch what real people do with it.

Eric Ries introduced the term in [The Lean Startup](https://www.leanstartup.co/), and it now anchors most modern product thinking. An MVP is not a cheap or broken version of your final vision. It is a deliberate experiment. Every release answers one question: will people actually use and pay for this?

The word "viable" matters as much as "minimum." A viable product delivers real value to a real user. A landing page with a fake button is a test, but it is not a product. The skill is finding the smallest build that still counts as both.

## What are the benefits of an MVP?

The main benefit is that you spend money learning instead of guessing. Building a full product on an untested idea is the most common way startups burn through cash. An MVP shrinks that risk to something you can afford.

Here is what a disciplined MVP buys you:

- Faster feedback — you hear from users in weeks, not quarters.
- Lower cost — you build one slice instead of the whole thing.
- Evidence before scale — you confirm demand before hiring or fundraising.
- A clear kill signal — if nobody wants it, you find out early and cheaply.

[McKinsey](https://www.mckinsey.com/) has documented how tightly scoped first releases help teams avoid over-building features customers never touch. Some research suggests a well-run MVP process can reduce product failures by up to 90%. That restraint is the whole game.

## How do I build a minimum viable product?

Building an MVP follows the Build-Measure-Learn loop. You build a small version, measure how people respond, and learn what to do next. Then you repeat the loop with a sharper question.

Follow these five steps:

1. Write down the single assumption that, if wrong, kills the idea.
2. Talk to 10-15 target customers before you write any code.
3. Define the one core feature that tests that assumption.
4. Ship it to a small group of real users.
5. Measure behavior, then decide to persevere, pivot, or stop.

I always start with step two. On my own projects, the customer interviews described in The Mom Test have saved me from building things nobody asked for. Skipping those conversations is how you end up with a beautiful product for an empty room. Code is expensive; a coffee-shop conversation is nearly free.

## What are the key characteristics of an MVP?

A real MVP is usable, focused, and measurable. It does one thing well enough to test a hypothesis. It is not a landing page with no product behind it, and it is not a half-finished app with fifty broken features.

The table below shows how an MVP differs from two things people often confuse it with:

| Type | Goal | Audience | Typical cost |
|------|------|----------|--------------|
| Prototype | Show an idea | Internal team, investors | Low |
| MVP | Test real demand | Early customers | $50,000-$200,000 |
| Full product | Serve the market | All customers | High |

Cost varies widely by industry — MVPs ship in software, e-commerce, and healthcare — but [ProductPlan](https://www.productplan.com/) notes the defining trait never changes: enough value to earn honest feedback. The dollar figures above are typical ranges, not rules.

## What common mistakes should I avoid?

The biggest mistake is building too much. Founders fall in love with features and call the result an MVP when it is really a full product in disguise. The second mistake is treating the MVP as a one-time launch instead of a repeating loop.

Watch for these traps:

- Adding features before validating the core one.
- Shipping only to friends instead of real target customers.
- Measuring vanity metrics like signups instead of actual usage.
- Ignoring feedback because it contradicts your original plan.
- Never defining what "success" or "failure" means before you launch.

Customer feedback is the fuel for the entire process. Without it, you are just guessing with extra steps and a bigger bill.

## How do I measure and improve an MVP?

You measure an MVP by whether it validated or killed your assumption. Pick one or two metrics tied to real behavior — activation, retention, or willingness to pay — before you launch. Then let the data, not your ego, make the call.

After each cycle you have three honest options:

1. Persevere — the data supports the idea, so keep building.
2. Pivot — the core assumption failed, so change direction while keeping what you learned.
3. Stop — the market said no clearly, so save your remaining runway for the next bet.

Iteration never truly ends. Steve Blank and Ash Maurya, author of Running Lean, both frame a startup as a search for a repeatable business model, and the MVP is your main search tool. Keep the loops short, keep the feedback honest, and improve one assumption at a time.

## Related reading

- [How to Validate a Business Idea Before You Build](/articles/how-to-validate-a-business-idea)
- [How to Build a Minimum Viable Product: A Skeptic's Guide](/articles/how-to-build-a-minimum-viable-product)
- [Remote Team Best Practices: Hire and Manage for Outcomes](/articles/hiring-managing-remote-team-best-practices)
- [How to Start a Solopreneur Business: A Practical Guide](/articles/how-to-start-a-solopreneur-business)

## Frequently asked questions

**What is a minimum viable product?**

A minimum viable product (MVP) is a product built with just enough features to satisfy early customers and produce feedback for future development. It tests a hypothesis rather than trying to be perfect.

**What are the key characteristics of a minimum viable product?**

An MVP is usable, focused, and measurable. It delivers real value with one core feature and lets you gather honest feedback, unlike a prototype or a fully built product.

**How do I develop a minimum viable product?**

Identify your riskiest assumption, interview 10-15 target customers, build the single feature that tests it, ship to real users, then measure behavior and decide to persevere, pivot, or stop.

**What are the benefits of using a minimum viable product?**

An MVP gives you faster feedback, lower cost, and evidence of demand before you scale. A disciplined MVP process can reduce product failure risk by up to 90%.

**How do I measure the success of a minimum viable product?**

Success is whether the MVP validated or killed your assumption. Track one or two real behavior metrics, such as activation, retention, or willingness to pay, chosen before launch.

**What role does customer feedback play in an MVP?**

Customer feedback is the core input of the Build-Measure-Learn loop. Without real feedback from target users, an MVP is just guessing, so talking to customers comes before building.

**Can a minimum viable product be used in enterprise software development?**

Yes. MVPs work in software, e-commerce, healthcare, and enterprise settings. The scope and cost grow, but the principle of testing one assumption before full build stays the same.