The collab was everyone’s favorite idea. Bea ran a product-design podcast out of Toronto; Sam taught a course from Atlanta; Marisol streamed from London. Their audiences overlapped just enough, and the co-hosted webinar practically pitched itself: one recorded deep-dive segment, then a live session the following week where all three would go on air together. Topic, outline, promo plan — settled in a single energetic call. Then they tried to schedule it, and the project entered the swamp.
A co-hosted webinar needs not one meeting but two: a recording window for the pre-taped segment, and the go-live itself, which — being public — could not be moved once announced. The thread began politely. “Does Thursday 3 p.m. work?” “Whose 3 p.m.?” “Mine. Wait, is yours the same as Sam’s?” It was, but nobody was sure, so everybody hedged. By week two the thread had passed fifty messages, and the words “or we could just” appeared in eleven of them.
Then came the incident that turned comedy into cost: a trial run where Marisol joined an hour early — someone had written “4 p.m. EST” in a thread that meant BST in her head — and sat alone in an empty studio call, on a weeknight, increasingly certain the collab was cursed.
Three calendars multiply — they don’t add
Scheduling a solo show is a decision. Scheduling three hosts is a negotiation where every host’s calendar constrains both meetings, and every message about it has to survive translation across two time zones. Each new proposal forced three people to do mental clock math, and each hedge — “should work, I think” — spawned two clarifying replies. And because the go-live had to be announced to two mailing lists and a stream schedule, nobody dared confirm anything less than certain. The thread wasn’t failing from lack of goodwill. It was failing from arithmetic, at scale, in prose.
Fifty messages in, they had agreed on everything except a time — the one thing a go-live cannot happen without.
Sam ended it the way these things always end: not with a better proposal, but with a better instrument. One link in the thread, one line of text — “Every window that could work, both sessions. Tap what you can make. No time-zone math, it shows you yours.”
Local time for everyone, one time on air
The poll held candidate windows for both the recording session and the live date. The trick that killed the confusion was almost invisible: each host saw every option in their own local time. Bea and Sam read Eastern; Marisol read London time; nobody converted anything, so nobody converted anything wrong. No accounts, no calendar access to grant — three hosts, three minutes, done.
The answer had been sitting inside the thread all along, unfindable: a Tuesday recording window that fit Marisol’s evening and both North American afternoons, and a go-live the following Thursday with all three hosts solidly green. Both rose straight to the top of the poll. Bea booked the studio, announced the live date to both mailing lists that night, and the promo clock finally started ticking.
The webinar went out on time, with all three hosts on air and nobody arriving an hour early. The fifty-message thread was quietly archived, unmourned. For any creator collab spanning time zones, that’s the whole pitch of Meeting Time: one poll instead of a thread, every host answering in their own local time with no accounts to make, and the windows that work for every calendar rising to the top — so the only thing left to produce is the show.