Working across time zones with clients: an async system
Make async the default, protect one overlap window, and write enough down that the work moves while you sleep.
On this page
You can work with clients across time zones without answering email at 3am by doing three things on purpose. Make async the default and live calls the exception, protect one small overlap window each day, and write enough down that the work keeps moving while you sleep. A ten-hour gap then becomes overnight delivery.
Here is the system, minus the burnout.
A time-zone gap is normal now
Remote work put most teams on different clocks. In Buffer's 2023 State of Remote Work survey, 62% of respondents said the people on their immediate team were spread across multiple time zones, and 43% were independent consultants or freelancers rather than employees (Buffer).
The shift is still moving. Owl Labs found that 38% of workers are now hybrid or remote, a 15% jump year over year, and that full-time remote work grew 57% (Owl Labs 2024). When client, supplier and work all sit in different cities, a gap of several hours is just a Tuesday.
So the goal is not to erase the gap. It is to build a way of working that does not need both people awake at once.
What the research says about distance
A gap costs live conversation. A 2024 study in Organization Science followed 12,038 employees at a large multinational and used daylight-saving shifts to isolate the effect. One extra hour of time-zone distance reduced synchronous communication by about 11% (Rice Business). The same write-up notes that losing an hour of shared work overlap was a 19% drop in the chances to talk, so communication fell proportionally less than the opportunity did.
The study also found that employees tried to make up the difference by moving conversations outside normal hours, and did so more the larger the gap (LSE Research Online). That is the trap. Nobody decides to work at midnight. It happens one "quick sync" at a time.
Make async the default
Async first means the work does not stall when you log off. Decisions, files and updates live somewhere the client can reach without you. A live call becomes something you schedule on purpose.
Time zones already rank among the top struggles remote workers name, cited by about 19% in the Buffer survey (Buffer). The calendar is crowded too. In Owl Labs' 2025 report, 82% of workers said they want meetings to end by 4pm (Owl Labs 2025). Put a cross-time-zone call into that and one of you is up late.
Async does not mean cold or slow. You replace "let's hop on a call" with a two-minute recorded walkthrough, a short written update, or a comment on the file itself. The client gets more detail on their own schedule and you get your evening back.
What writing it down looks like
- Decisions are logged where the client can find them, not buried in a chat both of you will forget.
- Every file you hand over comes with a short note saying what it is, what changed and what you need back.
- Questions are batched. One clear list the client can answer in a single sitting beats five one-line messages across the day.
Written updates also build trust. Clients relax when they can see progress without chasing you. If that part of the relationship feels shaky, read status updates that build client trust.
Find your overlap window and protect it
Almost every pairing of time zones has a few hours where both people are awake. London and Dubai share most of the day. New York and Berlin share the early afternoon. Even a hard split such as California and Singapore usually has an hour or two at the edges. Find yours and treat it as the only time real-time contact is allowed.
Two habits make it stick:
- Keep the client's current time in front of you. A second clock on your phone or a scheduling tool that shows both zones removes the mental math before you hit send.
- Do all live contact inside the overlap. Calls and genuinely urgent questions go there. Everything else waits for the async channel.
The payoff is calm. Workers value flexible hours: in the Owl Labs 2025 data they said they would give up 9% of their salary for them (Owl Labs 2025). If you run your own business you already have that flexibility. A protected overlap window is how you keep it from being eaten by a client's calendar.
Tools that carry the load
You do not need a big stack. You need a few tools that each remove a reason to be online at the same time:
- A shared world clock that shows the client's local time beside yours. It prevents the classic mistake of booking what turns out to be their 11pm.
- A scheduling link that shows your free slots in the client's own time zone. It ends the "does 3pm work? whose 3pm?" thread.
- Async video, such as a short screen recording, in place of a call neither of you can attend without pain.
- One shared home for the work. A client portal beats scattered email threads when you are hours apart, because the client opens one link and sees the current state of everything without waiting for a reply.
When you serve several clients in several zones, the coordination gets harder fast, and a repeatable system beats willpower. Managing multiple clients covers how to keep that under control.
Put response times in the contract
Most cross-time-zone friction comes from a mismatch in expectations. The client thinks a message sent at their 9am gets an answer within the hour. You are asleep. By the time you reply they feel ignored and you feel hurried. Nobody did anything wrong. The expectation was never set.
Set it in writing before the work starts. A few lines in the contract or statement of work are enough:
- Your working hours, stated in your time zone and theirs.
- A response-time promise you can keep. "I reply within one business day" is honest and generous across ten hours. Do not promise an hour.
- The overlap window, named as the time for any live call.
- What counts as urgent, and the single channel to use if something truly is.
This is not bureaucracy. It lets the client stop wondering and lets you stop apologizing. Have a lawyer check any contract wording that matters for your situation.
Turn the gap into something you can sell
A big gap is also an offer. If you are eight or ten hours ahead of a client, their end of day is your morning. They send feedback before they log off, you pick it up fresh, and the revised work is waiting when they start again. To them it feels like the work happened overnight, because it did.
Name that in your pitch. A client in New York working with someone in Dubai is not putting up with an inconvenience. They are getting a near round-the-clock cycle on their project.
The other half of working internationally is getting paid across borders without losing a chunk to fees or waiting two weeks for a transfer. Getting paid by international clients walks through the gateways that help.
How Delivvo helps with clients in other time zones
Delivvo keeps the whole client job in one place, so a client in another time zone can check progress, approve work and pay without waiting for you to wake up.
Here is the flow:
- A prospect books a call on your client scheduling page with a slot picker, so the "does 3pm work" thread is replaced by one click inside your overlap window.
- The quote, contract and deposit invoice go out as one link. The client signs and pays when it suits them, even if it is 2am your time.
- The client portal holds the files, versions, approvals and messages. The client opens it with a one-time code, so there is no password to lose, and sees the current state of the job at any hour.
- When you deliver, large files go through the portal, up to 50 GB a file on Pro and up, with resumable uploads that cope with a poor connection on either end.
5.
The detail that matters for a gap: the client pays through your own gateway and Delivvo takes 0%, so there is nobody in the middle to slow down a payment across the world. Booking types are limited to one on the Free plan and are unlimited from Solo up. When you bring on someone in another city, the team structure lets you place them in a box with a defined reach, so work can pass between people at the end of each day with a handover and an audit log of who did what. Read more on the client scheduling page.
Next, look at Delivvo for teams or how the CRM fits around it.
FAQ
How much time-zone overlap do I need with a client?
Two to four hours of shared working time is enough if the rest of the relationship runs async. That is room for one live call when it matters and for quick back-and-forth on anything urgent. Below two hours, rely more on recorded video and written updates so nothing waits a full day for a reply.
Should I change my working hours to match a client's time zone?
Shift by an hour or two if it buys a real overlap, but do not flip your day. The research above shows people tend to drift into late-night communication as the gap grows. Set a response-time promise you can keep from your normal hours instead.
What do I tell a client who expects instant replies?
Tell them before you sign. Put your hours and a response-time promise in the contract, such as one business day, and name one channel for real emergencies. Clients rarely mind a slower reply once they know it is coming. They mind silence they did not expect.
Is async communication worse for client relationships?
No, as long as it is clear. Distant clients often trust async work more because written updates and recorded walkthroughs leave a visible trail of progress. The relationships that suffer are the ones with no rhythm at all.
Delivvo runs the whole client cycle for service businesses, from the first inquiry to the quote, contract, deposit, invoice and delivery, so a client in any time zone can book, sign, approve and pay without waiting for you to be awake. Clients pay you directly through your own gateway, and Delivvo takes 0%. Start free