[verdict][curated prompt][source: calendly.com]
Can I vibecode Calendly?
// buildable in a weekend, but real gaps stay open
A single-user booking page is easy; production-grade scheduling needs OAuth, availability rules, time zones, reminders, payments, team routing, and trust.
confidence: high
what it is: Scheduling links for booking meetings without back-and-forth email
Buildability index · an editorial game
- Price 12 $/month · per seat weight: plus 2
- Time weekend weight: plus 2
- Category appointment scheduling no weight
- Moat integrations · execution quality weight: minus 2
- Confidence high weight: plus 1
- What you lose 4 items weight: minus 2
- Site calendly.com (si apre in una nuova scheda) no weight
They cancel out. This is where it comes down to how much the subscription annoys you.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
// free tier: The free plan covers one event type on one connected calendar.
What you build
Connect calendar, publish event-type pages, let guests choose available slots, create calendar events, and send reminders.
what you need
- Google/Microsoft calendar OAuth
- hosted app
- email notifications
- timezone handling
- auth
The booking page is easy. Calendar-sync OAuth is where weekends go to die; be honest with yourself about that before starting.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a personal booking page like Calendly. Requirements:
- A public /book page showing my available slots for the next 14 days; visitors
pick one, enter name + email + note, and get a confirmation page.
- Availability = weekly rules in a config file (e.g. Mon–Fri 10:00–17:00,
30-min slots, 15-min buffer between meetings, my timezone) minus existing
bookings, rendered in the visitor's local timezone.
- Google Calendar sync via OAuth (credentials in .env): busy events block slots,
and confirmed bookings are created in my calendar with the visitor invited and
a Google Meet link attached. Warn me in the README: this OAuth app setup is
the fiddly part · budget an hour for the Google Cloud console alone.
- Email confirmations to both sides via SMTP creds in .env.
- Cancel/reschedule links with a signed token in the email.
- SQLite storage, one Node process, no accounts, no framework lock-in. Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- polished Google/Outlook OAuth kept working for you
- team round-robin and routing
- SMS reminders
- the integrations directory
Why people still pay
They pay because double-booking or missed meeting invites is costly.
moat: Integrations Execution quality what a moat is
calendar integration/reliability
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (1) — and why
- Cal.diy (si apre in una nuova scheda) — Self-hostable, yes; also explicitly a hobbyist, non-production fork that expects database and security expertise.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- cal.com (opens in a new tab) — open-source Calendly; self-host and skip the OAuth pain
What it costs in a year
12 $/mese 144 $/anno
Listino 12 $ al mese a persona su Calendly. L’anno è dodici mesi pieni, senza sconti annuali.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.