MVP Building Advice
I’m not a big fan of building an MVP, especially a nice demo quality but, in fact, cheap and poorly production-ready.
Engineers extremely hate to build those, but probably some sales or CEO like that. While that approach is common, everyone seems to follow the same path. Here’s my suggestion if you have no other choice:
-
Build your MVP with just one thing—only one thing that is bug-free and better than your competitors.
-
Your first engineering team is likely not going to be great (99% of the time), so don’t expect them to produce something extraordinary.
-
Don’t expect to get better quality just because you spend more. It doesn’t work that way. Even if you spend over $1M, you will still get a cheap, dirty product if you don’t know how to build it internally.
-
Setting a strict timeline doesn’t mean you know how to make a product.
-
Don’t try to educate your customers; it will not work, no matter what.
-
Observe how customers react to your product, follow up, and improve what you need.
-
You need to think about operations, not just building. Wear and tear apply not only to houses but to startup products as well.
hashtag#MVP hashtag#startup