Build-Operate-Transfer (BOT) for GCCs, Explained

What a build-operate-transfer GCC actually is

A build-operate-transfer GCC is a captive engineering center that a partner sets up and runs on your behalf, then signs over to you — the legal entity, the team, the IP, all of it. You arrive at a wholly-owned Indian subsidiary without spending your first six months wrestling with company registration, banking, and labor law.

It is one of four common ways to put engineers on the ground in India. Outsourcing, staff augmentation, a managed GCC, and BOT sit on a spectrum that runs from "the vendor owns everything" to "you own everything." BOT is the only model designed to move you across that spectrum on a clock: the partner owns the entity at the start, and you own it at the end.

That handover is the whole point — and the whole problem. Done well, BOT is the lowest-risk path to a captive center. Done carelessly, you spend two years building something you can never cleanly take possession of.

The three phases, with realistic timelines

BOT has three named phases, and each has a window worth setting expectations around. The transfer window is wide on purpose: a good handover is tied to milestones, not a date on a calendar.

Build — months 1 to 6

The partner lays the foundation: entity incorporation, banking, statutory compliance, IT and security, HR policy, and the first hires. The anchor of the build is the site leader — a real engineering leader, not an office manager, and increasingly someone dual-mandated to run the India site and own a global function. Get that hire right and the pod compounds; get it wrong and it stalls.

Speed in this phase is better than most teams expect. A vetted pod can be live in weeks, with the first hire in roughly four weeks and a 5-to-15-person pod by about week five. If you want the week-by-week mechanics, see the 90-day GCC build playbook.

Operate — months 6 to 24

Here the partner runs the back office — payroll, HR, compliance, facilities — while you direct the engineering work day to day. This is where the team scales and where culture is either built or lost. India engineers optimize, in order, for competitive money, an impressive title, and growth. Give them ownership of something real and a global mandate, and you hold attrition below roughly 12%. Hand them a ticket queue and you will churn.

Transfer — lands months 18 to 48

In the final phase, employee contracts novate to your new entity, assets reassign, and the partner steps out. The window is wide because the transfer should fire on agreed conditions — headcount reached, milestones met, your in-country leadership ready — rather than on a fixed date that suits the partner's billing.

Why BOT deals fail at the transfer

Be candid about this before you sign: across the industry, BOT's weak point is the handover, not the build. Hiring 20 engineers is the easy part. The failures cluster in a few predictable places.

• Undefined price. If the transfer price was never fixed, the partner can reprice the entity once your team is irreplaceable. This is the single most common BOT failure.
• Attrition during novation. Moving people between legal employers is a moment of maximum anxiety. Without continuity-of-service and retention terms, your best engineers field other offers — and in India they often hold three or four at once.
• Unfinished compliance. Transfer pricing, FEMA, and IP assignment all have to land cleanly for the entity to be worth taking. Half-done, they become your problem.
• Misaligned incentives. A partner paid a flat per-head fee forever has no reason to ever let go.

Evaluate a BOT partner on completed transfers, not builds. Anyone can stand up a team. Far fewer have handed a working entity to a client and walked away.

How to de-risk the transfer before you sign

Every one of those failure modes is contractible. Negotiate the handover on day one, while you still have leverage and no team to hold hostage.

• Pre-agreed triggers. Define exactly what fires the transfer — headcount, time elapsed, specific milestones — so the partner cannot stall to keep billing.
• Step-down fees as headcount grows. The operating fee per head should drop as the team scales, removing the incentive to keep you parked in "operate" forever.
• Day-one employee-novation terms. Agree the transfer mechanics, retention bonuses, and continuity-of-service terms in the original contract — not in the heat of the handover, when leverage has flipped.
• A fixed transfer price. Lock the price, or a clear formula for it, before the build starts. This is the term that protects you most.

How BOT fees are structured

BOT pricing usually has three components: a one-time build or setup fee, a recurring operate fee (charged per head or as a fixed monthly retainer), and a transfer fee. The operate fee is where partners make their margin, which is exactly why the step-down and the fixed transfer price matter so much.

Bundle the regulatory work into "compliance-in-a-box" so it is not an afterthought at handover: India's transfer-pricing safe harbour sits at 15.5% cost-plus for IT and software (effective 1 April 2026), and the DPDP data-protection regime carries penalties up to ₹250 crore with compliance due by May 2027. Those obligations should be the partner's job during operate and a clean inheritance at transfer.

The fees buy something real. India tech talent runs roughly 3x cheaper than the US, and a representative 10-person pod costs about $744K a year all-in versus roughly $2.58M in the US — a gross saving near 71%. The model only pays off, though, if you actually complete the transfer. See the full 10-person pod cost breakdown for the line-item math.

Who BOT actually fits

BOT fits the company that is committed to a captive center but not ready to own an Indian entity on day one — typically a later-stage software business with the scale to justify a subsidiary and the patience to reach it over two to four years. If you want a branded team fast and the option to own it later, a managed GCC with a transfer path is often simpler and quicker to value. You can compare both routes on how it works.

Whichever path you choose, the principle is the same: a GCC succeeds when it owns something real and is led by someone senior. BOT is just the financing and risk structure wrapped around that truth — and the only version worth signing is one written to finish at the transfer, not to stall there.