MVP or the final product
Very often when someone asks me for an estimation he says “I have a limited budget so I want to build an MVP”. The problem is that when they describe the final effect they see the product as a fully blown app with extra features. So let’s put some definitions on the table and clarify things.
What is an MVP?
According to Wikipedia an MVP is a
product with just enough features to gather validated learning about the product and its continued development. Gathering insights from an MVP is often less expensive than developing a product with more features, which increase costs and risk if the product fails, for example, due to incorrect assumptions
Remember these 3 words: Learning, Validation, Assumptions. They all mean that you don’t even have to create a dedicated software. You can validate your hypothesis with solutions that already exist!
Are you curious how?
Read these 4 stories:
- Building an MVP, not Beta.
- How I built an MVP in 3 days?
- 3 inspiring MVPs
- MVP is not about the product
See, you don’t need a hard development at the beginning of your startup adventure. You need creativity, smart approach and using things that already exist. Small amount of tech skills always helps, but it is not necessary to solve the problem.
What your MVP can look like?
Some examples of an MVP:
- Kickstarter campaign
- Explainer video
- Excel spreadsheet
- Landing page
And many more...
Now go outside, find your clients, sell them the Idea and MVP and start making business. Then build your final product with buyers and real clients who want to contribute.
P.S. MVP below is extreme, but let’s say it honestly - it works! ;)