In 2008 the word "offshoring" quietly disappeared from sales decks and board papers. It was replaced by "rightshoring" — the idea that each activity should be performed wherever it can be done best, whether that is onshore, nearshore or offshore. Part of this was pure repositioning. It was a US election year, unemployment was rising, and no executive wanted to defend a slide with "offshore" printed across it. Providers understood the mood and changed their vocabulary faster than they changed their delivery models. But underneath the euphemism there was a real and overdue shift, and organizations that took it seriously built better operations than those that treated it as a naming exercise.
Why the Original Model Was Under Pressure
The first wave of offshoring rested on a simple proposition: the same work, performed by equally qualified people, at a fraction of the cost. By 2008 that proposition had developed several cracks. Wage inflation and attrition. Salaries in the established Indian delivery centres were rising at double-digit rates, and attrition in transactional roles ran at levels that would be considered a crisis in any domestic operation. Every departure meant retraining, and retraining meant errors charged to the client. Currency. Costs were incurred in rupees and revenues earned in dollars and pounds. Currency movement in the preceding period had compressed provider margins, and providers passed that pressure back through pricing and staffing mix. The coordination tax. Companies discovered that the arbitrage calculation had ignored the cost of managing distributed work — retained governance teams, travel, extended cycle times across time zones, rework, and the senior attention consumed by escalations. Recession. The downturn cut demand across the board. Academic analysis of the period notes that the offshoring market was materially affected by the 2008–2009 recession, with offshored finance functions particularly hit — at a time when the United States alone accounted for around sixty percent of Indian IT and BPO exports.
What Rightshoring Actually Means
Stripped of the branding, rightshoring is a discipline: decide location at the level of the activity, not the function. A finance operation is not one thing. It is invoice capture, exception handling, vendor queries, month-end journals, reconciliations, statutory reporting, treasury, and management analysis. Those activities have wildly different characteristics, and the sensible location for each is determined by a small set of factors:
- Time zone dependency. Work requiring live interaction with the business or customers belongs where the overlap exists. Work that only needs a completed batch by morning does not.
- Language and cultural proximity. Not just fluency — the ability to handle a frustrated supplier or a nuanced query without escalation.
- Judgement intensity. Rules-based work travels well. Work requiring contextual judgement, relationship knowledge or negotiation does not travel cheaply.
- Regulatory and data constraints. Some data cannot lawfully be processed in some jurisdictions. This has become a hard boundary rather than a preference.
- Volume and volatility. High, stable volumes support dedicated offshore teams. Spiky, low-volume work usually does not justify the coordination overhead.
- Talent availability at the required quality. Rate matters less than whether you can recruit and retain people who are good at the work. Applied honestly, this analysis rarely produces a single answer. It produces a distribution — which is exactly the point.
| Factor | Activity-level question |
|---|---|
| Time-zone dependency | Does the work need live overlap or a completed batch? |
| Language and context | Which queries require local language or relationship knowledge? |
| Judgement | How much context, negotiation or exception handling is needed? |
| Data constraints | Where may the activity's data lawfully and contractually be processed? |
| Volume | Is demand stable enough to support a dedicated team? |
| Talent | Can the location recruit and retain people at the required quality? |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
The Nearshore Middle Ground
The practical outcome was the rise of locations that split the difference: meaningful cost advantage combined with time-zone overlap and cultural closeness. European companies built delivery in Poland, the Czech Republic, Hungary and Romania. North American firms expanded into Mexico, Costa Rica and Colombia — continuing a pattern of production and services shifting to Mexico that stretches back decades. European and Gulf organizations increasingly used Egypt, Jordan and Morocco for Arabic and French language capability. The Philippines dominated voice work. Nearshore was almost never the cheapest option. It won on total cost of delivery once management overhead, cycle time and rework were included — which is a different metric from hourly rate, and the one most 2005-era business cases never calculated.
What Has Changed Since
Two forces have rewritten the location decision again. Automation removed the arbitrage layer. The high-volume, rules-based transaction processing that offshore economics were built on is precisely the work that document capture, workflow automation and now AI extraction handle. What remains offshore is more judgement-heavy, which means the sourcing question has shifted from "what is the rate?" to "can we recruit genuinely capable people here, and will they stay?" Location became a legal question. Data protection regimes across Europe, the Gulf and Asia now constrain where personal data may be processed and under whose jurisdiction the processor sits. A delivery location that fails a residency requirement is not a cheaper option; it is not an option. Location strategy now has to pass a legal test before it reaches the cost test. The result is that most mature operations run a deliberate mix: a small onshore core for judgement, relationships and regulatory accountability; a nearshore hub for exception handling and process management; an offshore centre for scale processing; and automation absorbing the volume in between.
Making the Decision Properly
- Inventory at the activity level. List every activity with volume, cycle time, error rate, judgement requirement, language need and data classification. Location decisions made at the function level are guesses.
- Compute total cost of delivery, not rate. Include retained management, travel, transition, error and rework cost, attrition-driven retraining, and the cycle-time impact on working capital.
- Do not split a process mid-handoff. The most expensive operating models are the ones that cut a process in half and create a queue between two locations that never speak to each other.
- Apply the data test first. For each activity, establish what data it touches and where that data may lawfully and contractually be processed. Do this before shortlisting locations.
- Standardise before you move. Moving a broken process offshore exports the dysfunction and adds a language barrier. The savings in these programmes come predominantly from standardisation, not geography.
- Set a review cadence. Wage inflation, currency, regulation and automation all move. A location strategy fixed in 2019 is already wrong; revisit annually.
- Measure the coordination tax explicitly. Count escalations, handoff delays and management hours consumed. If it is growing, the model — not the team — is the problem.
The Honest Summary
Rightshoring began as a defensive rebrand in a difficult political year. It survived because the underlying idea was correct: location is an activity-level decision driven by time zones, judgement, language, regulation and talent — with cost as one input rather than the whole equation. Companies that internalised that built resilient operations. Those that simply changed the word on the slide are still running the same fragmented model, now with a data protection problem attached.
Common Questions
What is the difference between offshoring, nearshoring and rightshoring?
Offshoring moves work to a distant, lower-cost country. Nearshoring moves it to a nearby country with time-zone and cultural overlap. Rightshoring is the discipline of deciding, activity by activity, which of onshore, nearshore, offshore or automation is appropriate.
Is offshore still cheaper?
On hourly rate, usually yes. On total cost of delivery — including management overhead, rework, attrition and cycle time — the gap is much narrower, and for judgement-heavy work it often disappears.
How does data protection affect delivery location?
Many regimes restrict where personal data can be processed and which jurisdictions' authorities can access it. Delivery location must be assessed against those rules before cost is considered.
How has AI changed location strategy?
It removes the high-volume, rules-based work that arbitrage economics depended on, leaving exception handling and judgement. That raises the importance of capability and retention relative to labour rate.
Delivery Location Review — Outpace maps your operations activity by activity, applies the data, judgement and time-zone tests, and builds a location and automation mix costed on total delivery rather than hourly rate.