Minimum Viable Product: What to Build First, and When
A minimum viable product (MVP) is the smallest version of a product that real buyers can use or pay for, built to answer one question: will people pay for this? Think of it as a test with a product attached. Before you build one, check that the problem is real and that people already pay to solve it, so the MVP tests your version of the solution, not whether the market exists.
What is a minimum viable product, in plain words?
An MVP has three parts, and each word in the name does a job:
- Minimum: the least you can build that still lets a buyer get the result. Everything else waits.
- Viable: it actually works for the buyer. A broken or confusing first version tests your bugs, not your idea.
- Product: someone can use it or pay for it. A survey or a pitch deck is research, not an MVP.
The point is learning. You ship the MVP to find out what buyers do, not what they say they would do.
What should an MVP prove?
Decide what the MVP has to prove before you build it, and write down the number that counts as a yes. Most MVPs try to prove one of these:
| Question | What the MVP tests | A yes looks like |
|---|---|---|
| Will they pay? | Your price and your offer | Paid orders or pre-orders at the price you set |
| Will they use it? | Whether the product delivers the result | Buyers come back and use it again |
| Can you reach them? | Your channel and your message | Signups or sales at a cost you can live with |
| Is this the right version? | Your angle on a known problem | Buyers pick you over what they use now |
One MVP, one question. If you try to prove all four at once, a weak result tells you nothing about which part failed.
What does the smallest MVP look like for each kind of idea?
The smallest honest version depends on what you sell:
| Kind of idea | Smallest MVP | What it costs you |
|---|---|---|
| Physical product | A pre-order page with photos of a sample, or a small first batch | A sample and a few days |
| Digital product | A short first version (one template, one module) sold at a low price | A weekend of work |
| SaaS | One workflow done well, or done by hand behind the scenes | A few weeks, or your own time |
| Mobile app | One core screen in a TestFlight beta, with a waitlist page | A few weeks |
For a SaaS, doing the work by hand at first (sometimes called a concierge MVP) is often the quickest test to start: buyers pay for the result, and you learn the workflow before you automate it. For a digital product, the first paid version is the MVP; see how to validate a digital product idea.
If you only want to learn whether people click “buy” before anything exists, that is a fake door test, which is cheaper still.
What should you check before you build an MVP?
An MVP is the most expensive test in the validation order, so run the cheap checks first:
- Pain. Do buyers describe the problem in their own words? Finding pain points on Reddit shows what real pain reads like.
- Pay. Do people already pay to solve it? Competitor prices, marketplace listings and ads that keep running say yes. See how to find competitors for a product idea.
- Room. Do buyers complain about what exists? Those complaints are your angle.
- Price. What will you charge, anchored on a real competitor? How to price a new product covers the method.
If those checks come back empty, building an MVP only confirms it slowly. The guide to signs your product idea is bad lists what an empty result looks like and what to change.
What are the most common MVP mistakes?
- Building too much. Features nobody asked for delay the answer and blur it.
- No number set in advance. Without a target, any result feels like a maybe.
- Testing with friends. Friends are kind. Strangers who pay are the signal.
- Skipping the price. Free signups prove interest, not payment. Ask for money, or at least a pre-order.
- Calling a weak result a pivot too early. A low number can mean the wrong channel, not the wrong idea. Check one variable at a time.
How do you know the MVP worked?
Compare the result with the number you wrote down before launch. Hit it, and you have a reason to build the next piece. Miss it badly, and change one thing (the buyer, the angle or the price) before you try again. Steady repeat use and buyers who would be upset to lose the product are the early signs of product market fit.
FAQ
How long should an MVP take to build?
As short as it can while still working for the buyer. Days for a pre-order page or a digital product, weeks for software. If it takes months, it is probably more than minimum.
Is a landing page an MVP?
A landing page with a real price and a buy or pre-order button is a test of demand. It is often the step right before an MVP, not the MVP itself.
Should an MVP be free?
A free MVP proves interest at best. A price, even a low one, proves people are willing to pay.
What comes after the MVP?
Either the next feature buyers keep asking for, or a change to the buyer, angle or price if the number missed.
Check the idea before you build the MVP with Vettoz
Vettoz checks a product idea inside Claude, ChatGPT or Cursor before you spend weeks on an MVP. For one idea he reads Reddit threads and comments, X posts, TikTok and YouTube videos, active Meta ads, Google, and TikTok Shop or the App Store depending on the kind of product. He scores pain, demand, pay, room and reach from 0 to 100, with a GO, TEST or RETHINK verdict, and your AI writes the report with every source linked.
Your first 2 checks are free, no card. A full idea adds Branding and Marketing, and packs of 1, 4 or 15 ideas are one-time payments that never expire. To try it, connect Vettoz to your AI and type “check this idea with Vettoz” with your idea in one sentence. You can also see how it works or compare the packs first.