Real Google Calendar availability. Encrypted token storage. Fail-closed when Google is down. One URL anyone can use to book time with you — wired into the rest of your outbound stack.
Sign in. Pick a handle. Share the link. Your real availability is wired up before you finish typing.
OAuth in seconds. BookMe reads your free/busy with the narrowest scopes — never your event titles, never your password.
Your URL becomes shaungodinho.com/book/your-name. One field, instant availability check.
Drop it in your signature, your LinkedIn bio, your outbound sequences. Each booking lands on your dashboard with email + calendar status.
Six things every booking page should do, and most don't.
Taken slots are unbookable in real time. No separate availability calendar to maintain, no sync delay, no double-booking.
Pick which Google calendars participate. Personal blocks merge in without exposing event titles to the public booker.
Refresh and access tokens decrypted only at the edge. Your DB row is useless without the runtime key.
If Google's API is unreachable, BookMe refuses to render slots rather than silently over-booking. Outage-aware by design.
Fixed-window protection on the public endpoint. Abuse surface is bounded by design, not by hope.
Every confirmed booking drops a follow-up record + auto-task in your dashboard. The booker never sees it.
More tiers when there's something worth paying for. Until then, every feature is free.
Paid tier coming. Multi-meeting types, custom domains, team workspace.
Follow @shaungodinho for updates.
If something isn't here, email me.
Yes. BookMe is built on Google Calendar's free/busy API today. If you don't have a Google Workspace or Gmail account, you can't host a booking page yet. Outlook and Apple Calendar are on the roadmap.
The booking page refuses to render slots. You won't get a silent over-booking during a Google outage — bookers see a clear "availability temporarily unavailable" message. Fail-closed by design.
Bookings live in a Supabase Postgres database hosted in the EU. Your Google refresh and access tokens are encrypted with AES-256 GCM at rest and decrypted only inside the edge function that needs them. The DB row is useless without the runtime key, which lives only in the edge runtime.
No. BookMe reads only free/busy windows from your selected calendars. Event titles, attendees, and descriptions are never fetched, never stored, never displayed.
Every confirmed booking creates a follow-up record + auto-task on your dashboard with the booker's name, email, and the slot they picked. It's wired into the rest of the CRM so you don't drop the thread. The booker never sees it.
Not yet. The codebase will likely be open sourced once the paid tier and team workspace land. Until then it's a single-operator product run from a single repo.
BookMe is built by Shaun Godinho — a BDR at Ciente in Pune, India. It's the first piece of a larger outbound CRM (Hunts) shared publicly. Running solo for now; that's why it's free during beta.
Sign in with Google. Pick a handle. Share the link. 60 seconds. Free during beta.
Claim your page →