Tips for building a minimum viable product
The developer behind Appbot â€“ a service for app developers who want their app store reviews and features in their email inbox â€“ has posted the lessons he learned when building his minimum viable product. There is nothing revolutionary here, but it is a good list of things to do. This is my summary:
1- Build something for yourself, that you would use, especially if you are a first time entrepreneur. There is no better way to understand a problem than to have it yourself
2- Validate the market â€“ e.g. via quick analysis of Google query volume
3- Build it quick â€“ focus on the key feature, everything else can come later (this is the 'minimum' bit)
4- Don't reinvent the wheel â€“ leverage every tool and platform you can
5- Pick a small test group to get started â€“ Appbot initially reached out to six developers
6- Build a story people care about "the key to word of mouth marketing is giving people a story they can tell (and will tell)
7- Reach out to early users for feedback
8- Let people know how to contact you
9- Listen to the feedback, but only implement the good stuff. When you decide not to implement something politely explain why.
10- Track and watch everything â€“ Google analytics, conversion rates, open rates, A/B testing etc (get the code right up front so you can track everything)
Appbot has had pretty good success with this model and many others will to. Those that don't will find out their idea sucks quickly, which is also good.
We still see a good number of plans that follow the old model of spending lots of money pre-launch to develop a full feature set. There are probably markets where that makes sense, but to say I far prefer the MVP approach would be an understatement.
(Nic Brisbourne is partner at DFJ Esprit, one of Europe's leading venture capital firms. The post has been reproduced with the author's permission from his blog, The Equity Kicker.)
To become a guest contributor with Techcircle, write to firstname.lastname@example.org.