The short definition
An MVP is a working product, not a mockup, with just enough features to deliver its core value to early users. Its job is to answer one question as cheaply and quickly as possible: will people use this, and will they pay for it?
What an MVP is not
- Not a prototype: prototypes are for showing; MVPs are for using
- Not a half-finished product: what's there should work well
- Not every feature on your roadmap: an MVP does one job brilliantly
- Not a throwaway: a good MVP is built so you can keep extending it
How to decide what goes in
Write down the one job your product must do for one type of user. Then list every feature and keep only those without which that job can't be done. Sign-up, the core workflow and a way to pay usually make the cut; settings pages, advanced reports and integrations usually don't.
Examples
PMBuddy started as a single flow: paste a PRD, get user stories. SportCliq started with booking and payments for one sport before expanding. Both launched as MVPs and grew from real feedback.
How long should an MVP take?
Most MVPs can be designed and built in 2–4 weeks with a tight scope. GetMVP's process launches most first versions in about 14 days.
Frequently asked questions
What does MVP stand for?
Minimum viable product: the smallest version of a product that delivers real value to real users.
What's the difference between an MVP and a prototype?
A prototype shows how a product might work; an MVP actually works and can be used by real customers.
How much does an MVP cost?
With GetMVP, from $230–$400 (about ₦350,000–₦620,000) to $1,190–$2,000 (about ₦1,845,000–₦3,100,000) depending on scope. See the full cost guide.