In 2004, when Goldman Sachs chose Bengaluru for its first India center, the decision was not made because of Goldman Sachs. It was made because of Bengaluru.
The city had been accumulating something for twenty years. It started with ISRO and HAL and the public sector defense and aerospace organizations that the Nehru government had planted there in the 1950s and 1960s. It continued with the software services companies that arrived in the 1980s, drawn by the engineering talent that those public institutions had been quietly producing. By the time Texas Instruments opened its India research center there in 1985, Bengaluru had already developed a specific character: it was a city that could absorb complex technical work, that had the educational infrastructure to produce engineers at scale, and that had accumulated enough institutional memory to make difficult problems tractable.
Goldman was in essence choosing a city that had, over decades, built the conditions under which consequential financial technology work could get done. That distinction — between choosing cheap and choosing capable — is the central argument for why cities deserve to be studied as seriously as the organizations that occupy them.
The Invisible Infrastructure
Every GCC that succeeds in India succeeds partly because of something the parent company did, and partly because of something the city did long before the parent company arrived.
This is obvious in retrospect but tends to be overlooked in the analysis of GCC success stories. When a company announces that its India center has grown from 500 to 5,000 people in eight years, and is now leading the global development of a core product platform, the story is usually told as a story about that company's strategic vision. And it partly is. But it is also a story about the city's talent pipeline, about the quality of the engineering institutions that trained the people in that center, about the density of other technology organizations in the same city that created the informal knowledge networks and cross-pollination that make ideas travel faster, about the stability of the local labor market, about the quality of the physical infrastructure that allowed the center to grow without constant operational friction.
Most of those achievements are attributable to the city in question. And understanding them requires studying the city as an institution in its own right.
Consider what it actually means for Bengaluru to be the world's second-largest hub for AI talent (as Zinnov's 2025 analysis describes it). That fact did not emerge from any single corporate decision. It emerged from the Indian Institute of Science, from decades of IIT graduates choosing to stay in or return to Bengaluru, from the startup ecosystem that created a demand for machine learning skills earlier and more intensely than other Indian cities, from the presence of Google and Microsoft and Amazon research operations that trained the first generation of Indian AI researchers, and from a culture of technical ambition that is genuinely specific to that city. Bengaluru commands roughly 40 percent of India's engineering research and development talent. One in three new GCCs that opened in FY2024-25 chose it. These are structural facts about a city and not consequences of any individual corporate strategy.
Or consider Hyderabad. The city's rise as a GCC destination is recent enough that it is easy to attribute it to policy: the Telangana government's T-AIM initiative, the AI City development, the TS-iPASS single-window system for corporate approvals. Policy matters, but it does not explain everything. What policy cannot manufacture is the specific quality of Hyderabad's talent market: its structural stability. Attrition in Hyderabad is consistently lower than in Bengaluru; meaning that teams built there tend to stay together longer, accumulate institutional memory more reliably, and develop the kind of organizational depth that makes complex, long-cycle work possible. This is a cultural and demographic fact about Hyderabad, rooted in its history as a city with a strong public-sector employment culture and a different relationship to mobility than the more intensely competitive Bengaluru market. Organizations that place long-duration, high-trust mandates in Hyderabad are implicitly relying on this fact, whether or not they have explicitly studied it.
What a City Decides
There is a useful thought experiment for understanding why cities matter. Imagine two GCCs with identical parent companies, identical mandates, identical budgets, and identical hiring timelines, one based in Bengaluru and one based in Pune. Will they develop identically?
They will not. And the differences will not be random. They will be systematic, predictable, and traceable to the specific character of each city.
The Bengaluru center will likely build faster. The talent is denser, the networks are richer, the startup ecosystem creates a constant flow of experienced engineers who have already done difficult things. But the center will also face more competition for that talent, higher attrition rates, and a more intense pressure to keep compensation competitive. The culture will tend toward the ambitious and the mobile: people who came to Bengaluru specifically because it is where the most interesting work happens, and who will leave if they stop believing that premise.
The Pune center will likely build more slowly but more stably. Pune has grown from 210 GCCs in 2019 to over 360 in 2025, according to industry data, and its attrition rate runs around 14 percent — meaningfully lower than Bengaluru's. The engineering talent is strong, particularly in embedded systems, automotive technology, and enterprise software. The culture tends toward the reliable and the tenured: people who chose Pune partly because it is a city that allows you to build a life (and not just a career). The center will develop a different kind of institutional character.
The verdict: Neither is superior. They are different instruments suited to different purposes. A company building a research-intensive AI operation probably wants Bengaluru's talent density, even at the cost of higher attrition. A company building a long-duration engineering program for an industrial product probably wants Pune's stability, even at the cost of slower initial build.
The point is that the city is a variable in the equation that is at least as important as the organizational variables. Charter, culture, compensation, leadership quality; all of these matter. But so does the city. Treating it as a background condition rather than an active factor is a significant analytical error.
The Six Tier-I Cities and What They Each Decide
India's GCC ecosystem is concentrated in six metropolitan areas: Bengaluru, Hyderabad, Pune, Mumbai, Chennai, and the Delhi NCR corridor. Each has developed a distinct character.
Bengaluru, with over 880 centers, remains the nucleus. It is home to one in three new GCCs added in FY2024-25 and commands the country's deepest concentration of engineering research and development talent. It is the city where India's GCC story began and where it is most densely layered. Its startup ecosystem (over 3,200 tech startups, the highest concentration of unicorns in India) creates a constant circulation of talent and ideas that no other Indian city matches. It is also the most expensive, the most competitive, and the hardest to retain talent in. Organizations that choose Bengaluru are making a deliberate trade: intensity for stability, innovation density for continuity.
Hyderabad, with over 355 centers, has built its GCC identity around a specific combination of policy reliability and talent stability. The Telangana government has been unusually focused and consistent in its GCC strategy: the T-AIM initiative, the AI City development, the quick turnaround on corporate approvals. The result is a city that global enterprises increasingly treat as a strategic constant. A place where long-cycle programs can take root and compound. Its particular strengths are in BFSI, cloud infrastructure, and cybersecurity. When organizations describe their Hyderabad operations as 'where the work runs,' they are referencing this city's specific talent character: lower attrition, deeper institutional memory, an ecosystem that rewards sustained engagement over rapid switching.
Pune is the fastest-growing GCC city in India, and its growth trajectory reflects a specific opportunity: organizations that want the engineering quality of Maharashtra without the cost and complexity of Mumbai, and the stability of a mid-sized city without the talent constraints of Tier 2 markets. Its proximity to manufacturing clusters has given it particular strength in automotive technology, embedded systems, and Industry 4.0 applications. Companies like Eaton, Mercedes-Benz Tech, and BMW have established engineering centers there precisely because of this manufacturing adjacency. The JLL India GCC Guide notes that Pune combines strong engineering talent with lower operating costs and high stability; a combination that suits organizations building for the long term.
Mumbai is India's financial and corporate capital, and its GCC character is shaped by that identity. The BFSI centers in Mumbai operate under a different set of constraints than technology-first centers elsewhere: tighter regulatory exposure, more complex compliance requirements, closer integration with the Indian financial ecosystem. Its global connectivity is unmatched. The density of international flights and the presence of major global financial institutions create a different kind of network effect. But Mumbai operates at a premium, and organizations that set up there have generally decided that the financial services context is worth that premium.
Chennai maintains a distinct profile anchored in engineering tradition and manufacturing proximity. Tamil Nadu's Semiconductor and Advanced Electronics Policy 2024-25 is the most recent evidence of a state that has consistently invested in industrial and engineering capability. Chennai's GCC character is shaped by this: its particular strengths are in engineering, healthcare, and the kind of manufacturing-adjacent technology work that requires deep domain knowledge. The Tamil Nadu Startup and Innovation Policy 2023 has added a startup layer to what was previously a primarily large-company ecosystem.
The Delhi NCR corridor (Gurugram, Noida, and parts of the capital itself) covers a different type of GCC than the tech-first metros. Its strengths are in business process, professional services, consulting, and the enterprise technology work that sits adjacent to large corporate buyers. The density of Indian corporate headquarters in the NCR corridor creates a different kind of demand for GCC talent: less focused on product engineering, more focused on the intersection of technology and business function. Organizations building GCCs in NCR are often making a deliberate choice to be close to large Indian enterprise clients and to the professional services ecosystem.
The Tier 2 Question
The most interesting city question in India's GCC ecosystem right now is not about the Tier 1 cities. They are understood, albeit, if imperfectly sometimes. The interesting question is about what happens next.
According to Nasscom-Zinnov projections, India's GCC workforce in Tier 2 and Tier 3 cities could reach 39 percent of the total by 2030. That is a remarkable shift from the current concentration. The Gujarat GCC Policy 2025-2030 is allocating Rs 10,000 crore to attract GCCs to Ahmedabad and other Gujarat cities. Maharashtra's GCC policy is specifically pushing expansion toward Nashik, Nagpur, and other secondary cities. Karnataka's "Beyond Bengaluru" initiative is promoting Huballi-Dharwad, Mysuru, Mangaluru, and Shivamogga.
The thesis behind all of these initiatives is that Tier 2 cities offer three advantages over saturated metros: cost efficiency running 25-30 percent lower than Tier 1 for comparable talent; lower attrition driven by fewer competing employers; and a talent pool that is currently underutilized because not enough demand has found it. For organizations willing to accept the infrastructure limitations and the slower initial build, the returns on Tier 2 investment can be genuinely attractive.
But the Tier 2 story is not uniform. Ahmedabad's GIFT City is a specific regulatory environment designed for financial services; it attracts a particular kind of GCC for particular reasons, and its success will not necessarily generalize to other domains. Coimbatore has genuine depth in manufacturing and engineering talent, but relatively thin infrastructure for the kind of large-scale product engineering that dominates the Bengaluru conversation. Bhubaneswar and Thiruvananthapuram have state-level support and early momentum, but they are building GCC ecosystems from a much lower base.
Second HQ's cities section will document all of this as a sustained effort to understand each city on its own terms — its history, its talent character, its infrastructure strengths and limitations, its cultural relationship to the kind of work that GCCs do.
Why Cities Get Their Own Section
The decision to give cities their own dedicated section in Second HQ is a substantive editorial claim.
The claim is this: you cannot understand a GCC without understanding the city it operates in, and you cannot understand a city's GCC ecosystem without understanding the specific organizations that have chosen it. The two objects of study are mutually constitutive. The Bengaluru GCC ecosystem is what it is partly because of the decisions that Goldman, Microsoft, Google, and hundreds of other organizations have made about how to build in that city. And the decisions those organizations made were shaped by what Bengaluru already was.
This is why the cities section will be updated in parallel with the company profiles. When a significant new GCC opens in Hyderabad, the Hyderabad city profile will be revised to reflect what that opening reveals about the city's trajectory. When Pune's attrition dynamics shift because of macroeconomic conditions, that will show up in the Pune profile before it shows up in any individual company profile.
The Zinnov Tier-I City Analysis Report 2025 describes the six major GCC cities as having evolved into 'a connected network of specialized ecosystems that together anchor India's global capability story.' That framing is exactly right. The cities are nodes in a system, and the system's behavior depends on how they relate to each other as much as on what any individual city does on its own.
Understanding that system — its logic, its tensions, its trajectory — is one of the core ambitions of this project. The companies are the foreground. The cities are the ground on which the foreground stands. Both deserve careful attention.
The Long View
In 1985, when Texas Instruments opened its R&D center in Bengaluru, the Indian software industry barely existed. The decision was made on the basis of a bet about talent: that a city with IISc, with decades of technical institution building, with a specific culture of engineering ambition, would eventually produce the kind of people who could do serious work. The bet was right. But the payoff came slowly, over decades, and it came in a form that Texas Instruments probably did not precisely anticipate: it came as an entire ecosystem, a city that became legible to global enterprise as a place where consequential work could happen.
That transformation was a function of decisions made by hundreds of organizations over thirty years, and it was also a function of the city's own accumulated character — the institutions it built, the culture it developed, the identity it formed.
The Tier 2 cities that are beginning their GCC journeys now are at the start of a similar arc. What Coimbatore becomes as a GCC city in 2035, or Bhubaneswar in 2040, will be determined partly by the organizations that choose them and partly by what those cities are building into themselves right now: the colleges they are investing in, the infrastructure they are constructing, the relationships they are forming with global enterprise, the culture they are cultivating around technical work.
That is why cities need their own ledger. The company profiles tell you about the present. The city profiles tell you about the conditions that make the future possible.
This is the third article in a three-part canon. The first explains why Second HQ exists. The second explains the logic behind documenting India's GCCs in structured batches all the way to 2,100.