The 7 Most Expensive Mistakes Companies Make When Setting Up a GCC in India

India's established Tier 1 GCC hubs — Bangalore, Hyderabad, Pune, and Chennai — are proven destinations with deep talent pools, mature MNC ecosystems, and well-developed infrastructure. For many companies, particularly those with technology-heavy functions, they are absolutely the right choice. The mistake is not choosing a Tier 1 city. The mistake is choosing any city without a structured, evidence-based analysis.

A location decision made on precedent rather than on your specific function mix, talent requirements, and retention priorities leaves significant value on the table. Talent competition dynamics across India's cities vary materially by function — and what works well for a product engineering centre may point in a very different direction from what works for an operations or finance hub.

Tier 2 cities like Ahmedabad, Coimbatore, Nagpur, and Kochi have become genuinely compelling options for the right function mix — with lower talent competition, growing talent bases, and significant cost advantages. In our experience, GCCs in well-chosen Tier 2 locations consistently run lower attrition than the national average, particularly for operations, finance, and shared services functions. A different company with a different function profile may well find a Tier 1 city is the right answer — and that is exactly the point.

The founding Managing Director or CEO of a GCC is the single most consequential hire in the entire setup process. This person sets the culture, attracts the first tier of leadership, manages the relationship with the parent organisation, makes hundreds of ambiguous calls in the first year, and — perhaps most importantly — pushes back when the parent is asking for the wrong thing.

Companies consistently under-invest in this search. They use a generalist recruiter instead of a GCC specialist. They settle for a strong functional leader who has never run a P&L. They hire someone with deep India experience but no global credibility — or the reverse. And then they spend the next two to three years wondering why the GCC isn't performing.

The founding MD's mistakes compound. Every culture norm they set, every leadership hire they make, every operating rhythm they establish becomes progressively harder to unwind. A weak MD in year one can define a struggling GCC for years.

Every GCC setup produces a detailed org chart. Boxes, lines, reporting relationships, spans of control. What almost no GCC setup produces is a clear governance model — and this omission quietly destroys more GCCs than any other single factor.

Governance vagueness looks like this: the GCC MD doesn't know who in the parent organisation to escalate to when the business pushes back on scope. COE heads get conflicting priorities from five different business unit stakeholders. Performance is measured purely on cost savings, so every value-added initiative gets deprioritised. Nobody is quite sure whether the GCC exists to serve the parent or to build its own strategic identity.

The result is an organisation that drifts. It becomes what the loudest voice in the parent wants it to be that week — which is usually a cheaper vendor, not a strategic capability.

The single most common thing I hear from GCC leaders struggling with attrition is: "It's just the India market — everyone deals with this." This is both factually wrong and strategically dangerous.

The average GCC in India runs 18–22% annual attrition. The best-run GCCs run under 10%. The gap between these numbers is not luck, geography, or compensation levels alone. It is the quality of the talent architecture — the career ladders, the culture design, the manager quality, the EVP, the engagement infrastructure.

High attrition is a design failure, not a market inevitability. When a GCC runs 25% attrition, it is telling you something: that talented professionals don't see a future there, or don't feel valued, or are being managed poorly, or were hired without a real career path in mind. Each of these is fixable — but only if you treat attrition as a signal, not an excuse.

The cost is not just financial, though that alone is sobering — replacing an experienced professional in India typically costs 6–9 months of their salary when you factor in recruitment, onboarding, and the productivity dip. The deeper cost is institutional knowledge destruction. A GCC that churns 20% of its people every year is perpetually restarting.

Boards love a compressed timeline. "Why does this take eighteen months? Can we do it in six?" The pressure to move fast is real, often coming from a new CEO who wants a visible transformation win, or from a CFO who wants the cost savings to hit the current year's numbers.

A GCC launched in six months under pressure will almost always have the same profile: wrong location chosen by default, leadership hire compromised because the search was rushed, governance undefined because there wasn't time to align, and a first cohort of talent hired at scale before the culture was ready to absorb them. Two years later, the company is restructuring.

The realistic timeline is 9–18 months, depending on scope and complexity. The companies that invest that time properly — in location analysis, in leadership search, in governance design, in a thoughtful talent architecture — consistently outperform the ones that cut corners to hit an artificial milestone.

A significant number of multinationals set up a GCC with the mental model of an outsourcing vendor. The GCC exists to deliver outputs at lower cost. It is managed at arm's length. Its people are not really part of the company — they are an offshore team. The culture, the career development, the strategic integration — these are not priorities.

The outcome of this approach is entirely predictable. The GCC performs like a vendor — transactional, disconnected, high attrition, low engagement, resistant to going beyond its defined scope. It delivers cost savings in year one and underperforms on everything else for years afterward.

A GCC is your organisation. Its people should feel — and actually be — part of the same company as their counterparts in Chicago or London or Singapore. They should have access to the same learning platforms, the same career opportunities (globally, not just locally), the same leadership development, the same cultural values. The companies that build GCCs with this mindset get strategic assets. The ones that don't get expensive headcount in another country.

The GCC advisory market in India has grown rapidly — and with it, the number of firms offering GCC setup services who have never actually built or run one. Strategy consultants from Big 4 firms. Generalist HR advisory firms. Location consultants who produce beautiful reports and disappear at implementation. Vendors with a financial interest in steering you toward their platform or real estate relationships.

The difference between a GCC advisor who has been operationally accountable for a GCC and one who hasn't is not subtle. It shows up in the questions they ask, the risks they flag, the specific decisions they push back on, and the network they bring. A location report written by someone who has never worried about retaining talent in that location is a different document from one written by someone who has.

Ask any GCC advisor a simple question: have you personally been accountable for a GCC's performance — not as an external advisor, but as the person whose job depended on it working? The answer will tell you most of what you need to know.