MVP definition: examples and a method to scope it right
MVP definition: what a minimum viable product is and isn't, how to prioritise features, measure results and iterate after launch, for apps, SaaS and tools.
Published on November 20, 2026 · 6 min read
By definition, an MVP (minimum viable product) is the first version of a product with just enough features to be used by real users and to test a key assumption: does the product meet a real need? It is neither a mockup nor a cut-price version, but a simple, usable product designed to help you learn fast. Well defined, an MVP lets you launch sooner, spend less before you have proof, and build what comes next on concrete feedback.
This article explains what an MVP is and what it is not, sets out a method to define and measure it, and shows how it applies to a mobile app, a SaaS product or an internal tool.
MVP definition in plain terms
An MVP is the leanest version of a product that already delivers real value to a user and teaches you something decisive. The three letters sum up the balance to strike:
- Minimum: you keep only what is needed to test the main assumption.
- Viable: the product works, it is reliable and usable without hand-holding. Users must get a real benefit from it.
- Product: it is a product delivered to real users, not a document or a pitch deck.
The concept was popularised by the lean startup movement, which proposes building products in short loops: build, measure, learn. The MVP is the first of those loops. Its purpose is not to do everything, but to reduce uncertainty as fast as possible on what really matters: do your users have this problem, and are they willing to change their habits for your solution?
What an MVP is not
An MVP is not a prototype, not a POC, and not a rushed version of the final product. The confusion is common, and it is expensive.
- A prototype is a simulation, often a clickable mockup. It is used to test a journey or usability before development. It does not handle real data and is not used day to day.
- A POC (proof of concept) checks technical feasibility: an integration, an algorithm, performance. It answers "is it possible?", not "is it useful?".
- A rushed version does lots of things badly. An MVP does few things, but does them well. An unstable product validates nothing: if users leave, you cannot tell whether the need or the quality is the problem.
These stages often follow one another: a prototype to validate the journey, possibly a POC to remove a technical doubt, then the MVP to put the product in front of the market. The design and prototyping phase comes precisely before MVP development.
How to define your MVP in 5 steps
Defining an MVP means starting from an assumption, a user and a journey, then removing everything that is not essential to test them.
1. State the main assumption
What is the belief the whole project depends on? For example: "tradespeople are willing to send quotes from their phone, on site" or "HR managers would pay to automate onboarding for new hires". If that assumption is wrong, the rest of the product is pointless. So the MVP must test it first.
2. Pick a specific target user
An MVP aimed at everyone convinces no one. Choose a narrow segment, the one that feels the problem most strongly, and design for it. You will broaden later.
3. Map the key journey
Identify the journey that delivers the value, from the first screen to the benefit. For a booking app, for example: find a slot, book it, receive confirmation. Anything off that path is a candidate for removal.
4. Prioritise features
The MoSCoW method helps you sort: Must have (essential to the key journey), Should have (important but can be worked around), Could have (comfort) and Won't have (excluded from this version). The MVP contains the Must haves, and rarely more. For each feature, ask: without it, can the user still get the main benefit?
5. Write down what you leave out
The exclusion list matters as much as the feature list. Online payment, multiple languages, an advanced dashboard, an Android version on top of iOS: whatever is excluded must be written down and owned, or it will creep back in mid-project. Early on, a manual task done behind the scenes often replaces a costly automation perfectly well.
This work is ideally done in workshops during a scoping phase, and it feeds straight into the app requirements document.
How do you measure an MVP's success?
You measure an MVP with a handful of metrics set before launch, backed by qualitative feedback from users. Without measurement, an MVP is just another first version.
The metrics depend on the assumption being tested, but they often include:
- Activation: the share of sign-ups who complete the key journey.
- Retention: do users come back the following week, the following month?
- Engagement: how often the main feature is used.
- Conversion: moving to a paid plan, booking an appointment, placing an order.
- Time saved or errors avoided, for an internal tool.
Set in advance the thresholds that will make you say "keep going", "adjust" or "stop". Add interviews: a few conversations with real users often explain what the numbers show without saying. Finally, build in analytics during development, not after launch.
What should you do after launching the MVP?
After launch, you iterate: you analyse the results, decide what comes next and ship improvements in short cycles. There are three possible outcomes:
- The assumption is validated: users adopt the product. You strengthen the key journey, handle the feedback, then add the Should have features.
- The assumption is partly validated: the interest is there, but not in this form. You adjust the target, the journey or the value proposition. This is what is called a pivot.
- The assumption is disproved: far better to find out with an MVP than with a full product. What you have learned remains valuable for what comes next.
One point that is often forgotten: a technically well-built MVP can grow into the final product without a full rewrite. Saving time on scope is healthy; saving it on code quality creates technical debt that you pay for with every change.
MVP for a mobile app, a SaaS or an internal tool: the differences
The principle stays the same, but what counts as "minimum" depends on the type of product.
- Mobile app: app store publication and perceived quality demand a higher level of polish. You can start with a single codebase for iOS and Android, or begin with a web app if the need allows. Notifications and offline mode are only worth it if they serve the key journey.
- SaaS: the MVP must prove that a customer will pay to solve their problem. Sign-up, the key journey and simple billing are often essential; advanced roles, multiple integrations and sophisticated dashboards can wait. Our guide to building a SaaS covers these steps in detail.
- Internal tool: users are known and easy to reach, which makes testing easier. The MVP often replaces a shared spreadsheet or a paper process within a limited scope, one team or one site, before being rolled out to the rest of the company.
Key points on how to define an MVP
An MVP is the smallest usable version of a product, built to test a decisive assumption with real users. Defining it means choosing a target, a key journey and strictly necessary features, writing down what you leave out, then setting the metrics that will tell you what to do next. That is the approach Lunify applies to its MVP projects: a tight scope, fast iterations and decisions based on real usage.
Have a product idea and want to know which MVP to build first? Let's talk.
Frequently asked questions
Related articles
November 20, 2026 · 6 min read
Mobile app development cost: what drives the price in 2026
Mobile app development cost explained: scope, platforms, design, back end, AI and maintenance. What drives the price and how to get a reliable quote.
November 22, 2026 · 5 min read
SSII vs ESN: What's the Difference and Why the Name Changed (History, Missions and Client Impact)
SSII vs ESN: what's the real difference? Learn why the name changed, how the profession evolved, and what it means when choosing a digital partner.
November 20, 2026 · 7 min read
App requirements document: outline, content and mistakes to avoid
How to write an app requirements document for a mobile or web app: a reusable outline, what each section covers, user stories and common mistakes to avoid.
A project in mind? Let’s talk about it.
Startup, SME or large group, whatever your industry: we help you frame the need and build the right product.