3 ms·
> The moat of Cal.com is not the code, it's the users who don't want to migrate. That's a very weak moat unless you have something else like the friction of ne
by notnullorvoid 6mo ago
> The moat of Cal.com is not the code, it's the users who don't want to migrate.
That's a very weak moat unless you have something else like the friction of network dependence similar to a social network.
- philipov 6mo agoSunk cost is sufficient friction for most people even without network dependence.
- shimman 6mo agoFor a meeting scheduler site? I feel like you're overestimating the capabilities of something that is akin to college graduate project. This company does not seem healthy at all: https://getlatka.com/companies/calcom https://getlatka.com/companies/calcom I agree with the other poster that mention this is likely a publicity stunt but all it's really showing is that VC is still incredibly stupid with their money. All the more reason to seize it from them then properly fund useful software and not subsidize vanity projects for stanford grads.
- cootsnuck 6mo agoAbout the friction, not the capabilities...I haven't switched off my biz calendar/appointment provider I'm paying for even though I've kinda outgrown it. I wouldn't under estimate switching friction.
- hrimfaxi 6mo agoHow much does your friction avoidance cost, if you don't mind my asking?
- jmcgough 6mo agoidk my mom still pays for her aol email account
- rhubarbtree 6mo agoBest business insight posted on HN. This. Your code is not your business.
- notnullorvoid 6mo agoEmail is actually a excellent example of something with network dependence. Changing email providers requires that you change your email address too (unless you own and use your own domain). An address change causes friction from having to update the network of contacts and services which used your old email address.
- eloisant 6mo agoExactly, that's why most Saas companies are in a very tough position. You have to bring value that goes beyond the source code and hosting, otherwise your clients are going to vibe code a custom solution instead of paying you.
- OccamsMirror 6mo ago> otherwise your clients are going to vibe code a custom solution instead of paying you. How many things do you want to be responsible for? How many vibe coded projects do you want to maintain? I think this line of reasoning is overblown. Just because you can doesn't mean a significant number of people will. I think the 3D printer comparison is apt.
- eloisant 6mo agoIndividuals and SMB might stick with Saas but those don't pay much. Enterprise customers have the means to develop in house, those are the customers that will leave. And those are the whales of the Saas business.
- OccamsMirror 6mo agoThey already have the means to develop in house. Why aren't they?
- eloisant 6mo agoThis is much less work (= cheaper) to develop in-house with AI now than before.
- OccamsMirror 6mo agoI don't think it's much cheaper. Writing some code to do some CRUD has always been easy. Getting to a proof of concept is definitely quicker. But creating something that can be relied upon in production? That's as difficult and time consuming as it has ever been.