The smallest version of a product that lets you test a single, falsifiable hypothesis about a buyer's behavior. Coined by Frank Robinson in 2001; popularized by Eric Ries in The Lean Startup (2011). Often not a working product at all (a landing page, a Wizard of Oz prototype, a manual concierge service). The defining feature: it can fail. If your MVP can't fail, it's not an MVP, it's just a small launch.
The fast version
An MVP (Minimum Viable Product) is the smallest version of a product that lets you test a single falsifiable hypothesis about a buyer’s behavior. Coined by Frank Robinson in 2001; popularized by Eric Ries in The Lean Startup (2011).
Ries’s definition:
“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.”
What’s in that sentence: validated learning, least effort. What’s NOT: a list of features, a number of weeks, an aesthetic standard.
What an MVP is NOT
The most common misuse: 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 (a landing page, Wizard of Oz, 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
- Landing page MVP. Describe the product, ask for sign-ups, measure conversion. Tests demand existence before any code is written.
- 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.
- Concierge MVP. You explicitly do the work manually for a small group of paying customers. Tests willingness to pay AND the underlying workflow.
- Single-feature MVP. The product does ONE thing. Tests whether that one thing is enough to drive retention.
- Smoke test MVP (Fake Door). 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 Fake Door Test. Workflow validity? Wizard of Oz or Concierge. Retention? Single-feature.
How to scope an MVP
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 option.”
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.
How ShipFit operationalizes this
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. The system applies MoSCoW and ICE so cuts are visible instead of hidden in a spreadsheet.
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.
Further reading
- MVP glossary entry, short definition + history of the term.
- MVP scoping spoke, the deeper workflow.
- The Lean Startup framework, the wider discipline MVP belongs to.
- Eric Ries, The Lean Startup (2011), the source.
Related
The Lean Startup
Eric Ries's Lean Startup, stripped of consultant fluff. Validated learning, Build-Measure-Learn, MVP, pivot or persevere. What it means and where it gets misapplied.
MoSCoW
MoSCoW prioritization scopes V1 by sorting features into Must, Should, Could, and Won't. The honest version cuts ruthlessly and ships in weeks, not months.
ICE Scoring
ICE Scoring multiplies Impact × Confidence × Ease to rank features and experiments. The honest version forces you to defend Confidence with evidence.
MVP Scope
Most founders ship an MVP that's actually V1.3 with bugs. Real MVP scoping cuts ruthlessly until you can name the one hypothesis V1 proves, and ships a product that tests it.
MVP (Minimum Viable Product)
The smallest version of a product that lets you test a falsifiable hypothesis about a buyer's behavior. Coined by Frank Robinson in 2001; popularized by Eric Ries in 'The Lean Startup' (2011). Not a stripped-down launch product. A learning tool.
Frequently asked questions
Is an MVP just a stripped-down version 1?
How long should it take to build an MVP?
What's the difference between an MVP and a prototype?
Should I ship the MVP publicly?
What if my MVP succeeds, do I keep building on it?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
Eric Ries's Lean Startup, stripped of consultant fluff. Validated learning, Build-Measure-Learn, MVP, pivot or persevere. What it means and where it gets misapplied.
The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.
Most founders ship an MVP that's actually V1.3 with bugs. Real MVP scoping cuts ruthlessly until you can name the one hypothesis V1 proves, and ships a product that tests it.
Most founder market research is a TAM slide that nobody believes. The numbers that actually matter are smaller, harder to defend, and tell you whether the market exists for the ten-customer version of your business.
Does each customer make you money? Or cost you money?
Run nine framework-backed decisions in order before writing code: define the buyer, prove the pain is painful, name the winning angle, scope V1 to the smallest test of the hypothesis, get behavioral evidence (paid pre-orders, signed letters of intent, or credit cards on file from a Fake Door Test), then ship. Most failed startups skipped at least three of those nine. Plan to spend two to four weeks on this. It saves six to nine months of building the wrong thing.
For indie hackers who've wasted months on dead ideas. ShipFit forces 9 decisions before you write a line of code. Proven frameworks, exports to Cursor.
If you want a conversation partner, Buildpad. If you want to stop researching and ship, ShipFit. Both solve different problems for different founders. Don't pick on hype.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.