I Left Calendly in 30 Minutes

My Calendly trial ended without much of a warning. (There was probably an email. It went wherever the rest of the “your trial is ending” emails go.) I found out the way you find out about a lot of these things: it broke for someone else first. People clicking the scheduling link on my site were hitting a 404. Not a “please upgrade” notice, not a degraded booking page, just a dead link where my booking page used to be.

The part I want to talk about isn’t the failure, though. It’s what came next.

The old version of this story is a bad afternoon, maybe a bad week. The website side was never the hard part; that’s mostly find-and-replace on one URL. The hard part is rebuilding the setup inside the new tool: re-creating every event type, re-entering availability, clicking through the configuration to get each booking option behaving the way the old one did. It’s the kind of “I’ll deal with it later” chore that sits on a list for a month, because the switching cost is just high enough to make staying annoyed feel like the cheaper option.

I opened Claude Code, pointed it at Cal.com, and described what I’d had set up. About 30 minutes later the event types were rebuilt, availability was configured, and the booking page was live (Cal.com is open-source and has a real API, which is most of why this was possible at all). This isn’t a story about the AI doing something magic. It’s a story about the pieces already being there, with the cost of assembling them dropped through the floor.

So: a dead booking link in the morning, a working replacement before lunch. Fine. Nice. But that’s the small version of the point.

The bigger version is that the thing keeping me on Calendly was never Calendly. It was the migration cost. “Lock-in” is, to a large degree, just the size of the chore it takes to leave. When the cost of re-creating your setup somewhere else drops from a weekend to half an hour, most of the lock-in evaporates with it. The vendor’s leverage was living in the gap between “annoyed enough to leave” and “willing to spend a weekend leaving.” Tools like this close that gap.

I don’t think the interesting story about agentic tools is that they write code. It’s what they do to the costs you had stopped questioning because they’d always been fixed. Switching vendors. Porting a config. Rebuilding a workflow on a different substrate. Those used to be load-bearing reasons to stay put. Increasingly they aren’t, and the “stickiness” a lot of products quietly depend on turns out to be stickier in the pricing deck than in my actual afternoon.

Calendly is a fine product, for what it’s worth. I didn’t leave because Cal.com is dramatically better. I left because a vendor let my service degrade silently and bet that the cost of leaving would keep me anyway. That bet is now wrong, and it’s worth knowing exactly how wrong.