# Minimum Viable Product

_Also known as: MVP_

**Category:** Validation
**URL:** https://skiporship.com/glossary/minimum-viable-product
**Last updated:** 2026-08-08

## Definition

A minimum viable product (MVP) is the smallest version of a product that delivers real value to real users and produces reliable learning about whether the underlying idea works.

## What it means in practice

The purpose of an MVP is learning, not launching. It exists to answer a specific question — will this buyer change their behaviour and pay for this outcome? — at the lowest cost that still produces a trustworthy answer. Every decision about scope should be judged against whether it improves the quality of that answer.

"Minimum" is the most misread word in the term. It does not license a broken product; a version so rough that people abandon it teaches you nothing about demand, because you cannot distinguish rejection of the idea from rejection of the execution. The right reading is minimum *scope* at adequate *quality*: do one thing narrowly and do it properly.

An MVP does not have to be software. A landing page with a pre-order, a concierge service delivered manually, or a spreadsheet operated on a customer's behalf can all validate demand faster and more cheaply than a build — and each produces the same signal that matters, which is whether someone will pay.

## Worked example

Validating an automated invoice-chasing tool for freelancers.

- Full build: automated integrations, dashboards, reminder sequences — roughly 4 months of work.
- MVP alternative: manually chase invoices for 15 paying freelancers using existing tools, for a monthly fee.
- Cost: two weeks and no engineering.
- Learning: whether freelancers will actually pay to have this taken off their hands.

**Takeaway:** The manual version answers the only question that matters — willingness to pay — in two weeks instead of four months, and the customers it recruits become the first users of the real product.

## Common mistakes

- Reading "minimum" as "low quality". A broken product generates rejection you cannot interpret.
- Building an MVP with no specific question attached, so the result cannot change any decision.
- Assuming an MVP must be software when a manual or concierge version would answer the question sooner.
- Expanding scope during the build until the MVP becomes the full product and the learning arrives months late.

## Related tool

[Landing page validation guide](https://skiporship.com/guides/landing-page-validation)

## Related terms

- [Product-Market Fit](https://skiporship.com/glossary/product-market-fit) — Product-market fit is the point where a product satisfies a real, urgent demand well enough that customers adopt it, keep using it, and tell others — so growth starts pulling rather than being pushed.
- [Idea Validation](https://skiporship.com/glossary/idea-validation) — Idea validation is the process of gathering evidence that a business idea solves a real, urgent problem people will pay for — before committing significant time or money to building it.
- [Customer Discovery](https://skiporship.com/glossary/customer-discovery) — Customer discovery is the practice of interviewing potential customers about their existing problems and workflows — rather than pitching a solution — to learn whether a problem worth solving genuinely exists.
- [Problem-Solution Fit](https://skiporship.com/glossary/problem-solution-fit) — Problem-solution fit is the stage at which you have confirmed a real, urgent problem exists and that your proposed solution genuinely addresses it — the milestone before product-market fit.

## FAQ

**How long should it take to build an MVP?**

For a focused single-workflow product, six to twelve weeks is typical. If your MVP will take longer than about three months, the scope is almost certainly too broad for something whose purpose is to produce a fast answer.

**What is the difference between an MVP and a prototype?**

A prototype demonstrates how something would work and is usually not used by real customers doing real work. An MVP is used by real customers for real outcomes, which is why it can validate willingness to pay while a prototype cannot.

**Should an MVP be free?**

Usually not. Charging is the sharpest validation signal available — people who pay have made a decision that free users never have to make. Free MVPs frequently produce encouraging usage that evaporates the moment a price appears.

---
Full glossary: https://skiporship.com/glossary · Site index: https://skiporship.com/site-index