How to set up a GCC in India: a practical timeline

Most conversations about setting up a Global Capability Center in India start with cost and end with confusion about timing. The honest answer is that a GCC has two clocks running at once: the clock on standing up the entity, and the clock on standing up the team. They overlap, and conflating them is why so many plans slip.

Here is how the phases actually sequence.

The two clocks

Entity readiness covers location selection, legal setup, compliance, and infrastructure. This is largely serial work with external dependencies — registrations, approvals, banking — and it sets the floor on your timeline.

Team readiness covers hiring, onboarding, and integration with your existing processes. Once a pipeline is running, onboarding a specialist onto an established team takes about 6 weeks. That number is not the same as standing up the center itself, and treating them interchangeably is the most common planning error we see.

Realistically, GCC operations reach operational startup in 90+ days. Scaling from a first cohort to 50+ specialists has taken us under 120 days, but that assumes entity work started early rather than after the hiring plan was approved.

Phase 1 — Location, entity, and compliance

Location selection is not just a cost exercise. It determines your talent pool depth, your attrition exposure, and which compliance regime you operate under. Cube27 runs its own delivery hub in Pune, which is also where we operate client centers.

Work in this phase:

• Location and site selection against the actual skill mix you need
• Legal entity setup and statutory registrations
• Compliance framework, including data and IP protection
• Infrastructure and network readiness

This phase gates everything downstream. Start it first.

Phase 2 — Talent and culture

A GCC fails quietly when it becomes a separate company that happens to share a logo. The teams that work are the ones deliberately aligned to the parent’s culture, processes, and architecture — not just its ticket queue.

This is also where retention is won or lost. Cube27 runs under 10% annual attrition, which matters less as a recruiting statistic than as a knowledge-continuity one: the engineer who understood your integration edge cases is still there next year.

Phase 3 — Operate and measure

Once the team is live, the center needs the same operational discipline as any other part of your business: defined SLAs, coverage windows, and escalation paths. We run 95% enterprise SLA and 24/7 coverage across NORAM, EMEA, APAC, and India, because a center that only overlaps with headquarters for two hours a day is a handoff problem, not a capability.

Choosing an engagement model

Two models cover most situations:

• Build-Operate-Transfer (BOT) — we establish and run the center, then transfer it to you as a going concern. Choose this when in-house ownership is the destination and you want the setup risk carried by someone who has done it before.
• Build-Operate (BO) — we establish and continue operating it. Choose this when the capability matters more than the org chart.

Both give you an extended team and outcomes rather than billable hours. The transfer option in BOT is real, not theoretical — it should be priced and planned from day one, not bolted on later.

What actually causes slippage

In our experience, delays cluster in three places: entity work started too late, a hiring plan written against job titles instead of the actual skill mix, and no agreed definition of “operational.” Fix those three and a 90-day startup is a plan rather than a hope.

---

Cube27 builds and operates dedicated Global Capability Centers through BOT and BO engagements. Talk to a Solutions Architect about your setup.