We have all heard about MVP’s (Minimum Viable Product). Or in layman terms, testing a product idea before pouring hours of work into the product itself. This usually saves up a lot of time when developing a product, which I cant disagree with. But one big question that I have in mind is..
How minimum should a minimum viable product be?’fredrick
Let’s have a look at a few MVP’s that are quite popular and any maker would know about.
Buffer uses a very simple MVP method. It consist of 3 pages with the first page being a brief description about the product itself with a huge call to action with ‘Plans and Pricing’. This call to action button would lead to a page with pricing options and once the user selects a plan it would take the user to a ‘we are not ready’ page. No major web development yet a simple way to validate the idea to see if people are willing to pay for the product.
Dropbox did a bit more for their MVP. They had basic functionality already setup, they released a demo video and created a signup page. This worked for them and now they are a tech unicorn.
Back to my point..
There are many product developers I see on IndieHackers, twitter and ProductHunt trying to launch products with some basic functionality in which they put some work into. What I’m trying to understand is how minimum should a MVP be?
Personally I think it should be as minimum as it can be, as long as you have a way to get the full details of your product out to your visitors and create a basic mailing list to get their contact info if they are interested in the product. This helps you save time when building your product, because you know the product is validated and people are willing to use it. If not you scrap the idea and move on.
What are your thoughts on this? Comment below or tweet me.