Embark
Embark

BOT vs EOR vs Own Entity: Choosing a GCC Model in India

Build-Operate-Transfer, Employer of Record or Your Own Entity?

How the three ways of building a Global Capability Centre in India compare on speed, control, risk and cost, and how to choose the right one for your stage.
GCC GuidesUpdated November 20, 20268 min readBy the Embark team

Own entity

full ownership and control from the day the entity is registered

BOT

a partner builds and runs the centre, then transfers it to you

EOR

India talent on a partner's payroll, with no entity required

In short

  • There are three main ways to build a GCC in India: your own entity with an assisted build, Build-Operate-Transfer (BOT) and Employer of Record (EOR).
  • EOR is the fastest way to start, BOT carries the least setup risk for a full centre, and an own entity gives the most control from day one.
  • The models are not permanent choices. Many companies start with EOR or BOT and move to their own entity once the centre has proven itself.

The three ways to build a GCC in India

Before incorporation, hiring or workspace, a company setting up a Global Capability Centre needs to decide who will own and run the centre in its early years. That choice sets how fast you can start, how much risk you carry and how much control you have. There are three common models.

Own entity with an assisted build

You incorporate your own Indian company, usually a wholly owned private limited subsidiary, and own it from the day it is registered. A partner handles incorporation, registrations, workspace, IT and the first cohort of hires as your vendor.

  • Best for: companies sure of their India plans that want full control from the start.
  • Speed: with Embark, a GCC can go live in about 30 days, with a full office by around day 120.
  • Risk: entity and employment risk sit with you from day one, though the partner de-risks each step.

Build-Operate-Transfer (BOT)

The partner builds your GCC under its own entity, runs it as a managed centre and transfers full legal ownership to you at a milestone defined in the contract. You get a running, staffed and documented centre without carrying the setup and early operating risk.

  • Best for: companies that want a full centre with the lowest setup risk and a clear path to ownership.
  • What to agree up front: transfer triggers, transfer price, which assets and contracts move, and the handover plan.
  • Watch for: transfer terms left vague, and processes that depend on the partner after handover.

Employer of Record (EOR)

The partner employs your India team on its payroll. You direct the work, manage performance and integrate the team into your global organisation. The partner handles employment contracts, payroll, statutory contributions such as Provident Fund and Employees' State Insurance, and HR administration.

  • Best for: pilots, proof-of-concept teams and companies that need India talent within weeks.
  • Speed: the fastest route, because no entity is needed.
  • Watch for: plan the conversion to your own entity early if the team will grow beyond a pilot.

Side-by-side comparison

Speed to start

EOR is fastest, then an assisted own-entity build, then BOT for a full centre.

Control

An own entity gives full control from day one. Under BOT you direct the work, and ownership follows at transfer. Under EOR you direct the work while the partner is the legal employer.

Risk

BOT and EOR keep entity and employment risk with the partner in the early phase. An own entity places it with you, which a good partner helps manage.

Path to ownership

Own entity: immediate. BOT: at the agreed milestone. EOR: when you set up your entity and move the team across.

How to choose the right model

  • If you need a small team in weeks to test the model, start with EOR.
  • If you want a full centre but would rather not carry the setup risk, choose BOT.
  • If your plans are firm and you want control from day one, choose an own entity with an assisted build.

See how Embark runs each one on the GCC engagement models page, or read the full step-by-step guide to setting up a GCC in India.

Talk to Embark

Planning a GCC in India?

Embark, backed by Embassy Group, sets up, runs and scales capability centres in India as one accountable partner, from strategy and entity setup to workspace, talent and day-to-day operations.

FAQs

Frequently Asked Questions

What is the Build-Operate-Transfer (BOT) model?

Under Build-Operate-Transfer, a partner builds your GCC under its own entity, runs it as a managed centre and then transfers full legal ownership to you at a milestone agreed in the contract. You receive a staffed, documented and running centre without carrying the setup and early operating risk yourself.

What is an Employer of Record (EOR) in India?

An Employer of Record employs your India-based team on its own payroll. You direct the day-to-day work and manage performance, while the EOR handles employment contracts, payroll, statutory contributions and HR administration. No Indian entity is needed.

Is BOT or EOR better for a GCC?

EOR is usually better for pilots, small teams and companies that want to start in weeks. BOT suits companies that want a full centre with lower setup risk and a clear path to ownership. Companies that are sure of their plans and want control from the start often choose to own the entity from day one with an assisted build.

Can we switch from EOR to our own entity later?

Yes. A common path is to start with EOR, prove the model, then set up your own entity and move the team across with continuity of employment. Embark plans the conversion on your timeline.

What happens at the transfer in a BOT?

At the agreed milestone, ownership of the entity or the business moves to you, along with employees, contracts, assets, processes and documentation. A well-run BOT defines the transfer triggers, price and handover plan in the contract at the start.