Skip to content

MVP: how to build the first version of your product without wasting a year

A founder spends eighteen months and most of their savings building an app with forty features. On launch day, people use five of them. The one feature customers love was added in the last week, almost as an afterthought. Nobody planned to waste a year. They simply built everything before learning anything.

Building software4 min readBy Reoncore Labs

Short answer

An MVP (minimum viable product) is the smallest version of a product that real users can use, built to test your riskiest assumption as quickly and cheaply as possible. It can be a landing page, a manual service behind a simple form, a clickable prototype or an app that does one job well. Decide in advance what result would prove or disprove the idea, launch to real users, measure, and only then build more.

01Two famous MVPs that built almost nothing

  • Dropbox. Before the product was ready, founder Drew Houston made a short video showing how file syncing would work. According to Eric Ries's account in The Lean Startup, the waiting list grew from about 5,000 to 75,000 people overnight. The video proved demand before the hardest engineering was finished.
  • Zappos. To test whether people would buy shoes online, founder Nick Swinmurn photographed shoes in local shops and posted them on a simple website. When someone ordered, he bought the pair from the shop and shipped it. No warehouse, no stock, just proof that customers would buy.

Neither MVP was a small version of the final product. Each was the cheapest way to answer the one question that mattered most.

02What an MVP is, and what it is not

The term was popularised by Eric Ries in The Lean Startup. The idea is a loop: build the smallest thing that tests an assumption, measure what real users do, learn, and decide what to build next.

An MVP is
Small, focused on one core job
An MVP is not
A full product with features removed at random
An MVP is
Built to learn something specific
An MVP is not
A launch to impress investors with features
An MVP is
Used by real users
An MVP is not
A demo only the team has seen
An MVP is
Safe with real data and payments
An MVP is not
An excuse to skip security, backups or honest terms

03Six kinds of MVP, from cheapest to most built

Kind
Landing page
What it is
A page describing the product, with a sign-up or pre-order button
Tests
Do people want it enough to leave a number or pay a deposit?
Kind
Concierge
What it is
You deliver the service by hand to a few customers
Tests
Does the solution actually solve their problem?
Kind
Behind the curtain
What it is
It looks automated to the customer, but people do the work behind it
Tests
Will they use it the way you expect, before you automate it?
Kind
Clickable prototype
What it is
Screens people can tap through, often built quickly with AI tools
Tests
Do they understand it, and does the flow make sense?
Kind
Single-feature product
What it is
Real software that does one job well
Tests
Will they use it repeatedly, and pay?
Kind
Pilot with one customer
What it is
A working version built with and for one paying customer
Tests
Does it deliver value in a real operation?

04Choosing what goes in

  1. 01Write down every assumption the idea depends on: who has the problem, how painful it is, whether they will pay, whether they will change habits.
  2. 02Mark the riskiest one: the assumption that, if wrong, kills the idea.
  3. 03Pick the cheapest MVP type that tests that assumption with real people.
  4. 04Define the one core job the product must do, and list everything else as “later”.
  5. 05Decide the success measure before launch, such as “30 of 100 sign-ups use it three times in the first two weeks”.

05Mistakes that sink first versions

  • Building for a year before showing anyone.
  • Adding features because a competitor has them.
  • No success measure, so every result can be read as encouraging.
  • Asking friends whether they like it instead of watching strangers use it.
  • Cutting the wrong corners: weak security or no backups once real users and data arrive.
  • Treating the MVP as the final architecture, and never rebuilding what was meant to be temporary.

06Is your MVP ready to launch?

  • We know the one assumption this version tests.
  • It does one core job well enough for a real user.
  • We have written down the result that would mean success, and the result that would mean stop.
  • We can reach at least twenty to fifty real potential users.
  • Real data and payments, if any, are handled safely.
  • We have time and budget to change direction after what we learn.

Key takeaways

  • An MVP is the smallest thing real users can use to test your riskiest assumption.
  • Often the best MVP is not software at all: a landing page, a manual service or a prototype.
  • Set the success measure before launch, then build, measure and learn.
  • Minimum means focused, not careless: real users and data still need safety.

Questions

What does MVP mean?

Minimum viable product: the smallest version of a product that real users can use, built to test the most important assumption behind the idea before investing in the full product.

What is the difference between an MVP and a prototype?

A prototype shows how something might work and is often only clicked through in a test. An MVP is used by real users in real situations, so you can measure whether they want it, use it and pay.

Should my MVP be a mobile app or a website?

Often a website or web app that works well on phones is faster and cheaper to build, update and share. A native app makes sense first when the core job needs phone features, offline use or frequent daily use.

How long should building an MVP take?

Weeks rather than many months for most ideas. If the plan takes a year, the scope is probably a full product. Look for a cheaper MVP type that tests the riskiest assumption sooner.

Last updated

Tell us what is not working.

Describe the problem in your own words. We will tell you honestly whether we can help, and how we would approach it.