SAASPOCALYPSEverdict #CAL-35D5
scanned 2026.04.27 · 14:55
subject of investigation
cal.com
▸ open-source scheduling & booking platform
verdict: MONTH
buildability score
48
/100
tier · month
the blunt take
“Cal.com is what Calendly would look like if it went to therapy, opened its source code, and got a team routing feature. The core is a weekend. The everything-else is a career.”
The happy path — connect a calendar, generate a booking link, send a confirmation email — is genuinely a weekend project. But Cal.com competes on depth: round-robin routing, team availability, embeds, webhooks, and a marketplace of integrations. That's months of polish, not hours of hacking.
cost breakdown.
their price ←→ your price
what they charge●
Teams plan
$12
/ user/mo
※ × team size; free tier exists for individuals
annual:$144
what it costs you✦
01 · Vercel Pro (for edge functions + preview envs)$20.00
02 · Supabase Pro (connections + DB size)$25.00
03 · Resend (transactional email, 3k/mo free)$0.00
04 · Google Calendar + Zoom OAuth apps (free)$0.00
05 · Domain + SSL$2.00
06 · Cron job service (e.g. Trigger.dev free tier)$0.00
07 · Stripe for paid plans (2.9% + $0.30 per txn)$10.00
TOTAL / mo57
▸ break-even:~5 seats — $60/mo vs $60/mo on Calendly Teams. Above that, you're laughing.
or, you know, use one of these.
if building feels spicy
option A
Cal.com (self-host)
Yes, the product you just scanned is open source. Docker compose up and you literally have it, for free, right now.
option B
Calendly free tier
One event type, unlimited bookings. Covers 80% of solo use cases without writing a line.
option C
Notion + Calendly embed
If your scheduling needs are simple, a free Calendly link embedded in a Notion page costs nothing and takes 10 minutes.
what'll actually be hard.
est. total: 6 weeks
▸ 1 weekend: calendar OAuth + freebusy · 1 weekend: booking link UI + availability grid · 1 week: timezone math, email confirmations · 2 weeks: team scheduling + round-robin · 1 week: embed widget + webhooks · 1 week: crying about edge cases
easy
medium
hard
nightmare
01
easy
Basic booking link + availability CRUD
Set your hours, expose a URL, let someone pick a slot. This is the whole Calendly MVP in a weekend.
02
easy
Google / Outlook Calendar OAuth
Follow the quickstart. Use freebusy.query. Avoid writing your own conflict logic.
03
medium
Timezone handling at scale
Use date-fns-tz or Luxon. Never store local times. You will learn this the hard way if you ignore it.
04
medium
Email confirmation & reminder flows
Resend + a simple queue. The tricky part is rescheduling and cancellation links with signed tokens.
05
hard
Round-robin & collective team scheduling
Requires querying multiple users' calendars simultaneously, merging free slots, and distributing fairly. This is where most clones give up.
06
nightmare
Embeddable widget + third-party integrations
An iframe that looks good in every host page, plus Zoom/Meet/Stripe/Zapier hooks. Each integration is its own OAuth rabbit hole.
recommended stack
Next.js 15 + App RouterSupabase (Postgres + Auth)Google Calendar API + nylas for multi-providerResend + React EmailStripe for paid tier gating
ready to build?
We'll email you the build guide. Cancel some plans.
▸ generated with love, by a heartless robotverdict v2.1 · saaspocalypse.dev