What is an MVP, and do I need one?
An MVP is the smallest version of your idea that real people can use. It shows you whether the idea works before you build all of it.
By Isaac Oluwayinka · · 3 min read
An MVP, or minimum viable product, is the smallest version of your idea that real people can use and that teaches you whether the idea works. You need one when you are not yet sure people want what you plan to build. It lets you find out before you build all of it.
An example
Say you want to build a platform that connects people with home tutors. The full product might have profiles, reviews, payments, messaging, a calendar and an app. That is a big build, and you would not know until the end whether parents want it.
The first version might be much smaller: a page listing a few tutors, and a form where a parent asks for a lesson. You handle the rest by hand, behind the scenes, at first. If parents use it, you know where to invest. If they do not, you found out early. (This is an example I made up to show the idea, not a project of mine.)
What goes in, and what stays out
A useful rule: keep the one thing that proves the idea, and leave out everything else for now.
- In: the main thing a user came to do, working end to end, even if some steps are manual.
- Out for now: extra features, polish nobody asked for, and anything that only matters once you have many users.
Leaving things out is not the same as building it badly. What you do build should be solid, because you will build on top of it.
Common mistakes
- Building too much first. Every extra feature delays the moment you learn something real.
- Building before talking to anyone. Even five conversations with likely users can change what you build.
- Treating the first version as throwaway. Done well, it becomes the foundation, so choose sound foundations even if the first version is small.
When you probably do not need one
If you are replacing something you already do and know well, such as a booking process your business already runs, you can often build the real thing in stages. The point of an MVP is to reduce risk when you are unsure. If you are sure, build what you know you need.
How I work on this
I build in stages, so you see working progress regularly. That naturally gives you a first usable version early, and lets you decide what to add based on what you see, not on guesses. You can read more on the startup MVP page.
Questions people ask
›Does an MVP mean low quality?
No. It means small, not careless. The parts it contains should work properly.
›How long does an MVP take?
It is usually much shorter than the full product, because it does much less. I can give you a realistic idea after we have talked about what yours needs.
›Can I add features later?
Yes. That is the point. You add the ones that real users ask for.
If you have an idea and want help deciding what the first version should be, ask for a free consultation. Before that, you may want to read what to prepare before you hire a developer, and after launch, what happens after my website launches.
Thinking about a project of your own?
Tell me what you have in mind and we will talk it through. The first consultation is free.
More to read
- What to prepare before you hire a developer
· 3 min read · Planning your project
You need less than you think. A few sentences about what you want, who it is for and what you like. Here is what helps, and what to ask.
- Website or app: which does my business need?
· 4 min read · Planning your project
Most businesses should start with a website. Here is how to tell when an app is worth building, and when it is not.
- Why is my website slow?
· 3 min read · Keeping it healthy
Slow websites are usually slow for a few ordinary reasons: big pictures, too many add-ons, struggling hosting. Here is how to check and what fixes it.