GCC Operating Models: Captive, BOT, Hybrid & Co-Innovation Explained

Why Your Operating Model Choice Matters More Than You Think

Every GCC in India ultimately performs the same function: it extends your company's capabilities into India's talent market. But how you structure that extension—who owns the entity, who manages the operations, who bears the risk during ramp-up—determines your cost trajectory, speed to market, and organizational complexity for years to come.

India hosts over 2,100 GCCs as of 2026, employing nearly 2 million professionals and generating $64.6 billion in annual revenue. These centers operate across four primary models, each suited to different company profiles, risk appetites, and strategic objectives. Getting the model right avoids the most expensive mistake in GCC buildouts: starting over 18 months in because the initial structure doesn't scale.

Model 1: Captive GCC (Full Ownership from Day One)

How It Works

A captive GCC is a wholly owned subsidiary registered as a private limited company in India. You own 100% of the entity, hire all employees directly, lease your own office space, and manage all operations. There's no intermediary—you're building and running an Indian company from scratch.

The registration process follows India's standard FDI pathway: file the SPICe+ form with the Ministry of Corporate Affairs, obtain PAN, TAN, and GST registration, declare your foreign investment under FEMA via the FC-GPR form, and register under your state's Shops and Establishments Act.

Timeline and Cost

Advantages

• Full control: You own the entity, the IP, the data, and the employee relationships. No vendor dependency.
• Cultural alignment: Your India team is your team—same values, same processes, same tools.
• Long-term cost efficiency: No management fees, no partner margins. At scale (200+ headcount), captive is the cheapest model.
• IP protection: All code, data, and trade secrets remain within your corporate boundary. Critical for companies in regulated industries or with sensitive technology.

Disadvantages

• High upfront investment: $1–2M before a single line of code is written.
• India expertise required: You need to understand Indian labour law, tax compliance, transfer pricing, and workplace culture from Day 1.
• Slow to start: 16–24 weeks to first operations versus 8–16 weeks for BOT and 4–8 weeks for managed models.
• All risk on you: Hiring mistakes, compliance errors, and cultural missteps are entirely your problem.

Best For

Large enterprises (Fortune 1000) with prior India experience, adequate capital reserves, and internal expertise in setting up international operations. Also ideal for companies in highly regulated sectors (banking, defence, healthcare) where data sovereignty and IP control are non-negotiable.

Model 2: Build-Operate-Transfer (BOT)

How It Works

In the BOT model, a local Indian partner (the "operator") handles the initial setup and operations on your behalf. The operator incorporates the entity, leases the office, hires the team, and manages day-to-day operations for a defined period (typically 18–36 months). At the end of the operate phase, the entire operation—entity, employees, assets, leases—is transferred to your ownership.

Think of it as buying a turn-key business that was built to your exact specifications, by a partner who has done it dozens of times before.

The Three Phases

Phase 1: Build (Months 0–6)

The operator handles entity registration, office selection and fit-out, leadership recruitment, and initial engineering hiring. They use their existing relationships with real estate developers, recruitment agencies, and compliance professionals to move faster than you could independently. Typical output: 20–50 employees operational in 8–16 weeks.

Phase 2: Operate (Months 6–24)

The operator manages day-to-day HR, payroll, compliance, and administration while you manage the technical work and delivery. Employees report to you functionally but to the operator administratively. This phase is where scaling happens—growing from 50 to 150–300 FTE with the operator's infrastructure and expertise.

Phase 3: Transfer (Months 18–36)

The operator transfers the entity, all employees (via novation agreements), office leases, assets, and operational processes to your ownership. This typically takes 1–3 months and involves legal due diligence, employee consent, and regulatory filings. Post-transfer, you run a fully captive GCC.

Cost Structure

For a 100-person center over a 24-month BOT engagement, total partner fees typically range from $500K–$1.2M. This premium versus captive is the price of reduced risk, faster setup, and operational expertise.

Advantages

• De-risked entry: The operator bears the initial setup risk and has solved every problem you'll encounter—from delayed GST registration to finding a resident director.
• Speed to market: 8–16 weeks to first operations, versus 16–24 for captive. The operator's existing infrastructure accelerates everything.
• Learn before you own: You observe Indian operations for 18–24 months before taking ownership, learning the nuances of Indian employment law, compliance calendars, and workplace culture.
• Cost savings of 50–70%: Compared to US/EU operations, even with the BOT partner's management fees.

Disadvantages

• Partner dependency: During the operate phase, your employees technically work for the partner entity. If the relationship sours, unwinding is complex.
• Cultural dilution: Employees may identify more with the operator's brand than yours during the operate phase, complicating the transfer.
• Management fee overhead: At $1,500–$3,000 per employee per month, a 100-person center pays $1.8M–$3.6M in management fees over 24 months. This is the premium for reduced risk.
• Transfer complexity: Employee novation, lease transfers, and vendor contract assignments create a 2–3 month transition period with operational disruption.

Best For

Mid-market companies entering India for the first time, companies without India operational expertise, and organizations that want to validate the model before committing full capital. The BOT model has gained massive popularity as the "de-risked" entry point in 2025–2026—particularly among US and EU tech companies setting up their first mid-size GCC in India.

