Most enterprises overestimate how long it takes to set up a GCC in India and underestimate how much can be locked in during the first ninety days. With a focused plan, a leadership-ready enterprise can move from board approval to a functioning India center with a small team in business inside one quarter. The plan below is the one we use most often when helping enterprises set up a GCC in India.
Why 90 days matters
A 90-day launch window forces decisions that often drift for months. Entity choice, city choice, leadership hiring, governance setup, and the first delivery mandate all benefit from being decided inside a single, time-boxed sprint. Once these are locked, scaling becomes a hiring and execution problem rather than a strategy problem.
The launch plan has three 30-day phases: foundations, leadership, and first delivery.
Days 1-30: foundations
The first month is about removing structural unknowns. Five workstreams run in parallel.
Entity and tax structure: choose between a private limited company, an LLP, or a branch office. For most enterprises building a long-term capability center, a private limited subsidiary is the right answer because it offers clean governance, full hiring flexibility, and access to standard tax incentives.
City and real estate: shortlist two or three cities. Bengaluru remains the deepest market for engineering, data, and AI. Hyderabad and Pune are strong alternatives, with Chennai and NCR leading in specific functions. Real estate options include managed office space, traditional leases, and SEZ units. Most 90-day launches use managed office space because it removes fit-out time.
Compliance and registrations: PAN, TAN, GST, professional tax, PF, ESI, Shops and Establishments, and STPI or SEZ registration where relevant. Most of this can be parallelized with entity setup using an experienced corporate services partner.
Governance design: define the India board, the reporting line from the India entity to the parent, and the initial set of policies covering data, security, HR, and finance.
Mandate clarity: write a one-page mandate that names the capabilities the India center will own in year one and the capabilities it will not own. This document anchors every later hiring and governance decision.
Days 31-60: leadership
The second month is about hiring the leadership spine. Without senior leadership in place, the center cannot make decisions, set culture, or attract the next layer of hires.
The minimum leadership spine for a new GCC is four roles: a country or site leader, a function or engineering leader aligned to the primary mandate, a head of talent acquisition, and a finance and operations lead. Some centers add a head of legal and compliance early; others share that role with the parent until scale justifies a dedicated hire.
Country leader hiring is the most important decision in the entire setup. The country leader sets the operating culture, owns relationships with the parent, and is accountable for translating mandate into delivery. Most enterprises underinvest here, assuming the country leader will emerge organically. The better path is to lead with this hire and let the country leader shape the next layer.
Leadership hiring in India typically takes 8 to 12 weeks per role. Starting in month two means the leadership spine is in place by the end of month three, which is exactly when the third phase needs it.
Days 61-90: first delivery
The third month is about putting the first delivery team in the field and shipping a visible outcome. This phase proves that the center can execute, not just exist.
The first delivery scope should be narrow, well-defined, and tied to a parent-organization priority. Good examples: a single product pod owning a defined module, a data engineering team standing up a specific platform capability, or an operations team taking over a defined process. Bad examples: open-ended platform engineering with no parent counterpart, or large process transitions that depend on dozens of stakeholders.
Hiring for the first delivery team starts in week six, runs through weeks seven to ten, and onboards in weeks eleven and twelve. Onboarding should include security, tooling, parent-organization context, and a structured ramp into the actual work. The goal is to have the first delivery team shipping inside week thirteen.
What slips most often
Three things slip the 90-day plan in practice. First, entity approvals can take six to ten weeks if not driven in parallel with everything else. Second, country leader hiring can stretch if the enterprise is unclear on the seniority profile required. Third, the first delivery scope can balloon when multiple parent-organization stakeholders try to load work onto the new center.
The fix in each case is the same: time-box the decision, escalate when needed, and protect the launch plan from scope creep.
Cost expectations
A 90-day launch for a GCC in India typically costs between USD 250,000 and USD 600,000, depending on legal, real estate, and advisory choices. This excludes salary costs for the leadership spine, which begin to land in months two and three. By the end of month three, a typical launched center is running at a monthly burn of USD 80,000 to USD 200,000, scaling further as the delivery team grows.
Conclusion
Ninety days is enough time to set up a GCC in India if the enterprise treats the launch as a focused program rather than a slow planning exercise. Foundations in month one, leadership in month two, and first delivery in month three is a proven sequence. The centers that follow it ship their first visible outcome inside the first quarter and earn the right to scale into a strategic capability platform.