Timeline to Launch a GCC in India: The Critical Path
The timeline to launch a GCC in India, milestone by milestone: the 2026 statutory clocks, notice-period math, and how BOT and BO models move the dates.
By Arpan Jain, Chief Executive OfficerUpdated November 8, 2026GCC, Build-Operate-Transfer, India, Operations, Pune
The timeline to launch a GCC in India depends on what you count as “launched” and who owns the entity. On a partner’s existing entity (BOT or BO), a first team can be seated in about 8 to 12 weeks. A new captive takes 3 to 6 months for a focused center, and the India leader’s hire and notice period usually decide where in that range you land.
Published estimates for the same question run from about six weeks to 18 months. Most of the gap comes from definitions. One guide counts the day the entity is filed, another the day the first engineer sits down, and others the first accepted deliverable or a center at steady state. Build-Operate-Transfer (BOT) and Build-Operate (BO) also take some clocks off the client’s plan, which moves the dates again.
Regulatory status as of November 2026. Confirm each statutory step with Indian counsel before you file.
Timeline to launch a GCC in India by operating model
| Model | Who carries the legal-employer clocks | What still sets your date | Published ranges |
|---|---|---|---|
| Build-Operate (BO) | Partner’s existing entity, ongoing | Notice periods, HQ security and access approvals | Starts like a BOT build phase, with no transfer event |
| Build-Operate-Transfer (BOT) | Partner’s entity until transfer | Same as BO, plus a transfer project later | First team in 8-12 weeks; transfer at 12-24 months |
| Captive / wholly owned subsidiary | You | Resident director, incorporation, registrations, leader hire, notice periods | 3-6 months focused, 6-12 months enterprise |
| EOR bridge | Employer-of-record provider | Notice periods, plus a later move to your own entity | Pilot from about 6 weeks |
The ranges are other publishers’ estimates, quoted as published. Few of them say which milestone they measure, so use them for orientation and not as a board date.
What “launched” means: go-live vs steady state
A GCC has several launch dates, and a different party controls each one. Naming them lets every date be pinned to a specific event.
| Milestone | Definition | Who controls the clock |
|---|---|---|
| M0 | Charter signed: scope, year-one and year-three headcount, model, city, and the definition of steady state | Client HQ |
| M1 | Legal employer ready: partner entity (BOT/BO) or your own entity with payroll and registrations (captive) | Partner, or you plus government |
| M2 | India leader seated | Candidate notice period |
| M3 | Operational startup: first cohort seated with laptops, VPN/VDI and system access approved, and working | Notice periods and client security |
| M4 | First accepted deliverable against the agreed scope | Client product owners |
| M5 | Steady state: SLA met for an agreed number of consecutive weeks at target headcount | Partner and client |
| M6 (BOT only) | Transfer complete: entity or shares, people, contracts, assets | Client, partner, RBI and MCA filings |
Quote every date against a milestone. For most boards, M3 or M4 is a fair definition of launch, and M5 is the point where the center stops being a project.
Measured on this ladder, our own GCC engagements typically reach operational startup (M3) in 90+ days, and we have scaled teams from 5 to 50+ specialists in under 120 days. Both figures assume entity and compliance work starts at M0, before the hiring plan is approved.
Write down what M5 means at M0. Without an agreed definition of steady state, nobody can say whether a center is on time or late, and a short plan can slip for months before anyone notices.
Two clocks: the legal employer and the team
Standing up a GCC means running two schedules at once. The first is the legal employer: city, entity, registrations, compliance, office and network. Much of that work happens in sequence and waits on government portals, banks and other outside parties. On a captive it puts a floor under the whole timeline.
The second is the team: the leader hire, cohort hiring, notice periods, onboarding, and getting new people working inside the parent’s processes and systems.
Why treating them as one causes slippage
Plans often assume incorporation is the slowest item. Published estimates put entity work in weeks, while a senior hire who has to serve notice takes months. If the leader search waits for the entity, the two schedules run one after the other. Open the entity work and the leader search in the same fortnight, at M0, and they overlap.
The critical path in the timeline to launch a GCC in India
Weeks 0 to 4: charter, city, model and the leader search
Sign the charter (M0) and open the India leader search in the same weeks. One published estimate puts hiring a GCC head at 8 to 16 weeks. Zinnov recommends having the leader in place before the first hires join, so they can set hiring standards and build relationships with HQ before delivery pressure starts.
The city choice (Bengaluru, Hyderabad, Pune, Chennai, NCR or Mumbai) decides how deep the talent pool is for your skill mix, how much attrition you face, and which state’s registrations and incentives apply. Build the hiring plan from the skills each workstream needs. A plan built from a list of role names tends to fill seats fast with the wrong people.
Entity and registrations (captive only)
Identify the resident director before anything is filed. The SPICe+ filing then bundles incorporation with several registrations. Published incorporation estimates are mostly in weeks: 1 to 3 weeks in one guide, 2 to 4 weeks via SPICe+ in another. Several statutory deadlines start running once the entity exists.
Under BOT or BO, this whole block runs on the partner’s existing entity and stays off your path.
Workspace and IT security access
According to JLL, GCCs took 41.7% of India’s office leasing in H1 2026, and flex leasing reached a record 10.23 million sq ft over the same six months. Workspace estimates depend on the route. A ready office is put at 4 to 8 weeks, while a custom fit-out adds 12 to 16 weeks. Flex space suits the first cohort, and the fit-out decision can wait until headcount is predictable.
HQ security is often slower than the office: VPN or VDI, device policy, and access to repositories and production systems. Name the approvers at M0, because an engineer who is seated but has no system access is paid while no work gets done.
Hiring: the notice-period math
The best numbers on notice periods are dated (published in 2022, updated in 2024), so read them as directional. Analytics India Magazine found that about one in three IT roles carry a 90-day notice period, rising to 43% for experienced IT staff with 14+ years. Across India Inc., 54.1% of jobs had a notice period of one month or less.
Apply those figures to the leader hire. The search starts in week 0 and takes 8 to 16 weeks to an accepted offer. A 90-day notice period, common at senior level, adds about 13 weeks, so the leader is seated around weeks 21 to 29 (M2). That is roughly five to seven months, at or past the top of the 3 to 6 months quoted for a focused captive. On a captive the leader therefore sets the critical path, unless the search opens before entity work or a partner supplies interim leadership. The 8 to 16 week figure may already include notice, in which case the real number is shorter.
Mid-level engineers are put at 4 to 8 weeks to hire, plus notice where it applies. An 8 to 12 week first team is only possible when a partner already has a pipeline running.
Onboarding is its own clock, separate from sourcing, notice and standing up the center. In the Build-Operate engagement described below, onboarding took 6 weeks, and that figure covers onboarding alone.
First cohort to steady state
Getting from M3 through M4 to M5 takes the same operating discipline as any other business unit: defined SLAs, coverage windows and escalation paths. We run to a 95% enterprise SLA with 24/7 global coverage. If the India team overlaps with headquarters for only two hours a day, most work ends up waiting overnight for an answer.
Statutory clocks you can’t compress
These apply to a captive entity, and to your entity at BOT transfer.
| Clock | Rule (paraphrased) | Effect on the plan |
|---|---|---|
| Resident director | At least one director who stayed in India 182+ days in the relevant period (Section 149(3)). Published summaries differ on whether that is a calendar or financial year | Identify before filing. Under BOT/BO the partner usually holds this seat until transfer |
| SPICe+ | One MCA filing covers name, incorporation, DIN, PAN, TAN, EPFO, ESIC, Maharashtra Profession Tax, bank account and optional GSTIN (Professional Utilities) | Removes several separate registrations. Processing estimates vary, so plan with buffer |
| Share allotment | Allot within 60 days of receiving application money, or refund it within the following 15 days (Treelife) | Time the parent’s capital wire to the board’s ability to allot |
| FC-GPR | File on RBI’s FIRMS portal within 30 days of allotment. Late filing means a Late Submission Fee or compounding (Treelife) | Does not block go-live, but needs an owner and a date |
| GST, standard route | Approval within 7 working days, or within 30 days with physical verification if Aadhaar authentication isn’t done or the applicant is risk-flagged (CGST Rule 9) | Plan for 30 days if signatories can’t authenticate |
| GST, Rule 14A | From 1 Nov 2025, eligible small B2B registrants (output tax up to ₹2.5 lakh a month) are registered within 3 working days or deemed approved (TaxGuru) | Check eligibility with a GST adviser |
| FC-TRS | File within 60 days of the share transfer or the receipt or remittance of funds, whichever is earlier (TaxGuru) | Applies to a BOT transfer done by share sale |
Two of these often catch teams out. Foreign-national signatories frequently can’t complete Aadhaar authentication, which moves GST registration from the 7-working-day path to the 30-day one, so check signatory status before you apply. The 60-day allotment clock starts when the capital lands, whether or not the board is ready to allot, so schedule the wire around the board calendar.
What changed in 2025-26 for GCC setup in India
Labour Codes in force since 21 November 2025
All four Labour Codes (wages, industrial relations, social security, and occupational safety) came into force on 21 November 2025, replacing 29 laws, according to PIB. They add no delay by themselves, but offer letters, payroll structures and policies drafted before November 2025 need rewriting before your first offer goes out.
DPDP Rules: phase-in to around May 2027
The DPDP Rules were notified on 14 November 2025 with an 18-month phased compliance period, which puts full compliance around May 2027. Requests from data principals must be answered within 90 days at most.
A center that launches in 2027 goes live as those obligations take full effect, so build consent, breach and rights-request processes into setup. In EY’s 2025 survey, concern about compliance complexity and data privacy rose to 42% from 32%.
Budget 2026-27 IT safe harbour
Budget 2026-27 put software development, ITeS, KPO and contract R&D into a single IT Services category with a 15.5% safe harbour margin. The eligibility threshold rose from ₹300 crore to ₹2,000 crore, a company can stay on the safe harbour for five years at a stretch, and unilateral APAs for IT services are to be concluded within about two years.
Transfer pricing was the top regulatory concern for 63% of GCCs in EY’s survey. The safe harbour should make the intercompany agreement quicker to settle, both under BOT or BO and after a transfer.
GST Rule 14A fast-track registration
The 3-working-day route applies only below the output-tax threshold in the statutory table. Some smaller centers may qualify; confirm eligibility before you plan around it.
BOT vs BO: which clocks the partner removes
Most centers are still run directly by their parent. EY found that 84% operate in-house, with outsourced operation up from 8% to 12%. Where BOT saves time depends on which clocks the partner carries.
| Clock | Captive / WOS | BOT (build-operate phase) | BO | BOT transfer phase |
|---|---|---|---|---|
| Resident director, incorporation, allotment, FC-GPR | You | Partner’s existing entity | Partner | Back with you: new entity or share purchase, FC-TRS within 60 days |
| GST, PF/ESIC, Profession Tax, Shops Act | You | Partner | Partner | You, if a new entity |
| Workspace and IT build | You | Partner builds; you approve security | Partner builds; you approve security | Lease and asset assignment |
| Candidate notice periods | You | Still applies | Still applies | Employees move to your entity under the Labour Codes |
| India leader | You | Partner can provide interim leadership | Partner | You appoint or retain |
| HQ decisions, access approvals, intercompany agreement | You | Still yours | Still yours | Yours |
A partner can carry the legal-employer clocks and keep a hiring pipeline warm before you need it. Notice periods and your own security sign-offs stay outside its control.
For a growing commerce and technology company, we set up a center under a Build-Operate model. We handled entity setup, infrastructure and compliance, then recruited teams across product engineering, commerce platforms and operations. Onboarding took 6 weeks, attrition stayed below 10%, and the team grew to 24/7 global coverage, working as dedicated contractors. We deliver both models through Cube27’s GCC-as-a-Service.
Planning the BOT transfer as its own project
M6 has its own timeline, which one published guide places at 12 to 24 months. Tying it to a milestone, such as M5 held for an agreed number of months, removes the dependence on the calendar. The work covers four things: choosing the mechanism (a new client entity, or buying the shares of the partner-held entity, with FC-TRS due within 60 days), moving employees to your entity on Labour-Code-compliant terms, assigning contracts, the lease and assets, and replacing the partner’s resident director.
Price and plan the transfer on day one. Terms added in year two are negotiated against a deadline.
When BO is the better answer
BO fits when you care about the capability more than about owning the entity, and nobody at HQ wants to run Indian entity administration.
Our annual attrition runs under 10%, close to the 9% GCC average EY reported for 2025 (down from 13% in 2023). At that rate, the engineer who learned your integration edge cases is usually still on the team a year later.
Why published estimates range from 6 weeks to 18 months
| Item | Range in published guides | What explains the spread |
|---|---|---|
| Overall launch | ~6-week EOR pilot to 18 months for a captive at scale (Wisemonk); 12-24 weeks (WeWork); 4-12 months (ivalueplus) | M1, M3 and M5 all get called “launch” |
| Entity incorporation | 1-3 weeks (ivalueplus); 2-4 weeks (Wisemonk); 4-6 months for a WOS (Pipal Tree) | Most estimates are in weeks; one is several times longer |
| Workspace | 4-8 weeks (ivalueplus); 6-12 months for a traditional lease (WeWork) | Flex space vs conventional lease and fit-out |
| BOT first team | 8-12 weeks (Plugscale); both 2-3 and 3-6 months in one guide (Pipal Tree) | Whether a pipeline exists; whether notice periods are counted |
| Notice periods | 60-90 days (Wisemonk); 30-90 days (Plugscale) | Seniority |
Market counts vary because the underlying data is of different ages. The current Nasscom-Zinnov figures, with data as of March 2026, show 2,117 GCCs, 3,728 units and 2.36 million people. Pages quoting lower counts are working from older reports.
Launching a GCC in Pune
In Maharashtra the SPICe+ bundle includes Maharashtra Profession Tax, so there is one less separate state filing. The Maharashtra GCC Policy 2025, approved in September 2025, targets 400 new GCCs, 4 lakh jobs and INR 50,600 crore of investment. Its incentives include stamp duty exemption and capital and rental subsidies, and Pune is one of the named hubs. Pune also accounted for 17.7% of India’s gross office leasing in Q2 2026.
Cube27’s global delivery hub is in Pune.
Where GCC setup delays in India come from, and the fix
- Entity work started after the hiring plan was approved. Start the entity, or sign the partner contract, in week 0.
- A late leader search. Open it at M0 and plan for a 90-day notice period.
- A hiring plan built from role names. Define the skill mix for each workstream.
- No agreed definition of steady state. Sign the milestone ladder at M0.
- HQ security and access approvals. Name the approvers and agree device and VDI standards in advance.
- The GST physical verification path. Check signatories’ Aadhaar status first, and budget 30 days if needed.
- A late FC-GPR filing. Assign an owner and a due date on the day of allotment.
Launch-readiness checklist
- Charter signed: scope, headcount, model, city
- Steady state (M5) defined in writing
- Resident director identified, or partner seat confirmed under BOT/BO
- Capital wire timed against the 60-day allotment window; FC-GPR owner named
- GST route chosen and signatories’ Aadhaar status checked
- India leader search open
- Hiring plan written against the skill mix
- HQ security and access approvers named
- Labour-Code-compliant offer letters and payroll structure ready
- DPDP consent, breach and rights-request processes designed
- Intercompany agreement drafted and safe-harbour decision made
- Workspace route chosen, with dates
- BOT transfer trigger, mechanism and price agreed
Cube27 builds and operates dedicated Global Capability Centers through BOT and BO engagements via GCC-as-a-Service. Talk to a Solutions Architect about your setup.