Calendar sync for fractional CTOs
Four tenants.
Three on-call rotations.
One pager that finds you.
Every engagement runs its own Workspace or M365, and none of them will federate with the others. The incident bridge, the deploy window, the architecture review — all scheduled in a tenant your own calendar cannot see.
14 days free · No credit card required
What breaks
You are the escalation path, in a rotation you cannot see.
The client's on-call schedule lives in their calendar, synced out of their paging tool into their tenant. You are the final escalation, and the only way you know who is holding the pager this week is to log into an org you visit twice a month.
The deploy window you booked over.
A release freeze goes on the client's calendar on Tuesday. Your own calendar shows Tuesday afternoon as open, so you take a call with another engagement. You find out when the rollback starts and nobody can reach the person who designed the migration.
Two clients in the same market.
"Vendor selection — datastore" and "Series B technical DD" are meeting titles that should never appear in anyone's calendar but yours. Sync the naive way and each client learns something about the other. That is not a bug report. That is the engagement ending.
twocal fixes this
Connect each client tenant to your own calendar. Their meetings land in yours as real native events, in about a second, over push notifications rather than a polling timer — so Find a time and Scheduling Assistant see them the same way they see anything else.
You choose what crosses, per engagement. Full detail for the client whose architecture you are deep in; a bare "Busy" block for the one whose competitor you also advise. Titles, attendees and agendas stay inside the tenant they came from.
- 1
Connect your own calendar — Google or Microsoft.
- 2
Add each client tenant as a sync source, with its own field rules.
- 3
Their calendar changes appear in yours in about a second — including the ones that move.
Audit it before you trust it
You have run enough incident reviews to know the failure mode that matters here is not the sync that errors — it is the sync that reports success and drops an event anyway. Nothing pages you. The logs are clean. You find out when someone asks why you were not on the call.
So twocal does not just sync. It continuously re-compares both calendars against its own ledger and reports how many events genuinely agree — then publishes that number live, alongside median propagation time and the share of syncs landing inside five seconds. Not a status page that goes green when the health check passes. The actual agreement rate.
If you want the long version of why that distinction matters, we wrote it up:the webhook never arrived, and that is still our problem.
About five minutes per engagement. OAuth to the tenant, pick the calendar, set the field rules. No admin consent required for a single user, no agent to deploy, nothing to run.
$19/month. One flat price — we don't charge per calendar or per tenant. 14-day free trial, no credit card required.