The schedule was
never the point.
We built @cal because the most common reason plans don’t happen isn’t lack of interest — it’s the friction of figuring out when. A coffee with a friend you haven’t seen in two years dies in the iMessage thread. A weekend trip dies in a Doodle poll. The schedule eats the intention.
Why we built it.
Calendars have spent twenty years getting better at one job — showing you what’s on your day — and almost no time getting better at the harder one: helping you get plans onto it.
Calendly tried to solve that with the link. It works for customer calls. It does not work for grabbing coffee with a friend. The whole social texture of asking — “hey, are you free Tuesday?” — gets replaced with a marketing-y URL that reads as transactional. Most people don’t send Calendly links to their friends. Most people who receive them don’t open them.
What if the calendar had a social layer that worked exactly like the rest of the social internet? You have a handle. You share it. When someone taps it, they don’t see your whole calendar — they see only the times you’re both free. They tap one. Done. No link, no thread, no back-and-forth. That’s @cal.
The constraint that makes it possible: titles, locations, attendees never leave your phone. We compute only the intersection. That’s what makes it safe to put your @handle in a public bio. That’s what makes it different from sharing a Google Calendar.
What we build by.
These aren’t marketing claims. They’re the four rules every product decision passes through.
Privacy by construction
Not by policy or by promise — by how the product is shaped. We never see event titles because the system can't read them.
The handle is the link
No Calendly URLs. No copy-pasting. Drop your @handle in a bio, send it in iMessage, write it on a card. That's the whole sharing story.
Spread without spamming
No referral bounties, no skip-the-line gimmicks. Growth comes from people inviting friends to plans they were going to make anyway.
One primitive, many shapes
Coffee, tennis, group dinners, weekend trips — same composer, different defaults. We don't ship 12 features when one with smart defaults works.
Small team, ambitious surface.
We hire designers and engineers who care about the small things — typography, motion, restraint — as much as the big ones. If you’ve gotten this far in our about page, you might be one of them.