The Indian GCC story: what 2,000 capability centres mean for SaaS founders

India crossed 2,000 Global Capability Centres in 2025. The Nasscom-Zinnov annual tracker puts the number at 2,100-plus as of early 2026, employing roughly two million people. For context: in 2015, there were around 900 such centres. The doubling happened in a decade, with the last 500-odd centres arriving in the past three years.

Most of the coverage focuses on what this means for the GCCs themselves, or for global companies setting up shop in India. Almost none of it addresses what it means for Indian SaaS founders. That gap is what this piece covers.

What 2,000 GCCs actually look like on the ground

The geography is concentrated but not uniform. Bengaluru accounts for roughly 35% of all GCC headcount; Hyderabad and Pune follow at 18-20% each. Chennai has grown significantly, particularly in engineering and manufacturing-adjacent centres. NCR holds roughly 15%, dominated by fintech and banking operations.

The more important shift is in the nature of the work. Early GCCs ran support, QA, and maintenance. The 2026 vintage runs core product engineering, ML infrastructure, and architecture decisions. Nasscom's data shows 45% of GCC work now falls into 'expertise' or 'frontier' functions. That number matters. You are no longer competing with a back-office operation. You are competing with teams doing interesting problems, reporting to global engineering leadership, and in many cases influencing product direction from Bengaluru.

The wave of new entrants also includes mid-market US and European SaaS companies setting up their first offshore engineering team of 20-100 people. These centres don't have the parent-company brand recognition of a JPMorgan or Microsoft India, but they pay similarly and offer smaller, faster-moving teams. For Indian engineers weighing options, that's a credible pitch.

The engineering talent market has split in two

The Indian engineering talent market in 2026 is not one market. It's two, and they've been diverging for the past 18 months.

The first: engineers with 0-4 years of experience. Supply genuinely outpaced demand following the 2023-24 global tech cycle. Salaries have held but not run away. GCCs and Indian SaaS companies compete in this band without either side having a structural advantage.

The second: engineers with 5-10 years of experience, specifically those with distributed systems, ML infrastructure, or cloud architecture depth. This segment is structurally short. Every well-funded entity in India draws from the same pool: GCCs, Big Tech Indian offices, unicorns, and Series B-plus SaaS companies. The supply constraint shows no sign of easing before 2028 at the earliest, given the lag between curriculum change and production-ready experience.

A staff engineer at a Bengaluru GCC backed by a US-listed company can earn Rs 45-65 lakh in base, receive RSUs valued at Rs 20-40 lakh per year vesting over four years, and carry a bonus target of 20-30% of base. The all-in package is competitive with San Francisco in purchasing-power terms, without the visa uncertainty.

Indian SaaS companies at Series A and B rarely have a matching answer for the RSU component. The equity pitch requires explaining cap table structure, growth trajectory, and why the exit multiple assumptions are defensible. GCC offers don't require that explanation. The RSU is in a publicly listed company the engineer already recognises. That asymmetry is real.

The compensation gap is real, but it is not about base salary

The standard founder response is 'we offer equity upside, career ownership, and faster growth.' That pitch is not wrong. It has a narrower addressable population than founders typically assume.

NASSCOM's 2025 GCC India Report has a finding worth repeating: when senior engineers leave GCCs, 42% cite limited career progression as their primary reason, 28% cite insufficient ownership over product outcomes, and 19% cite base salary gaps. More than twice as many leave for growth reasons as for money reasons.

That 42% is the population Indian SaaS companies can recruit effectively. They're engineers who've had the stability experience and now want the ownership experience. The pitch that works is not 'we pay more' but 'you will own a real surface and make the architecture calls, within 12 months.' The founders who say that specifically, with names and timelines, convert. The ones who say it abstractly don't.

