- 01
Market
Saudi Arabia
- 02
Written for
CTO, COO, Head of Digital
- 03
Decision
Work out what nearshore and offshore mean from a Gulf base and which to buy
- 04
Languages
EN · AR
The real variable
One Riyadh working day, shared with a team two hours ahead
This is what a well-run day looks like when the delivery team sits close to your clock. Nothing in it depends on the team being "nearshore" by anyone's label — only on the overlap being real and protected.
Diagram of a Riyadh working day shared with a delivery team two hours ahead: their early start clears reviews, core hours run live on both sides, an end-of-day handoff feeds their remaining hours, and the loop closes the next morning, with an agreed escalation path for after-hours incidents.
- 01
Their morning, your early morning
The delivery team starts two hours before Riyadh and clears review queues and overnight questions, so your day opens with answers waiting rather than requests pending.
- 02
Core shared hours
Most of the Riyadh day is live on both sides: standups, pairing, design sessions and decisions happen in real time, exactly as they would with a team in the next building.
- 03
The handoff at your close
Open questions and review requests are written down before your team leaves, so the remaining hours of the delivery team's day produce progress instead of guesses.
- 04
Next morning, closed loop
What was handed off is done, reviewed or answered when Riyadh opens — a daily cycle with no dead day in it, which is what distance costs when overlap is missing.
When something breaks after hours
An agreed escalation path with named people and response expectations covers the hours outside the overlap — written into the working agreement, not discovered during the first incident.
The arrangements
Three sourcing arrangements, measured in overlap and reachability
Drop the compass labels and sort arrangements by the two variables a Gulf buyer actually feels: how many live hours a day you share, and what it takes to get a person to your office.
| Option | Live overlap in your working day | Effort to get a person on-site | Cost structure | Where it strains | Best for |
|---|---|---|---|---|---|
| Adjacent-zone delivery (South Asia, from the Gulf) | Most of the day, natively: the time-zone gap is about two hours, so full overlap needs no shifted schedules — this is what Western buyers pay a nearshore premium to get. | A short, inexpensive flight plus a managed business-visa routine; days of lead time when the supplier runs visas as a standing process, longer when it does not. | Generally the lowest of the three, driven by the delivery country's salary base — the reason the arrangement exists at all. | Working-week mismatch if not contracted away, and on-site moments that need planning rather than being spontaneous. | Sustained build capacity where daily collaboration matters and the budget has to go far. |
| Far-zone delivery (many hours away) | A sliver of the day or none: collaboration becomes asynchronous by necessity, every question waits for the planet to turn, and a one-day task can take three calendar days. | Long flights and real travel budgets; on-site presence is an event, not a rhythm. | Varies with the country more than the distance; distance itself buys nothing, so a far pool has to win on cost or on rare skills to justify the collaboration tax. | Anything that needs live back-and-forth: discovery, design, incident response, the early weeks of any engagement. | Well-specified, separable work, or skills that exist nowhere closer — with the asynchronous cost accepted knowingly. |
| In-country or in-city team | Total: the same room is available whenever it matters, which no remote arrangement fully reproduces. | None — presence is the default rather than an arrangement. | The highest of the three, carrying local salary levels and the recruitment cost of a tight market. | Scale and specialisation: the local pool is finite, and paying proximity prices for work that never needed proximity is the quiet budget leak. | The work where physical presence is the point — regulated environments, on-site operations, the ownership layer. |
The models in between
Overlap guarantees and rotating presence buy back most of what distance takes
Between "everyone local" and "everyone far" sit arrangements that price the middle deliberately. The first is the overlap guarantee: a remote team whose contract specifies the live shared hours — which hours, every working day, protected from meetings drift and holiday mismatch — so the collaboration properties of proximity are bought without its salary levels. The second is rotating presence: the remote team's leads spend planned weeks at your office on a rhythm — heavier during discovery and launches, lighter in steady state — so relationships, context and trust are rebuilt in person on a schedule rather than left to decay over video. Combined, the two recover most of what a buyer actually wants from "nearshore" at a cost structure closer to offshore.
The test of either mechanism is whether it survives contact with the contract. An overlap guarantee that lives in a sales deck is a mood; one that lives in the working agreement with named hours and named consequences is a property of the engagement. The same goes for rotation: "we visit regularly" is a hope, while a planned quarterly rhythm with the travel costed into the price is a commitment. When you evaluate any supplier who claims the middle ground, ask to see where these terms are written — the answer sorts the arrangements from the marketing quickly.
Our role
Delivery from Pakistan with the middle-ground terms in writing
- 01
Overlap as a contract term
Our teams sit two hours from Gulf time, and the working agreement names the live shared hours and the Gulf working week — so the overlap this page argues for is a term you can hold us to, not a by-product of geography.
- 02
Presence on a rhythm, priced in
On-site weeks are planned into the engagement — front-loaded for discovery, recurring for the life of the work — with travel and visas managed as our standing routine and costed transparently rather than surfacing as surprises.
- 03
Response expectations by hour
The agreement states what response you can expect inside the overlap, outside it, and in an incident — because the difference between a good remote team and a frustrating one is almost always the unwritten expectations.
Whether your work needs proximity, overlap or merely competence is a question we will answer with you against the actual tasks — and the parts that genuinely need a person in the room, we plan around rather than talk around.
Common questions
What buyers ask
What does nearshore even mean for a company based in Riyadh?+
Taken literally, very little — the term was coined for American buyers using Latin America and European buyers using Eastern Europe, and it encodes their geography, not yours. Translated into what it is actually for, it means a delivery team that shares your working day and can reach your office without an expedition. By that functional definition, the regions a Western glossary files under "offshore" — Pakistan and the rest of South Asia — are the Gulf's nearshore: about two hours from your clock, a short flight from your cities. The practical advice is to stop using the words in supplier conversations and specify the substance instead: how many live hours a day the team will share with yours, guaranteed in the agreement, and how quickly a lead can be at your office. Any supplier who answers with a label rather than numbers is answering a different buyer's question.
How many shared hours a day does a development team actually need?+
It depends on the phase of the work more than on the work itself. Discovery, design and the first weeks of a new team need the most — close to a full shared day if possible — because this is when ambiguity is highest and every unasked question compounds. A team in steady delivery on a well-understood product needs less: enough for a standup, a review conversation and room for the unplanned question, which a handful of protected hours covers if they are genuinely protected. Incident response needs an escalation path rather than overlap, since incidents ignore schedules. The common failure is not too few hours but unprotected ones — a nominal overlap that meetings, holidays and week-structure mismatches quietly eat. Whatever number you agree, the working agreement should name the hours, name the shared working days, and treat them as a delivery commitment rather than an intention.
Is a rotating on-site rhythm worth what the travel costs?+
Usually yes, if it is a rhythm rather than a gesture — because the things it buys are the ones video degrades most. Early in an engagement, a week in the same room builds the context and trust that months of calls approximate slowly; at intervals thereafter, it renews them and surfaces the small frictions people do not raise on screen. The spend fails when the visits are ceremonial — a manager attending meetings that could have been calls — and pays when the right people come for the right weeks: leads during discovery, engineers during integration crunches, whoever owns quality during a launch. Because flights from a two-hour-adjacent region are short and cheap by international standards, the travel line is modest relative to a team's cost, and the practical questions are about execution rather than affordability: who comes, on what rhythm, planned how far ahead, and is it priced into the engagement or negotiated visit by visit. A supplier with ready answers has done it before; one without is improvising.
In this cluster
A working-agreement draft for your team: the guaranteed daily overlap, the on-site rhythm, and the response expectations — before any contract is discussed.
Specify it for your team
