If you are contemplating the establishment of a Global Capability Center (GCC) in India, chances are that you might have encountered the phrase “Build-Operate-Transfer (BOT) model India“.
In simple words, someone else builds and runs your India team first. Once it is stable, you take full ownership. That’s the whole idea behind the BOT model.
The BOT concept is discussed in detail and is explained in this article along with how the BOT process takes place, from its application in actual GCC models such as those that exist in Kituo Space, Gandhinagar, and Ahmedabad.
What Is the Build-Operate-Transfer (BOT) Model in India?
The BOT model distinguishes the GCC model in terms of stages as opposed to having one entity doing all.
A partner builds the operation first. This means registering the entity, getting the office ready, hiring the first team, and putting compliance and HR basics in place. Then the same partner operates the unit for a while, handling day-to-day work like finance, HR and technology. Once the operation is running well, ownership is handed back to the parent company fully, including the people and the systems that were set up along the way.
At Kituo Space, we run this as our GCC-BOTT service. We add one more step to the standard BOT process, a Transform phase, before the final handover. More on that below, since it’s actually the part that makes the biggest difference to how smooth the transfer turns out to be.
The idea of building something, running it, and then handing it over did not start in the GCC world. It goes back to large infrastructure projects, where governments let private companies build and run things like highways or power plants for a set number of years before handing them back. The same logic has simply been adapted to how companies set up their India teams today.
Why Companies Pick the BOT Model for India Entry
India keeps attracting global companies for fairly obvious reasons. There is a large pool of skilled talent, a services industry that already knows how to run global operations, and government policy that keeps favouring this kind of work.
None of that removes the actual difficulty of getting started, though. Entity registration, labour law, tax filings, day to day business norms, all of it looks different from what most companies are used to back home. Figuring this out alone from another country takes time most leadership teams don’t want to spend.
This is why the BOT model works well for a lot of companies. Instead of learning everything from scratch, an experienced partner handles the early groundwork while the company slowly builds its own understanding of how things run locally.
The part that matters most here is the word “eventually.” A BOT setup is built around a handover from day one, unlike a normal outsourcing contract where a vendor might keep control for years. Everyone involved knows the end goal is the parent company running the show on its own.
How the Build-Operate-Transfer (BOT) Process Works
Most GCC-BOT engagements go through the same broad stages, though the exact pace depends on the company and how ready it is to move.
Build. This is where the groundwork happens. Feasibility studies, picking the right entity structure, choosing a city, understanding local incentives and rules that apply. It also covers practical work like finding office space, starting recruitment, and putting together a realistic go-live timeline.
Operate. Once the entity is registered and the first team is in place, the partner takes over daily running of the unit. This can include finance and accounts, HR, ERP support, procurement help, and keeping an eye on compliance risk. During this phase the partner works almost like an internal department of the company, just sitting outside its own office walls for now.
Transform. This is the part which tends to be missed out in most BOT arrangements at an elementary level, and where the problems occur when it is not done. It requires the processes, reports and systems to be modified to conform to how the parent company runs rather than how the partner set it up. This is the main reason why GCC handovers tend to be problematic.
Transfer. Once the operation is stable and the transform work is done, ownership moves across formally. People, processes, systems, and any intellectual property built during the operate phase all shift to the parent company. Many partners, including us, don’t disappear right after this either. Staying on in an advisory capacity for a bit longer usually makes the handover go easier.
Some companies don’t want a fixed transfer date at all. In that case, a related setup called GCC-as-a-Service (GAAS) works better, where the partner keeps running things for longer instead of handing over at a set point. Knowing which one fits your plan matters more than people expect going in.
What Companies Actually Get Out of a BOT Setup
Talk to a few companies that have gone through this process and the same points come up again and again.
Speed. A partner who already knows local hiring, paperwork and infrastructure can get an operation running much faster than a company trying to work it all out on its own from another country.
Less pressure on leadership. Entity registration, first-round hiring, staying compliant, none of it moves quickly, and all of it pulls attention away from actual business priorities. Passing this to a partner frees up leadership to focus on strategy instead of paperwork.
A clear end point. Since a BOT setup is built around eventual transfer, there’s none of the open-ended uncertainty that regular outsourcing contracts sometimes carry. Everyone knows this is a stepping stone, not a permanent arrangement.
A more secure approach for testing the market. In case some firms are uncertain about the viability of India as their long-term option for a particular function, this framework will allow them to evaluate the performance of the operations before taking an irrevocable decision.
What to Look For in a BOT Partner
None of this works without picking the right partner. A good one should have real, demonstrated experience across entity setup, compliance, HR and technology operations, not just a good sales pitch.
Being upfront about the transfer process matters just as much. It’s worth asking exactly how ownership will move over, what documentation comes with it, what the transform phase will actually involve, and whether support continues after the handover is done.
Location matters too. At Kituo, we work out of Gandhinagar and Ahmedabad in Gujarat, both of which offer real advantages: a growing talent pool, supportive state policy, and easy access to GIFT City for companies in financial services. Every client also gets a dedicated senior advisor managing the India setup end to end, along with access to our pre-screened, university-linked talent network for early hires.
