Nearly a third of Microsoft's own internal meetings now span more than one time zone, up 35% since 2021, and meetings after 8pm are up 16% year over year, according to the company's own June 2025 Work Trend Index. That is Microsoft measuring itself, a company with time zone coverage and calendar tooling most 15-person agencies will never have. If the best-resourced software company in the world is watching its own workday stretch into the evening because its teams no longer share a clock, an agency running its first offshore subcontract pilot with a spreadsheet and good intentions is not going to solve it by accident. The teams that avoid it treat the overlap window as a number in the contract, not a vibe in a Slack channel.
What the data actually shows
The figures are specific enough to be useful. Microsoft's Work Trend Index, built from aggregated Microsoft 365 telemetry through February 2025 plus a 31,000-person survey across 31 markets, found that meetings spanning multiple time zones are up 35% since 2021 and now make up close to a third of all meetings. Meetings after 8pm are up 16% year over year. The average worker sends or receives more than 50 messages outside core business hours, and by 10pm nearly 29% of active workers are back in their inbox. None of that is a remote-work story in the abstract. It is what happens, measurably, when the people who need to make a decision together stop sharing a working day.
Add a subcontracted bench in a 12-hour time difference and the same mechanism runs faster, because now two calendars are stretching toward each other instead of one calendar stretching toward a deadline. A California team pushing its day later to catch a Pakistan-based engineer, and that engineer pushing later still to catch the California team's actual decision-makers, produces exactly Microsoft's pattern in miniature: more evening meetings, more after-hours messages, and a "quick call" culture that eats the cost advantage the arrangement was supposed to deliver.
Why the instinct is to add more meetings, and why that's backwards
When a distributed engagement starts feeling disconnected, the reflex is to schedule another sync. It is the wrong move, and Microsoft's own numbers hint at why: 57% of meetings in its data are ad hoc calls booked without a calendar invite, which means most of the sprawl is not planned coordination, it is people reaching for a call because something wasn't written down. Add a live meeting to a distributed team and you have not solved the documentation gap, you have scheduled around it, at a cost paid disproportionately by whichever side is working the evening shift.
The teams that hold up treat this the other way around. Decisions and unblocking get the live window. Status, updates and anything one person can absorb alone gets written and read asynchronously. That single rule does more to stop a bench from becoming an "infinite workday" for either side than any amount of goodwill, because it removes the reason for the ad hoc call in the first place.
The overlap window is a contract term, not a courtesy
A US team on Pacific time and a bench in Pakistan or India share roughly 12 to 13 hours of offset, which puts a 9am to 1pm Pacific window at 9pm to 1am on the other side. That is a real cost paid by real people, and pretending otherwise (calling it "flexible" instead of naming the hours) is how it quietly expands past what anyone agreed to.
Two things make it survivable. First, write the number down: how many hours, which hours, on which days, in the agreement itself rather than as an understanding. Second, protect it. If the daily standup, the blocked-ticket unblock and the design disagreement all compete for the same 90 minutes of overlap, the overlap window needs fewer meetings in it, not more people added to the same slot. A calendar block that anyone can fill with any call stops being an overlap window and starts being just another meeting time, indistinguishable from the sprawl Microsoft's data describes.
A worked example
Picture a 14-person Sacramento agency that just signed its first subcontract pilot: two backend engineers in Lahore, a $4,000 pilot task, four hours of contracted daily overlap. Week one goes fine. By week three, the daily standup has drifted from 20 minutes to 45 because status updates that could have been a written note turn into a discussion, a code review comment thread turns into "let's just hop on a call," and the Lahore engineers are logging on at 10pm three nights running to catch decisions that got made after their overlap window closed.
Nothing about that pilot failed technically. What failed was treating the four hours as available time rather than protected time. The fix the agency actually needs is not a fifth hour of overlap, it is a rule that standups stay at 20 minutes because status moves to a written channel, and that anything raised after the window closes waits until the next one unless someone is prepared to pay the cost of pulling a person back online at 10pm for it. That is a decision worth naming out loud before it happens by default, and it is the same discipline that makes a strong first week with an embedded engineer hold up past week one rather than quietly decaying.
What this doesn't fix
A protected overlap window will not rescue a team with no documentation habit to begin with. If nothing gets written down during the four hours that are live, there is nothing async to fall back on outside them, and the arrangement just relocates the same chaos to a shorter clock. It also will not fix a project that genuinely needs real-time pairing for most of the day, the rare case where the work itself, not just the relationship, needs synchrony. That project wants a same-timezone team or a much larger overlap budget, and an honest partner says so before the pilot rather than after the invoice.
What this means for your firm
- Put the overlap hours in the agreement as a number, not a description. "We're flexible" is how a standup drifts to 7am.
- Reserve the window for what actually needs two people live at once: decisions, unblocking, disagreement. Everything else goes in writing.
- Watch for ad hoc calls creeping in. They are usually a sign something should have been documented instead of scheduled.
- Judge the arrangement by whether the overlap window is shrinking in practice, not by whether the contract still says four hours.
We run our own delivery this way: overlap hours agreed in writing before work starts, and accountability that sits with a named person in California rather than a rotating inbox, whether that capacity rides on a subcontract pilot or sits inside a dedicated team. If your subcontract pilot is already drifting into evening calls on one side of the arrangement, that is usually fixable without adding headcount, and we're happy to look at how yours is structured. For the arithmetic behind the markup itself, the economics of white-label development covers what a fair arrangement pays each side, and vetting a global development partner has the questions worth asking before the first pilot starts.
Sources
- Microsoft WorkLab: Breaking down the infinite workday (Work Trend Index, published June 17, 2025; Microsoft 365 telemetry through February 15, 2025 plus a 31,000-person Edelman survey across 31 markets, February 6 to March 24, 2025)
- Microsoft WorkLab: The rise of the triple peak day