Your morning standup is our afternoon

The first thing US and European clients ask us is not about price or stack. It is "where are you, and will our hours collide?" Fair question. So here is the honest math for working with a studio in Alexandria, Egypt, and the checklist we actually run inside the overlap.

The math, not the marketing

Cairo sits at UTC+2 (UTC+3 in summer). Against the places our clients actually live:

• Berlin / Amsterdam / Paris: zero to one hour behind us. We are simply in your workday. Your 9am is our 9 or 10am. This is the easy case, and it is most of Europe.
• London: one to two hours. Same story. Your morning is our late morning.
• US East Coast: six to seven hours behind. Your 9am is our 3 or 4pm. Your entire morning lands in our afternoon, which is the window where calls, demos, and reviews happen.
• US West Coast: nine to ten hours. This is the hard one. Your 9am is our 6 or 7pm. Workable, but the live window is narrow and we say so up front.

The short version: EU clients get near-total overlap. East Coast US gets a dependable daily window. West Coast gets a real but smaller one, and anyone who tells you different is selling.

How we work inside the window

Overlap hours are for decisions, not status. The stuff that normally eats meetings gets written down instead, because that is how our process is built anyway:

• Weekly demos, not status decks. You watch the system grow on a schedule and redirect early, whether or not you can make the live call. A demo in writing plus a build you can click beats a meeting about the build.
• One document of record. Scope, milestones, price, and what "done" means are fixed on paper at kickoff. Async only fails when the plan lives in someone's head; ours never does.
• The people you talk to build it. No account manager translating across the ocean. Your message goes to an engineer, which is also why we can promise a real reply inside 24 hours instead of a callback window.
• Support has a schedule, agreed before launch. Maintenance is not "email us and hope." The calendar for patches, checks, and improvements is in the contract.

Where it breaks

If your project needs same-hours pairing every day, like a live war-room build for two straight weeks, remote-anywhere is the wrong shape and we would tell you that in the first call. The overlap window is for decisions and reviews. If the work itself must be done shoulder-to-shoulder in real time, hire locally.

The checklist

The exact list we run on distributed projects. Steal it for whoever you hire:

OVERLAP   agreed at kickoff, named in hours, not vibes
PLAN      scope + milestones + price fixed in one doc before work starts
DEMOS     weekly, recorded or written, always a clickable build
CHANNEL   one thread, one owner per side, no relay people
REPLY     a named SLA (ours is under 24h), not "as soon as possible"
SUPPORT   maintenance schedule in the contract, signed before launch

The takeaway

Timezone is the visible concern; visibility is the real one. What clients actually fear is not a six-hour offset, it is a black box. A team that shows you working software on a schedule is closer than a team two blocks away that goes quiet for a month. Ask for the demo schedule and the SLA in writing, whoever you end up hiring. If they hesitate, that is your answer.

← the journal