All Collections
Lean Startup Fundamentals
What is a Minimum Viable Product (MVP)?
What is a Minimum Viable Product (MVP)?

The smallest thing you can build that delivers customer value (and as a bonus captures some of that value back i.e. gets you paid).

Ash Maurya avatar
Written by Ash Maurya
Updated over a week ago

Race to Deliver Customer Value

The prime directive of an MVP is first and foremost racing to deliver on customer value. Furthermore, there is no business in your business model without revenue which also tends to be one of the riskier parts of the business model. 

This is why whenever your users are also your customers, I am a strong advocate of capturing back some of that value which is just a fancy way of saying “charge from day one and get paid”. 

When you have different users and customers, it is still critical to be able to identify 

  • how you capture monetizable value from your users and, 

  • how you convert this derivative asset to actual revenue with your customers.

A Stricter Definition?

This may seem like a stricter definition of MVP that you are used to seeing because it is. When Eric Ries, author of The Lean Startup, first used the term, he described it as:

A 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.

Over time it got simplified to: “the smallest thing you can build that lets you quickly make it around the build/measure/learn loop”. The problem with this simplified definition is that every thing shown in the image below would qualify as an MVP:

We've visited companies where some teams are launching landing pages, while other teams are building working prototypes. And both are labeled as MVPs. In order to meaningfully talk about a MVP, it is critical to standardize on a definition -- at least across your own company.

While many of the artifacts above are really (good) tactics for testing interest in a product though the use of a faster proxy for the product like a teaser page or demo, they aren’t a product by themselves and so fail the MVP test.

Here's how we triage them:


A cycle around the build/measure/learn loop is an experiment. It starts with a set of assumptions/hypotheses that you test which meets the textbook definition of an experiment.


An offer is used to test interest for your solution before building it and should come before your MVP. 

Solution interviews, teaser landing pages, smoke tests, and crowd-funding pages are all examples of offer types you can use at this stage. You use your offer both to test for customer pull and to refine your initial product specification (or minimum viable product).


Only if your offer is validated, do you give yourself permission to build out a MVP using one of the MVP archetypes: Release 1.0, Concierge, Wizard of Oz.

Did this answer your question?