Building an India tech center for a global firm — strategic playbook

Global Capability Centers (GCCs) — once derisively called 'offshore' or 'BPO' — have become the strategic engineering and operations hubs for many global firms. The 2026 GCC isn't a cost center; it's where some of the company's most senior engineering, product, design, data and operations talent sits. The strategic question for global firms isn't whether to have an India tech center, it's how to make it strategic from year one.

Four maturity stages

Foundation stage (5-30) — getting it right early

• Start with a senior engineering hire as the foundational presence.
• Use EOR for the first 5-15; subsidiary setup in parallel.
• First office — coworking (WeWork, Awfis) rather than long lease.
• Founder visits quarterly — set culture, build trust.
• Compensation at top half of Bengaluru market.
• Avoid the 'offshore' framing — these are engineers, not delivery resources.

Expansion stage (30-150)

• Own subsidiary required; full HR / finance / facilities team.
• First India head — engineering manager or director, ideally promoted from internal team.
• Physical office lease — Bengaluru Whitefield, ORR or HSR for tech; Hyderabad HITEC City; Pune Hinjewadi.
• Multi-function — add product, design, data, possibly operations functions.
• Structured onboarding programme for new hires.
• Performance management framework localised to Indian context.

Strategic GCC stage (150-500)

• India Country Head or India CEO — senior leader reporting to global C-suite.
• Multiple campus locations possible (Bengaluru + Hyderabad).
• End-to-end product ownership for specific product lines.
• Indian leaders on global leadership team.
• Innovation programmes — Indian R&D contributing globally.
• Indian fellowship programmes, intern pipelines, university partnerships.
• ESOP at parity with global peers; some India-specific equity programmes.

Mature GCC (500+)

• Hub for multiple business units or product lines.
• Indian leaders in global key positions (sometimes head global function from India).
• End-to-end customer-facing teams (sales, marketing, support globally).
• Innovation labs, applied R&D, patents filed from India.
• Public profile in India — campus visits, brand recognition.
• Some firms have IPOed India operations separately (rare but happens).

Operating model considerations

• Reporting lines — direct to global function leaders (cleaner) vs. matrix through India Head (more political but localised).
• Compensation philosophy — parity vs. local market (parity wins for retention).
• Performance management — same global framework, calibrated for Indian context.
• Promotion velocity — Indian engineers expect predictable promotion; benchmark against credible Indian SaaS unicorns.
• Equity at parity — discounting India equity is a structural retention risk.
• In-person time — quarterly off-sites; annual all-hands global.

Common mistakes scaling GCCs

1. Cost-arbitrage framing — treating India as where work is sent because it's cheap. Destroys retention.
2. Junior-heavy hiring — senior layer must come first; junior hiring follows.
3. Skipping the India Head appointment too long — global functions can't directly manage 100+ Indian engineers across multiple teams.
4. Tier-2 / cost-only optimisation — chasing tier-2 city savings before establishing brand presence in Bengaluru / Hyderabad / Pune.
5. No physical office for too long — by 100+ headcount, in-person hub becomes valuable.
6. Treating India as 'execution' — Indian teams shipping someone else's spec is the fastest path to attrition.

India-specific strategic considerations

• DPIIT Startup India recognition — if your subsidiary qualifies; unlocks ESOP deferral, 80-IAC tax holiday.
• STP / SEZ — for export-of-services businesses; tax benefits.
• GIFT City — for financial services / IFSC-eligible activities.
• R&D weighted deduction — 150% deduction for in-house R&D expenditure (Section 35).
• Local language / cultural fit for India-customer-facing teams (different talent profile from English-only roles).