The GCC Procurement Cascade: What a New Centre Buys in Its First 24 Months

A new Global Capability Centre is not a hiring plan. It is a procurement cascade: the decision to put a few hundred or a few thousand people in an Indian city sets off 20 to 30 separate buying decisions over the next two years, each with its own buyer, lead time and supplier market. The order of those decisions matters more than any single one of them.

Key Takeaways

• The cascade starts 12 months before opening day. City, incentives, entity and leadership choices are made long before the inauguration.
• Day one has hard dependencies. Laptops, identity, security baselines, payroll and background verification must all work before the first offer letter is honoured.
• Scale changes what you buy. Past roughly 500 people, scarce skills, platforms, SOC coverage and automation become the bottleneck.
• Global mandates bring a second wave. AI governance, process transition and transformation work arrive 12 to 36 months in.
• Buying late costs more. Late purchases are made under time pressure, with fewer options and weaker negotiating positions.

Why the cascade is getting bigger

India now hosts 2,117 GCCs operating 3,728 units, employing about 2.36 million people and generating $98.4B in revenue (Zinnov-Nasscom, FY2026). Arrivals are not slowing: JLL counts 200+ new GCCs entering India in the two years to early 2026, and GCCs took 31.4M sq ft of office space in 2025, 37.7% of all gross leasing.

Each of those leases sits at the front of a long chain of purchases. When DoorDash announced 3,000 jobs over two years at a Hyderabad hub, starting with 500 people in customer experience and trust and safety, it committed to far more than recruitment. It committed to transport for shift workers, background checks at volume, quality tooling, security monitoring and, before long, automation of the work itself.

The seven stages

We use seven stages, timed relative to T0, the day the centre opens.

Window	Stage	What happens	What gets bought
T-12 to T-6 months	India decision made	HQ commits and compares cities, structures and costs	Location intelligence, state incentives, entity and tax, leadership search
T-9 to T-3	Site selected	City and site chosen, lease or flex space signed	Lease or flex office, legal, fit-out, network, facilities
T-6 to T0	First leaders arrive	GCC head, HR, finance and technology leads join	Recruitment, payroll and benefits, background verification, HR tech, identity and SaaS
T-3 to T+6	50 → 500 people	First hiring waves land	Laptops and MDM, SaaS licences, security launch package, cloud landing zone, L&D, transport
T+6 to T+18	500 → 2,000 people	Scarce skills become the bottleneck	Specialised recruitment, automation, data platforms, SOC, DevSecOps
T+12 to T+36	Global mandates arrive	India starts owning products, AI and functions	AI transformation, product engineering, process migration, R&D, governance
Mature	Global owner	The centre runs global functions	Transformation, innovation, startup sourcing, specialist consulting

The windows overlap on purpose. A centre is usually choosing its site while still finalising its entity, and hiring its first engineers while the fit-out finishes.

Stage by stage: what usually goes wrong

Decision (T-12 to T-6). The most expensive mistakes happen here because they are hard to reverse. City choice fixes your talent ceiling and cost base. Incentive eligibility often depends on location, investment thresholds and registration timing, so a centre that picks its city before modelling incentives can leave significant money unclaimed. No invoice can flow from India to HQ until the legal entity exists and the intercompany service agreement and its transfer-pricing basis are signed.

Site (T-9 to T-3). Flex space is the usual first home for a new centre, with a move to a permanent lease typically following within a year or two. The fit-out, AV, network and facilities vendors chosen now will run the workplace for years. Redundant connectivity back to HQ must be ordered early; it is rarely the fastest item on the list.

First leaders (T-6 to T0). Whoever fills the first handful of India leadership roles shapes the culture and hiring bar for years. Before their first offer, payroll, provident fund, group health cover and an India-compliant HR system have to exist. Identity provisioning from the HQ directory should be automated from day one, not bolted on after the first hundred joiners.

Ramp to 500 (T-3 to T+6). This is where the cascade is most visible. Each joiner needs a laptop configured to HQ standards waiting on their first day, which at this pace means hundreds of devices. A security launch package covering zero-trust access, endpoint protection, data-loss prevention and logging must be in place before HQ data reaches India. Engineers need governed cloud accounts, not a ticket queue.

Scale to 2,000 (T+6 to T+18). Generalist hiring keeps working, but AI, cybersecurity, cloud and data roles do not. 58% of GCCs take more than 45 days to fill critical roles (Ceipal and People Matters, 2026). This is when specialist pods, developer platforms, SOC coverage and the first automation programmes appear.

Global mandates (T+12 to T+36). HQ moves products, functions and processes to India. Each move is a transition programme with knowledge-capture risk, and each is an opportunity to automate before moving rather than relocating an inefficient process.

The full category map

Across the cascade we track around 60 individual purchases in these categories:

• Location and setup: location intelligence, government incentives, entity and tax, GCC launch planning
• People: leadership search, volume hiring, scarce-skill hiring, contractor capacity, compensation benchmarks, employer branding, university partnerships, background verification, payroll and benefits, relocation, HR tech
• Workplace: office search, fit-out, facilities, employee transport
• Technology: laptops and MDM, identity and SaaS, office network, cloud landing zones, FinOps, developer platforms, data and ML platforms
• Security and compliance: security launch package, IAM and PAM, SOC or MDR, ISO 27001 and SOC 2 evidence, DPDP Act mapping
• AI and transformation: AI control plane, evaluations, process discovery and PoCs, function-by-function automation, AI upskilling
• Transition and growth: process transition, knowledge capture, vendor insourcing, training academies, startup scouting, IP support

Roughly half of these are high-skill engineering, security and transformation work. The rest are local services such as recruitment, BGV, transport and fit-out, where the challenge is finding, comparing and managing good suppliers in an unfamiliar market.

How to run the cascade instead of reacting to it

1. Map it before the GCC head arrives. Sequence every category against your target opening month and assign an owner, even if that owner is temporarily at HQ.
2. Decide early on what you will build, buy or bridge. Some capabilities belong in the captive from day one. Others, such as scarce-skill pods, are better bridged and transferred.
3. Consolidate the vendor layer. A new centre does not want 25 new vendor relationships while its procurement team is still being hired.
4. Model incentives before choosing the city. Location, investment timing and headcount ramps all affect what you can claim.
5. Make the centre AI-first from the start. Designing automation into the operating model is cheaper than retrofitting it in year three.

Map your own cascade

The GCC lifecycle page shows every purchase by stage, buyer and fulfilment route. To sequence it against your own opening date, sector and headcount, use the free 24-Month GCC Procurement Map. It flags which decisions are already in their window. Our team has set up and scaled GCCs for global enterprises, and a launch-readiness review turns the map into an owner-by-owner plan.