5 ms·
Perfect timing. I'm bootstrapping my own startup (http://moonlighter.io http://moonlighter.io) at the moment and had a couple questions about the MVP. 1) How c
by pbnjay 12y ago
Perfect timing. I'm bootstrapping my own startup (http://moonlighter.io http://moonlighter.io) at the moment and had a couple questions about the MVP.
1) How can you quickly validate a business with very little immediately visible value to the user? Direct user interviews won't work here because the service is very data-driven (collecting filesystem events), so it'll require a decent amount of data collection from the user (I'll offer something like a 14-30 day trial to allow this). Since it has to be done over a longer period of time, and it includes collecting information that might be sensitive to some people, it's not very easy to fully validate the business. I've had a few friends using it, and I'll be sharing with a small beta user list soon, but otherwise I was wondering if you had any other ideas.
2) I've put off writing the payment processing code, focusing on the product itself. Especially considering the "trial" period necessary to see value, are there any downsides to releasing the MVP without allowing payments and then adding them in after release? (Other than no cashflow of course...)
Thanks! I'm actually reading through the lean startup now (after reading way too much of it's principles on the internet first). So it's neat to be able to communicate with the author directly like this.
- eries 12y agoThat technique is actually very common. If you have a 30 day free trial, for example, you really don't need a payment processor for at least 30 days (and that's the optimistic scenario! I've seen startups that don't need payment processing for a lot longer, because nobody completes the trial) Remember that not only does your product have to create value for customers but they have to realize that it will create value for them, and both assumptions are important to test.