FOR FRACTIONAL CxOs
You run three, four, five concurrent fractional engagements. Each one has its own Google Workspace, its own Gmail, its own team you're building relationships with. Your calendar situation is a puzzle no generic scheduler was designed to solve. Meetingpad was.
You wake up and check which of your three inboxes has the day's first meeting. You log into Google Workspace A because a client booked via your Calendly-for-Client-A link — but did they also try to book you Thursday, when Client B has your quarterly review scheduled on Google Workspace B? Neither Calendly knows about the other.
You copy the Thursday event manually. Or you cross-share your calendars (leaking meeting titles between clients). Or you accept the double-booking and reschedule at the last minute, apologizing.
You install Meetingpad, connect Google Workspaces A, B, and C as three separate identities. Each gets its own booking link:
meetingpad.io/book/{clientA-token}/30min → invite sent from your Client A emailmeetingpad.io/book/{clientB-token}/60min → invite sent from your Client B emailmeetingpad.io/book/{clientC-token}/office-hours → invite sent from your Client C emailA guest books your Client A link. Meetingpad:
When someone tries to book Client B for the same slot on Thursday, your Client B booking page already shows it as taken — because the unified availability engine sees the "Busy" placeholder. No double-booking, no meeting-title leaks between clients, no manual copying.
Fractional CxO with 4 clients:
macOS 14 (Sonoma) or newer · Apple Silicon & Intel · Signed & notarized by Apple. Read the full documentation or the privacy policy.