Decision intelligence · Global Capability Centers
The GCC Business Case: Building One That Survives Finance Review
Most GCC business cases are rejected not because the economics are weak, but because they are presented as a single confident number that finance can dismantle in ten minutes.
A durable case shows the baseline it is measured against, the ramp it depends on, the assumptions that would break it, and what the organization gains beyond cost.
Decision intelligenceReviewed by Ramesh Rathi, Vice President — GCC Enablement & ImplementationPublished January 2026Last reviewed February 202611 min read
Direct answer
What makes a GCC business case credible?
A credible GCC business case states a verifiable current-state cost baseline, models a realistic hiring and productivity ramp rather than steady-state savings from day one, includes the full cost stack (compensation, statutory, facilities, technology, governance, transition and parent-company management time), tests sensitivity to attrition, wage inflation and ramp delay, and separates cost arbitrage from capability value. It presents a range with named assumptions, not a single number.
Start with a baseline finance already accepts
The single most common failure is a baseline nobody agreed. If the current cost of the work is estimated by the team proposing the center, the entire case is contested from the first slide.
Build the baseline from the same ledger finance uses: fully loaded cost of the roles in scope, plus the vendor spend the center would displace, plus the overhead that genuinely follows the work. Where the baseline is uncertain — often true for work spread across many teams — state the uncertainty explicitly and model a range.
Then define scope precisely. "Engineering support" is not a scope; a named set of processes, systems and service levels is. Vague scope produces a ramp curve that cannot be defended, because nobody can say what the first thirty people will actually do.
The cost stack most cases under-count
Compensation is the visible line. The lines beneath it are where cases are usually wrong.
| Cost component | Why it is commonly mis-stated |
|---|---|
| Compensation and statutory cost | Benchmarked at market median without adjusting for the seniority mix the work actually requires, or for the premium needed to hire quickly. |
| Recruitment and replacement | Costed once at build, then ignored — even though attrition means you hire the same seat repeatedly over five years. |
| Facilities and technology | Modelled at final headcount from day one, or omitted for hybrid working without checking what the operating model requires. |
| Transition and knowledge transfer | The most under-costed line. It consumes senior time in the parent organization, which is the scarcest resource in the whole program. |
| Governance and management | Site leadership, quality, security and compliance are treated as overhead to be added later rather than as a designed layer. |
| Parent-company management time | Almost never costed, and almost always the reason a program slips. It should appear in the case as an explicit commitment. |
| Productivity ramp | Assumed to reach parity in a quarter or two. Complex process work commonly takes longer, and the case should say what it assumes and why. |
The sensitivities a board will test
- Attrition at the level your city and role mix actually experience, not a target rate — and the replacement cost that follows it.
- Wage inflation over the modelled horizon, with a scenario where it exceeds the base assumption.
- Ramp delay: what happens to payback if hiring runs one or two quarters behind plan.
- Scope reduction: whether the case still works if only sixty per cent of the intended work transfers.
- Discount rate: the NPV under finance's rate, not a convenient one.
- Currency: the exposure created by a multi-year cost base in a different currency from the savings.
Present these before you are asked. A case that already shows its own downside is far more persuasive than one defended under questioning.
How to structure the case
- 01
Agree scope and baseline with finance first
Get the baseline signed off before modelling anything. A contested baseline invalidates every downstream number.
- 02
Model the ramp, not the steady state
Show headcount, productivity and cost quarter by quarter through the ramp; the payback point lives in that curve.
- 03
Cost the full stack
Include transition, governance and parent-company time. Omitting them is the fastest way to lose credibility later.
- 04
Run sensitivities and show the downside
Present a range with named drivers. Boards fund ranges they understand more readily than points they distrust.
- 05
State the capability value separately
Time-zone coverage, talent access, resilience and speed are real, but they must be argued on their own terms — not smuggled into the savings line.
- 06
Define the measurement regime up front
Agree how savings and capability outcomes will be verified after go-live, and who reports them.
NirjiX view
Our view: a cost-only case builds a center nobody defends in year three
Cost arbitrage is a legitimate reason to start, and a poor reason to continue. Centers justified purely on savings tend to be measured purely on headcount cost, which drives exactly the behaviours — junior-heavy hiring, ticket-count metrics, minimal investment in capability — that make them expendable in the next cost review.
The cases that hold up over five years present two ledgers: an unambiguous cost ledger that finance can audit, and a capability ledger with its own measurable commitments — cycle time, coverage, product ownership transferred, quality outcomes.
We also recommend modelling one scenario nobody asks for: the center succeeding faster than planned. Programs are routinely constrained by facilities, hiring pipeline and visa or governance capacity that were sized for the base case, and the cost of that constraint is real.
Frequently asked executive questions
- How do you build the business case for an India GCC?
- Start from the work portfolio rather than a headcount target: define what moves, then cost it fully — compensation with realistic escalation, attrition and rehiring, facilities, technology, entity and compliance, transition and knowledge transfer, and parallel running during handover. Model five years of cash flow, state the breakeven point explicitly, and test the case against attrition, wage inflation and discount-rate sensitivities before it reaches finance. A case that survives review names its assumptions and shows what happens when each one is wrong.
- How long does a GCC business case usually take to build?
- An indicative model can be produced in days using the NirjiX business case builder. A board-ready case typically takes four to eight weeks, most of which is spent agreeing the baseline and validating scope with the teams whose work would transfer — not on the modelling itself.
- What payback period is realistic?
- It depends on scope, role mix, ramp speed and how much transition cost the parent absorbs, so any single published figure is misleading. The more useful discipline is to model payback as a range across ramp scenarios and show which assumption moves it most.
- Should the business case include the AI opportunity?
- Yes, but separately and conservatively. Designing an AI-native center changes role mix and productivity assumptions, and those changes belong in a clearly labelled scenario. Blending speculative AI productivity into the base case is one of the fastest ways to lose finance's confidence.
- How do we handle attrition in the model?
- Model it as a recurring cost with a replacement-productivity lag, not as a percentage footnote. Use a rate consistent with your city, role mix and seniority, and run a downside scenario several points above it.
- Does the operating model change the business case?
- Substantially. Captive, build-operate-transfer, managed services and hybrid models have different cost curves, capital profiles, speed to first delivery and exit characteristics. The business case should be modelled against the operating model you intend to use, not a generic captive assumption.
Decide next
Related decisions
- 01 · GCC decisionGCC operating modelsCaptive, BOT, managed and hybrid compared on control, speed, cost profile and exit.
- 02 · GCC decisionGCC location strategyChoosing a city on talent depth, wage trajectory and competitive density, not brochures.
- 03 · GCC decisionGCC setup roadmapThe realistic sequence from decision to a functioning center, and where timelines slip.
- 04 · GCC decisionGCC talent and attritionWhat actually holds a capability center together once the first hiring wave lands.
Continue
Related intelligence
- DecisionGCC operating modelsCaptive, BOT, managed and hybrid — how each affects speed, control, cost and exit.
- PortalModel your business caseBuild a five-year model with ramp, attrition, sensitivities and NPV using your own inputs.
- PortalGCC feasibility assessmentTest intent, work portability, talent, governance and cost before modelling anything.
- HubGCC by industryHow sector conditions change what transfers and what it costs.
- ResearchGCC cost and setupThe structural cost components of establishing a capability center in India.
- HubGCC consulting hubFeasibility, business case, operating model, blueprint and advisor review in one path.
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.
Model your GCC business case with your own numbers
The builder takes your cost baseline, role mix and ramp assumptions and produces a five-year model with sensitivity analysis and NPV decomposition.
Model outputs are indicative and intended for advisor validation before investment approval.