Contents
To define an MVP is to choose exactly the features that let you test your most important assumption about users and the market – and to consciously leave out everything else. Version 1 of your app is not meant to impress; it is meant to learn: do you solve a real problem well enough that people use the app repeatedly or pay for it? This guide shows how to narrow down the scope systematically.
What an MVP is – and what it is not
A minimum viable product is the smallest version of your product that delivers real value to a clearly defined audience while giving you data you can act on. Two misconceptions come up in projects again and again:
- An MVP is not a half-finished product. Whatever is included must be stable, understandable and easy to use. Users forgive missing features, but not crashes or confusing flows.
- An MVP is not "the big vision minus 30 %". If you trim a little everywhere, you end up with a product that does many things averagely and nothing really well.
A better mental model is a narrow but complete path: a user arrives with a problem, completes their task from start to finish and experiences the core value of your app along the way.
Step 1: Write down your core hypothesis
Before discussing features, describe in one sentence what the MVP is supposed to prove. This pattern works well:
We believe that [target group] has the problem [problem] and would solve it with [solution]. We will know we are right when [measurable signal].
An example: "We believe that trade businesses with 5–20 employees want to handle their job-site documentation on a smartphone. We are right if, after four weeks, at least half of the pilot companies create photo reports every day." The measurable signal is crucial – without it you cannot tell later whether the MVP succeeded. If you have not validated the idea itself yet, start with our guide on how to evaluate an app idea in 7 steps.
Step 2: Map the critical user path
Sketch the route a typical user has to take to experience the core value. For the trade-business app, that might be: sign in → select job site → take photos → add a note → send the report as a PDF to the customer. Every feature on this path is a candidate for version 1. Everything beside it – time tracking, material ordering, chat – goes on the "later" list.
For each step, check whether it can be simplified or handled manually. Does the PDF really need to be generated automatically, or is an export that you polish behind the scenes good enough for the pilot? Such "concierge" solutions save development time as long as the user base is small.
Step 3: Prioritise features with three proven methods
Once your feature list is complete, you need a transparent way to prioritise so that discussions are not settled by gut feeling.
| Method | How it works | Best for |
|---|---|---|
| MoSCoW | Sort into Must, Should, Could and Won't (this time). Only "Must" goes into the MVP. | Quick alignment with stakeholders, workshops |
| Value/effort matrix | Rate each feature by user value and development effort. High value with low effort comes first. | Budget-driven decisions |
| Kano model | Distinguishes basic needs, performance features and delighters. | Differentiation from competitors, positioning |
In practice, many teams use MoSCoW for the rough split and a value/effort estimate for borderline cases. One important habit: write the "Won't" category down explicitly. It creates clarity and stops discarded wishes from sneaking back in through the side door.
What typically belongs in version 1 – and what does not
Every app is different, but some patterns repeat in almost every project.
Usually essential:
- The one core flow that solves the problem – complete and bug-free
- Simple, secure sign-in (e-mail login or a social login is often enough)
- Basic privacy features: privacy policy, consent handling, account deletion
- Analytics for the measurable signal in your hypothesis
- A feedback channel, for example a contact form inside the app
Usually deferrable:
- Extensive settings, themes and personalisation
- Admin dashboards with lots of reports (a plain back office is often enough at first)
- Multiple languages, if you are only testing one market initially
- Social features such as comments, likes or followers
- Complex role and permission models
There are exceptions: a marketplace app needs both sides of the market in the MVP, and in a community app the interaction between users is the core value. If your unique selling point is an AI feature, that is exactly what you should test – our article on the AI feature as an MVP explains how to do it lean.
Checklist: is your MVP scope realistic?
- Can you state the core hypothesis in one sentence, including a measurable success signal?
- Can a user experience the core value within a few minutes, without help?
- Is every feature on the critical user path or needed for measurement?
- Do you have a written "Won't" list?
- Have you checked which steps can be handled manually or with off-the-shelf tools for now?
- Does the scope fit a timeframe of roughly 4–8 weeks of development?
- Is it clear who analyses the data after launch and decides on the next steps?
If you hesitate on several points, the scope is probably still too large. A clickable prototype before development helps you resolve open questions with real users before any code is written.
Budget and timeline for an MVP
As a guideline, a simple MVP with us costs between 5,000 and 15,000 EUR with a development time of 4–8 weeks. Once login, payments, a custom API and both platforms (iOS and Android) are added, you are more likely in the range of 15,000–50,000 EUR and 2–4 months. Scope is the biggest cost driver – which is why a clean MVP definition is the most effective saving measure there is. AI-assisted development can reduce cost and time by up to 40 % on top of that, but it does not replace clear prioritisation. For a detailed breakdown, see our article on MVP costs in 2026.
One more tip: reserve budget for iteration after launch from day one. The MVP generates insights – the real value only appears once you can act on them.
Agentic coding workshop for your team? From €799 net – request a quote by e-mailConclusion
A good MVP does not come from cutting features by instinct but from a clear core hypothesis, a complete critical user path and documented prioritisation. Anything that does not directly contribute to learning waits for version 2. If you would like to sharpen your MVP scope with us, you can request a free analysis with a fixed-price offer via our offer wizard.
Frequently Asked Questions
How many features should an MVP have?
There is no fixed number. What matters is that every feature sits on the critical user path or serves to measure success – often that is only a handful of functions around one core flow.
Should an MVP be built for iOS and Android at the same time?
It depends on your target group. Cross-platform frameworks such as Flutter or React Native make both platforms possible without double the effort; with a clearly defined audience, one platform or a web app may be enough for the first test.
When is an MVP successful?
An MVP is successful when it clearly confirms or refutes your core hypothesis. A refutation is valuable too, because it protects you from expensive misinvestments.
What is the difference between a prototype and an MVP?
A prototype simulates the app, usually without working technology, and is used to test flows and design. An MVP is a real, usable product that is released to the market and delivers actual usage data.