Model 3: Hybrid GCC

How It Works

The hybrid model combines elements of captive and outsourced operations within a single GCC. You own the entity and employ your core team directly (typically senior engineers, architects, and product managers), while a service partner provides flexible capacity for functions that fluctuate or require specialized skills you haven't built internally.

Common hybrid configurations include:

• Core + Flex: 60–70% captive employees + 30–40% partner-supplied staff. Core team handles product engineering; partner team handles testing, data operations, or specialized projects.
• Function Split: Captive for engineering; partner for HR, finance, and administration. You focus on technology; the partner handles India-specific operations.
• Ramp-Up Hybrid: Start with a high partner ratio (70–80%) and gradually convert to captive as you build internal capabilities. The inverse of BOT—you own the entity from Day 1 but outsource operations until you're ready to internalize them.

Cost Structure

Hybrid models sit between captive and BOT in cost. Your captive employees cost the same as in a fully captive model. Partner-supplied staff cost 20–40% more than captive employees (the partner's margin), but you avoid recruitment costs, bench risk, and HR overhead for those positions.

For a 150-person hybrid center (100 captive + 50 partner), typical annual costs:

Advantages

• Flexibility: Scale up or down without the fixed costs and severance risks of a fully captive model. Partner staff can be ramped within 2–4 weeks.
• Risk distribution: Partner absorbs bench risk and recruitment uncertainty for non-core functions.
• Speed with control: You own the entity and core team from Day 1 while leveraging partner speed for rapid scaling.
• Optimized for uncertainty: Ideal when your hiring needs fluctuate by 20–40% quarter-to-quarter—common in project-driven businesses.

Disadvantages

• Dual management: Managing two employment populations (captive + partner) creates HR complexity, cultural friction, and potential equity issues around compensation and career paths.
• IP risk: Partner staff access your codebase and data but aren't your employees. This requires careful contractual protections and access controls.
• Harder to build culture: Two-tier workforce structures can create us-vs-them dynamics that undermine team cohesion.

Best For

Companies with variable workloads, project-based organizations, or those in fast-moving industries (e-commerce, fintech, gaming) where headcount needs fluctuate significantly. Also works well for companies that want captive ownership but lack the HR infrastructure to manage all functions internally.

Model 4: Co-Innovation GCC

How It Works

The co-innovation model is the newest and most strategic GCC structure. Instead of a client-vendor relationship, you and an Indian technology partner establish a joint operating model that pools talent, intellectual property, and delivery frameworks. This goes beyond outsourcing or staffing—it's a genuine partnership where both parties contribute capabilities and share outcomes.

Common co-innovation structures include:

• Joint Venture (JV): You and the Indian partner form a jointly-owned entity, typically with 51–74% owned by the foreign parent and 26–49% by the Indian partner. Both parties contribute capital, IP, and talent.
• IP Co-Development: Your GCC works alongside the Indian partner's R&D team on shared technology platforms, with pre-agreed IP ownership splits.
• Revenue-Sharing Model: Instead of fixed fees, the partner's compensation is tied to the GCC's output metrics—products shipped, revenue generated, or patents filed.

This model has gained significant traction in 2025–2026. According to a NASSCOM-Oliver Wyman report, GCCs and service providers are increasingly building joint operating models, with over 50% of Indian GCCs now functioning as transformation hubs driving digital innovation, 58% investing in agentic AI, and 83% scaling generative AI projects.

Legal Structure

Co-innovation GCCs are typically structured as either a joint venture company (under the Companies Act, with FDI routed through the automatic route or government approval route depending on the sector) or a wholly owned subsidiary with a strategic service agreement that functions as a de facto JV without shared equity.

For JVs involving a foreign partner, the shareholding pattern determines the FDI route. In most technology sectors, 100% FDI is permitted under the automatic route, so a 51-49% or 74-26% JV structure doesn't require government approval. However, certain sectors like defence (74% FDI cap) and multi-brand retail (51% cap) have restrictions that affect JV structuring. For sector-specific guidance, see our FDI advisory services.

Cost Structure

Co-innovation models are the hardest to generalize because costs depend on the specific arrangement. Common structures include equity contributions from both parties (the foreign partner typically invests $1–5M for a 51–74% stake), shared operating costs proportional to equity, revenue or IP royalty sharing agreements, and joint R&D budgets funded by both parties.

Advantages

• Access to partner's existing ecosystem: The Indian partner brings talent pipelines, infrastructure, vendor relationships, and regulatory expertise that accelerate your ramp-up.
• Shared risk: Both parties have skin in the game, aligning incentives around outcomes rather than headcount.
• Innovation amplification: Combining your domain expertise with the partner's technology capabilities can produce innovation that neither party could achieve alone.
• Market access: If your co-innovation partner serves the Indian market, the JV can serve as both a capability center and a market entry vehicle.

Disadvantages

• Governance complexity: Joint ownership requires board alignment, shareholder agreements, and conflict resolution mechanisms. Decision-making is slower than in a captive model.
• IP complications: Determining who owns what IP—especially for jointly developed technology—requires detailed upfront agreements and ongoing management.
• Exit difficulty: Unwinding a JV is significantly more complex than closing a captive subsidiary. Shareholder disputes, asset division, and employee allocation create legal and operational challenges.
• Partner risk: Your success is tied to the partner's capability, reputation, and financial health. A partner failure or strategic misalignment can derail the entire operation.

Best For

Companies seeking to combine India capability building with market entry, R&D-intensive organizations that benefit from a local partner's innovation ecosystem, and enterprises where the Indian partner brings genuinely complementary capabilities (not just staffing).

Head-to-Head Model Comparison

Decision Framework: Choosing Your Operating Model

Start with Your Risk Profile

The most important variable is your company's appetite for India-specific risk:

• Low risk tolerance + First time in India: BOT. Let a partner absorb the setup risk. You learn while they build.
• Low risk tolerance + Variable workloads: Hybrid. Own the core, flex the rest.
• High risk tolerance + India experience: Captive. Maximum control, lowest long-term cost.
• Strategic partnership appetite + Innovation focus: Co-Innovation. But only if the partner brings genuine complementary value.

Consider Your Timeline

If you need engineers delivering code within 8 weeks, a captive model won't get you there. The realistic timeline hierarchy is Managed GCC/EOR at 4–8 weeks, BOT at 8–16 weeks, Hybrid at 12–20 weeks, and Captive at 16–24 weeks.

Factor in Your Team Size

Operating model economics shift with scale:

• 10–25 engineers: EOR or Managed GCC. An entity setup doesn't justify itself at this scale.
• 25–100 engineers: BOT is the sweet spot. You need an entity but probably don't have the India expertise to run it solo.
• 100–300 engineers: Hybrid or transitioning from BOT to Captive. At this scale, the captive cost advantage starts to outweigh the BOT management fees.
• 300+ engineers: Captive. The management fee savings at scale are substantial—$5M+ annually versus BOT at 300 headcount.

For more on sizing your team appropriately, see our guide on GCC for mid-size companies.

Government Policy and Regulatory Context for 2026

Several 2025–2026 policy developments affect operating model decisions:

National GCC Policy Framework (Budget 2025–26)

The framework introduced single-window clearance for entity registration, fast-track FDI approvals, and state-level incentive packages. This primarily benefits captive models by reducing setup friction, though BOT partners also benefit from faster entity registration.

Transfer Pricing Safe Harbour (Budget 2026)

The uniform 15.5% safe harbour margin for transfer pricing, with the threshold raised from INR 300 crore to INR 2,000 crore, simplifies compliance for all models. This is especially significant for BOT models where the intercompany pricing between the operator entity and the parent company previously faced scrutiny.

New Labour Codes (November 2025)

India's four New Labour Codes came into effect on November 21, 2025, introducing the "50% Wage Rule" (basic pay must constitute at least 50% of CTC), changes to gratuity calculation and leave encashment, and new social security obligations. These apply to all models where you employ people directly. BOT models shift this compliance to the operator during the operate phase.

SEZ and STPI Benefits

SEZ units enjoy 100% income tax exemption on export profits for the first five years, followed by 50% for the next five years. STPI units offer duty-free imports and GST exemptions on domestic procurement. Both benefits apply regardless of your operating model, though the entity must be registered as an SEZ or STPI unit. For guidance on these benefits, see our tax advisory services.

The Evolution Path: How Models Transform Over Time

Most GCCs don't stay in their initial operating model forever. The typical evolution follows a predictable pattern:

Year 0–1: EOR or BOT for pilot and initial scaling (10–100 employees).

Year 1–3: Transition to captive or hybrid as the team reaches 100–200 employees and the company builds India expertise.

Year 3–5: Fully captive operations at 200–500+ employees, with the GCC increasingly taking on strategic functions (product ownership, R&D leadership, patent generation).

Year 5+: Some companies evolve into co-innovation models, partnering with Indian firms on joint R&D or establishing the India center as a global hub for specific technology domains.

This evolution isn't mandatory. Some companies run highly effective BOT or hybrid models indefinitely. But understanding the typical trajectory helps you plan your initial model with the end state in mind. For a comprehensive setup guide, see our complete GCC setup playbook and our GCC vs. Indian subsidiary comparison.

Key Takeaways

• Captive is the lowest-cost model at scale (200+ headcount) but requires the highest upfront investment ($1–2M) and India expertise. Best for large enterprises with prior international experience.
• BOT is the de-risked entry point for first-time India entrants. You pay a 15–25% premium in management fees but gain speed (8–16 weeks), operational expertise, and reduced risk during the critical first 18–24 months.
• Hybrid provides maximum flexibility for variable workloads. Own your core team, use partners for flex capacity. Watch for cultural friction between captive and partner employees.
• Co-Innovation is for strategic partnerships, not staffing. It works when both parties contribute genuinely complementary capabilities. IP governance and exit planning must be defined upfront.
• Plan for model evolution. Your Day 1 model probably isn't your Year 5 model. Choose an initial structure that allows a clean transition to your target state.