Verdict
A strong solo scheduling clone is realistic. Team routing and enterprise calendar politics are the cliff.
What you can rebuild
A public booking page, event types (15/30/60 min), timezone-aware slots, and Google Calendar create/block. Confirmation email/page. Works for freelancers.
What stays hard
Round-robin teams, complex availability rules, Salesforce/Zoom depth, and reliability when calendars disagree.
Starter prompt
Build a Calendly-like scheduler called OpenSlot. Users connect Google Calendar (or use manual availability hours), create event types (duration + buffer), and share a public booking link. Guests pick a slot in their timezone; you create a calendar event and show a confirmation page. Stack: Next.js, Tailwind, Google Calendar API, Supabase. Minimal, trustworthy UI.
Follow-up prompt
Add: buffer times before/after, max bookings per day, cancel/reschedule links, and Zoom/Meet link auto-attach. Handle daylight saving correctly.
Build it with these tools
Browse more in AI app builders.
Reference product: calendly.com. We are not affiliated. Prompts build inspired MVPs, not trademarked clones for commercial misuse.