What is an MVP (minimum viable product)? How to build one
What is an MVP? Minimum viable product meaning, Eric Ries' definition, MVP vs prototype vs proof of concept, and how to build one in 8-12 weeks.
An MVP (minimum viable product) is the simplest version of a product that tests one key assumption with real users - will people use it and pay for it. It is not a demo or a sketch. It is a working product, stripped of everything that test does not need.
What does MVP mean - the definition
The term was popularised by Eric Ries, author of The Lean Startup. His 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” (Ries, 2009). The key word is not “minimum” but “learning”: an MVP exists to find something out, not to save money.
What is an MVP in software development?
In software, an MVP is the first production version of an application: real login, real data, real payment, live on the internet. A user completes the whole path from first visit to payment with no manual work behind the scenes. The architecture is simple but clean, so it can be built on. (Not to be confused with MVP in sports and games, where it means most valuable player.)
MVP vs prototype vs proof of concept
| Proof of concept | Prototype | MVP | |
|---|---|---|---|
| Question | Can it be built technically? | Do users understand the solution? | Will people use it and pay? |
| Who sees it | The dev team | A few test users | Real users in the market |
| Does it work | Only the critical technical part | No, it is a clickable design | Yes, in production |
| Typical duration | Days to 2 weeks | 1-3 weeks | 8-12 weeks for a focused web MVP |
Why build an MVP at all
CB Insights analysed 431 VC-backed startups that shut down since 2023. Running out of capital was cited by 70%, but that is usually the final cause. The most common underlying reason was poor product-market fit - a product the market does not need - at 43% (CB Insights, March 2026). An MVP is how you find that out while the stake is still small.
Worked example: from 15 wishes to 5 features
Take an app for booking hair salon appointments online. The main assumption: clients will book online and pay a deposit instead of phoning. The founder brought a list of 15 wishes. For each one we asked: “If we remove this, can we still test the assumption?”
Five features stay in v1 (our hour estimates):
| Feature in v1 | Hours |
|---|---|
| Booking without signup, email confirmation | 60 |
| Salon calendar: opening hours, services, durations | 50 |
| Card deposit payment (Stripe Checkout) | 30 |
| Email reminder 24 hours before the appointment | 15 |
| Basic stats: bookings and cancellations | 25 |
| Setup, hosting, testing | 60 |
| Total | 240 |
That is roughly six weeks for one full-time developer, which fits the development part of the plan below.
Moved to v2: iOS and Android apps, user accounts, a loyalty programme, reviews, SMS reminders, multiple locations, chat with the salon, a till connection, coupons and staff roles. By our estimate the mobile apps alone would add more hours than the whole first version. The success metric was agreed upfront: the share of online bookings in three pilot salons after four weeks.
How to build an MVP: the 12-week plan
- Weeks 1-2: discovery. User conversations, main assumption, v1/v2 split, success metrics.
- Weeks 3-4: design and architecture. 3-5 key screens, stack choice, launch plan.
- Weeks 5-10: development. Weekly demos, gradual integration.
- Week 11: testing. Internal QA plus a beta with 5-10 external users.
- Week 12: launch. Production, analytics, first real users.
Twelve weeks holds for a focused web MVP like the example. Mobile apps, two-sided platforms or regulated industries take longer - we break down realistic timelines in how long custom software development takes. Even Ries’ first MVP, for IMVU, took six months.
Common mistakes
- Too much scope. If the MVP takes six months or more and did not have to, you are building the full product.
- No payment. A free version only shows whether people will try something for free.
- No success metrics. Write down the number that means “continue” before launch, not after.
- No conversations after launch. Numbers show what happens; conversations reveal why.
What comes after the MVP
If the data confirms the assumption, the product grows in phases - see phased software delivery for how to cut them. If you are not a startup but an existing business that needs one narrow tool, small-scope software projects fit better.
For development after launch we offer a monthly partnership for software maintenance and development, and we build the MVP itself through custom software development. Work outside the agreed scope is billed hourly at €40-60 excl. VAT.
Frequently Asked Questions
What does MVP stand for? MVP stands for minimum viable product. It is the simplest version of a product that works with real users and tests one key assumption - usually whether people will use the product and pay for it.
Is an MVP the same as a prototype? No. A prototype is a clickable design that does not work and checks whether users understand the solution. An MVP is a real product in production, with real data and payments, that tests demand.
How long does it take to build an MVP? A focused web MVP takes roughly 8-12 weeks, including discovery, design, development and testing. Mobile apps and two-sided platforms usually take longer. The timeline depends most on how strictly the scope is cut.
Can an MVP grow into the final product? Yes, if the architecture is clean from the start. A good MVP is not throwaway code but a foundation that gets extended in phases with what users actually asked for.
When should we decide to continue or stop? Usually 4-8 weeks after launch, against success metrics written down in advance. A shorter period rarely gives enough data for a decision.
Related Articles
- How long does custom software development take?
- Phased software delivery: how to split a project
- Custom software for small-scope projects
Thinking about an MVP?
Book a free intro call. We will help you reduce the idea to one testable assumption, cut the scope of the first version and set success metrics.
Reach out at info@tsunami-digital.com or via the form on our homepage.