Add your team.
Enter names and time zones together. Start with a sample if you want to see the result first.
FOR TEAMS ACROSS TIME ZONES
Stop giving the same teammate the late call.
Plan eight weeks of recurring meetings. Respect everyone’s boundaries, share the unavoidable inconvenience, and show your team why the rotation makes sense.
Free beta · No account needed · Your manual setup stays on your device
Built for Remote team leads · Global agencies · Distributed product teams
YOUR WEEKLY TEAM SYNC8-week draft
Across the map.
On the same page.
AAlexNew York
SSamLondon
NNoorKarachi
EXPLAIN THE TRADE-OFFS✓ Hard boundaries respected
Loading the verified example…
Preferred AcceptableFictional team · declared hours
MAKE THE INVISIBLE BURDEN VISIBLEA working meeting.
A working meeting.
A fairer eight weeks.
One fixed time can keep putting the same person outside their preferred hours. Compare it with a rotation that reduces the largest individual burden first.
This example is generated from fictional availability. Results depend on your team’s hours and exceptions.
Largest individual burden— minutes
Loading the verified reference example.
Counted in acceptable minutes, over eight weeks.Explore a live team ↗
FROM TIME ZONES TO A PLAN
Three steps. Fewer scheduling debates.
Define comfortable and allowed.
Set preferred hours, explicitly acceptable hours, and date exceptions. Everything else is unavailable.
Review, adjust, share.
Read the fairness ledger, pin a valid weekly time, and export a draft your team can review.
A PLAN YOUR TEAM CAN QUESTIONYou keep the judgment.
You keep the judgment.
The ledger keeps the score.
Manual overrides recalculate the whole cycle. A valid time picker keeps unavailable hours off limits.
See each person’s local date and time across daylight-saving changes. Export eight tentative calendar events.
If no valid schedule exists, see the blocked weeks. Shorten the meeting, change a permitted day, or go async.
SIMPLE PLANS. ONE ORGANIZER PAYS.
Start free. Help shape what comes next.
The current beta is free for teams of up to 12. Prices below describe our proposed launch packages; paid subscriptions are not open.
Free
$0
Try the fairness engine with your own team.
- One team, up to 4 people at launch
- Eight-week plans and fairness ledger
- Manual hours and date exceptions
- Slack summaries and calendar export
Team
$12/ team / month
Less chasing availability. More informed plans.
- One team, up to 12 people
- Saved plans across devices
- Member setup and connection links
- Google Calendar free/busy checks
Agency
$39/ month
Keep several distributed teams organized.
- Up to 5 separate team workspaces
- Up to 12 people in each team
- Separate availability and plans
- Team calendar features when launched
THE NEXT STEP: CALENDAR-AWARE FAIRNESS
Available hours are only half the picture.
We’re preparing optional Google Calendar connections so busy intervals can be excluded as well as unavailable hours. Each person authorizes their own connection. Calendar integrations require service activation and are not included in the current manual beta.
Check connection availability ↗G
Google CalendarFree/busy integration prepared
Activation pendingMicrosoft 365Planned after Google
LaterOur first calendar integration requests occupied intervals. It does not request event-writing permission.
A FEW GOOD QUESTIONSKnow what you’re
Know what you’re
bringing to the team.
What does “fair” mean here?
We minimize the largest individual total of minutes inside explicitly acceptable hours, then the team total, then meeting-slot changes. Preferred hours cost zero. This measures the declared eight-week cycle, rather than guaranteeing equal inconvenience or accounting for historical attendance.
Will the meeting time always rotate?
No. If one fixed local slot is preferred for everyone across all eight weeks, it stays fixed. We do not make comfortable meetings worse to force equal counts.
What if nobody has a shared available window?
The planner reports the blocked weeks and preserves hard boundaries. Try a shorter duration or another permitted day, review allowed hours with the team, or use an async update.
Do I need to connect a calendar?
No. Manual planning works without an account or calendar access. The current beta uses the hours and exceptions you enter. Optional Google Calendar integration is prepared separately and needs activation before it can be used.
Where is my team’s information stored?
Manual mode stores the setup on your device. Team JSON downloads let you back it up or move it. Optional connected workspaces require server storage and a separate sign-in; see our privacy and beta information.
Can I invite everyone directly from an export?
The ICS download contains eight tentative events and does not send invitations. The Slack summary gives you text to share for review. Direct event publishing is deferred.
Give your next eight weeks
a little more balance.
Try the sample team ↗Start with a fictional team. Bring your own when you’re ready.