MVP (Minimum Viable Product)
An MVP is the smallest version of a product that delivers real value to early users — built to test a business hypothesis with maximum learning per euro spent, not a cheap or low-quality first release.
What it is not
The most common confusion: an MVP is not a prototype and not a PoC. A PoC proves a technical assumption works; a prototype explores design and usability; an MVP is a real product — with real users and real feedback — scoped down to the one feature set that tests whether anyone wants the thing at all.
Good MVP scoping is subtraction with a thesis: pick the riskiest business assumption, ship the minimum that could disprove it, instrument the result. Teams that build “the MVP” as a phase-one feature list usually ship a small bad product instead of a learning instrument. Our MVP vs PoC vs prototype guide walks through the decision.
Frequently Asked Questions
What does MVP stand for?
Minimum Viable Product — the smallest product version that real users can use and that produces validated learning about whether the business idea works. Coined in the Lean Startup methodology, it is a test instrument, not a budget version of the final product.
What is the difference between an MVP and a PoC?
A PoC answers “can we build it?” — a disposable technical spike that de-risks feasibility. An MVP answers “should we build it?” — a real, minimal product put in front of users to test demand. You typically PoC first when technology is risky, MVP when the market is risky.
Further Reading
Products & Services
Need help with this?
We consult and build across all of these domains — tell us what you are working on.
