Hub-plus-one: adding a second GCC city
Hub-plus-one means running your main GCC hub plus one or more additional centers, and it is now the default pattern rather than the exception. Adding a second India city lets a company escape the cost and talent-pool ceilings of a saturated hub without doubling its overhead, because the entity, playbook, and governance from the first center carry over while the hiring engine has to be built fresh. The move rewards a first center that is already running well and punishes one that is used to paper over problems.
What hub-plus-one means
Hub-plus-one is the strategy of anchoring on one primary GCC location and adding a second (and eventually third) center rather than concentrating all capability in a single city. The "hub" is your established center; the "plus-one" is a deliberate second site chosen to add talent, reduce risk, or lower cost, not a random expansion.
This is no longer a contrarian idea. Industry analyses identify "hub-plus-one" and multi-hub networks as the defining 2026 GCC pattern, with Tier-2 expansion a core trend (Business of GCC, 2026). The shift matters because it reframes what a second city signals: a few years ago, operating outside a single mega-hub read as a compromise, and now the companies building well are the ones spreading deliberately across locations. The scale underneath makes it viable, since there is real depth beyond the top metros: India hosts 2,100+ GCCs, including 583 mid-market centers (Zinnov-Nasscom GCC Landscape FY2026). A market that size supports serious second-city talent pools, which is precisely what hub-plus-one depends on.
Why companies add a second GCC city
Companies add a second GCC city for three recurring reasons: to break through a talent-pool ceiling, to relieve the cost and attrition pressure of a saturated hub, and to reduce concentration risk. Usually more than one of these is in play at once, which is what tips a single-hub company into a multi-hub one.
The talent-pool ceiling is the most common trigger. A first center in a saturated metro eventually competes for the same finite pool as everyone else, and each incremental hire gets slower and more expensive as the local market tightens. A second city in a less saturated market opens a fresh pool for the roles the first hub struggles to fill. Cost and attrition pressure is the second reason, and it compounds: saturated hubs carry the highest salaries and the sharpest churn, so shifting some growth to a lower-cost, calmer-retention city improves the blended economics of the whole operation. The third reason is concentration risk, the operational and continuity exposure of having all capability, and all institutional knowledge, in one place. Spreading across two cities is a hedge against that single point of failure. When a company feels two or three of these pressures together, adding a city stops being optional and becomes the obvious next move.
How to choose the second city
Choosing the second city is the same disciplined evaluation you would run for any GCC location, applied with your first center's gaps in mind: score candidates against your specific plan rather than default to a ranking. The criteria that decide it are talent depth for your stack, attrition, cost, connectivity, ecosystem, and incentives.
Rather than repeat the framework here, it is the same six-point check we lay out in detail in the honest case for Ahmedabad and GIFT City, where the checklist is written to be run against any city in an afternoon. The one adjustment for a second city is that you are not scoring in a vacuum: you are scoring for what the first hub cannot give you. If the first center already covers mainstream engineering well but strains on a particular function, the second city should be scored hardest on its depth for that function. If cost is the pressure, weight cost and retention. The evaluation is the same; the weighting follows the gap you are trying to close, which is why a generic "best cities" list is a poor substitute for scoring candidates against your own plan.
What transfers from the first center, and what does not
The single biggest reason a second center is faster to stand up than the first is that a lot transfers, but the thing that most determines success, the hiring engine, does not. Knowing which is which is what keeps a second-city plan realistic.
What transfers is substantial: the legal and compliance groundwork is often extendable rather than rebuilt from zero, the operating model and governance are already designed, and the playbook for how the center integrates with the parent exists and has been debugged once already. That is genuine leverage, and it is why the second setup should be quicker and less risky than the first. What does not transfer is the hiring engine and the local knowledge behind it. Recruiting in a new city means new sourcing channels, a new understanding of the local market's salary bands and competition, and a fresh ramp before new hires are productive, none of which you can copy from the first location. Culture is the other thing that has to be built rather than shipped: a second center needs its own identity and local leadership, not a remote outpost run entirely from the first hub. Companies that assume the hiring engine transfers are the ones whose second-city timelines slip, because they under-resource the one part that genuinely starts over.
Satellite versus a full second center
The honest threshold between a satellite and a full second center is ownership: a satellite extends the first hub's work under the first hub's management, while a full second center owns distinct capability with its own leadership. Choosing between them is about how much the second location will own, not how many people it will have on day one.
A satellite makes sense when the need is capacity rather than a new capability, when you want a modest presence in a new market, perhaps to test its talent, without yet committing to local leadership and full governance. It is lower-commitment and quicker, at the cost of never becoming truly self-sufficient. A full second center makes sense when the second city will own a distinct product, function, or platform end to end, which is where hub-plus-one delivers the most, because coherent ownership keeps decision-making local and accountability clear. The trap is a large satellite: enough headcount to need real governance, but structured as an outpost without local leadership, which combines the cost of a center with the fragility of a satellite. If the second location is going to be substantial, commit to it as a real center with its own leadership rather than letting it grow into an ungoverned one.
When not to add a second city
The honest counterpart to all of this is that some companies should not add a second city yet, and recognising that is as valuable as knowing when to expand. Two situations argue strongly against it: a first center that is not yet solid, and a management team without the bandwidth to run two.
If the first center is sub-scale, still churning, or under-governed, a second city will not fix it; it will duplicate the problem in a new location and stretch already-thin oversight further. The first hub earns the right to a second by running well, and a shaky first center is a reason to fix that center, not to open another. The second constraint is management bandwidth. Running two centers is more than twice the coordination of running one, because it adds cross-site alignment on top of each site's own management, and a team already at its limit governing one center will govern two badly. Adding a city to escape a genuine talent ceiling, from a stable base, with the bandwidth to lead both, is the strategy working as intended. Adding one to escape a problem the first center has not solved is how a single struggling site becomes two. For the strategic and cost sides of getting this right, our playbook for GCCs in PE portfolio companies and the Ahmedabad GCC cost breakdown go deeper, our global capability center work is built around standing centers up cleanly, and a scoping conversation is the fastest way to test whether a second city is the right next move for you.
