[verdict][generated prompt][source: savvycal.com]
Can I vibecode SavvyCal?
// buildable in a weekend, but real gaps stay open
The core booking-link loop can be cloned, but calendar reliability, time-zone correctness, reminders, and polished link UX make it more than a trivial script.
confidence: medium
what it is: Scheduling links with overlay calendars and nicer booking UX
Buildability index · an editorial game
- Price 12 $/month weight: plus 2
- Time weekend weight: plus 2
- Category appointment scheduling no weight
- Moat integrations · execution quality weight: minus 2
- Confidence medium weight: zero
- What you lose 6 items weight: minus 3
- Site savvycal.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.
What you build
Read availability, generate shareable scheduling pages, write booked events, and email confirmations.
what you need
- calendar OAuth
- hosted backend
- email service
- timezone library
- auth
Good smaller-brand page; open-source prior art makes the verdict nuanced.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a solo booking page to replace SavvyCal: one person, one calendar, a few link
types. Requirements:
- Node + Express + better-sqlite3 on my VPS behind HTTPS; server-rendered pages, Luxon
for timezone math.
- Link types in links.json: slug, title, duration, buffer, allowed hours (e.g. /intro,
30-min slots, 15-min buffer, weekdays 10:00-16:00 my time).
- Availability from Google Calendar free/busy (googleapis, OAuth creds in .env); show
open slots for the next 14 days in the visitor's detected timezone with a timezone
switcher.
- Booking form: name + email + note. On submit, create the event on my calendar with the
guest as attendee so Google sends the invite, and store the booking in SQLite.
- Re-check free/busy at submit time, not just render time, so two guests cannot grab the
same slot.
- Confirmation email to guest and me via Resend or SMTP (creds in .env), including a
cancel link that deletes the event.
- No accounts, no telemetry beyond my own server logs.
- Out of scope: team links, routing, payments, and reminder sequences. One calendar,
mine.
- README: the Google Cloud console OAuth steps (budget an hour, it is the worst part)
and the DNS/HTTPS notes.Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- overlay-calendar UX
- team links
- routing
- payments
- reminders
- support
Why people still pay
They pay for a nicer, reliable scheduling experience that avoids friction with guests.
moat: Integrations Execution quality what a moat is
calendar integration/polish
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.com Free (si apre in una nuova scheda) — Excellent free scheduling, but no equivalent overlay-calendar booking experience.
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 scheduling platform covering the main booking-link mechanics. (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
