MVP
What is an MVP, and what should yours include?
Oluwole Olarewaju
CEO, 24 Design Co. · · 5 min read
In this guide
An MVP, or minimum viable product, is the smallest version of your product that real users can use, so you can test your idea before you spend on everything else. A good MVP is not broken or half-finished. It solves one problem well. This guide explains what an MVP is, what to include and cut, how it differs from a prototype and a full product, and how long it takes.
What is an MVP?
"Minimum" means only the features needed to deliver the core value. "Viable" means it genuinely works and is good enough that people will use it. "Product" means real people use it in the real world, not a demonstration.
The point of an MVP is learning. You release something small, watch what people actually do, and use that evidence to decide what to build next. It is much cheaper to learn this from a small product than from a large one.
MVP, prototype and full product
| Prototype | MVP | Full product | |
|---|---|---|---|
| What it is | A clickable mock-up of the screens | A working product with the essential features | A complete product with a wide feature set |
| Real functionality | No | Yes, for the core job | Yes |
| Used by | Testers, investors, your team | Real early users | The wider market |
| Purpose | Test the idea and the design | Test the market | Grow and scale |
| Typical timing | During discovery | First launch | After you have learned from the MVP |
A Discovery Sprint produces the prototype and the plan. The MVP is the first real build.
What an MVP is not
- Not a cheap, messy product. A small product can still be well designed and reliable.
- Not a demo. Real users should be able to use it.
- Not every feature at a lower quality. It is fewer features at a good quality.
- Not the end. It is the start of learning.
How to decide what to include
- Define the problem in one sentence, and who has it.
- Choose one main type of user. Serving everyone at once makes the product vague.
- Describe the core journey, from the moment the user arrives to the moment they get value.
- List every feature you can think of.
- Sort them into must-have, should-have and later. A must-have is something the core journey cannot work without.
- Cut until it feels slightly uncomfortable. Then check that the core journey still works.
A useful test: for each feature, ask "if this were missing, could a user still get the main value?" If yes, it can wait.
What to include and what to cut
Usually include
- The core feature that delivers the main value
- Simple account creation, if you need to know who the user is
- Payments, if payment is part of the value
- A basic admin view so you can run the product
- Analytics, so you can see what users do
- A way for users to send feedback
Usually cut or postpone
- Secondary user types
- Advanced settings and customization
- Social features and sharing, unless they are the core value
- Complex reporting
- Extra platforms before you know which one your users prefer
- Integrations that are not essential
Two examples, to show the thinking. A booking product for one venue might start with a calendar, an enquiry or payment step and a simple admin screen. A marketplace might start with one category in one city, with manual support behind the scenes.
Types of MVP
Not every MVP needs a full app.
- Landing page test: a page that explains the idea and collects sign-ups, to measure interest.
- Concierge MVP: you deliver the service manually to a few customers to learn what they value.
- Wizard of Oz MVP: the product looks automated to the user, but people do the work behind the scenes.
- Single-feature app: one feature done well.
- No-code or low-code prototype: a quick working version built with existing tools.
A Discovery Sprint helps you choose the lightest approach that can answer your biggest question.
How long does an MVP take?
At 24 Design Co., a focused MVP typically takes 8 to 12 weeks from the start of the build, after a one-to-two-week Discovery Sprint. The timeline depends on the number of features, platforms and integrations, and is confirmed in a fixed quote.
How do you know your MVP worked?
Decide before you launch what "worked" means. Useful signals include:
- Activation: do new users complete the core action?
- Retention: do they come back?
- Willingness to pay: will they pay, or commit, for it?
- Feedback: what do users say, and what do they do instead?
Write down the numbers you expect, then compare them with reality. Real behavior is a better guide than compliments.
What comes after the MVP
Based on what you learn, you can improve the product, change direction, or scale what works. This is also when many founders add technical leadership, such as a CTO partner, to plan the roadmap, keep the product secure and guide the next stage.
Frequently asked questions
How much does an MVP cost? It depends on scope, platforms and integrations. Our guide to the cost of building an app in Nigeria explains what drives the price, and a Discovery Sprint gives you a fixed quote.
Can I build an MVP with no-code tools? Sometimes, especially for testing demand. If the product needs custom logic, scale or tight security, a custom build may be better.
Do I need a technical co-founder? Not necessarily. You need someone accountable for the technical decisions. Many founders work with a technical partner instead of a co-founder.
Should I build for iPhone or Android first? Choose the platform most of your first users have, or ask whether a cross-platform approach fits.
Oluwole Olarewaju
CEO, 24 Design Co.
Leads every product from idea review to launch, and stays on as CTO partner.
More about Oluwole