Build Operate Transfer for
an owned India GCC
BOT is right when leadership wants an owned India footprint but needs a partner to handle the early complexity. Transfer mechanics, IP, access, and people continuity are defined from the start.
Clear term, clear ownership, defined transfer
MedRec builds and operates the centre while you retain strategic control, then transfers people, systems, and operating knowledge when you are ready to own it directly.
3–5 years
Typical term
20–100+
Engineers
Transfer
Exit path
| Best suited for | Companies planning to establish a long-term captive GCC |
|---|---|
| You keep | Strategic direction, roadmap, and leadership alignment |
| MedRec carries | GCC setup, operations, hiring, infrastructure, governance, and scaling |
| Exit path | Full operational transfer to client |
Three phases, one destination
BOT is right when leadership wants an owned India footprint but needs a partner to handle early complexity. Transfer is designed in from day one, not negotiated when the centre is already large.
Build
Roles, hiring bar, workplace, access paths, and governance are set so the centre can scale without informal shortcuts.
Operate
MedRec runs hiring, infrastructure, HR, and day-to-day GCC operations while you keep strategic direction, roadmap, and leadership alignment.
Transfer
People, systems, and operating knowledge move into your India entity at the agreed point. That is planned in parallel, not left to the final quarter.
What must be ready before handover
The programmes that transfer cleanly fund people, systems, and knowledge work in parallel throughout the operate phase, not as a scramble in the last six months.
- People continuity: employment transition, benefits, and notice aligned to local law and your entity
- Systems: repositories, identity, devices, and environments rotated or reassigned with least privilege
- Knowledge: runbooks, escalation paths, and delivery rituals documented for your leadership chain
- Facilities and vendors: workplace and subprocessors mapped so nothing is orphaned at handover
Security and access evidence should be reviewable early. See India GCC security posture →
Built for teams that intend to own the centre
You expect to bring payroll, facilities, and IP under your own entity over time
You want early operating complexity handled while the roadmap proves itself
You need a clear path for repository, identity, people, and process transfer
Customers or regulators expect a distinct in-market entity with credible controls
Typical team makeup
- Country Lead: 1 (transferred)
- Engineering Manager: 2–4
- Engineers (full-stack, BE, FE): 20–60
- QA / DevOps / Security: 5–10
- HR / Finance: 2–3 (transferred)
Same partner, different destination
Both models keep you in control of product and standards. Choose BOT when ownership of the India entity is the plan; choose dedicated when you want durable capacity without that overhead yet.
| Question | Build Operate Transfer | Dedicated team |
|---|---|---|
| Destination | Your own India captive GCC | Long-term capacity without creating an India entity first |
| Typical term | 3–5 years | 1+ years |
| You keep | Strategic direction, roadmap, and leadership alignment | Product priorities, delivery direction, and roadmap |
| Exit path | Full operational transfer to client | 90-day transition notice |
Deeper IP and culture comparison: BOT vs dedicated teams → · Dedicated India engineering teams → · India GCC overview →
Own the centre later, without building chaos first
Captive India centres often fail in the first two years for operating reasons, not hiring reasons: unclear ownership, weak integration with headquarters, informal security paths, and local leaders accountable for outcomes without authority to improve them. BOT exists so you can get past that early complexity with a partner while still designing toward your own entity.
During operate, you keep strategic direction, roadmap, and leadership alignment. MedRec carries GCC setup, operations, hiring, infrastructure, governance, and scaling. Transfer is not a ceremony at the end of a slide deck. It is a funded programme of people continuity, systems rotation, and knowledge handoff with a typical term of three to five years.
If you are not sure you want an India entity, start with a dedicated team. Many companies prove the operating rhythm first, then move to BOT only when board, customer, or regulatory expectations make a captive structure the right destination. The decision frame is documented in our insight on when BOT makes sense versus a dedicated team.
When BOT vs dedicated team → · Why centres stall near forty engineers →
BOT mechanics
What transfers, who owns what during operate, and when BOT is the right choice.
What is Build Operate Transfer (BOT)?
MedRec builds and operates the centre while you retain strategic control, then transfers people, systems, and operating knowledge when you are ready to own it directly.
How long does a typical BOT engagement run?
A typical BOT term is 3–5 years, with transfer mechanics, IP, access, and people continuity defined from the start.
What transfers at the end of BOT?
People, systems, and operating knowledge move into your own India entity at the agreed transfer point. Repository, identity, facilities, and process handoff are planned in parallel, not left to the final quarter.
Who keeps strategic control during the operate phase?
You keep strategic direction, roadmap, and leadership alignment. MedRec carries gcc setup, operations, hiring, infrastructure, governance, and scaling.
When is BOT a better fit than a dedicated team?
BOT fits when you expect to own the India footprint later and need a partner for early complexity. Dedicated teams fit when you want durable capacity without creating your own India entity first.
What team size does BOT typically support?
BOT engagements commonly run from roughly twenty engineers upward, with room to scale past one hundred as the captive destination firms up. Exact shape follows your roadmap, not a fixed template.
Plan a BOT path before you scale hiring
We will map transfer mechanics, team shape, and controls against your timeline, so year-three ownership is designed in from day one.