K
KnowMBAAdvisory
OperationsAdvanced7 min read

Nearshore Strategy

Nearshore strategy delivers work from a country geographically and culturally close to the customer, typically with significant time-zone overlap. For US buyers, nearshore = Mexico, Costa Rica, Colombia, Brazil, Argentina, Dominican Republic. For Western European buyers, nearshore = Poland, Romania, Czech Republic, Portugal, Morocco, Egypt. For Asian buyers, nearshore = Vietnam, Malaysia, Indonesia for Japan/Korea/Singapore. Nearshore sits structurally between onshore (high cost, full overlap) and offshore (lowest cost, full distance) — typical labor arbitrage of 35-55% below onshore (vs 60-70% for offshore), but with 3-5 hours of business-day overlap, lower cultural distance, and easier travel for governance. The model exploded post-2015 as Indian IT wage inflation eroded offshore arbitrage and as buyers learned that the productivity tax of 12-hour time gaps was higher than they'd modeled. Mexico has emerged as the dominant nearshore for US buyers — Guadalajara is now a major IT delivery hub with 100K+ tech workers, and the IT services export market from Mexico to the US grew ~15% annually through 2020-2024.

Also known asNearshoringNearshore OutsourcingRegional SourcingTime-Zone Aligned Sourcing

The Trap

Treating nearshore as 'offshore lite.' The mental model 'cheaper than onshore, more expensive than offshore, mediocre on both axes' misses what nearshore actually delivers: time-zone overlap that fundamentally changes how work flows. With nearshore, your offshore engineering team can join your daily standup live; your contact center supervisor can call your VP without scheduling 48 hours ahead; your back-office processor can flag an exception that gets resolved same-day instead of next-day. That synchronous collaboration capacity is worth 15-25% productivity vs offshore — which often closes the cost gap entirely. Second trap: assuming all nearshore is the same. Costa Rica's talent pool is deep but small (~5M population, saturated for senior tech roles); Mexico is huge but quality varies by city; Colombia has strong language and is rising; Brazil has scale but Portuguese (not Spanish) and tax complexity. Third: under-investing in country-specific governance — nearshore is closer but it's still a foreign jurisdiction with its own labor law, tax structure, and political risk.

What to Do

Use nearshore for work where these conditions hold: (1) you need synchronous daily collaboration with onshore teams (engineering, product, complex customer support); (2) cost reduction is meaningful but not the dominant lever; (3) you want a faster ramp than India offshore (nearshore hiring cycles in Mexico are typically 30-50% faster); (4) regulatory or customer expectations make full offshore unworkable. For US buyers, run a country selection matrix: Mexico (highest scale, best for IT/BPO, USMCA labor flexibility), Costa Rica (best for English-language premium services), Colombia (rising fast, especially for sales/CX), Brazil (scale but complexity tax). Build governance assuming you'll travel quarterly — nearshore is close enough that on-site reviews are practical and underused. Don't pick a city solely on cost; talent depth at the role you need is the binding constraint.

Formula

Nearshore Effective Cost = Loaded FTE Cost × (Onshore Productivity Ratio) + Coordination Premium

In Practice

Mexico's IT services export industry has scaled from ~$2B in 2010 to ~$10B+ in 2024, driven primarily by US nearshore demand. Guadalajara — sometimes called 'Silicon Valley of Mexico' — hosts development centers for Oracle, IBM, Intel, HP, and dozens of mid-tier US tech companies. The economics: senior engineer in Guadalajara at ~$45-65K loaded vs ~$180-220K in San Francisco, with full Pacific-time-zone overlap and a direct flight from SFO under 4 hours. Costa Rica went the premium English-language nearshore route: Intel established its first non-US semiconductor plant there in 1997, and the country built a knowledge-economy strategy around it. By 2024 Costa Rica was a key delivery location for Amazon, Microsoft, and IBM — focused on customer experience, finance shared services, and engineering work for North American clients. Both economies illustrate nearshore's strategic logic: time-zone overlap and cultural proximity are worth a premium over pure offshore for certain work types.

Pro Tips

  • 01

    For engineering work, nearshore typically delivers 90-100% of onshore productivity — close to no productivity penalty. For complex domain work (finance, legal, healthcare back-office) the gap is similar to onshore. The productivity penalty that hits offshore (12-15%) often disappears at nearshore.

  • 02

    USMCA gives Mexican operations significant operational flexibility for US buyers — no work permit issues for short-term onshore assignments, simpler tax structure, and lower duty exposure than offshore manufacturing relationships. Build this into your nearshore business case.

  • 03

    Nearshore wage inflation has been more moderate than India (typically 5-7% in Mexico vs 8-12% in India) but the trajectory is the same — early movers locked in the best talent at the lowest cost. Late entrants pay the new equilibrium rate, which is closer to onshore than the original arbitrage suggested.

