A GCC proposal that shows savings in Year 1 is usually the first one a board sends back. Directors have approved enough offshore plans to know the first twelve months cost more than the status quo. A deck that hides that tells them every other number is optimistic too. This GCC business case template is built for the opposite reaction: a board that sees the downside first and approves anyway.
Appetite for capability centers is not the constraint. Your competitors are already in India, and your board has read the headlines. What slows approval is the document itself.
Most proposals arrive as a cost arbitrage slide dressed in strategy language. They compare an Indian salary to a US salary, multiply by headcount, and call the difference ROI. Boards distrust that math because it skips the productivity ramp, the leadership layer, the months of dual running, and the transfer pricing setup finance will ask about in the first five minutes.
So this guide does not give advice about the deck. It gives you the deck. You get six slides in the order a board reads them, a 3-year financial model for a 100-seat engineering center with every assumption labeled, a sensitivity check that shows what breaks the case, and the exact decision to ask for. Swap in your own inputs and the structure holds.
The numbers are deliberately conservative. In the model, a captive center loses money against a vendor in Year 1 and roughly breaks even against onshore hiring. That is the point. A GCC business case template that survives honest Year 1 numbers is one a CFO will sign.
As of FY26, India hosts 2,117 GCCs across 3,728 units with roughly 2.36 million employees, and an estimated 506 Forbes Global 2000 companies run operations there. Total ecosystem revenue is $98.4 billion. The same report found that 96% of GCCs set up after FY21 launched with product or portfolio mandates from day one.
TL;DR
This is a board-ready GCC business case template for CFOs, CTOs, and strategy leads seeking approval for an offshore capability center. It follows the six-slide order boards read: problem, options, recommendation, financials, risks, and decision requested.
The headline number: in our illustrative 100-seat model, a captive center costs about $12 million over three years. The same output hired onshore costs about $29 million. Against a vendor, the gap shrinks to $2.8 million, and Year 1 runs $1.7 million behind.
By the end, you will know which comparator to lead with. You will know how to build a GCC ROI model that survives finance review. And you will know how to ask for stage-gated capital instead of one large cheque.
What Is a GCC Business Case Template?
A GCC business case template is a structured decision document that lets a board approve, reject, or stage-gate investment in a Global Capability Center. It states the business problem, compares sourcing options, recommends one, models three years of cost and output, lists risks with mitigations, and ends with a specific, time-bound decision request.
Why a Capability Center Business Case Gets Sent Back
Boards rarely reject GCCs on strategy. They reject the arithmetic. Three gaps show up in almost every capability center business case that comes back for rework.
The comparator is rigged. Comparing a loaded India cost to a $150,000 US engineer produces a huge saving on paper. But the board’s realistic alternative is often a vendor already delivering from India. In our model, the same center that shows 59% savings against onshore hiring shows only 19% against a vendor over three years.
Year 1 is presented as a savings year. Setup, dual running, and ramp-up mean the first twelve months cost as much as or more than the status quo. In the model below, Year 1 captive spend is $3.31 million against $3.15 million for equivalent onshore output.
The cost line is a salary, not a loaded cost. EY’s benchmarking put overall cost per FTE in India GCCs at ₹23.9 lakh per annum in 2022, up from ₹17.0 lakh in 2019. Workforce accounted for ₹20.3 lakh of that, with facility, IT, travel, and admin making up the rest. A fully loaded cost per FTE is the only honest input, and engineering-heavy centers carry skill premiums on top.
Each gap on its own is fixable. Together, they tell the board the author was selling, not analyzing. The GCC business case template below closes all three by leading with the honest comparator.
The GCC Business Case Template, Slide by Slide
Six slides, in this order. Every GCC board presentation that clears on the first pass follows some version of it. The sequence mirrors how directors reason: what is broken, what else could fix it, why this option, what it costs, what could go wrong, and what exactly you want from them.
How to Build a GCC Business Case for the Board
- Define the capability gap in business terms. Use open roles, time-to-fill, and roadmap slippage, not “we need to scale.”
- Pick the honest comparator. Model the vendor option, not just onshore hiring.
- Shortlist four sourcing models. Onshore expansion, vendor or managed services, build-operate-transfer, and an own-entity captive.
- Build a three-year model with labeled assumptions. Every input needs a source or a clear “planning assumption” label.
- Stress-test the three inputs that move the answer. These are productivity ramp, attrition, and wage inflation.
- Write the decision as a stage-gated task. Release capital against milestones, not all at once.
Slide 1: The Problem, Not the Solution
Do not mention India or a GCC on this slide. Quantify the gap first. A strong version reads like this: 42 open engineering roles, a median time-to-fill of 94 days, and a platform roadmap two quarters behind. These are example figures; use your own.
The board should agree the problem is real and expensive before it sees a solution. If they do not accept Slide 1, nothing after it matters.
Slide 2: Options Considered
Show four options with one line each on cost, speed, control, and exit flexibility. Include managed services and build-operate-transfer (BOT) even if you plan to reject them. A deck with one option reads as a decision already made, and boards push back on that instinctively.
This is the slide most drafts skip. A GCC business case template without a credible vendor option invites the audit committee to build that comparison themselves, usually with less favorable assumptions.
Slide 3: The Recommendation
One sentence, then three reasons. For example: “Establish a 100-person engineering GCC through our own Indian entity, with an employer-of-record bridge while incorporation completes, typically 2–3 months.”
Lead the reasons with strategy, not cost. Ownership of IP, control over the capability roadmap, and building AI and platform depth in-house tend to carry the room. Cost is the third reason, not the first. If you are still weighing entity models, independent GCC setup services or IT consulting services can validate the choice before you commit it to a slide.
The GCC ROI Model: Three-Year Financials for a 100-Seat Center
Slide 4 is where the GCC financial justification lives or dies. Present it as three views: assumptions, the three-year comparison, and sensitivity. Every figure below is an illustrative planning input. Replace each with your own quotes and salary benchmarks before the deck goes to the board.
The Assumptions Slide
| Input | Planning assumption |
| Headcount (average) | Year 1: 35, Year 2: 80, Year 3: 100 |
| Loaded cost per FTE, excluding site leadership | $35,000 (about ₹30 lakh at ₹85/USD), rising 8% a year |
| Site leadership and G&A layer | $0.50M in Year 1, rising to $0.60M |
| One-time setup (entity, fit-out, IT, legal) | $1.0M |
| Transition and dual running | $0.40M in Year 1, $0.20M in Year 2 |
| Recruitment and backfill | $3,000 per hire, 12% annual attrition |
| Productivity vs a fully ramped team | Year 1: 60%, Year 2: 85%, Year 3: 95% |
| Onshore comparator | $150,000 loaded per engineer, rising 4% a year |
| Vendor comparator | $40/hour blended × 1,880 hours, about $75,000 per FTE-year, rising 5% a year |
The ₹30 lakh loaded figure sits above EY’s 2022 benchmark deliberately. It reflects four years of wage growth and the premium for engineering, cloud, and AI roles.
The Three-Year View (USD millions)
| Line item | Year 1 | Year 2 | Year 3 | Total |
| Captive GCC total cost | 3.31 | 3.92 | 4.73 | 11.96 |
| Onshore cost for equal output | 3.15 | 10.61 | 15.41 | 29.17 |
| Vendor cost for equal output | 1.58 | 5.36 | 7.86 | 14.80 |
| Net saving vs onshore | (0.16) | 6.69 | 10.68 | 17.21 |
| Net saving vs vendor | (1.73) | 1.44 | 3.13 | 2.84 |
Comparators are priced on productive output: 21, 68, and 95 FTE-equivalents across the three years. That adjustment is what makes the model credible, because it stops the captive center from getting credit for engineers who are still onboarding.
Read the bottom two rows together. Against onshore hiring, the payback period lands just past month 12. Against a vendor, it lands around month 25. Put both on the slide. A GCC business case template that shows only the first row is a sales document. One that shows both is a total cost of ownership analysis, and boards know the difference.
Sensitivity: What Breaks the Case
Three inputs move the answer more than anything else.
- Productivity ramp. If Year 1 productivity is 40% instead of 60%, productive output falls from 21 to 14 FTE-equivalents. Year 1 cost per productive FTE rises from about $158,000 to $236,000, and the Year 1 gap against the vendor widens to $2.26 million.
- Attrition. At 20% instead of 12%, direct backfill cost barely moves, about $24,000 more in Year 3. The real hit is lost output. Eight extra exits with four-month re-ramps cost roughly $220,000 a year, valued at vendor rates.
- Wage inflation. At 12% instead of 8%, Year 3 run cost rises from $4.08 million to about $4.39 million. The case survives, but the vendor gap narrows.
Show this slide even if nobody asks. It answers the question that sinks most decks: “What happens to this number if the first 30 hires take nine months instead of four?”
Slides 5 and 6: Risks, Mitigations, and the Decision Requested
Slide 5: Risks and Mitigations
List five or six risks, each paired with a named owner and a specific mitigation.
- Hiring ramp slips. Start sourcing before the lease is signed and use a specialist partner for volume roles. Supersourcing, for instance, typically delivers interview-ready shortlists in 7–10 working days, with a 98% candidate joining rate. Dedicated RPO services can run the ramp while your internal HR team is still being built.
- Site leader hired late. Hire the site head first, before the office. A center led by an interim manager from headquarters loses 2–3 months of hiring momentum.
- Transfer pricing exposure. Set up a cost-plus inter-company arrangement backed by a transfer pricing study in Year 1. Retrofitting it after a tax audit costs far more than doing it at incorporation.
- Knowledge transfer resistance. Parent-team engineers slow-walk handovers when they read the GCC as a replacement plan. Frame it as capacity expansion and tie parent-team leads’ goals to the GCC’s ramp milestones.
- Niche skill competition. EY’s 2025 pulse survey found 58% of India GCCs already investing in agentic AI, with another 29% planning to scale within a year, so AI and cloud talent is contested. Budget a premium, and plan early if you need to hire cloud engineers at senior levels.
- IP and data security. Assign IP to the parent through the entity’s employment contracts, and put an ISO 27001 roadmap on the risk register from day one.
Slide 6: The Decision Requested
End with a sentence the board can vote on. Vague asks like “approve the GCC strategy” get deferred. A specific task gets decided.
A working version: “Approve $3.3 million for Year 1, released in three gates.” Gate 1, at month 3, requires an incorporated entity, a hired site leader, and 15 hires. Gate 2, at month 6, requires 40 hires and measured productivity of at least 50%. Gate 3, at month 12, requires 60 heads and productivity of at least 60%, which triggers the Year 2 budget.
Stage-gated funding turns a large, irreversible bet into a series of small, reviewable ones. That is the single biggest lever for moving a hesitant board to yes. It also makes the GCC business case template self-auditing, because every gate is a checkpoint against the model.
Two Board Reviews, Two Outcomes
These are illustrative scenarios built on the model above, not client disclosures.
Scenario A: the case that got deferred. A mid-market SaaS company’s first draft led with 59% savings against onshore hiring and showed no vendor comparison. The audit committee built one itself, found the $1.7 million Year 1 gap the deck had omitted, and deferred the decision by a quarter. The resubmitted GCC business case template led with the vendor view and stage-gated the capital, and it was approved in one session.
Scenario B: the case that got approved the first time. An enterprise weighing BOT against its own entity showed both, plus the sensitivity slide, and asked for Gate 1 funding only. The board approved $1.2 million for the first six months against clear hiring and productivity targets. It released the rest of Year 1 when Gate 2 was met.
Board Approval for an Offshore Center: Choosing the Model
Use this table on Slide 2, or as a backup slide. Timelines are typical ranges, and cost figures come from the model above.
| Model | Time to first productive team | 3-year cost (100 seats) | Control and IP | Best fit |
| Onshore expansion | Depends on local market; often 3–4 months per senior role | ~$29.2M | Full | Small teams, roles that must sit near customers |
| Vendor or managed services | 4–8 weeks | ~$14.8M | Contractual | Short horizons, uncertain scope |
| Build-operate-transfer | 2–3 months | Between vendor and captive, plus a transfer fee in Years 2–3 | Full after transfer | First-time GCC builders who want an exit ramp |
| Own-entity captive | 4–6 months | ~$12.0M | Full from day one | Long horizons, core product or IP work |
BOT is the most underrated option on this list. It trades some Year 1–2 margin for speed and a partner who absorbs setup risk. That makes it the easiest model to get through a cautious board.
What Most Teams Get Wrong
The most common error in a GCC business case template is benchmarking the center against onshore salaries. Boards already know India is cheaper than San Francisco. What they are actually asking is whether owning the capability beats renting it.
If your case only works against onshore cost, it is a cost arbitrage pitch, not a business case, and finance will find the vendor comparison on its own.
Three other patterns show up repeatedly:
- One blended rate for every role. A center with 15 senior architects and 85 mid-level engineers does not cost 100 × the average. Model at role-family level, or the pyramid surprises you in Year 2.
- Leadership last. Teams hire engineers first to show momentum and hire the site head in month five. The site leadership layer should be the first line item filled, not the last.
- All capital up front. Asking for three years of funding in one vote maximizes the board’s perceived risk. Asking for Gate 1 minimizes it.
The fix for all three is the same: show the board the version of the model you would want to see if you were the one signing.
Before Your Board Pack Goes Out
If your GCC board presentation is six weeks away and the financials still rest on a single salary comparison, that is the slide to fix first.
Supersourcing has spent 10+ years helping enterprises hire, scale, and set up capability centers, and our team can review your assumptions, rebuild the comparator view, and model the hiring ramp against real sourcing data.
Send the draft deck to mayank@engineerbabu.com, or book a working session. We’ll tell you which slide the board is most likely to push back on, and why.
Frequently Asked Questions
What should a GCC business case template include?
It should include six sections: the business problem, options considered, the recommendation, three-year financials, risks with mitigations, and the decision requested. The financials need labeled assumptions, comparisons against both onshore hiring and a vendor, and a sensitivity view. A GCC business case template without the vendor comparison or sensitivity analysis usually comes back for rework.
How long does it take for a GCC to break even?
It depends on the comparator. In our illustrative 100-seat model, payback against onshore hiring lands just past month 12, while payback against a vendor lands around month 25. Slower productivity ramps or higher attrition push both dates out, which is why the sensitivity slide matters as much as the base case.
What does a GCC cost per employee in India?
EY’s benchmarking put overall cost per FTE at about ₹23.9 lakh per year in 2022, with workforce making up roughly 85% of it. Engineering-heavy centers in 2026 should plan higher. Our model uses about ₹30 lakh loaded, excluding site leadership, to reflect wage growth and skill premiums for cloud and AI roles.
Should a GCC start with build-operate-transfer or its own entity?
BOT suits first-time builders who want speed and a partner absorbing setup risk, with ownership transferring in Years 2–3. An own entity suits companies with long horizons, core IP work, and internal capacity to run incorporation, compliance, and hiring. Many boards approve BOT more readily because it limits Year 1 exposure.
What do boards ask most often about GCC proposals?
Expect four questions: what the vendor alternative costs, what happens if hiring runs slow, who leads the center, and how capital is staged. Answer all four in the deck before anyone asks. A proposal that anticipates them signals the author has already stress-tested the plan.
How do you calculate GCC payback period?
Subtract annual captive cost from the cost of equivalent productive output under your comparator, then track the cumulative figure month by month until it turns positive. Price the comparator on productive output, not headcount, so the captive center does not get credit for engineers still ramping up.
Can we pressure-test our GCC business case before the board meeting?
Yes, and you should do it at least two weeks before the board pack is due. An outside review of the assumptions, comparator pricing, and hiring-ramp plan usually surfaces the questions directors will ask. Firms that run GCC setups regularly can benchmark your inputs against live hiring data for your target city.
