Decision guideIndia GCC Decision Guide
Our position on when a capability center is the right answer, what belongs inside it, what should stay with a partner or at headquarters, and how to build a case finance will accept.
Used for: Deciding whether to proceed at all, before choosing a model or a city.
What it needs
- — Work inventory and its dependency on local context
- — Cost-to-serve and quality baseline today
- — Governance capacity at headquarters
What it produces: A go, defer or partner recommendation with the scope and the value logic attached.
Decision guideCaptive vs BOT vs Managed GCC Decision Guide
A comparison of the four practical entry routes on control, speed to first output, cost profile over time, and what exit actually costs under each — including the transfer terms that decide whether BOT works.
Used for: Choosing an entry route once the decision to build has been taken.
What it needs
- — Required control over IP and people decisions
- — Tolerance for time to first output
- — Appetite for fixed versus variable cost
What it produces: A recommended route with the transfer or exit terms that must be negotiated up front.
ScorecardGCC Location Decision Scorecard
A structured way to rank candidate Indian cities on talent depth for the specific roles being hired, wage trajectory, competitive density, infrastructure and incentive reality — weighted to the scope rather than to a generic index.
Used for: Choosing a city defensibly, and knowing what would make the second choice the right one.
What it needs
- — Role mix and seniority profile
- — Scale trajectory over three to five years
- — Attrition tolerance and wage inflation assumptions
What it produces: A ranked shortlist with the sensitivity that would reorder it.
Design guideAI-Native GCC Design Guide
How to design a capability center around AI-enabled delivery from the start — role architecture, evaluation and assurance capability, and the governance link back to headquarters — rather than staffing a traditional center and adding AI later.
Used for: Designing a new center, or repositioning an existing one whose headcount logic is being eroded by automation.
What it needs
- — Work that AI genuinely changes versus work it does not
- — Assurance and evaluation requirements
- — Headquarters governance model
What it produces: A role architecture and governance design that does not rely on headcount growth for value.