India’s GCC market hit a size most forecasts had pencilled in for 2030, four years early. India now hosts more than 2,100 centers employing 2.36 million professionals, in a market worth close to $100 billion. With that many companies already in, the hard question has changed. It is no longer whether to build a team in India. It is who carries the risk while that team is being built.
The build operate transfer model answers that question. A local partner sets up the entity, hires the team and runs delivery. On a date you agree upfront, the whole center becomes yours.
Here is the part most buyers miss. They negotiate the monthly fee hard and barely read the transfer clause. That order is backwards. In the deals our team has priced, the transfer terms routinely move more money than every fee concession put together. In a 100-person center, a transfer fee of one month of billing per head versus six months is the gap between a ₹1 crore exit and a ₹6 crore exit. Same team. Same output.
Speed is the other half of the case. Under a build operate transfer model, a partner with an existing Indian entity can put your first engineers on payroll in 4–8 weeks. Doing it yourself usually takes 4–6 months before hire number one, because incorporation, bank accounts, PF and ESI registration and an office all come first.
So the real decision is not “BOT or not.” It is whether a build operate transfer model fits your headcount, your timeline and your India leadership bench, and which contract terms you lock before you sign. That is what this guide covers.
India’s GCC ecosystem is now a market of nearly $100 billion, with more than 2,100 centers and 2.36 million professionals, per the joint Nasscom and Zinnov report. IBM Consulting’s June 2026 partnership with Quintes Global was set up partly to give enterprises a more structured route through BOT and BOTT
TL;DR
This guide explains the build operate transfer model for leaders planning an India GCC. It is for CTOs, CFOs and heads of engineering who want to own an India team without the year-one setup risk.
The one number to know before you sign: transfer fees run from about 1 to 6 months of billing per employee. On 100 people, that is the difference between a ₹1 crore exit and a ₹6 crore exit.
By the end, you will know how the BOT model runs phase by phase, what each phase costs, how long it takes, and which five contract terms decide whether it pays off.
What Is the Build Operate Transfer Model?
The build operate transfer model is a GCC entry structure where a local partner builds your offshore center (entity, office and team), operates it under agreed SLAs for a fixed period, usually 18–36 months, and then transfers the employees, assets and entity to you for a pre-agreed fee.
Three things make it different from plain outsourcing. The team is built only for you. You direct the engineering work from day one. And ownership legally moves to you at transfer, instead of staying with the vendor forever.
It is also not a joint venture. There is no shared equity while the partner operates the center. The partner owns the entity until the transfer event. After that, you own 100% of it.
Why Going Alone in India Stalls in Year One
Most companies that try a do-it-yourself global capability center underestimate year one. Not the salaries. The setup.
A typical first-time setup looks like this:
- 4–6 months before the first hire. Incorporation, bank accounts, statutory registrations and an office all have to land first.
- ₹1.5 — 4 crore of upfront and first-year fixed cost. Entity setup, deposits, fit-out and senior leadership hires, all committed before you know the center works.
- 60–90 day notice periods for senior engineers, plus 2–4 weeks of background verification. A “four-week hire” is really 8–10 weeks from job description to first day.
- 12–18 months to wind down a foreign subsidiary in India if the plan fails.
Plain outsourcing avoids these costs, but you never own the team. The vendor margin stays in every invoice for as long as the contract runs.
That leaves a clear gap. Companies that want 40–150 engineers over 3–5 years need ownership eventually but cannot absorb year-one setup risk today. Build operate transfer in India exists for exactly that gap. It is also why the build operate transfer model has become a default entry path for mid-sized firms entering India for the first time.
How a BOT GCC Runs, Phase by Phase
A BOT GCC moves through six stages, not three. The “build, operate, transfer” label hides the two steps that cause most of the trouble: choosing the entity structure and auditing transfer-readiness. Everest Group’s 2026 assessment of GCC setup providers in India groups the market into three main setup routes, with BOT listed alongside assisted build-outs and joint ventures.
Here is how the build operate transfer model works in practice:
- Scope the headcount curve (weeks 0–4). Document a ramp, not a number. “15 in Q1, 40 by month 9, 100 by month 24” prices are very different from “100 engineers.”
- Choose the entity structure (weeks 2–6). Decide whether the team sits in a dedicated SPV or inside the partner’s main entity. This one choice decides how hard the transfer will be.
- Build the center (weeks 4–16). The partner secures the office, hires the site head and first leads, and starts the recruitment engine. First engineers can join in 4–8 weeks; productive output usually starts at 12–16 weeks.
- Operate under SLAs (months 4–30). The partner runs payroll, PF, ESI, gratuity and compliance. Your engineering leaders own delivery, priorities and the performance bar.
- Audit transfer-readiness (months 12–18). Check employment contracts, IP assignment deeds, statutory filings, vendor contracts and lease assignability. A defect found now costs a memo. Found at transfer, it costs a quarter.
- Transfer and stabilise (months 24–48). Ownership moves to you. An SPV share transfer typically closes in 60–120 days. A carve-out from the partner’s main entity takes 6–12 months.
Build Phase: What the Setup Fee Should Cover
In a build operate transfer model, a legitimate build fee pays for legal structuring, office selection, the first leadership hires and the hiring engine. Fit-out itself is usually billed as a pass-through, at actual cost.
Get the paperwork order right. Entity registration, the shareholder and board documents, and the labour-law registrations follow a fixed sequence, set out in this checklist of legal documents required for GCCs in India. Hire the site head before you register anything, not after. Buyers who reverse that order take months longer to reach full capacity. Specialist leadership hiring services help most here, because the site head shapes every hire that follows.
The first engineering wave is a volume problem. Partners who run dedicated RPO services for the ramp can hold a 7–10 working day shortlist cycle for mainstream stacks, which keeps cohort dates from slipping.
Operate Phase: How the Monthly Fee Is Built
Operate fees in a build operate transfer model commonly land at 1.25x–1.5x of employee cost-to-company (CTC). Make the partner break that number down:
- Employee CTC (salary plus statutory): 60–75% of the fee, passed through at actuals
- Facilities, IT and admin: 8–15%
- HR, payroll and compliance: 3–6%, the employer-of-record burden
- Recruitment amortisation: 3–8%, or billed per hire
- Partner margin: 10–20%, the only band that is truly negotiable
Below 1.2x, ask what has been moved into pass-through billing. Above 1.6x, you are paying for someone else’s inefficiency. During this phase the partner carries the employer-of-record liability, the same role that payroll processing and EOR services play for smaller teams that are not yet on a transfer path.
Track four KPIs monthly and write them into the master services agreement: time to shortlist, offer-to-join rate (target 90%+), rolling 12-month attrition (India tech benchmark: 12–18%) and cost per FTE against the model.
Transfer Phase: What Actually Moves to You
India has no automatic transfer mechanism for a build operate transfer model. Every employee consents individually, through novation or a fresh contract with your entity. Your transfer clause should cover, at no extra cost:
- Every employee who consents, with service continuity for gratuity
- EPFO and ESIC accounts
- The office lease, by novation
- Tools and licences used only for your engagement
- All code repositories, runbooks and architecture documents in your own version control
Knowing how the BOT model works for GCC transfers at this level of detail is what stops month 30 from turning into a renegotiation.
How Much Does a Build Operate Transfer Model Cost in India?
For a 50-person center, plan three budget envelopes. Build: ₹30–80 lakhs. Operate: ₹8–20 crore a year, all-in. Transfer: ₹50 lakhs–2 crore. Pass-throughs like fit-out, deposits and laptops sit on top in year one.
Then add the cost almost everyone forgets. After transfer, HR, payroll, compliance and IT support stop being shared across the partner’s business. For a 100-person center, rebuilding them adds roughly ₹60 lakhs–1.5 crore a year. The full fee anatomy and break-even math are covered in this breakdown of GCC BOT economics.
How Long Does a Build Operate Transfer Model Take?
The honest median is 3–4 years from signature to a center that runs without the partner. Most contracts set an 18–24 month minimum before you can trigger transfer. Transferring earlier usually means maximum fees on an immature entity. Drifting past year five turns the arrangement into permanently marked-up outsourcing.
What BOT Looks Like in Real Engagements
These two engagements come from our own delivery portfolio. Client names are withheld.
Case 1: SAP S/4HANA migration center, 28 months to transfer. A DAX-listed industrial manufacturer chose a build operate transfer model with Supersourcing in 2021 for a brownfield SAP S/4HANA migration, starting with 65 consultants in Bangalore. The partner ran delivery for 28 months and the transfer closed in Q2 2026. The client inherited a 71-person team, a lease locked at 2021 rates and three years of runbooks. Their setup fee was $280K. Building an equivalent captive from scratch at 2026 rates would cost $1.4M or more.
Case 2: The model that lost on paper and won in practice. A US insurance technology company modelled all three options for a 60-engineer ServiceNow practice. Five-year NPV came out at $41M for staff augmentation, $29M for BOT and $24M for a captive. The captive won on paper by $5M. They chose the build operate transfer model anyway, because they had no India leadership to run a captive through years one and two. The best financial answer was the wrong operating answer.
Across 12 completed engagements in the same portfolio, the build operates transfer model became cheaper than equivalent staff augmentation at month 28, on average.
Where the BOT Model in IT Beats Captive and Vendor Teams
The BOT model in IT sits between renting a team and owning one. The right choice depends on headcount, time horizon and how much India management bandwidth you have today.
| Factor | Offshore vendor (staff aug) | BOT | Captive GCC |
| First engineer productive | 6–10 weeks | 12–16 weeks | 5–7 months |
| Year-1 setup cost (50 engineers) | $0 | $150K–400K | $600K–1.1M |
| Who owns the team | Vendor, always | You, at transfer | You, from day one |
| Compliance burden on you | Low | Low until transfer | Full |
| Best fit | 5–60 engineers, 1–3 years | 40–150 engineers, 3–5 years | 80+ engineers, 5+ years |
Read the table as a sequence, not a menu. Many companies start with a vendor, move to a build operate transfer model once the India plan is real, and transfer into a captive in year three or four.
Choose a build operate transfer model when you want a captive eventually but not the year-one pain, have no India site head yet, and can wait 90–120 days for the first productive engineer. Skip it below roughly 20 engineers. At that size, it is leaner to hire dedicated development teams and revisit ownership later. The wider trade-off between owning and renting is covered in captive center vs outsourcing, and the full set of GCC operating models compares BOT with managed, hybrid and virtual centers.
What Most Teams Get Wrong
The most expensive mistake in a build operate transfer model is treating the transfer as paperwork. It is a priced, human event. Buyers who negotiate the monthly fee down 5–10% and accept the partner’s transfer formula as drafted usually lose more at handover than they ever saved. If you can win only one point, win a unilateral transfer right with a sliding-scale fee inside a dedicated SPV.
Four patterns show up again and again:
- No fixed transfer date. A BOT contract without one quietly turns into outsourcing with a higher price tag.
- Assuming the team moves automatically. In our GCC Benchmark 2026 across 340 engagements, attrition in the 90 days around a BOT transfer averaged 23%, against 13% the year before. Buyers who negotiated a 6-month partner-funded retention clause held it to 11%.
- Modelling savings at today’s salaries. Senior engineering pay in India keeps rising every year, faster in AI and ML roles. Build 8–10% annual wage inflation into any five-year model.
- Skipping the reference that matters. Ask to speak with a client who completed a transfer, not one still in the operating phase. Then search that client’s Indian entity on the MCA registry. No entity means no transfer.
Pressure-Test Your BOT Plan Before You Commit
If you are weighing a build operate transfer model for an India center, the most useful hour you can spend is on your own numbers: the fee breakdown, the transfer formula, the SPV question and the break-even against going alone for your headcount plan.
Supersourcing’s GCC setup services team runs this review as a working session, drawing on 527+ delivered engagements and 10+ years of building teams in India. If plain RPO or a dedicated team is the better answer for your situation, we will say so. Bring your term sheet or headcount plan to supersourcing.com/contact-us, or write to mayank@engineerbabu.com.
FAQ
What is the difference between a BOT model and a captive center?
In a captive center, you incorporate your own Indian company and hire directly from day one. You carry all setup costs, compliance and hiring risk yourself. In the build operate transfer model, a partner carries those for the first 18–36 months, then hands the entity and team to you. You trade a monthly fee premium for speed and lower year-one risk.
How long does the operating phase last before transfer?
Most contracts set an 18–24 month minimum before you can trigger the transfer, and most transfers happen between months 24 and 48. Going earlier usually means paying maximum transfer fees on an entity that is not mature yet. Waiting past year five erodes the savings that justified the model in the first place.
What is a typical transfer fee in a build operate transfer model?
Common structures are a per-head fee of ₹1–4 lakhs, a multiple of 1–6 months of per-FTE billing (2–3 months is a common midpoint), or a lump sum near 5–15% of annual contract value. A sliding scale that shrinks the longer you stay is the structure worth negotiating before signature.
Do employees have to agree to a BOT transfer?
Yes. Indian law does not let you move employees to a new employer without their consent. Most agree when pay, benefits and growth prospects are equal or better. Plan a retention bonus pool of about 0.5–1 month of salary per person, keep gratuity continuity in writing, and expect a small share to decline the move.
What is the minimum team size for BOT to make sense?
Roughly 20 engineers. Below that, the build fee and fixed operating machinery cost more than the savings you get after transfer. The build operate transfer model works best between 40 and 150 engineers over a 3–5 year horizon. Smaller teams are usually better served by staff augmentation or a dedicated team inside a partner’s existing entity.
Is BOT the same as managed services?
No. In managed services, the vendor owns the outcome and you pay for results, indefinitely. In a build operate transfer model, you direct the engineering work while the partner provides the legal, HR, payroll and facilities layer. Ownership moves to you at the end. Managed services never transfer anything back to you.
How do I know if a BOT term sheet is fair before I sign?
Test it against four things: a monthly headcount ramp (not steady-state headcount), 8–10% annual wage inflation, a fully priced transfer scenario including retention costs, and the post-transfer overhead you will rebuild. If any of these is missing from the vendor’s model, get a second opinion on the fee structure and transfer clauses before signature.
