Underestimating SaaS Complexity 💡

I think a lot of people, when they imagine SaaS, they think that it's just a website that you put on the web that's doing some work for you. They don't visualize all the payment layer that you need to think about, all the payment complexity. They don't think about, you know, all the layers that you have to deal with, like authentication, you know, figuring out how to do the different integration. There are so many layers that are not really visible, and it is this big iceberg of things that you need to figure out along the way. And then oftentimes people get stuck. Uh, throughout that process as well. So I think people tend to underestimate the amount of obstacles they're going to face, and they tend to overestimate how much they're going to get back from, you know, from whatever they're building. So for example, I used to do service for, for about like 13 years, and then a lot of people will ask me to build a SaaS for them, and they expect that as soon as the website goes live, that they're instantly going to get customers. And if they didn't get customers, they say, what's wrong with the product? I'm like, it's not the product. You're not getting— Mm-hmm. Right, right, exactly. I also think that people tend to think that they can create demand, but I think you cannot really create demand. Like, there's demand or there isn't. So, and even when, for example, there's a new product in a new category, it's always an extent of a demand that was already there. So I think that people sometimes assume that if they have a cool idea, that it's going to be enough for people to want to use the product, but they never even think about the demand and there's no demand and then they're surprised that it fails.