"You don't need 250k to 300k, and if you had it you'd wish you had 500k or 750k anyway."
Spending a quarter mill on a prototype seems like a horrible decision, TBH...
Spending a quarter mill on a prototype seems like a horrible decision, TBH...
If you can use Excel spreadsheet or Google form to build your product. Do it for your first 100 users.
Obviously if you're in deep tech then this doesn't apply. But with deep tech and moonshots the value isn't the product, it's your arbitrage opportunity and expert patentable knowledge.
You need to have a MVP in the target market. You need to demonstrate that it can scale. Therefore, if your business model works for 100 customers on the web, it does not necessarily mean that it will be successful on a larger scale on mobile.
But how long are they actually using the half baked prototype?
I thought the purpose of the half baked prototype was to validate the idea, get good user feedback and get as much information as possible before dedicating resources and making more permanent design/architecture choices.
If you are spending massive time and resources before this is achieved, you are doing it wrong IMO...
I'd rather have something with a brutal/nonexistent GUI but provides useful functionality and gives me a warm fuzzy that the developers have some use cases in mind, or a suggested workflow.
Yes there is a first-mover advantage to getting into a domain early.
Well, if you're spending significant resources upfront on content from accredited professionals for a mental health app...you're probably doing it wrong.
The problem in the mental health space isn't the lack of information, or access to information...