The problem
Overlap is a shared brand we are part of rather than a client, which is worth saying before anything else — the positioning below is ours, and so is the mistake at the end of this page.
Every offshore engineering practice makes the same claim on its homepage, and it is always the same sentence: significant timezone overlap with US teams. The sentence is doing no work. A prospect who has been burned before reads it as marketing, because it is indistinguishable from marketing — the studio that overlaps for six hours and the studio that overlaps for ninety minutes write it identically.
The objection underneath is not really about hours. It is “will I be able to reach you when something is on fire”, and no amount of prose answers it, because prose is exactly the medium the reader has learned to discount.
What we decided, and why
Show the clocks. Do not describe the overlap — draw it.
The page carries two live clocks, one per zone, and a 24-hour band with the shared six hours shaded. That is the entire argument, and it works because it is checkable. A visitor can look at their own watch, look at the page, and confirm it is telling the truth right now. A claim that can be falsified in one second and survives is worth more than three paragraphs that cannot be tested at all.
It also fails honestly, which is the part worth keeping. Land on the page at three in the morning Karachi time and the band shows you are outside the overlap. A marketing site would never volunteer that. Volunteering it is what makes the shaded hours believable when you land during them — the component is not selling, it is reporting, and a reader can tell the difference.
The rest of the site stays deliberately quiet so the clocks are the only thing doing work: React on Vite, Tailwind, Lenis for the scroll, Vercel.
What went wrong
The page made its argument well, and the argument was not what stood in the way.
That is an awkward thing to publish about your own work and it is the honest account. The clocks do what they were built to do: they answer the timezone objection, immediately and checkably, in a way prose cannot. What we had assumed — without ever testing it — is that the timezone objection was the one holding enquiries back. It was the objection people said, which is not the same thing, and a site can only answer the objections it is pointed at.
The failure was upstream of the build. We took a stated objection at face value and engineered a very good answer to it, and the thing that actually needed work was the offer behind the site rather than the site. A studio page can make a scheduling argument beautifully and still not resolve the questions a prospect is really weighing: whether this team has done the specific thing before, who is accountable if it slips, and what happens when it does.
The engineering lesson is small and the other one is not. The component is still the right idea, and we would build it again. We would not again treat “what do prospects object to” as answered by asking them, or assume that the most articulable objection is the binding one.
Where it is now
The site is live. The offer behind it is being reconsidered, which is the honest answer and follows directly from the section above.
Overlap is a shared brand rather than an unrelated client — a vehicle for selling US-hours delivery out of Pakistan — so the positioning problem is ours to fix, not a lesson we watched somebody else learn. The clocks stay. What sits around them is being rebuilt around the questions prospects were actually weighing, rather than the one they found easiest to say out loud.