The true cost of an India GCC is the sum of setup cost, recurring operating cost, ramp productivity loss, governance overhead, attrition and replacement cost, technology and workplace costs, and an appropriate risk contingency.
Salary cost alone materially understates total cost of ownership, especially during the first 12–24 months, when setup and ramp land in full and productive capacity has not yet arrived.
Why salary arbitrage is not a cost model
Almost every GCC conversation opens with a salary comparison: this role costs X at home and a fraction of X in India. The arithmetic is usually correct and the conclusion is usually wrong, because it compares one layer of a six-layer cost structure against a fully loaded retained cost.
Three distortions follow. Arbitrage compares steady state against a programme that will not reach steady state for four to eight quarters. It excludes the layers that sit in home-country budgets — governance, travel, transition management — so they never enter the case. And it prices a seat rather than a unit of delivered output, which during ramp are not the same thing.
The correction is structural, not arithmetic: price every layer, then compare totals. That is what the architecture below is for.
The NirjiX GCC Cost Architecture
We use the same six-layer structure on every engagement, because it is the smallest set of layers that still produces a total a CFO cannot pull apart.
Six layers, one total. A cost model that omits any one of them will understate the programme — most often ramp and governance, which are the two layers that sit outside the local budget.
| Cost layer | What it includes | Why it is often missed |
|---|---|---|
| Setup cost | Entity and incorporation, recruitment, workplace fit-out, technology build, advisory, launch | Usually separated from run-rate comparisons, so per-seat economics look better than the programme's actual cash profile |
| Run cost | Compensation and benefits, office, IT and licences, vendors, statutory compliance | Normally modelled, but often at base salary rather than fully loaded cost, and rarely inflated forward |
| Ramp cost | Training, knowledge transfer, reduced early productivity, dual running with the retained team | A seat filled is not a seat productive; the gap is months, and it lands entirely in the first budget year |
| Governance cost | HQ leadership time, travel, controls, internal audit, transition PMO, centre management | Sits in home-country budgets, so it never appears in the local cost model that gets approved |
| Attrition and replacement | Backfill recruitment, vacancy gaps, re-ramp of replacements, lost institutional knowledge | Modelled as an HR metric rather than a cost line, even though it compounds every year of the horizon |
| Risk contingency | Schedule slippage, wage inflation above plan, hiring difficulty, currency movement | Omitted because a single deterministic number reads more confidently to a board than a range |
One-time setup cost
Setup is everything you spend before the centre produces anything. The categories are stable across programmes even though the amounts are not: legal entity formation and registrations; recruitment fees and leadership hiring, including notice-period buyouts; workplace fit-out or the commitment cost of a managed workspace; endpoint, identity, network and security build; transfer-pricing study and inter-company agreement design; and external advisory through launch.
Two design choices move this layer more than any negotiation. The first is entity form — an employer-of-record or managed structure defers incorporation cost but carries a per-head margin, while a wholly owned subsidiary front-loads cost and gives clean IP assignment. The second is workplace: managed space converts capex into a monthly line and keeps exit cheap at small scale, while an own lease pays back only above a committed seat count on a multi-year term.
Setup should be priced from live quotes in your shortlisted cities, not from a benchmark. Every category above is quotable before you commit.
Recurring run cost
Run cost is the layer most organisations already model — usually incompletely. Fully loaded compensation means base plus variable plus benefits plus employer statutory contributions, and the gap between base and fully loaded is large enough to change a conclusion on its own.
Beyond compensation, run cost carries workplace on a per-seat basis, technology and licences per person, connectivity and endpoint management, vendor and payroll services, and recurring statutory compliance: statutory and tax audit, transfer-pricing documentation refresh, company secretarial work and payroll filings. Compliance is a standing operating cost, not a setup item that ends at launch.
Run cost must also be inflated forward. A centre sized on today's compensation curve will be re-benchmarked inside its first two years in any competitive talent market, and a flat five-year run line is the single most common modelling error we correct.
Ramp productivity and dual running
Ramp cost is the difference between a seat filled and a seat productive, and it is almost always the largest under-modelled layer. It has three components: the direct cost of training, documentation and knowledge transfer; the productivity shortfall of new joiners against a fully productive baseline; and dual running, where the retained team continues to carry the work while the new team learns it.
Ramp duration scales with role complexity rather than with seniority. Transactional and process roles reach steady output fastest; engineering, analytics and platform roles take materially longer; domain-heavy, customer-facing or regulated work takes longest, because competence there depends on context that cannot be documented quickly.
Model ramp as productive capacity by month, not as offers accepted. A hiring plan that reports headcount without a productivity curve will show benefit arriving roughly two to three quarters before it actually does.
Governance and HQ overhead
A capability centre consumes management attention in the parent organisation, and that attention has a price. The layer covers home-country leadership time in steering and operating reviews, travel in both directions, the transition PMO for as long as it runs, internal audit and control extension, and centre leadership plus local HR and finance support.
This layer is systematically excluded because it sits in home-country cost centres while the business case is written locally. That accounting boundary is also why sub-scale centres disappoint: governance is largely fixed, so below a certain headcount it consumes most of the arbitrage that justified the programme.
Price governance explicitly, even approximately. An acknowledged estimate survives board challenge; a silent omission does not.
Attrition, replacement and vacancy
Attrition is a cost line, not an HR metric. Each departure carries backfill recruitment, a vacancy period in which the work either stops or is absorbed elsewhere, re-ramp of the replacement through the same productivity curve as the original hire, and the loss of accumulated process knowledge that no handover fully transfers.
It compounds. A centre with meaningful annual attrition is re-hiring a visible share of its population every year of the horizon, and each of those hires re-enters the ramp layer. Applying an attrition rate only to recruitment fees captures a fraction of the real cost.
Attrition also varies sharply by city, role and employer brand, which is one more reason a single national benchmark is not usable. Model it against your own role mix in your own shortlisted locations, and test it as a sensitivity rather than fixing it as a constant.
How city and role mix change the number
After headcount, the two largest swing factors are where you build and who you hire. Compensation, real estate and attrition each vary by city; talent depth varies by discipline within the same city; and role mix changes the average seniority you are buying, which moves both compensation and the ramp curve.
This is why NirjiX does not publish a universal per-seat figure. An averaged benchmark overstates cost for a junior-weighted operations centre and understates it for a senior engineering build, so it is wrong in both directions at once and defensible in neither.
Location choice is a structured evaluation in its own right — talent depth, cost, time-zone overlap, regulatory friction and existing footprint. We work through that separately in the GCC location strategy guide.
How the operating model reprices the layers
The operating model does not remove cost layers; it changes who carries them and when they land. A captive centre carries setup, entity and governance from day one and reaches the lowest long-run unit cost. A managed model converts setup into a monthly fee and transfers hiring risk to a partner, priced as margin, at the cost of some strategic latitude. Build-operate-transfer defers the setup layer and adds a transfer payment plus transfer risk in a later year.
Compare models on discounted total cost across the full horizon, not on year-one cash. The model that looks cheapest at launch is frequently the most expensive by year five, and vice versa. The trade-offs are set out in full in the operating model guide and the engagement model comparison.
How to calculate true GCC TCO
- Step 01
Fix the horizon and the role plan. State headcount by role and by year for the full horizon — five years is the usual board window — because every other layer is driven off it.
- Step 02
Price fully loaded compensation per role, in each shortlisted city, using live offer data rather than survey averages. Include benefits and employer statutory contributions.
- Step 03
Add per-seat workplace and technology cost for the workplace model you have actually chosen.
- Step 04
Quote setup as a one-off, itemised by category, from real quotes: entity, recruitment, fit-out, technology build, advisory.
- Step 05
Apply a productivity curve to each joining cohort and charge the shortfall against benefit in the year it occurs. Add dual-running cost for as long as the retained team carries the work.
- Step 06
Add governance as an explicit annual line, including HQ time and travel, even where it sits in another cost centre.
- Step 07
Apply attrition to backfill recruitment, vacancy and re-ramp — not to recruitment fees alone.
- Step 08
Inflate both the retained and target cost lines forward at separate, stated rates.
- Step 09
Discount the annual totals to present value at your own hurdle rate.
- Step 10
Size contingency from the sensitivities that move your case most, and state it separately rather than burying it in the layers.
The NirjiX GCC business case builder runs exactly this sequence on your own inputs, and returns "more information required" rather than a fabricated figure wherever an input is missing.
An illustrative TCO shape — not a benchmark
The table below is illustrative only. It uses no real client data and no published benchmark. Its purpose is to show the shape of a TCO profile — where cost concentrates and when benefit actually arrives — using index values rather than currency, where 100 is the annual fully loaded cost of the retained team the centre is intended to replace at full scale.
| Year | Share of target headcount | Cost layers landing | Benefit realised |
|---|---|---|---|
| Year 1 | Partial — leadership and first cohorts | Setup in full, run cost on part-year headcount, heaviest ramp and dual running, governance at its peak intensity | Lowest of the horizon; frequently net negative once setup is included |
| Year 2 | Approaching plan | Run cost rising with headcount, residual ramp on late cohorts, attrition entering the model, governance still elevated | Rising; this is where most credible cases cross into positive contribution |
| Year 3+ | At plan | Steady-state run cost, inflation compounding, attrition and replacement recurring annually, governance normalising | Steady state — the figure salary arbitrage assumed would be available from month one |
The point of the illustration is the timing, not the amounts. Benefit is back-loaded and cost is front-loaded, which is precisely the profile an arbitrage comparison hides.
What would change the cost conclusion?
A cost model is only trustworthy if you can say what would break it. In our experience five variables account for most of the movement.
- Wage inflation above plan in the target city. Compounds across the whole horizon and erodes the gap faster than any other variable.
- Hiring slower than plan. Delays benefit while setup and governance continue, which pushes break-even out disproportionately.
- Attrition above plan. Re-enters the ramp layer every year and quietly resets productivity gains.
- Scale below plan. Governance is largely fixed, so a shortfall against target headcount hits unit economics hardest.
- Currency movement. A cross-border cost model denominated in two currencies carries an FX position whether or not anyone named it.
Each of these should be run as a stated sensitivity with a visible effect on the total, which is how the business case guide turns this cost structure into an approvable investment decision.
Where cost models break in practice
The failure we see most often is not an over-optimistic number. It is a missing layer. A model that prices compensation carefully and omits governance and ramp entirely will be internally consistent, professionally presented, and wrong by a margin that only becomes visible in year two — at which point the programme is defending itself rather than scaling.
The second failure is false precision. A three-decimal per-seat figure carried across five years invites a challenge no one can answer, because the underlying inputs were never that precise. A stated range with a sensitivity behind it survives the same boardroom that rejects the point estimate.
Our working rule: every number in a client cost model traces to that client's own data or to a quote they can obtain. Where neither exists, we show a range and say so. A business case built on borrowed benchmarks collapses the first time a CFO tests one of them.
Reviewed by Ramesh Rathi, Vice President — GCC Enablement & Implementation.
Sources and methodology
This page describes a cost structure, not a benchmark set. Every claim on it falls into one of three categories, and each is labelled where it appears.
| Claim type | How it is used here | Basis |
|---|---|---|
| Structural | Which cost layers exist, what each contains, and how they behave over a programme horizon | NirjiX practitioner experience designing, costing and standing up capability centres in India — the same logic used in the NirjiX GCC business case builder |
| Directional | Statements about relative magnitude and timing, such as ramp being longer for engineering than for transactional roles | Observed patterns across NirjiX client engagements; directional, not measured, and stated without false precision |
| Illustrative | The index-based TCO shape in the illustrative section | Constructed for explanation only. No client data and no external benchmark. Explicitly labelled as illustrative in the section itself |
We deliberately do not publish universal per-seat or per-FTE cost benchmarks. 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.
Models we build with clients use the client's own baseline cost, role mix and ramp assumptions, then stress-test them with sensitivity ranges rather than presenting a single deterministic number. Reference period for this page: 2026-08-27. Geography: India, with cross-border comparison against the client's retained location.
Cost structure versus business case
This page owns cost mechanics: the layers, their behaviour, and how to total them into TCO. It stops at the total.
The GCC business case guide picks up from there and owns the investment decision built on that total — scenario comparison, ROI, NPV, break-even and the approval logic a board applies. Read this page first if you are asking what it costs; read that one if you are asking whether to approve it.
Executive FAQs
What does a GCC in India actually cost per employee?+
There is no single credible per-employee number, and any provider quoting one without your role mix is guessing. Fully loaded annual cost per seat is driven by role seniority, city, benefits design and workplace model, and the same headcount can differ by a factor of two or more across those variables. The defensible approach is to price your own role mix against live offer data in your shortlisted cities, add benefits and employer contributions, then layer facilities, technology, governance, attrition and contingency on top. That total — not the salary line — is your cost per employee.
Why is salary arbitrage an incomplete comparison?+
Salary arbitrage compares one layer of a six-layer cost structure. It excludes setup, ramp, governance, attrition and contingency entirely, and it compares a steady-state figure against a programme that will not reach steady state for 12 to 24 months. Business cases built on arbitrage alone routinely show savings in year one that the cash flow contradicts, because the setup and ramp cost sits outside the comparison.
How is GCC cost different from the GCC business case?+
This page covers cost mechanics: what the layers are, how they behave, and how to total them into TCO. The business case covers the investment decision built on top of that total — scenario comparison, ROI, NPV, break-even and the approval logic a board applies. Model the cost structure first; the business case is only as good as the TCO underneath it.
How long before a GCC reaches steady-state cost?+
Steady state is a function of hiring pace and role complexity, not calendar time. Transactional roles reach full productivity fastest, engineering and analytics take materially longer, and domain-heavy or regulated work longer still. Until the last cohort has ramped, your cost per productive unit of output is higher than your cost per seat — which is why the first two budget years should be modelled separately rather than averaged.
Does the operating model change the cost structure?+
It changes which layers you carry and when. A captive centre puts setup, entity and governance cost on your balance sheet from day one but gives the lowest long-run unit cost. A managed model converts setup into a monthly fee and shifts hiring risk to the partner, at a margin. Build-operate-transfer defers the setup layer but adds a transfer payment and transfer risk later. The layers do not disappear; they are repriced and re-timed.
Should we include a contingency, and how large?+
Yes — a board-quality case carries one. Rather than a flat percentage, size it against the variables that actually move your case: wage inflation above plan, hiring slower than plan, and currency. Test each one at a stated adverse level and let the resulting swing in NPV set the contingency, so the number is defensible when challenged rather than a convention.
Do city choice and role mix change the answer materially?+
They are the two largest swing factors after headcount. Compensation, real estate and attrition all vary by city, and role mix changes the average seniority you are buying. This is why NirjiX does not publish a universal per-seat benchmark: an averaged figure is usually wrong in both directions at once, overstating cost for junior-weighted centres and understating it for senior engineering builds.
We've built and run these, not just advised on them.
Bring us your role plan and your retained cost base, and we will price all six layers against your own data — then tell you where the model breaks.