For much of its history, the GBS case was built around a simple proposition: consolidate work, standardise it and deliver it at a lower unit cost. That logic created real value. But it also encouraged an operating model in which efficiency was gained by concentrating people, knowledge and process execution in fewer places.
In a stable environment, concentration looks like scale. In a volatile one, it can become a single point of failure.
The risk environment has changed faster than many delivery models. Armed conflict, sanctions, tariff shifts, cyber threats, data-sovereignty rules and critical-supply constraints now reach deep into routine business decisions. They alter the cost of freight, the availability of cash, the legality of serving a customer, the location of data and the ability of people to work—all at the same time.
This is the opening for GBS to assume a larger enterprise role. Not because it should replace treasury, risk, legal or supply chain, but because it sits where their decisions become transactions.
Geopolitical risk now travels through operations
The financial effect of geopolitical disruption is no longer theoretical. Research cited in the source material suggests that geopolitical and macroeconomic forces influence a substantial share of large-company returns, while many organisations still lack a robust framework for managing the exposure. The gap is not awareness. It is operational preparedness.
Four transmission channels appear repeatedly across sectors.
Supply and tariff disruption
Trade routes, sourcing economics and contract assumptions can change faster than annual plans or vendor strategies.
FX and liquidity pressure
Currency movements, inflation and capital controls can compress margin and restrict the movement of cash between markets.
Sanctions and regulatory fragmentation
Customers, vendors and payments may require immediate re-screening as regimes change or restrictions expand.
Data sovereignty and cyber risk
Localisation rules, cloud restrictions and state-backed attacks can fracture global platforms and operating standards.
Finance feels these channels quickly. A disrupted shipping lane can reprice freight, insurance and energy within weeks. A sanction can stop a payment immediately. A currency shock can turn a profitable contract into a loss before the next forecast cycle closes.
That is why CFOs are moving toward scenario-based planning anchored in cash, working capital and operational drivers. Treasury can see liquidity and balance-sheet risk. FP&A can model scenarios. GBS can connect both to the underlying transactions and process capacity needed to act.
The location decision is no longer a cost decision
India remains central to the global services model. It offers scale, deep functional talent and an increasingly important base for analytics and AI. Yet the question facing leaders is no longer “India or nearshore?” It is how to construct a portfolio in which each location has a deliberate role.
Tariff uncertainty, local-first employment policies, visa restrictions and data rules make extreme dependence on one delivery country harder to defend as a risk position.
The same pressures can encourage organisations to place more decision ownership and specialist capability inside their own GCCs rather than depend on cross-border movement or fragmented vendors.
These forces do not cancel each other out. Together, they change the design principle. India can remain the scale and capability anchor, supported by regional hubs closer to customers, regulators and critical markets. The objective is not duplication everywhere. It is sufficient operational interoperability to avoid dependence on any single geography.
A mature GBS should therefore be able to explain what work must remain concentrated, what work should be distributed, what capacity is warm in a secondary hub and how quickly critical processes can move.
Resilience is more than a business-continuity plan
Most large organisations already have continuity documents. They identify alternate facilities, recovery contacts and technology dependencies. The problem is that documented recovery is not the same as executable recovery.
A secondary hub may be named in the plan but lack current process knowledge. Staff may have laptops but not production access. Standard operating procedures may exist but lag the latest policy or system change. Decision rights may still sit with leaders in the affected location. In each case, the backup exists on paper while the operating capability does not.
For GBS, genuine resilience requires a standing level of interoperability across locations. Critical processes need common definitions, compatible workflows, current documentation and cross-location access. Secondary teams need enough live volume to remain competent. Leaders need explicit authority to reroute work, prioritise payments or relax non-critical service levels without waiting for a lengthy escalation.
This does not mean every process should run active-active across multiple countries. The cost would be difficult to justify. It means tiering processes by criticality and designing the recovery model accordingly. Payroll, treasury operations, sanctions screening and month-end close may require warm capacity and frequent testing. Lower-risk work may rely on a slower transfer model.
The distinction matters because geopolitical disruption rarely arrives as a clean site outage. A location may remain open while a cloud service becomes unavailable, employee mobility is restricted, a banking route closes or a new rule changes which data can cross a border. Resilience must therefore be designed around failure modes, not buildings.
Multi-hub models also create their own risk when roles are vague. Parallel centres can duplicate governance, compete for mandates and introduce inconsistent controls. Each node needs a defined purpose: scale engine, regional interface, specialist centre, regulatory anchor or recovery partner. Portfolio design works when the hubs are complementary, not interchangeable labels on an organisation chart.
Six moves turn GBS into a resilience function
Own risk sensing and scenario execution
Build rolling models around tariff shifts, sanctions, currency shocks, supplier failure and cash constraints. The value is not the model alone; it is the ability to translate a scenario into actions across payments, collections, procurement and reporting.
Design a portfolio footprint
Move beyond one-country concentration. Give each hub a clear role, pair critical processes with an active secondary location and make capacity-transfer rules explicit before disruption occurs.
Own capabilities, not merely tasks
Centres that execute narrow activity fragments are easier to move or reduce. Centres that own end-to-end outcomes, specialist knowledge and decision support become part of the enterprise’s response capacity.
Productise compliance and data sovereignty
Embed sanctions screening, jurisdiction-aware data handling and regulatory controls into P2P, O2C and master-data workflows. Compliance agility should be a managed service, not an emergency project.
Use insourcing windows selectively
Restrictions on talent mobility can make a GCC more attractive as a long-term capability base. The case should be framed around continuity, expertise and ownership—not a short-lived labour-cost comparison.
Report risk posture to the board
GBS leadership should show where critical work sits, which dependencies are exposed, what recovery has been tested and where decision authority resides when headquarters or a hub is unavailable.
Measure resilience alongside efficiency
A strategic mandate needs a different scorecard. Cost and service-level performance still matter, but they say little about the organisation’s ability to absorb a shock.
These measures change the leadership conversation. A hub with the lowest unit cost may not be the lowest-cost outcome if it cannot fail over, cannot retain specialist talent or exposes the enterprise to regulatory interruption.
The reporting cadence matters as much as the measures. A quarterly resilience pack assembled for a committee will always lag the operating reality. The better model is a small, live dashboard owned by GBS and reviewed with treasury, enterprise risk, cyber, legal and HR. It should show exceptions and trend movement—not simply a static risk rating.
That dashboard should answer practical questions. Which hub currently carries the largest concentration of critical activity? Which recovery test last failed, and why? Where are access rights or documentation out of date? Which market event would trigger a workload shift? How much capacity is genuinely available elsewhere?
This is where GBS can add something that a corporate risk register cannot: operational evidence. It can connect a geopolitical signal to the processes, people, vendors, systems and cash flows that would be affected, then show whether a mitigation action has actually been completed.
GBS Location Risk Assessment Checklist
Evaluate delivery hubs across geopolitical and macroeconomic stability, regulation and data sovereignty, infrastructure, workforce safety, and operational interoperability. The checklist includes a five-point scoring framework, risk-action matrix and rapid mitigation template.
Request the checklistThe leadership decision
The case for resilience is not an argument against efficiency. It is an argument for understanding efficiency in a less fragile way.
For GBS leaders, that means moving before the risk committee forces the issue: assess concentration, define the role of each hub, build real transfer capability and connect the network to enterprise scenario planning.
Cost savings may have justified the original model. Resilience is what will justify its next mandate.
Draft editorial note: Selected market statistics and policy references are based on the research inputs supplied for this article. They should be source-verified and footnoted before publication.