GCCs are also getting better at career pathing. The era of 'join a GCC and peak at senior engineer' is ending. Centres in the 2023-26 wave are building explicit tracks to architect and principal roles with genuine global product input. That narrows the ownership pitch without eliminating it. 'Owning a surface' at a GCC still means owning within a perimeter defined by a team in Seattle or Amsterdam.

Why GCCs are your most qualified untapped customer segment

Here is the part most Indian SaaS founders miss entirely.

Two thousand GCCs employ two million people. Each centre has a procurement budget, an IT function, an HR team, and Indian compliance obligations. They are not all running their parent company's global enterprise stack. Many have discretionary local budgets and are buying software the parent's IT catalogue doesn't cover.

A mid-size GCC at 800-1,200 headcount looks a lot like a Series B Indian startup in terms of software spend per employee. They need document workflows, HR onboarding tools, signing infrastructure for India-local contracts, and invoicing that handles GST correctly. The procurement cycle is slower than a startup's, but the contract value is typically four to eight times larger.

The specific opening: GCCs operating in India are required to comply with Indian law. DPDP data residency expectations, IT Act-compliant electronic signatures for India-local contracts, GST-format invoicing, and Aadhaar-based workflows where applicable. Every global enterprise SaaS vendor sold to the parent company handles these requirements as edge cases at best. The gap is structural, not a product gap any large vendor is racing to close.

The practical wedge is the Indian IT or operations lead who has a local compliance problem they cannot solve with the parent's approved tool. This person has real pain, some budget discretion, and a mandate to make it work locally. They are a warm inbound lead sitting inside a company your sales team has never thought to call.

What this means for how you hire in 2026

Three adjustments have proven consistently useful watching this market develop:

Stop competing on total compensation in the 5-10 year experience band. You'll lose 54% of the time by design. The engineer who is deciding purely on total comp will go to the GCC. Write job descriptions that filter in the candidate who wants ownership and filter out the ones who'll accept the next GCC offer that arrives.

Invest more deliberately in the 2-5 year segment. GCCs are structurally slower to promote than well-run startups. A three-year engineer running a real feature surface at a startup is genuinely rare inside most GCC teams. You can offer that. Be specific: not 'you'll grow fast' but 'within six months you'll own the payments surface and make the call on schema design.'

Make the equity story numerical. Most GCC offers don't come with upside projections. Most startup equity conversations are vague gestures. Give the candidate a spreadsheet: current valuation, ARR target, realistic exit multiple range, what their specific grant is worth at each outcome. It takes 10 minutes per conversation. Almost no one does it.

What this means for how you sell in 2026

GCCs are not easy to sell to. Procurement is slower, legal is more involved, and decisions often cross between the India entity and the parent. But the ACV is large enough to justify the longer cycle, and the Indian compliance angle is a genuine wedge that the parent's preferred vendor cannot close quickly.

Three things that work in practice:

Find the Indian IT or engineering lead with a local compliance problem. This person is often not the budget owner but can pull you into a conversation procurement alone wouldn't initiate. The problem is typically: 'Our global tool doesn't handle GST correctly' or 'We need IT Act-compliant document signing for India-local employment contracts.' That's your entry point.

Invoice in INR from an Indian entity with proper GST. GCCs buying locally expect Indian invoices in Indian currency. If your billing setup isn't built for this, the deal stalls at the finance team even after the IT team says yes. Sort the invoicing setup before the sales cycle, not during it.

Run the expected-value calculation before deciding whether to pursue a GCC deal. A typical GCC deal takes 8-12 weeks versus 2-4 for a startup deal. The ACV is usually four to eight times larger. At a close rate of 20-25%, the expected value per sales hour is comparable to your startup pipeline. Founders ignoring GCCs as a segment are leaving that math uncalculated.

The headline number is 2,000 GCCs. The number that matters to an Indian SaaS founder is the count of mid-size centres in your city with Indian compliance gaps your product already solves. In Bengaluru alone, that list runs into the hundreds. It is not a headcount problem. It is a prospecting list.