← Blog · 2026-08-02
Sync tools, OneCal, SyncThemCalendars, Reclaim, Amie's sync features, solve the double-booking half of the multi-calendar problem and quietly create three new problems in exchange. Here's the anatomy of why fractional operators keep signing up and then ripping them out.
You have three or four Google accounts, maybe personal + Client A + Client B + your own consulting LLC. Each account has its own calendar. Google, by design, treats those calendars as isolated silos. Book you at 3pm on Client A's calendar and Client B has no idea. So Client B's assistant sends an invite for 3pm and you now have two meetings on top of each other.
Sync tools bridge the gap by copying events between calendars: an event created on Calendar A gets a ghost copy on Calendars B and C. Now when someone tries to book you on Calendar B at 3pm, they see you're busy. Problem solved.
The default copy behavior on most sync tools mirrors the source event's title and attendee list. So Client A's "Strategy call re: layoffs, do not forward" shows up on your Client B calendar as "Strategy call re: layoffs, do not forward". Anyone at Client B who has permission to see your calendar (their assistant, their team members if you're on a shared calendar view) can read it.
The good sync tools offer a "private title" mode that redacts the copied event's title to something like "Busy". Turn that on. But you're still trusting the tool to hold that setting across every future event and every future account you add.
Every real meeting now exists 2–4 times in your calendar universe. Your weekly view is a mess of duplicates. Worse: any automation that watches your calendar (Slack "in a meeting" status, focus-time auto-blockers, meeting note tools like Granola or Fathom) sees the ghost copies too. Some of them handle duplicates gracefully. Others show a meeting starting on Calendar A, then start a fresh session when it "starts again" on Calendar B ninety seconds later.
Sync tools solve the read side (blocking time so nobody double-books). They don't solve the write side. If a prospect wants to book a meeting with you and you hand them a Calendly link, that link still lives on one account. Invites still come from that account's Gmail. If the prospect is a Client A counterpart and your Calendly is on your Client B Gmail, the invite arrives from an email address they don't recognize. Bad look.
To fix send-identity you end up back on Calendly Teams ($16/seat/month × N accounts) or Cal.com Teams, running on top of your sync tool. Two subscriptions, three ghost copies of every meeting, and you still get bit by "why is the sync 47 seconds behind reality?" once a quarter.
The fractional-operator problem is really three problems bolted together:
Solve them together, not by stacking two tools. That's what we built Meetingpad for. Meetingpad reads your calendars via Google's freeBusy API (times only, never titles), writes short titleless "Busy" placeholders on the other calendars when a booking arrives, and gives each connected account its own booking link that sends invites from that account's Gmail. One Mac app, $5/month, unlimited identities.
To be fair to the category: if you're not fractional and privacy between your calendars doesn't matter (personal + your one work account, say), a well-configured sync tool with private titles is lightweight and fine. The failure mode is specifically the cross-client scenario where meeting titles are confidential and send-identity matters. If you're there, sync isn't the shape of the answer.
Meetingpad is a macOS menubar app for people juggling multiple Google Calendar accounts. Download for Mac →
