Minimum viable product (MVP)
Also: MVP
What is Minimum viable product (MVP)?
A minimum viable product is the smallest version of a product that real users can use to complete a real job end to end, built to learn what to build next rather than to be complete.
What Minimum viable product (MVP) means
An MVP is a working product with one job done properly. A user can start, finish and get value without a demo operator standing beside them. For an AI product that means the model, retrieval, permissions, the interface, and the fallbacks when the model is unsure are all present, but only for a narrow scope: one user type, one workflow, one integration. Everything else is explicitly out.
Viable is the word people skip. An MVP that crashes, leaks data or cannot be measured is not viable; it is a prototype. AI MVPs need an evaluation harness and usage instrumentation from day one, because the point of shipping early is to learn from real usage, and you cannot learn from a system you cannot measure.
An MVP is not a POC, which proves a technical approach without real users. It is also not a stripped-down version of the full product roadmap; it is the full version of one thin slice. The most common failure is scope creep during the build, which is why Eazyware pairs every MVP with a scope lock.
Who it really matters to
- Founder / CEO: it is what investors and early customers can actually try, and it is the fastest way to find out whether the idea holds.
- Product manager: it forces the choice of the one job that matters, and produces usage data to decide the next one.
- CTO / Head of Engineering: a thin but complete slice, with security and measurement built in, is far cheaper to extend than a wide prototype to harden.
- CFO: a fixed-price, fixed-date MVP caps the cost of learning whether the product has a market.
Why it exists
Products fail more often from building the wrong thing well than from building the right thing badly. The MVP exists to reach real users before the budget is spent, so the next decisions are made on evidence. For AI products it also exists to discover how the model behaves on real inputs, which no amount of planning predicts. The trade-off is that a narrow scope disappoints stakeholders who wanted more, and an MVP that is too thin teaches nothing. The discipline is to keep the slice narrow but make it complete, including the parts that are not exciting: permissions, logging, and what happens when the AI is wrong.
Where it is applied
- A SaaS startup shipping a copilot that handles the ten most-asked user jobs inside one screen, instrumented to show which get used.
- A fintech launching a WhatsApp collections assistant for one loan product and one language before expanding.
- A clinic network going live with a voice agent that only books and reschedules appointments, with everything else handed to a human.
- A D2C brand launching personalised WhatsApp reorder prompts for repeat customers only.
- An edtech company shipping an admissions-enquiry agent for one intake season and one programme.
Is Minimum viable product (MVP) a skill?
Eazyware programEazyware delivers AI MVPs as Launch 6, a six-week fixed-price, fixed-date program with a scope lock, evals, and a shadow-mode rollout built in. The client owns the code, prompts and infrastructure at the end.
Eazyware service that covers it: AI-Accelerated MVP. Starting prices are on the pricing page.
Frequently asked questions
How is an AI MVP different from a normal software MVP?
It needs an evaluation harness, fallbacks for when the model is unsure, and usage instrumentation from the start. Without those you cannot tell whether the AI is working, and an MVP you cannot measure cannot teach you anything.
How small should an MVP be?
One user type, one workflow, done end to end with security and measurement in place. If a user cannot complete a real job without help, it is too thin; if it has three user types and five integrations, it is not an MVP.