Build-Operate-Transfer (BOT): How the Model Works for Global Capability Centres in India

Key takeaways

• Build-Operate-Transfer (BOT) is a model where a partner builds a capability, runs it until it’s mature, then hands ownership to you. 

• For a global capability centre (GCC) in India, BOT gives you speed and local expertise at the start, without giving up long-term ownership. 

• The transfer is where most BOT arrangements succeed or fail. Agree what transfers, when, and how readiness is measured before anything is built. 

 Search for “build operate transfer” and most of what comes back is about toll roads, power stations and public infrastructure. That’s where the model started. But over the past decade, BOT has become one of the most common ways for global companies to set up a capability centre in India, and the questions a business leader needs answered are very different from those of a highways authority. 

This guide explains how the build-operate-transfer model works for a GCC, what happens in each phase, how it compares with the alternatives, and what to get right before you sign. 

What is the build-operate-transfer (BOT) model?

Build-Operate-Transfer (BOT) is an arrangement where a partner builds a capability on your behalf, operates it until it reaches agreed maturity, and then transfers ownership to you. You get the partner’s local knowledge, hiring networks and operating experience at the start, and full control at the end. 

In infrastructure, the partner builds and runs an asset such as a road or plant, recovers its investment over a concession period, then hands it to the government. In a GCC, the “asset” is a working team, its processes and its facilities. 

What is a global capability centre?

A global capability centre is a company-owned hub, often in India, that delivers technology, operations or business services for the wider organisation. The best GCCs aren’t cost-saving back offices. They’re Value Centres that own outcomes, build new capability and contribute to how the business competes. We explore that shift in Global Capability Centre as a Value Centre, Not a Back Office. 

How BOT works for a GCC: the three phases

1. Build

The partner sets up the legal and physical foundations, recruits the first teams, puts processes and tools in place and agrees service levels with you. Your job in this phase is to define what the GCC is for, which capabilities it will own, and what “ready to transfer” will mean. 

• Key decisions: location, legal structure, initial scope, leadership roles, governance and the transfer criteria. 

2. Operate

The partner runs the centre day to day while it grows and matures. Delivery is measured against agreed service levels, the team expands into new capabilities, and your own leaders become increasingly involved in running it. 

• Key decisions: which capabilities move in next, how performance is reported, and when your own leadership takes over key roles. 

3. Transfer

Ownership moves to you: people, processes, contracts, systems and knowledge. A well-run transfer is gradual, planned from the start and measured against criteria agreed in the build phase, not negotiated at the end. 

• Key decisions: timing, what transfers and in what order, and what support (if any) continues afterwards. 

BOT vs captive vs third-party delivery

	Build-Operate-Transfer	Captive (build it yourself)	Third-party delivery
Who builds it	A partner, to your design	You	The provider
Who owns it long term	You, after transfer	You, from day one	The provider
Speed to launch	Fast: uses the partner’s set-up experience	Slower: you learn as you go	Fast
Up-front risk	Shared with the partner	Carried by you	Carried mostly by the provider
Control	Grows over time, full at transfer	Full	Limited to the contract
Best for	Long-term capability, without building from scratch	Organisations with in-country experience	Defined services you don’t need to own

 Why set up a GCC in India using BOT?

India has one of the deepest technology and business services talent pools in the world, and a mature ecosystem of existing capability centres. But hiring, compliance, facilities and culture all have local complexity. BOT lets you draw on a partner who already knows how to hire, set up and operate in-country, while keeping the end goal clear: a centre that belongs to you. 

Common BOT risks, and how to avoid them 

• A vague transfer clause. If “transfer” isn’t defined in detail at the start, it becomes a negotiation at the end. Write the criteria, timeline and scope into the contract. 

• Knowledge that never leaves the partner. If processes live in the partner’s heads and tools, you inherit a team without the know-how. Require documentation and shadowing throughout. 

• A cost-arbitrage mindset. Centres set up only to cut cost tend to stay low-value. Give the GCC ownership of outcomes from the start. 

• Leadership left too late. If your own leaders only arrive at transfer, the team has no relationship with them. Bring them in during the operate phase. 

• Culture as an afterthought. The GCC should feel like part of your organisation, not the partner’s. Plan how that happens. 

The BOT transfer checklist

Before you agree the build phase, make sure the contract covers each of these: 

1. People: which roles transfer, on what terms, and how this complies with local employment law. 
2. Leadership: who will run the centre after transfer, and when they’ll be in place. 
3. Processes and documentation: what must be written down and handed over, and how completeness is checked. 
4. Contracts and suppliers: which vendor agreements, leases and licences move to you. 
5. Systems, tools and data: what’s transferred, re-licensed or rebuilt. 
6. Intellectual property: who owns what was created during the build and operate phases. 
7. Readiness criteria: the measurable conditions that trigger transfer. 
8. Post-transfer support: whether the partner stays on for a defined period, and in what role. 

How Allied approaches BOT

At Allied, BOT is our core commercial model for GCCs in India. We build the capability, operate it to maturity, then transfer ownership to you, with the aim of creating a value centre rather than a back office. Capability Building runs through every phase, so the team you inherit can keep improving without us. 

We apply the same model to the Enterprise Digital Twin: Allied builds it for your organisation, operates it, then transfers it, so it ends up as your asset. And where a GCC needs to absorb changing demand, we bring the same thinking behind our Mutable Operating Model: structures designed to flex, rather than headcount fixed at the peak. 

Questions to ask a BOT partner

1. How do you define “ready to transfer”, and can we write it into the contract now? 
2. What happens to the people you hire when the centre transfers? 
3. How will our own leaders be involved before the transfer? 
4. How do you document processes and knowledge so nothing is lost? 
5. What outcomes will the centre own, beyond cost? 
6. What support do you offer after transfer, and for how long? 

Conclusion

Build-Operate-Transfer gives you a faster, lower-risk route to your own capability centre in India, as long as the end is designed at the beginning. Treat the transfer as the goal, not an afterthought, and give the centre real outcomes to own. That’s the difference between a GCC that saves money and one that creates value. 

Planning a global capability centre in India? Talk to our team about how a BOT model could work for you.