GCC Setup Readiness
By Akkul Dhand · Published 26 October 2026
Test whether an India capability centre has a credible operating case before committing to the setup.
Who this is for: Business sponsors assessing a captive capability centre in India, including teams considering their first overseas operation.
A location and a hiring plan are not an operating model. Start with work, ownership and the reason for bringing capability in-house.
1. Diagnose before acting
Answer each question with a concrete example or piece of evidence. Mark unknowns openly. This is a discussion aid, not a validated scoring instrument.
- What capability will the centre own beyond providing additional headcount?
- Is the work stable and documented enough to transfer?
- Who in the parent business owns service demand and acceptance?
- Have transition, management, technology and resilience costs been included?
- Is there a named India leader with authority and sponsor access?
2. Put the method to work
1. Define the mandate
State which business outcomes the centre will support, which capabilities it will own and what remains with the parent organisation. Compare a captive centre with the status quo and other delivery options. Record assumptions instead of presenting the preferred option as inevitable.
2. Assess work readiness
Map process volumes, complexity, exceptions, systems, data sensitivity and knowledge concentration. Choose a pilot with a reachable outcome and a stable handoff. Resolve unclear process ownership before transferring the confusion across borders.
3. Model the full cost
Include recruitment, leadership, transition overlap, training, technology, facilities, specialist advice, travel, security and business continuity. Model ramp-up and slower hiring. Keep steady-state economics separate from the first-year cash requirement.
4. Design governance and transition
Name the executive sponsor, parent process owners and India operating leader. Define service measures, decision rights, escalation routes and acceptance gates. Obtain qualified advice for applicable entity, employment, tax, transfer-pricing, data and sector obligations before commitments.
5. Use readiness gates
Approve discovery, setup, pilot and expansion separately. Require evidence for each gate: funding, leadership, access, training, controls and service acceptance. Run parallel delivery where needed and retain a tested rollback or continuity route.
3. A worked example
Illustrative example: a parent business proposes transferring an entire finance support team. Process mapping reveals that exceptions rely on one individual and source data is inconsistent. The sponsor narrows the pilot to one documented workflow, assigns a parent owner and delays expansion until service quality and reconciliation pass the agreed gates.
4. Working sheet
The first row shows how to fill this in. Use the blank rows for your own business. Add evidence links and review dates to your working copy.
| Readiness area | Evidence required | Gap | Accountable owner | Gate decision |
|---|---|---|---|---|
| Knowledge transfer | Pilot SOP, exception log and observed practice | Single-person dependency | Parent process owner | Hold expansion until backup demonstrates delivery |
5. Action plan
- Week 1: agree mandate, alternatives and sponsor.
- Week 2: map candidate work and build a full-cost scenario.
- Week 3: resolve leadership, security and specialist-review gaps.
- Week 4: decide whether to proceed to a bounded pilot, revise the case or stop.
6. Check whether it worked
- Critical readiness items closed with evidence, not merely marked green.
- Pilot quality, turnaround and exception rates against agreed acceptance criteria.
- Actual ramp-up spend and capacity against the scenario.
This is an operating readiness guide, not legal, tax or location-selection advice. A low salary estimate cannot compensate for an unclear mandate, weak sponsorship or uncontrolled data access.
What you should leave with: A sponsor-owned business case, readiness register and evidence-based pilot decision.