Glossary
The first version of a piece of software reduced to its essential functions, put into service quickly to validate real needs with real users before investing in the rest.
An MVP (minimum viable product) is the smallest version of a piece of software that solves a real problem for real users. Not a mockup, not a throwaway prototype: a production system, limited to the core. The goal is to learn fast what matters before building what may never matter.
Requirements written on paper are always partly wrong. Once the software is in employees' hands, priorities shift: the feature deemed essential is barely used, and a forgotten detail blocks everyone. The MVP surfaces those surprises after two months rather than a year, while the budget is still there to adjust.
For a WMS, it is barcode receiving and picking, without advanced reports or carrier integration. For a CRM, it is the opportunity list and follow-ups, without email automation. For a custom ERP, it is often the most painful module (quoting, production or inventory) delivered on its own and connected to the existing accounting.
It is not an excuse to ship sloppy work. An MVP is reduced in scope, not in quality: the features it includes are tested, secured and production-ready. A poorly built MVP turns into technical debt by phase two.
Updated on
From 6 to 16 weeks for SMB management software, depending on required integrations. Beyond four months, the scope is probably too broad for an MVP.
No. Unlike a prototype, the MVP is the foundation the following phases build on. That is why its technical quality matters as much as the final product's.
