Batch questions rather than sending them singly, write briefs that anticipate the obvious follow-ups, and hold one overlapping call each week. The cost is round trips, not hours.

The cost is round trips

A twelve-hour difference does not cost you twelve hours. It costs you a day per exchange.

You send a question in the morning, they answer during your night, you read it the next morning and have a follow-up, and two questions have consumed two days.

A project needing twenty such exchanges takes a month longer than the same project with somebody down the road, and none of that time appears on anybody's invoice.

Which means the discipline is not about working unusual hours. It is about reducing the number of round trips.

Write to prevent the follow-up

The single most valuable habit, and it is a writing skill rather than a scheduling one.

Before sending a question, ask what they will need to answer it, and include that.

Before sending feedback, ask what they will ask you next, and answer it in advance.

Change the heading is one round trip. Change the heading to this exact text, at this size, and if that does not fit on mobile use this shorter version instead, is none.

It takes an extra two minutes and saves a day, which is the best exchange rate available in this whole subject.

Batch, do not trickle

The second habit, and it changes the arithmetic.

Sending questions as they occur means each one costs a day and they queue.

Collecting them into one message at the end of your day means twelve questions cost one day rather than twelve.

The same applies to feedback on a design: consolidated feedback from everybody, once, beats four people sending comments over three days, which is bad practice anyway and disastrous across a time difference.

Keep a running note during the day and send it before you finish, at a time that lands at the start of theirs.

Find the overlap and protect it

Almost every pairing has some overlap, even a small one, and it is worth treating as valuable rather than inconvenient.

One call resolves the things that would otherwise take a week of messages, which is why the weekly slot is worth more than any tooling.

Share the inconvenience

A point about fairness that has practical consequences.

Where the overlap is genuinely poor, somebody has to be uncomfortable, and it should not always be the same person.

Alternating who takes the early or late call is a small gesture that noticeably affects how a working relationship goes over months.

The alternative, where the supplier is always the one starting at six or finishing at eleven, tends to produce a slow decline in responsiveness that nobody names.

Also be explicit about what you expect outside their hours. An expectation that messages will be answered at any time is a common source of resentment and is rarely stated openly.

A worked example

A firm engaged a developer eleven hours ahead and found a six-week project taking four months.

Reviewing the exchanges showed the cause plainly: two hundred and forty messages, most of them single questions, each costing a day.

They changed three things.

Questions were collected and sent once daily, at the end of their afternoon.

Feedback was consolidated by one named person rather than sent by three people.

And they booked a recurring thirty-minute call in the two hours of overlap, alternating between early for one side and late for the other.

The remaining work finished in five weeks against an original estimate of four.

Nobody worked different hours and nothing about the developer changed.

What actually goes wrong beyond timing

Two things that get blamed on time zones and are not.

Ambiguity in written English between people with different first languages, where a phrase like make it pop or tidy it up carries no information and produces a guess.

Be concrete: reference an example, give exact text, specify sizes, and attach a screenshot with an arrow on it.

And assumed context, where a supplier does not know your market, your customers, or what your competitors look like, and is filling gaps with reasonable guesses that are wrong.

Both are worse across a distance because the correction cycle is slow, and both are fixed by writing more precisely rather than by meeting more often.

Public holidays and working weeks

A practical detail that causes avoidable surprise.

Different countries have different public holidays, and some have several consecutive weeks where very little happens.

Ask at the start for their holiday dates over the project period and put them in your own calendar.

The working week also differs in some regions, so a Thursday deadline may fall differently than you expect.

None of this is a problem when known in advance and all of it is a problem when a deadline lands in the middle of a week nobody is working.

The counter-case

The distance is sometimes an advantage rather than a cost to manage.

A well-briefed piece of work handed over at the end of your day and returned by the start of the next is genuinely faster than the same work done locally, and that pattern suits defined tasks with clear specifications.

It also gives access to skills and rates that may not exist locally, which for a small business can be the difference between doing something and not.

Where it works badly is exploratory work, where the answer is not known at the start and the process is a conversation, since that is exactly the work that requires many short exchanges.

Match the arrangement to the work: defined tasks travel well, discovery does not.

Making it work

  1. Batch questions into one daily message.
  2. Answer the obvious follow-up before it is asked.
  3. Consolidate feedback through one person.
  4. Book one weekly call in the overlap.
  5. Alternate who takes the awkward hour.
  6. Be concrete: exact text, sizes, and screenshots.
  7. Get their holiday dates at the start.

Steps one and two together account for most of the recoverable time, and neither requires anybody to change when they work.

Keeping a schedule two people can rely on is covered in a shared calendar two people can trust.


Frequently asked questions

What does a time difference actually cost?

A day per exchange rather than the hours themselves. A project needing twenty round trips takes a month longer, and none of that appears on an invoice.

How do I reduce round trips?

Answer the obvious follow-up before it is asked. Change the heading is one round trip; giving the exact text, the size, and a mobile fallback is none.

Should I send questions as they occur?

No. Collect them into one message at the end of your day. Twelve questions then cost one day rather than twelve.

Is a regular call worth it?

Yes. One short weekly call inside the overlap resolves things that would take a week of messages, and it is worth more than any tooling.

Who should take the awkward hour?

Alternate it. A supplier who is always the one starting at six tends to become slowly less responsive, and nobody names the reason.

When does distance work badly?

On exploratory work where the answer is not known at the start, since that requires many short exchanges. Defined tasks with clear specifications travel well.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Project taking three times the estimate?

Count the messages. If most are single questions, batching them daily will recover most of the difference.

Start a Conversation