How to pick the right Indian city for your GCC: a 9-factor scorecard for Pune, Mumbai, Bangalore and Hyderabad

Site selection is too important for vendor brochures. A weighted scorecard across nine factors, with function-fit mapping that tells a head of GCC which city wins for which work.

TL;DR

There is no universally best Indian city for a GCC. There is a best city for a specific function, headcount, IP profile and parent geography. On a 9-factor weighted scorecard with equal weights, Pune leads at 7.4, Hyderabad at 7.1, Bangalore at 6.9 and Mumbai at 6.6. Change the weights to reflect a BFSI mandate and Mumbai jumps to first. Change them for AI and Bangalore takes the top spot. The scorecard is the tool; the weights are the decision.

We have been asked the same question by site selection committees roughly 60 times in the last 18 months: which Indian city should we put our GCC in? The answer is never a single city, and the answer that comes from a 90 minute boardroom debate is almost always wrong. The right answer comes from a structured scorecard with weights that reflect your specific mandate. This post walks through the scorecard we use, the data behind each factor, and three worked examples.

The nine factors

1. Talent depth in the relevant function
2. Salary cost and inflation trajectory
3. Real estate cost and Grade A availability
4. Attrition and tenure of mid-level staff
5. Infrastructure quality (airport, metro, power, internet, water)
6. Regulatory and policy support for GCCs
7. Ecosystem depth (vendors, peers, leadership pool)
8. Time-zone alignment with parent geography
9. Quality of life and ability to relocate parent staff

Factor 1: Talent depth (scores out of 10)

Bangalore 9.6 (tech, AI, product, deep engineering)
Mumbai 9.2 (BFSI, capital markets, insurance, media)
Pune 8.8 (Accounting, FP&A, engineering, Japanese GCCs)
Hyderabad 8.5 (pharma, semiconductors, product, life sciences)

Factor 2: Salary cost (lower is better, scored inversely)

Hyderabad 8.4 (most cost competitive of the four)
Pune 8.2
Bangalore 6.4 (highest salary cost)
Mumbai 6.8

Factor 3: Real estate (Grade A, INR per sqft per month, fitted)

Hyderabad 8.6 (INR 75 to 95)
Pune 7.8 (INR 95 to 140 depending on submarket)
Bangalore 6.0 (INR 145 to 175 ORR)
Mumbai 4.8 (INR 210 to 280 BKC)

Factor 4: Attrition and retention (lower attrition is better)

Pune 8.4 (16 to 19%)
Mumbai 8.0 (17 to 20%, BFSI 14 to 16%)
Hyderabad 7.4 (19 to 22%)
Bangalore 6.4 (22 to 26%)

Factor 5: Infrastructure quality

Hyderabad 8.6 (ORR, metro, airport, power, water all in the top quartile)
Pune 7.6 (new Purandar airport pending, metro under expansion)
Bangalore 6.8 (airport excellent, intra-city commute famously poor)
Mumbai 7.4 (metro expansion strong, BKC infra excellent, suburban commute weak)

Factor 6: Regulatory and policy support

Maharashtra (Pune and Mumbai) 8.8 (Industrial Policy 2024 to 2029 explicitly targets GCCs)
Telangana (Hyderabad) 9.0 (T-Hub, T-Works, GCC specific incentives, fastest single window)
Karnataka (Bangalore) 7.8 (mature but slower on new GCC incentives)

Factor 7: Ecosystem depth (peer GCCs, vendors, leadership pool)

Bangalore 9.8 (500 plus Fortune 500 GCCs, deepest leadership pool)
Hyderabad 8.4 (200 plus GCCs, fast growing)
Mumbai 8.2 (BFSI ecosystem unmatched)
Pune 8.0 (250 plus GCCs, strong Accounting and Engineering depth)

Factor 8: Time-zone alignment by parent geography

All four cities sit in IST (UTC plus 5:30) so this factor differentiates only at the margin via flight connectivity and overlap with parent business hours. Mumbai wins on long haul connectivity (direct flights to NYC, LON, SIN, DXB, HKG, FRA, more frequencies than the other three combined). Bangalore is second. Pune is improving via Purandar. Hyderabad is solid but thinner on long haul.

Factor 9: Quality of life and parent staff relocation

Pune 8.6 (climate, education, expat community, lowest pollution of the four)
Hyderabad 8.2
Bangalore 7.0 (traffic and pollution drag scores down)
Mumbai 7.4 (cosmopolitan but cost of living for expats is highest)

Equal weighted aggregate scores

Pune 7.4
Hyderabad 7.1
Bangalore 6.9
Mumbai 6.6

Worked example 1: a BFSI middle office GCC for a US bank

Reweight: Talent (25%), Regulator proximity (20%), Ecosystem depth (15%), Attrition (10%), Cost (10%), Others (20%). Mumbai jumps to 8.7, Pune to 7.4, Bangalore to 7.0, Hyderabad to 6.8. Mumbai wins decisively. The right answer for a US bank doing capital markets, treasury and regulatory reporting is Mumbai, full stop.

Worked example 2: an AI platform engineering GCC for a US SaaS company

Reweight: Talent depth (35%), Ecosystem (20%), Leadership pool (15%), Cost (10%), Others (20%). Bangalore jumps to 9.0, Hyderabad to 7.4, Pune to 7.0, Mumbai to 6.8. Bangalore wins. The cost premium is real but the talent depth justifies it.

Worked example 3: an Accounting and FP&A GCC for a Japanese manufacturer

Reweight: Cost (20%), Attrition (15%), Talent (20%), Cultural fit (15%), Others (30%). Pune jumps to 8.6, Hyderabad to 7.3, Mumbai to 6.8, Bangalore to 6.5. Pune wins, with the Japanese industrial corridor cultural fit being decisive.

The dual city pattern that increasingly wins

For mandates above 250 FTEs spanning two function families (e.g. BFSI plus Accounting, or Engineering plus Pharma R&D), the highest scoring solution is usually not a single city but a primary plus a satellite. Mumbai plus Pune for BFSI plus Accounting. Bangalore plus Hyderabad for AI plus Pharma. The 150 km Mumbai-Pune expressway and the 570 km Bangalore-Hyderabad corridor both make this operationally feasible.

What this means for your committee

Stop debating which city wins in the abstract. Build a weighted scorecard sized to your mandate, populate it with data (not vendor pitches), and let the math decide. If you would like our Excel scorecard template with the underlying data sheets, request it via the enquiry form on this page and we will send it within one business day.