Shared services location decisions are usually presented as a cost model. Someone builds a comparison of fully loaded salary by city, applies an attrition assumption, adds facilities and connectivity, and produces a ranking. Poland versus the Philippines versus keeping the work closer to home. The lowest number wins, the business case goes to the board, and the site opens. Two years later the picture is different. The cost per transaction is close to plan but the quality is not. Attrition ran higher than modelled. The processes that required real judgement never transferred properly and are being done informally back in the business units. And the escalation path involves a nine-hour time difference, which means every genuine exception costs a day. The location decision was never really about salary arbitrage. It was about which processes can be separated from their business context, and the cost model asked none of those questions.
What the Established Locations Actually Offered
By 2014 the shared services map had settled into recognisable clusters, each with a distinct proposition rather than simply a different price. Central and Eastern Europe — Poland, the Czech Republic, Hungary, Romania, Slovakia — sold language depth and proximity. A centre in Kraków or Bucharest could staff German, French, Italian, Spanish and Nordic language capability, sit within one or two time zones of Western European operations, operate inside the EU regulatory and data protection perimeter, and be reached by a short flight when something needed a face-to-face conversation. The cost saving against Western Europe was real but moderate; the operational advantages were substantial. This is where finance processes requiring European statutory knowledge and customer-facing language work concentrated. The Philippines and India offered scale and depth that Europe could not match. Large English-speaking graduate populations, mature provider ecosystems, well-understood delivery models and a cost base low enough that high-volume transactional work became genuinely cheap. India carried additional depth in technical and analytical work; the Philippines carried a strong voice and customer-service orientation. The trade-offs were time zone distance from Europe, higher wage inflation in mature locations, and attrition rates that fundamentally shaped what kinds of work could be done well. Nearshore and onshore alternatives — secondary cities in the home country, or neighbouring lower-cost regions — offered the smallest saving and the fewest problems. Same regulatory regime, same language, same working hours, same employment law. For processes requiring heavy judgement, close business interaction or regulatory sensitivity, this frequently delivered better total economics than an offshore centre that needed constant support.
The Variable the Cost Model Missed
The useful way to make this decision is not to rank locations. It is to segment the work, and then place each segment where it will actually succeed. Transaction volume with low judgement — invoice processing, payment runs, standard journal entries, basic reconciliations, master data maintenance — transfers well to distant, lower-cost locations. It is rule-based, documentable, measurable, and does not require business context. This is where offshore arbitrage genuinely works. Judgement-heavy work — complex reconciliations, technical accounting, exception resolution, business partnering, anything requiring a conversation with a commercial manager — transfers badly regardless of the talent available. Not because the people cannot do it, but because the work depends on context that does not travel: knowing why this customer always disputes, which manager needs to be called, what the commercial arrangement actually was. Moving this work usually means the visible process moves and the real decision-making stays behind, informally, uncounted. Language and regulatory work must go where the language and the regulatory knowledge are. European statutory reporting needs people who understand local requirements. Customer contact in eight languages needs eight languages. And time-zone-sensitive work — anything requiring same-day interaction with the business — needs overlap. A four-hour overlap makes exception handling workable. A two-hour overlap makes every exception a next-day item, which is the hidden cost that appears in the second year. The mistake almost everyone makes is treating the location decision as singular. The right answer for most organizations of any scale is multiple locations with work allocated by characteristic, accepting the coordination cost that creates.
| Work characteristic | Placement question |
|---|---|
| Routine transactions | Can the rules, documents and measures transfer without local context? |
| Judgement and exceptions | Who holds the business context and can they be reached when needed? |
| Language and regulation | Does the team have the required language and current local knowledge? |
| Time-sensitive interaction | Is there enough shared working time for the actual escalation process? |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
The Cost Model's Missing Lines
Several significant costs are systematically absent from location business cases: Transition cost and duration. Knowledge transfer, parallel running, travel, documentation and the productivity dip during and after the move. This is routinely underestimated by a wide margin and rarely revisited after approval. Attrition-driven retraining. At thirty percent annual attrition, a centre retrains a third of its workforce every year, permanently. The cost is not just recruitment; it is the quality variance from a workforce that is perpetually part-new. Wage inflation. Mature offshore locations experience salary growth well above the home market. A saving modelled on today's differential narrows every year, and the one-time nature of the arbitrage becomes apparent around year four. Retained organization. The people who remain to manage the relationship, handle exceptions and own the process. Frequently more expensive and larger than planned. Rework and quality cost. Errors found downstream, corrections, disputes, audit findings — all of which land somewhere other than the centre's cost line. And coordination overhead. Handoffs, status calls, escalation, and the simple friction of working across distance and time. This does not appear in any cost model and is a permanent tax on the operating model.
Practical Guidance for Location Strategy
- Segment the work before ranking the locations. Judgement content, language requirement, regulatory sensitivity and time-zone dependency should drive placement, not cost alone.
- Model total cost including transition, attrition, retained organization, rework and coordination. Salary differential is the smallest interesting number in the comparison.
- Assume wage convergence over the business case horizon. A differential modelled as static will not be.
- Require four hours of working overlap for exception-heavy processes. Below that, every exception costs a day.
- Check the regulatory and data protection position before shortlisting. Cross-border personal data transfer rules can eliminate a location for certain processes entirely.
- Assess the local labour market for your specific skills, not in general. A city with abundant graduates may have a thin market for qualified accountants or Arabic-language specialists.
- Plan for multiple locations with deliberate allocation. Single-location strategies force the wrong work into the wrong place.
- Measure quality and cycle time from the start, not just unit cost. Cost-only measurement guarantees cost-only optimisation.
The Regional Angle
For groups headquartered in the Gulf, the standard Poland-versus-Philippines framing is the wrong starting question, because the region's own geography changes the answer. Time zone is the region's structural advantage. The Gulf sits within a few hours of South Asia, close to Europe in the morning, and within reach of North Africa and the Levant. A shared services centre in Dubai, Riyadh or Cairo can work the same day as operations across Europe, the Middle East, South Asia and much of Africa. That overlap is worth more than a salary differential for any process involving exceptions. Regional cost hierarchy is its own map. Cairo offers a large, well-educated, bilingual Arabic-English workforce at a significantly lower cost base than the Gulf, and has become a serious delivery location for regional back office work. Amman, Beirut historically, and parts of North Africa play similar roles. Riyadh and Dubai cost more but sit closer to the business and to the regulators. Bangalore and Manila remain available for high-volume transactional work at greater distance. The practical answer for a regional group is usually a tiered model rather than one site. Arabic-English bilingual capability is the binding constraint for regional work. Anything customer-facing, government-facing or involving Arabic documentation needs genuine bilingual staff, and that requirement excludes most traditional offshore locations. Cairo, Amman and the Gulf itself are where this capability actually exists at scale. Regulatory proximity matters more than it does elsewhere. WPS payroll submission, GOSI and social insurance filing, gratuity calculation, VAT and corporate tax returns, ZATCA e-invoicing clearance — these require current local knowledge and, in some cases, in-country presence or authorised representation. Placing them far from the jurisdiction produces a dependency on a small number of people who know the rules, which is exactly the concentration risk shared services is supposed to remove. Data residency can make the decision for you. Where personal data or regulated financial data must be processed in-country, the location question is answered by law rather than economics. This should be checked before shortlisting, not after. Nationalisation requirements shape the staffing model. Saudisation targets and Emiratisation requirements affect hiring plans, cost structure and the feasibility of scaling a centre quickly. A business case built on unrestricted hiring of expatriate staff at a given cost may not survive the compliance requirement. And workforce mobility cuts both ways. The Gulf attracts skilled staff internationally, which makes building capability quick. Employment-linked residency also means departure is absolute and immediate, which makes documentation and cross-training defensive necessities rather than good practice. Calendar differences are an operational design issue. Weekend days differ across the region and have changed in recent years, and Ramadan working hours reduce throughput for a month annually. A multi-country centre needs explicit coverage design rather than an assumption of five common working days.
Where the Model Went
The location conversation has largely been absorbed into a broader one. Global business services models moved organizations away from single-site thinking toward networks of centres with work allocated by characteristic — which is what the analysis always implied. Hybrid and remote working, accelerated after 2020, weakened the assumption that a shared service must be a building, and allowed talent-pool thinking that is less tied to a specific city. Automation changed the arithmetic more fundamentally. When a large share of high-volume transactional work can be automated, the case for placing that work in a low-cost location weakens, because the comparison is no longer cheap labour versus expensive labour but labour versus software. What remains after automation is exception handling, judgement and relationship work — precisely the categories that transfer badly to distant locations. The logical endpoint is fewer, more capable centres placed for context and time zone rather than for cost. AI accelerates that shift and adds a new one. Language capability, which was one of the strongest reasons to choose a particular location, is partially commoditised by machine translation and multilingual assistants. Document processing and first-line query handling are increasingly automated. What is left is the work that requires accountability — someone who can be asked why a number is what it is and whose answer carries weight. That work is best placed where it can be reached, in a compatible time zone, close to the business and the regulator. Which is an argument for regional centres, and a reversal of the logic that sent the work far away in the first place.
Common Questions
Should location be chosen on cost?
No. Cost is one input and usually the least predictive. Judgement content, language requirement, regulatory sensitivity and time-zone overlap determine whether the work will succeed in a location; salary determines only what it costs when it does.
What work transfers well to distant offshore locations?
High-volume, rule-based, documentable work with low business-context dependency — invoice processing, payments, standard journals, master data maintenance. Judgement-heavy and relationship-dependent work transfers poorly regardless of the talent available.
How much time-zone overlap is needed?
About four hours of shared working time for exception-heavy processes. Below that, each exception becomes a next-day item and cycle times degrade in ways that no cost model captured.
What is different about GCC location strategy?
The region's own time zone reaches Europe, South Asia and Africa in one working day; Arabic-English bilingual capability is a binding constraint that most offshore locations cannot meet; regulatory processes such as WPS, GOSI and ZATCA need local knowledge and sometimes in-country presence; data residency rules can decide the question outright; and nationalisation requirements shape the staffing model.
Location Strategy Workshop — Outpace segments your processes first, then places each one where it will actually work.