How to set up a GCC in India: a step-by-step roadmap

Setting up a global capability center in India generally takes 6-10 weeks to first hires when using a build-operate-transfer partner's existing entity, or 4-6 months when incorporating your own entity from scratch. The steps are the same either way: entity and compliance setup, hiring pipeline, office or infrastructure, and a ramp-up period before the center reaches steady operational output. What changes is who does the work and how much of it happens in parallel.

Step 1: Entity registration and compliance

If you're going it alone, this is where most of the calendar time goes. Incorporating a wholly owned subsidiary in India (typically a private limited company) involves registering with the Ministry of Corporate Affairs, obtaining a PAN and TAN for tax purposes, setting up GST registration if applicable, and registering for statutory employer obligations: Provident Fund (PF), Employee State Insurance (ESI) where it applies, and professional tax registrations that vary by state.

Realistically, this stretches 8-16 weeks on its own before you can legally run payroll. A build-operate-transfer partner skips this entirely for your first hires, because you're operating under their already-registered entity while your own incorporation runs in parallel, if you're planning an eventual transfer.

Step 2: Hiring pipeline and initial team

Once you can legally employ people (or are operating under a partner's entity), hiring starts. India's talent pool is deep, particularly in Ahmedabad, Bangalore, Pune, and Hyderabad, but a serious pipeline needs sourcing channels, a structured interview process calibrated to your actual bar, and competitive offers benchmarked to local market rates, not home-country rates translated at exchange rate.

For a first cohort, realistic timelines run 3-6 weeks per hire for mid-to-senior technical roles once the pipeline is warm, faster if a partner has an existing bench of pre-vetted engineers.

Step 3: Office and infrastructure

Some GCCs start fully remote and add physical space later. Others need a registered office address for compliance purposes from day one, even if it's a small serviced office rather than a full campus. Decide this early because it affects your entity registration paperwork and your hiring pitch. Many candidates in India still weigh hybrid or in-office options heavily when comparing offers.

Step 4: Operational ramp-up

A center with 5 people behaves differently than one with 50. The ramp-up phase, typically the first 6-12 months, is where you build management layers, define who reports to whom, set up local HR and IT support, and establish the communication cadence with headquarters that keeps the center genuinely integrated rather than operating as a silo.

Realistic timeline

Common mistakes going it alone

Companies that skip a build-operate-transfer partner and self-run from day one most often underestimate three things: compliance timelines (registrations take longer than a website checklist suggests), local hiring market dynamics (compensation benchmarks, notice periods that run 30-90 days in India, and counteroffers), and the management overhead of running HR, payroll, and IT support for a location the leadership team has never operated in before.

Why the BOT model exists

A build-operate-transfer arrangement front-loads the operational risk onto a partner who already has the entity, the compliance processes, and the local hiring relationships in place. You get engineers working within weeks instead of months, and a clear contractual path to transfer full ownership, IP, and management control once the center is stable, typically 12-24 months in. It's the difference between learning Indian labor compliance by trial and error and inheriting a working system.

If you're evaluating whether to build alone or with a partner, start by reading through what a global capability center engagement actually covers, and separately look at hiring developers directly if your near-term need is smaller than a full center.

The compliance calendar you inherit

Registering the entity is a milestone, not the finish line. An Indian employer runs on a monthly statutory rhythm: provident fund and state insurance contributions with fixed deposit deadlines, tax deducted at source on salaries remitted monthly and reconciled quarterly, GST filings if the entity invoices services, and professional tax in many states. Annually there are financial statements, statutory audit, and corporate filings. None of it is exotic, but each missed deadline carries penalties and all of it lands on whoever runs the back office, which is precisely the function a build-operate-transfer partner exists to carry.

Budget lines first-time builders underestimate

Salaries are researched carefully and the rest gets hand-waved. The items that surprise: employer-side statutory contributions on top of gross salaries, a real recruiting cost per hire whether paid to agencies or carried as internal effort, IT hardware and licenses per seat, office deposits that commonly run several months of rent, an annual compliance and audit budget, and attrition backfill, because even a sticky team loses people and every replacement costs a hiring cycle. Building the model with these lines from day one keeps the year-one number honest and the year-two comparison against outsourcing meaningful.

What to keep at headquarters vs move to the center

The centers that work are built around whole capabilities, not leftover tasks. Product strategy, pricing, and anything that changes weekly through customer conversations stays close to the market. What moves well: platform and product engineering with clear ownership, QA and release engineering, data engineering, internal tooling, and support engineering that follows the sun. The test for any function is simple: can success be defined and measured without someone at headquarters translating daily? If yes, the center can own it outright, and outright ownership, not task execution, is what makes GCC economics work.

The first hire matters more than the first office

Everything in the ramp compounds from the anchor hire: the senior engineer or engineering manager who sets the bar for everyone who follows. Strong anchors attract former colleagues, cutting recruiting costs for the next several hires, and they carry your engineering culture into every interview. Weak anchors do the opposite and the damage takes a year to undo. This is why experienced builders spend disproportionate time and money on the first two or three people, sometimes months, while treating office decisions as easily reversible. An office lease can be changed in a quarter. A center that hired its first ten people against the wrong bar is a rebuild, not a fix.