People talk about time zones as an inconvenience. They are not an inconvenience. They are a fixed tax on a working week, charged in hours, and the bill lands whether or not you planned for it.
My clients are mostly in the United States. My base has not always been. When the gap is small, say a European base against East Coast clients, the tax is manageable: a few hours of overlap in my late afternoon, a normal morning of my own. When the gap widens to something like a Southeast Asian base against a Pacific-time client, the arithmetic changes shape entirely. Los Angeles and most of Southeast Asia sit roughly fourteen hours apart. Their morning is my night. There is no clever calendar that dissolves that.
Which hours actually go dead
The useful way to think about it is not "how many hours of overlap do I have" but "which of my good hours does the overlap consume". Those are different questions, and only the second one predicts how a week goes.
My best thinking hours are the first four after waking. That is when architecture work, writing, and any decision I will have to defend later get done. If the overlap window sits in my evening, those hours survive intact and the cost is social rather than professional. If the overlap window sits in my early morning, the tax is severe: I am spending my highest-value hours on synchronous conversation, and the deep work moves to whatever is left afterward, which is worse hours by definition.
A big gap can therefore be cheaper than a medium one. An eight-hour offset is often the worst case, because it lands the overlap right on top of the morning block for one side or the other. A fourteen-hour offset is brutal on paper and sometimes easier in practice, because it separates the two working days cleanly enough that you stop pretending they overlap and start designing around the fact that they do not.
What moves, and what refuses to
Three kinds of meeting exist and they behave differently under a large offset.
Status meetings should not survive. If a recurring call exists only to confirm that things are on track, a written update in a shared channel does the same job better and costs nobody a night. Every base move I have made has killed a few of these, and none of them were missed.
Working sessions can move but they cannot compress. Two engineers debugging something together, or a workshop where a decision gets made in the room, needs real synchronous time and needs people who are not exhausted. These are what the overlap window is for, and the discipline is to protect that window for exactly this and nothing else.
Escalations do not move at all. When something is broken in production, or a client is unhappy, the meeting happens when they need it to happen. That is the part of the tax you cannot plan away, and it is the reason a base with a fourteen-hour offset is a different commitment than one with four. You are agreeing, in advance, to lose some nights.
What async genuinely absorbs
A lot, if the writing discipline is there, and almost nothing if it is not. The difference between a team that works well across a big offset and one that grinds is not tooling. It is whether people write decisions down with enough context that the other side can act on them without a follow-up question. One badly written update costs a full day: they read it, they do not understand it, they ask, and by the time I answer their day is over.
So the async discipline is specific. Write the decision, the reasoning, the thing you considered and rejected, and the exact next action with an owner. Anticipate the obvious question and answer it in the same message. It takes longer to write and it converts a two-day round trip into a one-day one, which over a quarter is an enormous amount of recovered time.
Agentic tooling has moved this line meaningfully. A lot of what used to require a synchronous handoff — reproducing a bug, drafting an approach, working through a codebase — now happens overnight against the other side's day, and I read the result with my coffee. That is genuinely new, and it is one of the reasons a big offset is more workable now than it was five years ago.
Where the tax outweighs the base
Every base offers something in exchange for the overlap tax: cost, training infrastructure, food, family, a visa position that works, weather that lets you train outdoors year round. The question is never whether the tax exists. It is whether the exchange is favourable, and the answer changes with the client mix.
My own threshold, learned the expensive way, is roughly this. If more than one engagement needs live escalation coverage in US business hours, a base twelve or more hours away stops being a lifestyle choice and becomes a staffing problem, and the honest fix is a person in that time zone, not a heroic calendar. If the work is mostly advisory, mostly written, with a predictable weekly synchronous block, a large offset costs surprisingly little and buys a lot.
The mistake I made early was measuring the tax in meetings and not in sleep. Meetings you can count. Sleep debt accumulates quietly for six weeks and then presents as a bad decision, a missed training block, or a short reply to a client that should have been a considered one. That is the real invoice, and it arrives late.
Which is why the base decision is not a travel decision at all. It is a scheduling decision with a city attached to it. I wrote up how I weigh the rest of the criteria in Choosing a Base City as a Criteria Problem, and what the flights themselves do to a training block in Training Through Long-Haul.
← Back to Travel
Ready to Train Smarter?
Get personalized training zones, race predictions, and performance insights with our free calculators.
