MVP (Minimum Viable Product)

What it is

A Minimum Viable Product (MVP) is the smallest version of a product that lets you test a single, falsifiable hypothesis about a buyer’s behavior. The phrase was coined by Frank Robinson in 2001 and popularized in mainstream startup vocabulary by Eric Ries in The Lean Startup (Crown Business, 2011).

Ries’s definition is the one most people quote:

“The minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.”

Notice what is in that sentence: validated learning, least effort. Notice what is NOT in that sentence: a list of features, a number of weeks, an aesthetic standard. The MVP is defined by the hypothesis it tests, not by feature count.

What an MVP is NOT

The most common misuse of the term: founders treat MVP as a synonym for “version 1.0 with fewer features.” That misses the point.

What it actually is	What people often mean
A test for a specific hypothesis	A stripped-down launch
Designed to be killed if the hypothesis fails	Designed to be the foundation
Often not a working product at all (could be a landing page, a Wizard of Oz prototype, a manual fulfillment)	Always a working product
Measured by what you learned	Measured by how much you shipped

If your MVP cannot fail, it is not an MVP. It is just a small launch. The defining feature of an MVP is that it can produce evidence that kills the idea.

Common MVP types

Eric Ries and others (Steve Blank, Eric Migicovsky) catalogued recurring MVP patterns:

1. Landing page MVP. Describe the product, ask for sign-ups, measure conversion. Tests demand existence before any code is written.
2. Wizard of Oz MVP. The user thinks they are using software; humans are doing the work behind the curtain. Tests whether the experience is valuable before you automate it.
3. Concierge MVP. You explicitly do the work manually for a small group of paying customers. Tests willingness to pay AND the underlying workflow.
4. Single-feature MVP. The product does ONE thing. Tests whether that one thing is enough to drive retention.
5. Smoke test MVP. An ad campaign or pre-order page for a product you have not built. Tests whether marketable demand exists at the price point you intend.

The right type depends on what hypothesis you are testing. Demand? Use a landing page or smoke test. Workflow validity? Wizard of Oz or Concierge. Retention? Single-feature.

How to scope an MVP

The discipline is to write down one hypothesis BEFORE you scope:

“[Buyer segment] will [take specific action] in response to [product offering] because [underlying reason].”

Example: “Solo founders will pay $50 to receive a custom-generated buyer persona report within 24 hours, because they are stuck on Stage 2 of validation and have no other affordable options.”

Then ask: what is the smallest test that could falsify this? Often the answer is not a product. It’s a landing page, a Twitter post offering the service, or an email to ten people in your network.

If the smallest test takes six months and $50K, you didn’t pick the smallest test. You picked a launch.

Common mistakes

1. Equating MVP with version 1.0. They are different things. Version 1.0 is your launch product. The MVP comes earlier and is allowed to die.

2. Refusing to ship until it’s beautiful. The MVP exists to learn, not to launch. If you cannot ship something embarrassing, you cannot learn fast.

3. Building a “stripped down” product without naming the hypothesis. A feature-trimmed product without a learning hypothesis is just a small launch. You will not know what to do with the result.

4. Treating the MVP as the foundation. If the MVP succeeds, you often need to throw most of it away and rebuild for scale. The MVP’s job was learning, not load-bearing architecture.

5. Skipping the MVP because “we’re past that.” Even mature companies should test new bets with MVPs. The Lean Startup framework is not just for pre-seed; it is a discipline for any new initiative whose outcome is uncertain.

How ShipFit approaches MVP scoping

ShipFit’s Stage 5 (What’s V1?) explicitly forces you to write down the hypothesis your MVP tests, then scopes the product down to the smallest version that could falsify it. The output is a feature list paired with the metric that defines success or failure. If your hypothesis is “buyers will pay $50 for a persona report,” the MVP is a landing page and a Stripe checkout, not a full SaaS dashboard. The dashboard comes after the hypothesis is validated.

The point is to refuse to scope an MVP without first naming what you are trying to learn from it.

Further reading

• Eric Ries, The Lean Startup (Crown Business, 2011). The popular source. Chapters 6-7 cover MVP types in detail.
• Frank Robinson’s writing on the original 2001 coinage of “MVP.”
• Steve Blank, The Four Steps to the Epiphany (2005). The customer-development methodology that the MVP concept slots into.
• Lean Startup validation framework. The wider discipline MVP belongs to.
• Product-Market Fit glossary. The goal an MVP works toward.