The hourly rate is not the price

Two quotes land on your desk. One is US$35 an hour, one is US$75. The cheaper team is nine and a half hours ahead of you. Most procurement processes stop there, because the second number is the only one on the page.

The thing that is not on the page is how many times a week your project stops moving.

Latency compounds, cost does not

A developer hits an ambiguity — the spec does not say what happens when a payment is refunded after the subscription is cancelled. With overlapping hours they ask, you answer, work continues. Elapsed time: twenty minutes.

With a twelve-hour gap they ask at the end of their day, you read it at the start of yours, you reply, and they read it at the start of theirs. Elapsed time: a day. Not a day of work — a day of nothing, on a question that took you ninety seconds to answer.

The overlap, calculated

Business-hours overlap between a 9-to-6 day in each city and a 9-to-6 day at UTC-3 — which is Brazil, and which does not observe daylight saving:

• New York — 8 hours of overlap. Effectively the whole day.
• Chicago — 7 hours.
• San Francisco — 5 hours. Their morning is your afternoon.
• London — 5 hours. Their afternoon is your morning.
• Bangalore — 30 minutes.

That last line is the entire argument. Thirty minutes a day is not a working relationship, it is a handover window — and handovers are where context goes to die.

What the gap actually costs

Take a project with six ambiguities a week, which is conservative for anything non-trivial. With overlap, they cost minutes and resolve the same day. With a twelve-hour gap, each costs a day of elapsed time, and a fraction of them get guessed at instead of asked.

Six days of elapsed delay per week does not mean the project takes six days longer — it means the calendar stretches while the invoice keeps running. A build quoted at three months lands in five. At US$35 an hour across five months you have not saved anything against US$75 across three, and you have spent two extra months not having the product.

When offshore is the right answer

When the work genuinely does not generate questions. A well-specified migration, a defined set of test cases, maintenance on a system nobody is changing — that work parallelises across timezones perfectly, and paying for overlap you do not use is waste.

The distinction is not the size of the project. It is whether the specification is finished. If you are still discovering what you are building — which is most first versions — you are buying conversations, not hours, and conversations have to happen while both people are awake.

What to ask for instead of a rate

1. 01How many hours of your working day overlap with theirs. Ask for the number, not the region.
2. 02What happens when a developer is blocked — who they ask, and how long the answer takes.
3. 03Whether the people on the call are the people writing the code.
4. 04What currency you are invoiced in, and whether payment costs you a bank transfer.

None of those appear in an hourly rate, and all of them show up in the delivery date.