I Won’t Work With People Multiple Time Zones Away
Written By: Shane Clark on June 25, 2026
There is a tax on every project that stretches across too many time zones, and it never shows up in the contract. It shows up at eleven at night when the person you need is asleep, and again at nine in the morning when your window with them has already closed. I have paid that tax enough times to stop paying it. My rule now is simple: work my hours, or adapt to the business hours where my clients are, or we don’t work together. Real time zone overlap is not a nice-to-have. It is the deal.
The hidden cost of a wide time zone gap
When your workday and someone else’s barely touch, everything slows to the speed of the handoff. A question that should take five minutes takes a full day, because you ask it while they sleep and they answer while you sleep. Decisions stall. Momentum dies in the gap. None of that is anyone’s fault, and all of it is real drag on the work.
One time zone is fine, several is a different animal
Let me be clear about where the line sits. An hour or two of offset is nothing. You still share most of a working day, so the handoff is quick and the project keeps moving. The trouble starts when the gap stretches to eight, ten, or twelve hours. At that point your day and their day overlap for a sliver, and everything queues behind that sliver. That is the difference between a small offset and a broken schedule.
The late-night problem
Here is the part people gloss over. When your morning is their midnight, you are not getting their best work. You are getting the tired tail end of their day. People get sleepy. They get slow. They go quiet. Someone answering you at their 1 a.m. is not sharp, and the work shows it. I would rather have a rested person on my clock than an exhausted one straining to reach it.
The chase
This is the part that wears on you. You send a message and wait. They reply while you are asleep. You reply while they are asleep. A conversation that should take an hour turns into a three-day thread. I am not staying awake for someone else’s clock, and I am not going to chase a person through a two-hour window every day just to keep a project alive.
The rule: real time zone overlap, or the client’s hours
So here is the standard. Everyone works the same hours, or they adapt to the business time zone where our clients are. If the client runs on US business hours, the work runs on US business hours. I do not care where a person physically sits, as long as they are truly on that clock. Someone who will shift their schedule to the client’s day is a yes. Someone who wants me and the client to bend to theirs is a no. You serve the client’s day, not your own.
Why AI makes this matter more, not less
You might think async tools solve this. They soften it, but they do not solve it. In the AI era, speed is the product. AI collapsed the workday into parallel threads, and the build that used to take a week now takes an afternoon. So the bottleneck is no longer the work, it is the human handoff. A wide time zone gap re-introduces the exact latency AI just removed. You compress the build to a few hours, then lose three days waiting for one reply across the clock. That is also why I bill the way I do, which I covered in priced on outcomes, not hours.
The follow-the-sun myth
There is a tidy theory called follow-the-sun, where teams hand work around the globe so something is always moving. It sounds great on a slide. In practice, each handoff loses context, and the person picking up at their morning has to reconstruct what the last person meant. For most small operations, follow-the-sun is not 24-hour progress. It is 24-hour telephone.
How to screen for it
Ask the plain question early: what hours do you actually work, and will you work mine or the client’s? If the honest answer is “I can give you two hours of overlap,” you already have your answer. You want real time zone overlap or a real willingness to adapt, and nothing softer than that. This is criterion nine on my hiring checklist for an AI operator: works my hours, not multiple time zones away.
The takeaway
Same hours, or adapt to the client’s hours. One zone over is fine. Several zones away with no willingness to shift is a hard no. In a world where speed is the entire advantage, a time zone gap is the one source of drag you can simply refuse to accept. So I do. If a person can’t keep my hours or the client’s, they are not the AI operator I want on a project, no matter how good they look on paper.
Frequently asked questions about time zone overlap
How much of a time zone difference is too much?
One or two hours is nothing, you still share most of a working day. The trouble starts around eight to twelve hours, when your days overlap for a sliver and everything queues behind it.
What if someone is a great worker but far away?
Skill does not fix a schedule. A brilliant person you can only reach for a two-hour window each day still stalls the work. The overlap matters as much as the talent.
Can async tools solve the time zone gap?
They soften it, they do not solve it. Async helps for slow, batchable work, but the moment a decision needs a quick back-and-forth, the gap turns a one-hour conversation into a three-day thread.
What is your actual rule?
Work my hours, or adapt to the business hours where the client is. If the client runs on US business hours, the work runs on US business hours. Where a person sits does not matter, as long as they are truly on that clock.
Isn't it unfair to make someone change their schedule?
It is a choice, not a demand. Plenty of people are happy to work the client's hours, and those people are welcome. The ones who want the client and me to bend to their clock are the mismatch.
Why does the time zone gap matter more in the AI era?
Because speed is the product now. AI compressed the build from a week to an afternoon, so the human handoff is the bottleneck. A wide gap re-introduces the exact latency AI just removed.
What about follow-the-sun, where work moves around the globe?
It sounds good on a slide. In practice each handoff loses context and the next person has to reconstruct what the last one meant. For a small operation it is often 24-hour telephone, not 24-hour progress.
How do you screen for this when hiring?
I ask early and plainly: what hours do you work, and will you work mine or the client's? If the honest answer is a two-hour overlap, that is my answer. I want real overlap or a real willingness to adapt.
Does this mean you only hire locally?
No. Location does not matter, the clock does. Someone across the country or even a country over is fine if they keep the client's working hours. Someone half a world away who won't shift is not.
