[0xferruccio]

I can resonate with this so much.

Just recently I had an idea for a product and rushed to building it because it “solved” a problem.

But then when it came to trying to get some sales it has been a failure. The only people that were willing to buy the product didn’t understand it.

When starting out in my opinion if you don’t have a large network of people in the tech industry it’s important to focus on products that either increase sales or save a lot of money (3-4x cheaper than existing solutions).

I find that the products that sell have to be a no brainer deal.

I wrote about what I learned building and selling a cybersecurity saas here, don’t make my same mistakes: https://ferrucc.io/posts/sales-for-cybersecurity-saas/

[lbriner]

I think a similar issue is rushing to fix something in an industry you have no experience of. You might not think you need to know about property before you start an AirBnB but actually they had to learn from mistakes and wrong assumptions, fortunately they were agile enough to pivot.

Engineers often assume that everything is as simple as "my product can do that, please pay me money" when there are a raft of other blockers in certain industries, some already mentioned above. The more you understand these before you start, the less time you spend trying to understand e.g. why a hospital won't just buy some random new product even though it promises to fix a big problem.

[0xferruccio]

Asking questions and trying to sell something is an amazing learning experience.

Especially if you don’t have experience in an industry the best thing you can do to learn is to try and sell something or schedule calls with people in the industry.