> One way to allay such concerns is to have a quick prototype
Once you've discovered a need for a potential product, this is the most important bit. You should spend as little time as possible trying to build the MVP.
It's really important to stick to the 'minimum' and not over-engineer it. That means if you have the choice of using ML that will take 6 months to build, or you can build it in a month and then spend 12 hours a day juggling spreadsheets, you should do the later.
Once you get to market, and (hopefully) have real customers paying you, you'll discover much more valuable insights than you ever could just by talking to prospects up front.
Once you've discovered a need for a potential product, this is the most important bit. You should spend as little time as possible trying to build the MVP.
It's really important to stick to the 'minimum' and not over-engineer it. That means if you have the choice of using ML that will take 6 months to build, or you can build it in a month and then spend 12 hours a day juggling spreadsheets, you should do the later.
Once you get to market, and (hopefully) have real customers paying you, you'll discover much more valuable insights than you ever could just by talking to prospects up front.