11 November 20257 min read
Two teams do the same amount of work for the same rate. One is an hour from your clock, the other is seven. At the end of the quarter the near-shore engagement has shipped more. Nothing in the timesheets explains it, and the difference is not effort or ability. It is that a question cost one team four minutes and the other team a day.
That difference has a name worth using, because naming it makes it something you can estimate rather than something you discover. Call it the time-zone tax: the throughput you lose to the round-trip latency of a question.
Where the tax is actually levied
Not in meetings. Meetings can be scheduled across almost any offset if one side is willing to be slightly inconvenienced, and one side usually is. The tax is levied on the unplanned exchanges: the ambiguity in a ticket, the API that does not behave as documented, the design that does not say what happens when the list is empty.
Each of those is a small decision that needs input. Across a shared working day it costs minutes. Across a seven-hour gap it costs a day, or it costs a guess. Both outcomes are expensive, and the guess is the more expensive of the two because it is invisible: the work continues, looks like progress, and is discovered to be wrong at review.
The tax is a function of the work, not the distance
This is the part most comparisons get wrong. The offset is a constant; the tax is not. Multiply the offset by the number of unplanned decisions the work generates per week, and the answer tells you where the work belongs.
- Work with settled requirements and a checkable definition of done generates few unplanned decisions. The tax is near zero, and far-shore is simply cheaper.
- Work that is discovered as it is built generates several per day. The tax is the dominant cost and it will exceed any rate difference you negotiated.
- Queue-shaped work that runs continuously has a negative tax. A large gap means the queue drains while you sleep, which is worth more than shared hours and is exactly why the large offshore support markets exist.
Say that last one out loud, because it is the honest half of this argument. For overnight batch processing, ticket triage, moderation queues and QA runs, a twelve-hour gap is a feature you would pay extra for. A near-shore team cannot offer it from a single location, and pretending otherwise would be nonsense.
What far-shore genuinely buys
Beyond overnight throughput there are two more advantages that near-shore does not have and should stop pretending it does.
The first is scale. The large far-shore markets can staff a rare specialism at volume on a timeline no small market can match. If your constraint is forty engineers in a specific stack next quarter, the time-zone tax is not your binding problem and you should go where the people are.
The second is vendor maturity. Decades of large-programme delivery have produced process certification, established procurement paths and vendors your compliance function has already assessed. If you are running an audit-heavy programme inside a large organisation, that well-worn path has real value, and a younger market does not have an equivalent.
What near-shore buys, stated without inflation
One thing: the price of a question drops to nearly nothing, so ambiguity gets resolved while it is small. Everything else people claim for near-shore, cultural fit, communication quality, engagement, is either a property of the individual provider or a polite way of saying something that should not be said about a nationality.
That one thing is worth a lot for work that changes as it is built, which for most product teams is most of the work. It is worth nothing for work that does not.
The split most mature buyers end up with
The interesting outcome is not that one wins. It is that a company of any size has both kinds of work, and the mature answer is to place each kind where it belongs: a far-shore partner for well-specified, high-volume work, a near-shore team inside your working day for the parts that change weekly, and in-house staff on whatever genuinely differentiates the product.
Running two partners has a real overhead of its own, so it is not free, and below a certain size it is not worth it. But if you are already unhappy with a single arrangement, check whether the actual problem is that you put conversational work in a place designed for batch work, or batch work in a place you are paying near-shore rates for. Both are common, and neither is fixed by changing vendor within the same category.
What to take away
Stop asking which region is better. Ask how many decisions per week your work generates, and place it accordingly. If the answer is high, buy overlap hours and accept that you are not buying the cheapest hour available. If the answer is low, do not pay a premium for a shared working day you will not use.