Myth vs Reality

Myth

Nearshore is just expensive offshore

Reality

Nearshore solves problems offshore can't — synchronous collaboration, real-time customer interaction, faster decision cycles, easier governance. The right comparison isn't cost-per-FTE; it's productivity-adjusted cost per outcome. For collaboration-heavy work, nearshore often beats both onshore and offshore on total cost.

Myth

Nearshore talent pools are too shallow for serious scale

Reality

Mexico has ~700K IT workers, Poland ~500K, Romania ~150K, Costa Rica ~50K. The small countries have depth limits, but Mexico, Poland, and Brazil can sustain operations of 5K-10K seats. Most failures come from picking the wrong city in the right country (e.g., trying to scale in San José, Costa Rica, when the local market is saturated).

Try it

Run the numbers.

Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.

🧪

Knowledge Check

You're choosing between offshoring engineering to India (60% labor savings) vs nearshoring to Mexico (45% labor savings). The work requires daily collaboration with US-based product managers. What should drive the decision?

Industry benchmarks

Is your number good?

Calibrate against real-world tiers. Use these ranges as targets — not absolutes.

Nearshore Labor Arbitrage vs Onshore (loaded FTE cost)

IT services and BPO from Latin America to US-based buyers, 2024

Mexico (Guadalajara, Monterrey)

55-65% lower

Colombia (Bogotá, Medellín)

60-70% lower

Costa Rica (San José)

45-55% lower

Brazil (São Paulo, Curitiba)

50-60% lower

Source: Everest Group LATAM Sourcing Report 2024

Real-world cases

Companies that lived this.

Verified narratives with the numbers that prove (or break) the concept.

🇲🇽

Mexico IT Services Industry

2010-2024

success

Mexico's IT services export industry grew from ~$2B in 2010 to ~$10B+ in 2024, driven primarily by US nearshore demand. Guadalajara — branded 'Mexico's Silicon Valley' — became the largest concentration: hosting development centers for Oracle, IBM, Intel, HP, and dozens of mid-tier US tech companies. The combined Mexican IT workforce reached ~700K by 2024. Drivers: full Pacific-time-zone overlap with US West Coast, USMCA labor mobility, $45-65K loaded cost for senior engineers (vs $180-220K in SF), 4-hour flight for governance. The growth accelerated 2020-2024 as Indian wage inflation eroded the offshore margin and US buyers re-evaluated full-offshore models post-pandemic. By 2024 Mexico was the second-largest LatAm IT exporter (behind Brazil) and the dominant nearshore destination for US buyers.

Mexico IT Services Exports (2024)

~$10B+

Total Mexico IT Workforce

~700K

Guadalajara Tech Workforce

~100K

Senior Engineer Cost (Guadalajara)

~$45-65K loaded

The nearshore boom is a structural correction, not a fad. Time-zone overlap matters more than the offshore industry's first-generation business cases admitted. Mexico has scaled because it solves a real problem India can't: synchronous collaboration with US teams.

Source ↗
🇨🇷

Costa Rica (Intel + downstream tech ecosystem)

1997-2024

success

Intel's 1997 decision to build its first non-US semiconductor manufacturing plant in Costa Rica catalyzed a knowledge-economy transformation. The country invested heavily in bilingual STEM education, English-language corporate training, and special-economic-zone tax incentives. By 2024, Costa Rica hosted delivery operations for Amazon, Microsoft, IBM, HP, and dozens of mid-market firms — focused on customer experience, finance shared services, and engineering work. The country became the LatAm leader for English-language premium services (CSAT scores from Costa Rican contact centers consistently exceed Indian and Filipino benchmarks for English-language work). Costa Rica's IT/BPO sector employs ~50K people — small in absolute terms but high quality, and the country's stable democracy and strong rule of law make it a low-risk nearshore for sensitive work.

Costa Rica IT/BPO Workforce

~50,000

Multinationals with Operations

300+

English Proficiency (EF EPI 2023)

Among top in LatAm

Avg Senior Engineer Cost

~$50-70K loaded

Costa Rica shows the 'premium nearshore' play: smaller talent pool, higher quality, stable governance. Best for clients who need English-language premium services and don't need 5,000-seat scale. The opposite of the Mexican play (volume) — and equally valid for the right work.

Source ↗

Related concepts

Keep connecting.

The concepts that orbit this one — each one sharpens the others.

Beyond the concept

Turn Nearshore Strategy into a live operating decision.

Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.

Typical response time: 24h · No retainer required

Turn Nearshore Strategy into a live operating decision.

Use Nearshore Strategy as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.