SchedulingCAN I VIBECODE
Calendbook?
BUILD FIRST
- One defined user and a repeatable end-to-end job
- A small, clear data model with sign-in only if it is genuinely needed
- Loading, empty, error, and success states that make the workflow feel complete
LEAVE FOR LATER
- Large integration marketplaces
- Multi-region scale and enterprise administration
- Every power-user setting from the established product
RESEARCH NOTES
What this tool actually does.
Calendbook (calendbook.com) is a SaaS appointment scheduling platform headquartered in Bari, Italy, with a distributed team of about 3 people. It lets users set custom availability (buffer times, timezone rules, custom hours), share booking links or embed them on websites, and two-way sync with Google, Microsoft, and Apple calendars. Payments are collected via Stripe at booking time with a 0% platform fee. Automatic WhatsApp reminders reduce no-shows. Integrations include Zoom, HubSpot, Telegram, Zapier, and webhooks, plus custom connectors via API. The permanent free tier offers unlimited bookings, 1 event type, and 1 calendar connection. Paid tiers add unlimited event types, 10 calendar connections, lead-qualifying questions, Gmail sending, custom branding, accept/reject scheduling, round-robin events, API/webhooks/Zapier, SAML/SSO/SCIM, and audit log. Pricing is positioned as up to 70
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a self-hosted scheduling web app reproducing the core Calendbook workflow: a host defines recurring availability with buffers and timezone rules; a public booking link is generated; invitees pick an open slot, optionally pay via Stripe at booking; the booking two-way syncs to the host's Google Calendar; WhatsApp reminders fire automatically. User-facing requirements: availability editor (custom hours, buffers, timezone display), public booking page plus embeddable widget, Stripe checkout with pass-through fees, WhatsApp/Twilio reminder automation, and a dashboard listing upcoming/confirmed bookings. Technical requirements: Node.js/TypeScript backend, PostgreSQL via Prisma, Next.js frontend, Google Calendar API with push-channel sync plus polling fallback, Stripe Payment Intents, and a BullMQ queue worker for reminders. Store availability as recurring RRULEs and compute open slots by subtracting existing bookings and calendar busy blocks. Do not copy Calendbook's brand, logo, marketing copy, or UI — build a neutral, accessible interface. Deliberately out of scope: round-robin team scheduling, CRM integrations, custom connectors, SAML/SSO, audit logs, and tenant/billing management. Deliver a README covering setup (env vars for Google OAuth, Stripe keys, Twilio), database migrations, and important limitations: single-host scheduling only, no multi-tenant auth, best-effort reminders, and Google API quota costs.