Decision intelligence · India GCC
How Should a GCC Evolve After Launch?
Most capability centers reach a plateau somewhere in year three: the initial scope is delivered, the savings are booked, and nobody has decided what the center becomes next.
Scaling is a mandate decision before it is a hiring decision. Centers that grow headcount without expanding mandate become expensive execution units.
Decision intelligenceWritten by NirjiX GCC AdvisoryReviewed by Ramesh Rathi, Vice President — GCC Enablement & ImplementationPublished January 2026Last reviewed February 20269 min read
Direct answer
How should a GCC evolve after launch?
Move from execution to ownership, then from ownership to capability leadership. That requires three deliberate changes: expanding the mandate to include design and improvement rather than only delivery, building leadership depth so the center is not dependent on its founding head, and changing governance from transition oversight to business-unit governance. Centers that scale headcount without expanding mandate plateau — they become larger execution units, are benchmarked against vendors on cost, and lose the senior people who joined to build something.
The year-three plateau
The first phase of a capability center has clear objectives: stand it up, transfer the agreed scope, stabilize service, deliver the savings in the case. Those objectives are finite, and centers usually meet them.
What follows is frequently undecided. The transition programme closes, the sponsoring executive's attention moves on, and the center continues delivering the same scope competently. Growth becomes incremental headcount against existing work rather than expansion into new value, and the most capable people — who joined to build a capability — begin to leave.
The failure is not operational. It is the absence of a decision about what the center is for once the founding mandate has been discharged, and that decision has to be made deliberately by the group rather than proposed upward by the center.
Maturity stages and what has to change
Each stage requires a different mandate, a different leadership profile and a different governance posture.
| Stage | What the center does | What has to change to progress |
|---|---|---|
| Execution | Performs transferred work to agreed standards, escalating exceptions. | Grant ownership of exceptions and outcome measures, not only throughput. |
| Ownership | Owns processes end to end, including quality and improvement. | Give design authority and a budget for improvement the center controls. |
| Capability leadership | Sets standards, leads global initiatives, builds capability other locations adopt. | Place globally accountable roles in the center, not only locally accountable ones. |
| Strategic node | Hosts business-critical capability the group depends on, with global leadership resident. | Board-level recognition of the center in operating model and succession planning. |
Signals a center is plateauing
- Growth is entirely incremental headcount on existing scope.
- No globally accountable role sits in the center.
- Senior hires are difficult because the roles have no design authority.
- The center is periodically benchmarked against outsourcing providers on unit cost.
- Improvement ideas are raised and never funded, because the center has no improvement budget.
- The founding leader is the only person the group's executives know by name.
These appear before the attrition data does, and they are visible to anyone looking.
How to scale deliberately
Make these decisions before the plateau rather than in response to attrition.
- 01
Decide the next mandate explicitly
Agree what the center will own in two years and communicate it. An unstated mandate defaults to the current one, and the ambitious people leave to find a stated one elsewhere.
- 02
Place globally accountable roles in the center
Nothing changes perception, or retention, faster than a genuinely global role reporting from the center. It also tests whether the group means what it says about the center's status.
- 03
Build leadership depth below the top
Develop successors and a second leadership layer. Dependence on a founding leader is a concentration risk that materializes at the worst possible time.
- 04
Change governance to match maturity
Retire transition-era oversight forums. Governing a mature center with the machinery designed for its first eighteen months signals that nothing has changed.
- 05
Fund improvement, not only delivery
Give the center a budget it controls for process and automation improvement. Without one, ownership is nominal and improvement stays an aspiration.
NirjiX view
The NirjiX view
The strongest predictor of a center's trajectory is whether globally accountable roles sit in it. Everything else — mandate language, governance forums, town-hall messaging — is interpreted locally through that single fact, and it is interpreted accurately.
We also advise groups to plan the second mandate before the first is complete. Deciding what the center becomes while the transition programme is still running is far easier than reconstituting momentum after eighteen months of competent, unremarkable delivery.
Frequently asked executive questions
- When should a GCC's mandate be expanded?
- While the first mandate is still being delivered well, not after it has been fully discharged. Expansion negotiated from a position of demonstrated competence succeeds; expansion proposed after a plateau has set in reads as the center seeking work rather than the group placing it.
- How do we keep senior talent in a capability center?
- Give them scope worth staying for: design authority, globally accountable roles and a visible progression path. Compensation matters, but senior people in this market leave centers because the work stopped growing, not primarily because of pay.
- Should a GCC take on work from multiple business units?
- Yes, once it can absorb it without diluting ownership. Multi-business scope is a strong maturity signal, but it requires clear demand governance — otherwise the center becomes a shared queue with several masters and no coherent mandate.
- How should governance change as the center matures?
- From transition oversight to business-unit governance: fewer forums, outcome measures, and delegated authority proportionate to demonstrated capability. Retaining launch-era governance into year four actively signals distrust and is read that way by the leadership team.
- What would justify keeping a center at execution stage?
- A narrow, highly regulated scope where design authority genuinely cannot be delegated. That is a legitimate design choice, but it should be a stated decision with the retention consequences understood, not the accidental result of never revisiting the mandate.
Decide next
Related decisions
- 01 · GCC decisionGCC governanceReporting lines, decision rights and the measures that set the center's ceiling.
- 02 · GCC decisionGCC talent and attritionWhat actually holds a capability center together once the first hiring wave lands.
- 03 · GCC decisionAI-native GCCDesigning a center around automated work, senior roles and unit economics.
- 04 · GCC decisionGCC operating modelsCaptive, BOT, managed and hybrid compared on control, speed, cost profile and exit.
Continue
Related intelligence
- DecisionGCC governanceReporting lines and decision rights that set the center's ceiling.
- DecisionGCC talent and attritionWhy mandate and progression drive retention more than compensation.
- DecisionAI-native GCCDesigning for capability and unit economics rather than headcount growth.
- PortalBuild the GCC blueprintDesign the target-state operating model, mandate and organization.
Transparency
Sources and methodology
This page reflects NirjiX practitioner experience designing, costing and standing up capability centers in India, and the same modelling logic used in the NirjiX GCC business case builder and blueprint.
We do not publish generic per-seat or per-FTE benchmarks as if they were universal. Compensation, real estate, statutory cost and attrition vary materially by city, role mix, seniority and hiring speed, and a business case built on an averaged benchmark is usually wrong in both directions at once.
The models we build with clients use your own baseline cost, your own role mix and your own ramp assumptions, then stress-test them with sensitivity ranges rather than presenting a single deterministic number.
Test the decision against your own numbers
The GCC assessment establishes whether the workload and economics support a center; the business case builder models the cost, savings and sensitivities behind it.
Outputs are preliminary and intended for advisor validation before investment decisions.