There is no universally best GCC operating model. The right choice depends on how much control you need, how fast you need to move, how much capital and internal India readiness you have, how strategically critical the capability is, how sensitive your IP is, and how long a commitment you are prepared to make. Captive, BOT, hybrid and EOR each answer that trade-off differently.
Answer six questions to get a directional starting point for your India GCC operating model decision.
This tool is a planning framework only. Final operating, legal and tax structures should be evaluated with appropriate professional advisors.
A GCC operating model is the framework that determines how a Global Capability Centre in India is built, governed and run day to day — who owns it, who controls hiring and delivery decisions, and how much of the setup is handled directly versus through a partner. It is distinct from two related but separate decisions.
Legal structure is the actual Indian entity through which the GCC operates — typically a wholly owned subsidiary, a partner-operated entity, or no separate entity at all in the early stages. Employment model is how the people working in the centre are legally employed — directly by the parent's Indian entity, by a BOT or managed partner, or through an employer of record. A company can hold a captive operating model with a wholly owned entity, or run an EOR employment arrangement with no Indian entity at all. Confusing these three layers is one of the most common mistakes in India GCC planning.
A captive GCC is a wholly owned Indian entity, set up and run directly by the parent company from day one. The parent owns governance, hiring, technology and IP outright, with no intermediary operator.
The parent incorporates an Indian entity, builds leadership locally, and hires, manages and scales the team under direct company policies and reporting lines.
Companies with a long-term India commitment, strategically critical capabilities, highly sensitive IP, and the internal bandwidth to manage entity setup, compliance and local leadership recruitment.
Full governance control, direct IP ownership, complete visibility into hiring and culture, and the ability to build a durable long-term capability centre rather than a transactional arrangement.
Longer setup timelines, higher upfront responsibility for entity formation and compliance, and a real dependency on having or building credible India leadership early. Captive is not always the cheapest route — its economics depend heavily on scale and how efficiently the entity is run.
A BOT GCC model uses a partner to build and initially operate the centre, with a pre-agreed path to transfer ownership, employees and operations to the parent company at a later stage.
Build: the partner sets up the entity or operating structure, hires the initial team and stands up infrastructure. Operate: the partner runs day-to-day operations, governance and delivery under agreed service levels while the parent retains oversight. Transfer: ownership, employment contracts, technology, IP and operating control move to the parent under terms defined upfront in the agreement.
The value of BOT depends heavily on how well the transfer conditions, employee continuity, IP ownership, technology handover, contracts and liabilities are defined at the start — not after operations have already begun.
A hybrid GCC model is typically a parent-owned centre that selectively uses third-party support for specific functions rather than running every function in-house from day one.
Common areas handled externally in a hybrid model include recruitment, payroll, facilities management, IT support, specialist technical vendors, and initial operational support while local leadership is still being built. The core entity and governance usually remain parent-owned — hybrid is not necessarily a distinct legal entity type, but an operating choice layered on top of a captive or BOT structure.
Hybrid tends to appeal to companies that want direct control over strategic decisions and culture, but do not want to build every operational function internally in year one.
An employer of record lets a company hire employees in India through a third-party legal employer, without setting up an Indian entity. It is an employment mechanism, not an operating or ownership model.
EOR can help a company build an initial India team quickly, before or while it decides on a longer-term GCC structure. It is a genuinely useful entry or transition route — but it is not equivalent to owning a GCC.
Testing India as a location, hiring a small pilot team, moving fast on a time-sensitive capability, or bridging the gap while entity setup is in progress.
Reduced upfront entity and compliance responsibility, and the ability to start hiring without waiting for incorporation to complete.
Less direct governance and control than a captive or BOT structure, per-employee cost structures that do not always scale efficiently at larger headcounts, and constraints on the depth of IP and infrastructure control compared with an owned entity. EOR is not automatically cheaper or faster than every alternative in every scenario — the comparison depends on team size, duration and the specific capability being built.
| Factor | Captive | BOT | Hybrid | EOR |
|---|---|---|---|---|
| Entity ownership | Parent-owned | Partner, then parent | Parent-owned | None required |
| Control | Full | Shared, increasing over time | High, with selective outsourcing | Limited |
| Speed | Slower to launch | Faster than captive | Moderate | Fastest to first hire |
| Upfront commitment | High | Moderate | High | Low |
| Internal expertise required | High | Lower initially | Moderate | Minimal |
| IP control | Strongest, if structured correctly | Depends on agreement terms | Strong on core functions | Requires careful contractual protection |
| Vendor dependency | Lowest | High during build/operate phase | Moderate, function-specific | High |
| Best use | Long-term strategic capability | Fast build with planned ownership transfer | Owned core with flexible support functions | Market validation or fast initial hiring |
This comparison reflects general tendencies, not fixed rules. Actual outcomes depend on contract terms, governance design and company-specific execution.
There is no single cheapest model across every timeframe. Cost depends on scale, duration and how efficiently each structure is run.
In the short term, EOR or managed approaches can reduce upfront investment because there is no entity to set up. In the medium term, BOT can balance speed with shared setup responsibility, spreading initial cost and risk with a partner. In the long term, captive can develop stronger unit economics at scale, though this depends entirely on company-specific assumptions about headcount, efficiency and how well the entity is managed.
Comparing models on salary alone misses most of this equation. PlugScale's GCC ROI Calculator is designed to help model these variables against a company's specific plan.
As a general tendency, control decreases moving from captive to hybrid to BOT to EOR. Captive offers full direct governance; EOR offers the least, since a third party is the legal employer.
This is a tendency, not an absolute rule. Actual control in any structure is determined by the specific contracts, governance mechanisms, outsourced scope, ownership terms and decision rights negotiated — a well-structured BOT agreement can preserve more parent control than a loosely governed captive with weak internal oversight.
Partner-led and employment-led routes generally reduce initial setup friction because they avoid the time required to incorporate and operationalize a new entity. EOR is typically the fastest way to make a first India hire; BOT is typically faster to operational scale than a pure captive build.
Actual timing in any model depends on entity formation requirements, sector-specific approvals, hiring market conditions, location and office readiness, contract negotiation, and how quickly the right roles can actually be filled. No fixed timeline applies universally across companies or sectors.
Team size is a useful input, not a rigid trigger. For a small initial team, an EOR or managed route often makes sense while a company validates its India thesis. As the team grows, BOT or hybrid structures tend to become more attractive, balancing scale with shared setup responsibility. For a large, long-term team, captive economics and direct control typically become more compelling.
There is no universal employee count at which a company must change models. The right transition point depends on growth trajectory, capability criticality and internal readiness, not a fixed headcount threshold.
IP assignment terms, confidentiality obligations, access controls, data processing practices, cybersecurity posture, source code handling, employee invention clauses and vendor access all shape how much direct control a company needs over its India operation.
Strategically sensitive capabilities — core product engineering, proprietary algorithms, regulated data — often favour models with greater direct ownership and governance, because IP protection is easier to enforce end-to-end when the company controls the entity and employment relationship. This does not mean EOR structures are inherently weak on IP protection; it means IP terms need to be built deliberately into the contract regardless of which model is chosen.
| Objective | Potential Fit | Reason |
|---|---|---|
| Test India talent | EOR | Low commitment, fast to start, easy to unwind |
| Hire an initial team | EOR / Managed | Avoids entity setup before India strategy is confirmed |
| Build quickly and transfer later | BOT | Combines partner speed with a defined path to ownership |
| Long-term engineering centre | Captive | Direct control and durable governance for a core capability |
| Mixed internal + outsourced operations | Hybrid | Owned core with flexibility on non-strategic functions |
| Strategic R&D | Captive | IP sensitivity and long-term commitment favour direct ownership |
| Flexible support functions | Hybrid / EOR | Lower criticality allows for vendor-supported delivery |
| Global CoE | Captive / Hybrid | Requires deep integration with global operating structure |
Technology / SaaS companies often lean toward captive or hybrid models given the centrality of engineering IP and the depth of product talent in hubs like Bengaluru. Manufacturing GCCs frequently use BOT or hybrid structures, pairing engineering and R&D talent in cities like Pune and Chennai with partner support during ramp-up. BFSI operations, concentrated heavily in Mumbai and increasingly Gurugram and Noida, tend to prioritize models with strong compliance and governance control given regulatory exposure. Healthcare and life sciences GCCs, with growing presence in Hyderabad, weigh data sensitivity heavily in their model choice. Engineering and R&D centres, common across Bengaluru, Pune and Chennai, generally favour models that protect IP and support deep technical integration with global teams.
These three layers are often collapsed into one decision, but they are separable and should be evaluated independently.
Operating Model — how the centre is governed and run: captive, BOT or hybrid.
Legal Entity — the Indian corporate structure through which the centre exists, or the absence of one in an EOR arrangement.
Employment Model — how people are legally employed: directly, through a BOT partner, or through an EOR.
Layered on top of these are the commercial model — how costs, fees and service terms are structured between parties — and the governance model — how decisions actually get made day to day, regardless of what the legal paperwork says. A company can have full legal ownership through a captive entity and still run weak governance if reporting lines and decision rights are not clearly designed. Getting the operating model right requires deliberately designing all five layers together, not just picking a label like "captive" or "BOT" and assuming everything else follows.
Every GCC operating model carries tax and regulatory implications that need dedicated professional review. At a high level, companies should expect to evaluate entity structure options, related-party transaction design, transfer pricing methodology for intercompany services, GST treatment, withholding tax obligations, FEMA requirements for cross-border investment and remittance, employment law compliance, IP ownership documentation, and permanent establishment risk depending on how the operating model is structured.
These considerations vary by structure, sector and company specifics, and change over time as regulations evolve. Structure-specific legal and tax advice should be obtained before implementation — this article does not substitute for that advice.
A well-designed BOT agreement protects the parent's interests during the operate phase and ensures a clean transfer later.
Each of these needs to be defined before operations begin. Agreements that leave transfer terms vague tend to create disputes exactly when the parent is most dependent on a smooth handover.
There is no fixed employee count that triggers a move from EOR to a fuller GCC structure. The signals tend to be qualitative: sustained headcount growth beyond what a pilot team implies, a confirmed long-term India commitment, capabilities becoming more strategically important, a need for more direct governance than a third-party employer can provide, rising IP sensitivity, the availability of credible local leadership, EOR costs beginning to outweigh the benefits at scale, and a growing need for dedicated infrastructure and deeper organizational integration.
When several of these signals appear together, it is usually time to start entity and operating-model planning, even if the transition itself takes time to execute properly.
Yes. Two common paths are EOR into entity planning and direct captive setup, or EOR into a BOT arrangement that later transfers into captive ownership. Both are workable, but neither happens automatically — they require deliberate planning.
Key considerations in either path include how existing employees migrate to new contracts without disrupting benefits or continuity, how IP created under the EOR arrangement is properly assigned to the new entity, how data and payroll systems transition, how compliance obligations shift, and how the change is communicated to the team to avoid uncertainty or attrition during the switch.
A simple decision sequence can narrow the choice before deeper evaluation begins.
Need immediate hiring? → Evaluate EOR or a managed route.
Strategic, long-term capability? → Evaluate captive.
Need partner-led build with a later transfer? → Evaluate BOT.
Need direct ownership with selected external support? → Evaluate hybrid.
This is a decision framework to guide initial thinking, not a universal rule that fits every company's circumstances.
Scoring each model against weighted criteria helps make the trade-offs explicit rather than implicit.
| Criteria (Weight) | Captive | BOT | Hybrid | EOR |
|---|---|---|---|---|
| Control (20) | 18 | 12 | 15 | 7 |
| Speed (15) | 6 | 10 | 9 | 14 |
| Cost efficiency (15) | 10 | 11 | 10 | 9 |
| IP protection (15) | 14 | 10 | 12 | 8 |
| Scalability (15) | 13 | 12 | 12 | 7 |
| Internal readiness needed (10) | 3 | 6 | 5 | 9 |
| Risk management (10) | 8 | 7 | 7 | 6 |
Illustrative scoring to demonstrate the framework. Weight and score each criterion against your own priorities before drawing conclusions.
Captive: higher setup responsibility in year one, transitioning into a directly operated model, building toward long-term ownership economics.
BOT: partner fees plus operating costs during build and operate phases, followed by a defined transition into direct ownership.
Hybrid: an owned core function from the start, combined with selected outsourced functions that can flex up or down as needs change.
EOR: a per-employee arrangement with lower initial setup responsibility, with the option to transition into a fuller structure as the team grows.
Illustrative framework. Actual economics depend on company-specific assumptions about scale, duration and execution efficiency — no financial figures here should be treated as a forecast.
This is one possible pathway, not a mandatory sequence. Companies with a confirmed long-term commitment sometimes move directly to captive without passing through every stage.
PlugScale supports GCC workforce planning, India talent mapping, GCC hiring, operating-model evaluation, recruitment and workforce scaling for companies expanding into India.
A GCC operating model is the framework for how a Global Capability Centre in India is built, governed and run — covering ownership, control and delivery responsibility. It is separate from the legal entity used and the employment model chosen, though the three are often designed together.
The main approaches are captive, build-operate-transfer (BOT) and hybrid, with employer of record (EOR) commonly used as an entry or interim employment route. Each offers a different balance of control, speed, cost and commitment.
A captive GCC is a wholly owned Indian entity set up and operated directly by the parent company, with full control over governance, hiring, IP and technology. It suits companies with a long-term commitment and strategically critical capabilities.
A build-operate-transfer model uses a partner to set up and initially run the centre, with ownership, employees and operations transferring to the parent under pre-agreed terms. It balances faster launch with an eventual path to direct ownership.
A hybrid GCC model is typically a parent-owned centre that selectively outsources specific functions such as recruitment, payroll or IT support. It is not necessarily a distinct legal entity type, but an operating choice layered on captive or BOT ownership.
Not exactly. EOR is an employment mechanism that lets a company hire in India without setting up an entity. It can support an early-stage or interim GCC strategy, but it is not equivalent to owning and governing a GCC.
A captive is parent-owned from inception with full direct control. A BOT starts under partner ownership and operation, with a defined transfer of ownership and control to the parent at a later stage.
BOT is an operating model involving entity setup, governance and a path to ownership transfer. EOR is purely an employment arrangement with no entity and no ownership transfer built in, typically used for faster, lighter-weight hiring.
Often cheaper upfront for small teams, since there is no entity to establish. At larger scale and over longer periods, per-employee EOR costs can exceed the economics of a well-run captive or BOT structure, so the comparison depends on team size and duration.
BOT suits companies that want to move faster than a self-built captive allows, while still planning to take direct ownership once the centre is operational and transfer terms are clearly defined upfront.
Captive suits companies with a confirmed long-term India commitment, strategically important capabilities, sensitive IP, and the internal readiness to manage entity setup and local leadership from the outset.
Yes. Companies commonly start with EOR to validate their India plan, then transition into entity planning and captive ownership, or move through a BOT structure first. Employee continuity and IP assignment need careful handling during the switch.
Captive generally provides the most control, since the parent owns governance, hiring and IP directly. Actual control in any model ultimately depends on contract terms, governance design and decision rights, not the label alone.
EOR is typically the fastest way to make an initial India hire, since no entity is required. Actual launch speed for any model depends on entity requirements, sector approvals, hiring conditions and location readiness.
EOR or a managed route generally suits small initial teams, avoiding the cost and complexity of entity setup while a company validates its India strategy before committing further.
Captive is generally best suited to a confirmed long-term strategy, given its stronger governance, IP control and scalability. Hybrid is a strong alternative for companies that want direct ownership with selective outsourced flexibility.
Models with more direct ownership, such as captive, make end-to-end IP protection more straightforward to enforce. IP can still be well protected under BOT or EOR arrangements if assignment and confidentiality terms are built into the contracts from the start.
Different structures create different related-party transactions, entity obligations and transfer pricing considerations. Specific tax and FEMA implications vary by structure and should be reviewed with qualified advisors before implementation.
A strong BOT agreement covers ownership, transfer triggers and timelines, employee continuity, IP assignment, technology handover, data terms, cost structure, performance standards, exit provisions and post-transfer transition support.
Start by assessing required speed, control, internal India readiness, expected team size, capability criticality and IP sensitivity. These factors together point toward EOR, BOT, hybrid or captive as a starting framework for deeper evaluation.