Why India GCCs Stall After Launch, and How to Scale Beyond Delivery
Launching a Global Capability Centre is a visible milestone. Scaling it is quieter and harder. Many centres reach a few hundred people, deliver steadily, and then stop growing in influence. They remain a place where work is done, not where decisions are made.
The Nasscom-Zinnov 2026 report suggests this gap is now the central issue. This article explains the maturity stages, why centres stall, and how leaders can diagnose and move a plateaued GCC.
What the maturity data says
Zinnov's GCC Maturity Framework, used in the Nasscom-Zinnov 2026 report, describes four stages: Outpost, Satellite, Portfolio Hub and Transformation Hub. The report finds that nearly 50% of India's GCCs now operate at a high maturity stage, and that nearly 75% have the potential to become Portfolio or Transformation Hubs over the next five years. Nasscom's president described GCCs increasingly taking ownership of global products, platforms and business outcomes.
Two points follow. Potential is not progress: "could evolve" depends on choices the parent and the centre make. And maturity is defined by ownership and decision authority, not headcount. A 3,000-person centre running tickets can be less mature than a 300-person team that owns a product line.
Why GCCs stall
The following causes are analysis based on common patterns in the sector, not findings from the report. Test each against your own situation.
Decision rights stay at headquarters
If the centre can only execute decisions made elsewhere, talented leaders leave and scope stops growing. Explicit decision rights over architecture, prioritisation within a product area and hiring are a prerequisite for ownership.
The centre is measured on activity, not outcomes
Headcount, utilisation and ticket closure are easy to count. They do not show whether the centre improves a product, reduces incidents or shortens lead time. Without outcome measures, headquarters has little reason to extend more responsibility.
Engineering practices vary and are rarely measured
Delivery predictability, release frequency, change failure rate and recovery time are widely used engineering indicators. Centres that do not track them cannot show improvement or find bottlenecks.
Leadership depth is thin
Scaling needs architects, engineering managers and product-aware leaders. When these roles are filled late or by people with no authority, every decision escalates abroad.
Knowledge stays in people's heads
Where runbooks, design records and onboarding are weak, attrition becomes a recurring crisis and managers spend their time re-explaining context.
Security and platform reliability are treated as someone else's problem
Higher-value work carries higher risk. Headquarters will hesitate to hand over critical systems to a centre whose security posture and reliability record it cannot see.
A short diagnostic for leaders
Answer these honestly for your own centre:
- Can the centre name three outcomes it owns end to end?
- Who decides architecture and priorities, and where do they sit?
- Which engineering metrics are tracked, and who reviews them?
- How many senior technical leaders were hired or promoted locally in the last 12 months?
- If a key engineer left tomorrow, what knowledge would be lost?
- Does headquarters trust the centre with its most important work? If not, why?
Multiple weak answers point to an operating-model problem, not a hiring problem.
A practical path from delivery to ownership
Step 1: Assess
Review mandate, structure, delivery data, technical governance and relationships with global teams. An independent view often surfaces issues that internal teams find awkward to raise.
Step 2: Pick one area to own
Choose a product, platform or capability where the centre already has depth. Transfer genuine decision rights and accountable outcomes for it.
Step 3: Fix the foundations
Standardise engineering practices, introduce a small set of delivery and reliability metrics, and improve knowledge management.
Step 4: Build leadership bench
Define technical career paths and fill architect and product-engineering roles.
Step 5: Prove it, then extend
Show results in the first area, and use them to negotiate the next.
An illustrative scenario (hypothetical)
Consider a centre of 400 engineers that maintains a legacy platform under tickets raised by headquarters. Leadership agrees that the centre will own the platform's roadmap, reliability and cost, tracked through four metrics. Within a year, headquarters has a basis to move adjacent components. This scenario is illustrative, not a client case.
Where advisory support helps
For organisations with an existing Indian GCC, Lakhlani International helps assess technology and engineering maturity, identify operational bottlenecks, improve alignment with global product and business teams, strengthen technical governance and plan a roadmap for higher-value capabilities.
Technology, Product Development & GCC Setup and Scaling
Maturity assessment, operating-model design, technical governance and a roadmap to higher-value capabilities.
Explore the capabilityGCC setup in India: a leadership guide
For organisations still deciding whether and how to build: the mandate, the five decisions and the sequencing.
Read the foundational guideCaptive, BOT or outsourcing
How the operating model you choose shapes how much ownership a centre can take on.
Compare the modelsContact Lakhlani International
To discuss a plateaued centre, start with a conversation.
Go to contactFrequently asked questions
What are the stages of GCC maturity?
In the Zinnov framework used in the Nasscom-Zinnov 2026 report, the stages are Outpost, Satellite, Portfolio Hub and Transformation Hub, reflecting increasing ownership and strategic influence.
How do I know if my GCC has stalled?
Warning signs include decisions made only at headquarters, no end-to-end ownership of outcomes, flat scope despite growing headcount, and senior attrition. The diagnostic above can help structure the review.
Is headcount a good measure of GCC success?
Not on its own. Headcount shows size, not value. Outcomes owned, delivery performance, reliability and quality are better indicators of maturity.
How long does it take to move up a maturity stage?
There is no verified universal timeline. Progress depends on leadership, mandate changes and results in the first owned area.
Who should own the scaling roadmap, the GCC or headquarters?
Both. Headquarters must grant decision rights and accountability; the centre must demonstrate delivery and governance. A joint roadmap with agreed metrics avoids mismatched expectations.
When should we bring in an external adviser?
When internal views conflict, when progress has plateaued, or when you need an independent assessment of engineering maturity and governance before committing to more scope.
References
- →Nasscom-Zinnov, GCC Landscape in India 2026. https://media.zinnov.com/wp-content/uploads/2026/05/zinnov-nasscom-india-gcc-landscape-2026-report.pdf
- →Zinnov, GCC Landscape 2026 and maturity framework. https://zinnov.com/centers-of-excellence/zinnov-nasscom-india-gcc-landscape-2026-report/
- →CXOToday, report launch coverage (May 2026). https://cxotoday.com/others/from-delivery-engines-to-ai-nerve-centers-indias-gccs-take-the-global-lead/