What is Minimum Viable Product (MVP)?
Minimum Viable Product: The smallest working version of a product that real users can use, built to test whether the core idea solves a real problem before you spend more.
A minimum viable product is the first version of a product that does one job well enough for real people to use it and give you honest signal. "Minimum" means you cut everything that does not test the core bet. "Viable" means it actually works: a user can sign up, get the outcome, and come back. A clickable mockup is not an MVP, and neither is a half-built app that crashes on the second screen.
The point of an MVP is learning, not launching. You pick the riskiest assumption (will people pay for this, will they change their habit, can the AI do the job accurately enough) and build the least software that answers it. Everything else goes on a later list. For AI products, the MVP usually wraps one model-powered workflow with just enough login, data handling, and UI to put it in front of paying users.
Why it matters when you build or buy AI
Most MVPs fail by being too big, not too small. If your scope document has more than one core workflow, a settings page with twelve toggles, and an admin dashboard, you are building version two before you know version one works. We cap MVPs at a fixed scope and a fixed date for this reason: a deadline forces the cuts that a budget never does. Do not buy an MVP if you have not talked to at least a handful of the people you expect to pay you; software will not fix a guess.
Example
A founder wants an AI tool that writes Shopify product descriptions. The MVP is a single page: connect a store, pick ten products, get descriptions back, approve and publish. No bulk editing, no team seats, no brand voice library yet.
Related terms
More in MVP & Product
Book 20 minutes, or send a brief
A former CTO replies. You leave with a written plan and a fixed estimate.
Prefer LinkedIn? Connect with Harish.