Hacker News new | ask | show | jobs
by mindhash 3332 days ago
I have spent usually between 1-3 months to build MVPs..but you can't generalise as it really depends whats viable. Talk to your prospects to define what is viable. For enterprise softwares its usually longer due to various reasons.

My first product was into travel and we spent months just to build MVP that we thought was viable. Stupidest thing we could do. The product didn't go anywhere.

Second product was into logistics. I spent most of my initial month travelling in field with my cofounders and doing stuff manually. This helped me understand what was viable and build product in a month's time.

My third product was education platform. This was a funded startup so they had sales people. I used them to gather information. Like what profs think about the problem space, what students think then what type of devices are they using, do they have good internet access. This greatly helped us figure out whats minimum that we need in product. Like we discovered that students in our country rarely have a laptop or desktop. They use desktops in school's lab.

My current product is about team productivity. I am on call with most of my ex colleagues, friends to figure out what would be minimum. My problem statement is kind of validated as most have felt a need for solution.

So spend more time with prospects to figure out MVP or MRP (Minimum Remarkable Product).