Decision intelligence · Global Capability Centers
How to Build a GCC Business Case: The NirjiX Executive Framework
A GCC business case is not a labour-cost comparison. It is a multi-year investment case with a setup profile, a ramp curve, a governance layer and a set of assumptions that finance will test individually.
This guide sets out what belongs in the case, how the financial outputs are constructed, which assumptions decide the answer, and what usually breaks a case in review.
Decision intelligenceReviewed by Ramesh Rathi, Vice President — GCC Enablement & ImplementationPublished January 2026Last reviewed February 202614 min read
Direct answer
What should a GCC business case include?
A credible GCC business case should compare the proposed centre with the organization's true current-state operating cost and the relevant alternatives. It should include setup investment, talent, location, transition, technology, management overhead, ramp productivity and governance; model benefits over several years; test downside scenarios; and connect the financial case to the work portfolio, operating model and execution risk. Salary arbitrage alone is not a sufficient basis for approval.
Why a GCC business case is different from a labour-cost comparison
A labour-cost comparison asks a single question: what does this role cost here versus there? A capability-centre case has to answer a harder one: what does it cost this organization to own and run a capability in another country for five years, and what does it receive in return?
The difference is structural. A centre carries setup investment before it produces anything, a ramp during which cost is fully incurred and output is partial, a governance layer that does not exist in the current model, and management attention drawn from the parent organization. None of those appear in a rate-card comparison, and each of them changes the payback point.
There is also a benefit side that a rate comparison cannot express. Coverage across time zones, access to skills that are scarce in the home market, resilience against single-site concentration and the ability to own a product roadmap rather than buy delivery are legitimate outcomes — but they must be argued and measured on their own terms rather than folded into a savings percentage.
The practical consequence: build the case as an investment appraisal. State the baseline, the investment, the cash-flow profile and the assumptions. Then let finance test it, because they will.
The NirjiX GCC Business Case Framework
This is the sequence we work through with clients, and the same structure that drives the NirjiX assessment, business case builder and board investment pack. Each element depends on the one before it: a financial model built before the work portfolio is settled will be re-modelled.
NirjiX GCC Business Case Framework — eight elements
- 01
Strategic rationale
Why a capability centre is being considered at all, and what strategic problem it solves that the current model cannot. A case with no articulated problem is a cost exercise looking for a sponsor.
- 02
Current-state baseline
The fully loaded cost and the current performance of the work in scope, agreed with finance before anything is modelled. This is the reference every later number is measured against.
- 03
Work portfolio
What should move, what must remain, what is piloted first, what should be automated and what should be redesigned rather than relocated. Scope precision decides whether the ramp curve is defensible.
- 04
Cost architecture
Setup, recurring, ramp, governance and risk costs, each with its own driver. Costs that scale with headcount, with sites and with time behave differently and should be modelled separately.
- 05
Benefit architecture
Savings, capacity, capability, control, resilience and innovation — separated into a financial ledger finance can audit and a capability ledger with its own measurable commitments.
- 06
Financial model
TCO, NPV, ROI, payback, peak cash requirement and the funding profile over the modelled horizon, expressed as cash flows rather than an annualized saving.
- 07
Scenarios and sensitivity
Base, downside and upside cases with explicit assumptions, plus single-variable sensitivity on the drivers that move the answer most.
- 08
Execution risk
The assumptions that could invalidate the case or delay value — hiring pace, transition capacity, attrition, governance maturity — each with an owner and a mitigation.
The framework is the public methodology behind the NirjiX GCC business case builder. The builder applies the same eight elements to your own inputs; the calculation logic within it is proprietary, but nothing in the structure above is hidden.
Current-state baseline: what must be measured before you model India
- Fully loaded cost of the roles in scope — compensation, employer statutory cost, benefits, and the overhead that genuinely follows the work rather than an allocated corporate rate.
- Third-party and vendor spend the centre would displace, including contractor rates, managed-service fees and licence costs attached to the work.
- Current performance: throughput, cycle time, quality and service levels, so that a like-for-like comparison is possible after go-live rather than only a cost comparison.
- Capacity constraints in the current model — unfilled roles, deferred work, backlog — because a centre often buys capacity that the baseline never actually delivered.
- Management effort the work consumes today, which is the most useful predictor of the governance layer the centre will need.
- Where the baseline is uncertain, state the uncertainty and model it as a range. A stated range is credible; a precise number nobody can source is not.
The most common reason a case is contested is that the baseline was produced by the team proposing the centre. Build it from the same ledger finance uses, and agree it in writing first.
Cost architecture: setup, run, ramp, governance and contingency
Compensation is the visible line. The lines beneath it decide whether the case survives. Each entry below is a structural cost category, not a benchmark figure — the values belong to your role mix, city and operating model.
| Cost category | Principal driver | Commonly mis-stated as |
|---|---|---|
| Setup and entity | One-off: incorporation, registrations, legal, advisory, initial fit-out and deposits. | A single line at the start of year one, with statutory and advisory follow-through omitted. |
| Compensation and statutory cost | Role mix, seniority and hiring speed, escalated over the modelled horizon. | Market median for a junior-weighted mix, with no premium for hiring at pace. |
| Recruitment and replacement | Hiring volume in ramp plus recurring attrition replacement thereafter. | Costed once at build and then ignored, though the same seat is filled repeatedly over five years. |
| Facilities and workplace | Seats required at each stage of ramp, plus the operating model's on-site expectation. | Final headcount from day one, or omitted entirely on a hybrid-working assumption never tested. |
| Technology and security | Devices, licences, connectivity, access controls and the security posture the work requires. | Extrapolated from home-market per-seat cost without the controls a remote site actually needs. |
| Transition and knowledge transfer | Process complexity, documentation maturity and parallel-running duration. | The most under-costed line: it consumes senior parent-organization time, the scarcest resource in the programme. |
| Governance and management | Site leadership, quality, risk, compliance and reporting designed for the scope. | Treated as overhead to be added later rather than as a designed layer with named roles. |
| Parent-company management time | Executive, functional and technical time drawn away from the home organization. | Almost never costed, and frequently the reason a programme slips. |
| Ramp productivity | Time to competence by role type and process complexity. | Assumed parity within a quarter or two, which few complex processes achieve. |
| Contingency | Uncertainty in scope, hiring pace and transition duration. | Omitted, so the first variance is read as a failure of the case rather than a modelled outcome. |
Benefit architecture: financial and strategic value
Benefits are stated in two ledgers. The financial ledger is auditable and belongs in the NPV. The strategic ledger is real but must carry its own measurable commitments rather than be converted into a savings percentage.
| Benefit | Ledger | How it is evidenced |
|---|---|---|
| Unit cost reduction on transferred work | Financial | Cost per unit of output against the agreed baseline, verified by finance after steady state. |
| Displaced third-party spend | Financial | Contract value retired or not renewed, traced to specific agreements. |
| Capacity released or added | Financial and strategic | Work delivered that the baseline model could not absorb, measured in throughput rather than headcount. |
| Capability ownership | Strategic | Named products, systems or processes transferred from vendor or parent ownership to the centre. |
| Coverage and cycle time | Strategic | Time-zone coverage achieved and measured change in end-to-end cycle time. |
| Resilience and concentration risk | Strategic | Reduction in single-site or single-vendor dependency for defined critical processes. |
| Innovation and engineering leverage | Strategic | Roadmap items delivered by the centre that were previously deferred for lack of capacity. |
Scenario comparison: current model, outsourcing, captive, BOT and managed
The case is only meaningful against alternatives. Model the options that are genuinely available to your organization; if BOT is not procurable in your governance environment, leave it out rather than including it for completeness.
| Option | Investment profile | Speed to first delivery | Control | Exit |
|---|---|---|---|---|
| Current model (do nothing) | No new investment; existing cost trajectory and its escalation continue. | Immediate — but capacity constraints continue. | Full, within existing limitations. | Not applicable; the constraint remains. |
| Outsourcing / managed services | Largely opex, low upfront, priced per unit or per FTE. | Fastest; capability exists on day one. | Contractual: you control outcomes, the provider controls delivery. | Contractual exit, though the work can become practically unmovable. |
| Captive GCC | Highest upfront and fixed; lowest marginal cost at scale. | Slowest: entity, hiring and governance are all yours. | Full — entity, employment, IP, culture and roadmap. | Costly and slow; the centre is an owned asset. |
| Build-Operate-Transfer | Fee-based during build, then a transfer consideration and a step change to direct cost. | Fast; the partner already has entity, premises and hiring machinery. | Partial during build, full after transfer. | Defined by the transfer terms — the clause that decides the option's value. |
| Hybrid (captive core, partnered periphery) | Mixed; requires disciplined allocation between the two. | Fast for partnered scope, slower for the captive core. | Differentiated by work stream. | Partial: the partnered layer can flex, the core cannot. |
Financial outputs: TCO, NPV, ROI, payback and peak cash
Five outputs answer five different board questions. Presenting only one — usually annual saving — is why cases get sent back. Variables are defined so a CFO reader can reconstruct the arithmetic.
| Output | The question it answers | How it is constructed |
|---|---|---|
| Total cost of ownership (TCO) | What does owning and running this centre cost in full over the horizon? | Sum of all setup, recurring, ramp, governance, transition and contingency costs across the modelled years, before any benefit is netted. |
| Net present value (NPV) | Is the investment value-creating at finance's cost of capital? | Discount each year's net cash flow (benefits minus costs) back to today at the organization's discount rate and sum them. Use the rate finance mandates, not a convenient one. |
| Return on investment (ROI) | What return does the invested capital produce? | Cumulative net benefit divided by cumulative investment over the horizon, stated with the horizon named — ROI without a period is meaningless. |
| Payback period | When does cumulative benefit overtake cumulative cost? | The point at which the cumulative net cash flow crosses zero, read off the quarterly ramp curve rather than annual averages. |
| Peak cash requirement | How much cash must be funded before the centre turns cash-positive? | The most negative point of the cumulative cash-flow curve. This, not NPV, is usually what determines whether the programme is approvable this year. |
Sensitivity analysis: which assumptions actually matter
- Ramp delay — the single most influential variable in most models. Show payback if hiring runs one and two quarters behind plan.
- Attrition at the rate your city and role mix actually experience, not a target, with the replacement cost and productivity lag that follow it.
- Wage inflation across the horizon, with a scenario meaningfully above the base assumption.
- Scope reduction — whether the case still holds if only part of the intended work transfers.
- Productivity at steady state, since a small change in assumed output per person compounds across every modelled year.
- Discount rate, tested at finance's mandated rate and at a stress rate above it.
- Currency exposure created by a multi-year cost base denominated differently from the savings.
Vary one assumption at a time against the base case and report the effect on NPV and payback. Present these before you are asked — a case that shows its own downside is far more persuasive than one defended under questioning.
What usually breaks the business case
- A baseline finance did not agree, which invalidates every downstream number in a single question.
- Scope stated as a function name rather than a defined set of processes, systems and service levels.
- Steady-state savings claimed from year one, with no ramp curve behind them.
- Transition cost and parent-company management time absent from the model.
- A single deterministic number with no range, no named assumptions and no downside case.
- Speculative AI or automation productivity blended into the base case instead of a labelled scenario.
- Attrition treated as a footnote rather than a recurring cost with a replacement lag.
- Benefits that exist only as adjectives — 'agility', 'innovation' — with no measurement commitment attached.
In review, cases fail for a small number of recurring reasons. Most are avoidable at modelling time.
What would change the recommendation
- If the portable work portfolio is materially smaller than assumed, a captive build may be the wrong instrument and a managed or hybrid model becomes the stronger option.
- If first delivery is required within two quarters, the ramp inherent in a captive build cannot meet it regardless of the economics.
- If the parent organization cannot commit named senior time to transition, the case should be deferred rather than de-scoped — under-supported transitions fail expensively.
- If peak cash exceeds what the organization can fund in the approval year, phase the scope rather than compress the ramp.
- If the work is heavily regulated or data-restricted in ways that prevent transfer, the portfolio, not the location, is the constraint.
- If attrition or wage inflation in the target city runs materially above the sensitivity range, revisit location strategy before revisiting the model.
A case should state the conditions under which its own conclusion flips. This is the section that most increases board confidence.
NirjiX view
Our view: a cost-only case builds a centre nobody defends in year three
Cost arbitrage is a legitimate reason to start and a poor reason to continue. Centres 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 mistake we see most often at executive level is precision without agreement: a beautifully constructed model built on a baseline nobody signed. The second is optimism in the ramp, where a plan assumes hiring and competence at a pace the market and the transition team cannot sustain. The third is presenting one number, which invites the board to test it rather than to fund it.
The cases that hold up over five years present two ledgers: an unambiguous cost ledger 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 centre succeeding faster than planned. Programmes are routinely constrained by facilities, hiring pipeline and governance capacity sized for the base case, and the cost of that constraint is real.
Frequently asked questions
- What should a GCC business case include?
- Strategic rationale, an agreed current-state baseline, a defined work portfolio, the full cost architecture (setup, recurring, ramp, governance, transition and contingency), a benefit architecture split into financial and strategic ledgers, the financial model (TCO, NPV, ROI, payback and peak cash), base, downside and upside scenarios with sensitivity analysis, and a named set of execution risks with owners and mitigations.
- 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 several years of cash flow, state the payback point and peak cash explicitly, and test the case against attrition, wage inflation, ramp delay and discount-rate sensitivities before it reaches finance.
- Is salary arbitrage enough to justify a GCC?
- No. Arbitrage explains why the unit cost is lower; it does not explain whether the organization can absorb setup investment, sustain a ramp, govern a second site and retain the capability. A case built on arbitrage alone also sets the centre up to be measured on cost alone, which limits what it is later allowed to become.
- What payback period is realistic for an India GCC?
- It depends on scope, role mix, ramp speed and how much transition cost the parent absorbs, so any single published figure would be misleading. The more useful discipline is to model payback as a range across ramp scenarios and show which assumption moves it most — usually ramp delay, then attrition.
- What is the difference between TCO and NPV in a GCC case?
- TCO is the gross cost of owning and running the centre across the horizon, before benefits. NPV nets benefits against costs year by year and discounts them to today at your cost of capital. TCO answers what it costs; NPV answers whether it is worth doing. Boards generally need both, plus peak cash to know what must be funded.
- How long does a GCC business case 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.
- 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. Model the case against the operating model you actually intend to use rather than a generic captive assumption.
- Should the AI opportunity be included in the business case?
- Yes, but separately and conservatively. Designing an AI-native centre 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.
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 cost structureThe structural components of capability-centre cost and how each one behaves as the centre scales.
- DecisionGCC operating modelsCaptive, BOT, managed and hybrid — how each affects speed, control, cost and exit.
- DecisionGCC location strategyHow city choice changes talent depth, attrition, wage escalation and therefore the model.
- DecisionAI-native GCC designHow designing for AI from the outset changes role mix, ramp and the productivity assumptions in the case.
- PortalModel your business caseApply the eight-element framework to your own inputs and produce a five-year model with sensitivities and NPV.
- HubGCC consulting hubFeasibility, business case, operating model, blueprint and advisor review in one path.
Explore
Connected guides
Go deeper on this topic
- Funding and Approval
Four things. The downside case: what the economics look like if hiring is slower, attrition higher and productivity lower than assumed, and whether the decision still holds.
The same decision on the other side
- AI ROI
Define the single business metric the use case is meant to move, record its baseline before the build, and estimate the benefit as the modelled change in that metric multipli…
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.
Evidence labelling on this page: cost and benefit categories, scenario characteristics and failure patterns are NirjiX practitioner judgement drawn from capability-centre engagements. Financial definitions (TCO, NPV, ROI, payback, peak cash) are standard investment-appraisal constructs. No external benchmark percentages, savings figures or payback claims are published here, because compensation, attrition and real-estate conditions vary by city, sector and role mix to a degree that makes a single published figure misleading.
Reference period and limitations: the practice described reflects engagements through the current advisory cycle stated in the page metadata above. Where your own model requires benchmark inputs, they should be sourced for your target city and role mix at the time of modelling and labelled as client-specific inputs, external benchmarks or illustrative assumptions inside the model itself.
Model your GCC business case with your own numbers
The builder applies the same eight-element framework to your cost baseline, role mix and ramp assumptions, and produces a multi-year model with sensitivity analysis, payback, peak cash and NPV decomposition.
Model outputs are indicative and intended for advisor validation before investment approval.