Minimum viable product (MVP)

Business basics2min read

A minimum viable product (MVP) is a version of a new product that lets a business test a key assumption with real users before investing in a fuller build. The aim is useful evidence with the least necessary effort.

Outside business, MVP often means "most valuable player." "Viable minimum product" (VMP) is not the standard expansion of the business term.

How it works

Start with a risky question: will customers pay, return or change their behavior? Build only what you need to test it. Set a success threshold before launch so you cannot redefine success afterward.

An MVP can be a manually delivered service, not just software. "Minimum" removes unnecessary features; "viable" means customers get enough of the promised value to make the test meaningful.

Four paying customers before writing code

A founder wants to sell automated inventory reports to restaurants. Instead of building software, she prepares reports in a spreadsheet.

For this hypothetical test, she sets a threshold: at least 4 of 10 restaurant owners must pay $50 for one report.

MeasureCalculationResult
Owners offered the serviceTest group10
Owners who payActual purchases4
Purchase rate4 ÷ 1040%
Revenue4 × $50$200

The test meets her chosen threshold, not an industry benchmark. It supports further testing of demand. It does not prove customers will renew or that delivery will be profitable. Her next step is to test repeat purchases before funding a full software build.

Questions people ask

What is MVP and why is it important?

An MVP tests whether a product idea deserves more investment. For a startup, that can mean preserving runway by discovering weak demand before spending months on development. Shipping a small product without measuring anything misses the point.

Is an MVP the same as a prototype?

A prototype can test design or technical feasibility. An MVP tests business assumptions through customer evidence. A prototype can serve as an MVP if it produces that evidence.

Related terms

Sources

  1. Eric Ries, The Lean Startup, 2011.