TL;DR
The build operate-transfer model is a phased approach where a specialized partner builds your offshore operation, runs it for 18 to 24 months, and then hands over full ownership to you. It has become the dominant path for setting up Global Capability Centers (GCCs) in India, with adoption jumping from under 10% to roughly 40% of all new GCC setups. The model combines the speed of outsourcing with the long-term cost savings and control of an in-house center, though the transfer phase is where most failures happen.
Also known as: BOT model, BOT framework, BOT outsourcing model
Related terms: BOOT, GCC, captive center, GCC-as-a-Service, Employer of Record
What Is the Build Operate-Transfer Model?
The build operate-transfer model is a three-phase engagement where a service provider sets up an offshore operation on your behalf, manages it through a stabilization period, and then transfers complete ownership, including the team, legal entity, infrastructure, and processes, to your organization.
Think of it as a guided path to ownership. You get the speed and local expertise of an outsourcing partner during the early months, but unlike traditional outsourcing, the end goal is full captive control. The BOT model is the mechanism. The GCC is the destination.
The concept originated in infrastructure and public-private partnerships, where private entities would finance, build, and operate toll roads, power plants, or airports before transferring them to the government. Wikipedia notes that this project delivery method has been used for large-scale infrastructure since the late 20th century. By the 1990s and early 2000s, US companies began adapting the same framework to set up captive technology centers overseas. Today, the term is used almost exclusively in the IT and GCC context.
The surge in adoption has been dramatic. According to Everest Group research, less than 10% of GCCs were set up using the build operate-transfer model just a few years ago. That figure is now closer to 40%. Combined with assisted setup models, these approaches account for over 90% of provider-supported GCC launches.
Explore NeoIntelli's GCC setup and launch services.
How Does the Build Operate-Transfer Model Work?
The BOT model breaks into three distinct phases, each with clear deliverables and ownership boundaries. Some practitioners expand this into five stages (adding pre-build and transfer preparation), but the core logic remains the same.
Build Phase (Months 1 to 6)
The provider handles everything needed to get the operation off the ground: incorporating a legal entity in India, securing office space, setting up IT infrastructure, establishing compliance frameworks, and recruiting the initial team. During this phase, the provider draws on its local networks and institutional knowledge to compress what would normally take a first-time entrant 16 to 24 weeks into 8 to 16 weeks.
Key activities include registering for statutory requirements (EPF, ESIC, professional tax, Shops and Establishments Act), standing up security and data governance controls, and hiring your first wave of engineers or analysts. NeoIntelli's talent services are designed to deliver first hires within 21 days, which is critical when the build phase timeline is tight.
Operate Phase (Months 6 to 24)
Once the center is staffed and operational, the provider manages day-to-day delivery. This includes performance management against agreed SLAs, process optimization, team scaling, and knowledge creation. The operate phase is where the center proves its value, building a track record of delivery that justifies the eventual ownership transfer.
During this stage, the cost per FTE in India typically runs between USD 18,000 and USD 35,000 annually, depending on the role. The provider's margin is embedded in these fees, which is a trade-off practitioners consistently flag. As one vendor management blog put it: "You're paying a premium for the convenience of the build and operate phases. Their profit margin is baked into the deal." For a detailed breakdown of what an India center actually costs, see our India GCC cost benchmarks.
The operate phase also carries a specific tax risk. Permanent Establishment (PE) exposure is often the most significant tax concern for US companies during this period. If the arrangement isn't structured carefully, the parent company may inadvertently trigger PE status in India.
Transfer Phase (Months 18 to 30)
This is where ownership formally shifts from the provider to the client. The transfer involves establishing or activating the client's own Indian legal entity, moving all employees from the provider's payroll, migrating IT systems and data, transferring lease agreements and vendor contracts, reassigning statutory registrations, and completing financial settlements.
Transfer timelines typically run 3 to 6 months for the execution itself, though preparation should begin much earlier. In 2026 and 2027, most organizations are choosing overall BOT timelines of 18 to 24 months before triggering the transfer.
Timeline overview:
| Phase | Typical Duration | Key Deliverables |
|---|---|---|
| Build | 1 to 6 months | Entity setup, first hires, infrastructure, compliance |
| Operate | 12 to 18 months | SLA delivery, team scaling, process maturity |
| Transfer | 3 to 6 months | Legal entity transition, employee migration, IP handover |
The Build Operate-Transfer Model in the GCC Context
India's GCC ecosystem has reached a scale that makes the BOT model not just viable but often the smartest entry strategy. The NASSCOM-Zinnov GCC 2026 Landscape report shows India now hosts 2,117 GCCs employing 2.36 million professionals, generating nearly USD 98.4 billion in revenue. The market is expected to cross $100 billion by 2030.
For a company with no India presence, going directly captive means navigating entity incorporation, real estate, labor law, tax registration, and talent acquisition simultaneously, all in an unfamiliar regulatory environment. The build operate-transfer model removes that cold-start problem. The provider absorbs the execution complexity while the client retains strategic direction and IP control from day one.
Everest Group estimates the service provider opportunity linked to GCCs already exceeds $25 billion in 2026, growing at roughly 25% year over year. That growth is being driven largely by mid-market companies entering India for the first time through BOT arrangements.
The Micro-GCC Starting Point
Not every company needs to start with 50 engineers. For teams of 5 to 15, a micro GCC is a natural entry point. You validate the India model at small scale, prove delivery capability, and then scale through a full BOT engagement. This sequencing reduces risk and gives the board tangible evidence before committing to a larger operation.
AI-First BOT Considerations
Modern GCCs increasingly carry AI and data engineering mandates, which adds real complexity to all three BOT phases. During the build phase, you need MLOps and LLMOps infrastructure, not just desks and laptops. During the operate phase, model governance and data pipeline management become ongoing responsibilities. And during transfer, AI infrastructure (model registries, training pipelines, responsible AI frameworks) must transition alongside people and processes.
No competing guide covers this angle, but it matters. A center that transfers without its AI governance layer isn't a functioning GCC. It's a team with orphaned models. For organizations pursuing this path, NeoIntelli's AI-first GCC services cover the full lifecycle from strategy through operational handover.
BOT vs. Captive vs. Outsourcing vs. GCCaaS
Choosing between the build operate-transfer model and its alternatives depends on your timeline, budget, IP sensitivity, and experience operating in India. Here's how the options compare:
| Dimension | BOT Model | Captive GCC (Direct) | Outsourcing | GCCaaS / Managed |
|---|---|---|---|---|
| Ownership at start | Provider | Client | Provider (permanent) | Provider |
| Ownership at end | Client | Client | Provider | Varies |
| Setup speed | Fast (8 to 16 weeks) | Slow (16 to 24+ weeks) | Fastest (1 to 3 weeks) | Fast |
| Year-1 cost | Medium (spread via fees) | High (lumped upfront) | Low to medium | Medium |
| Long-term cost | Lower (post-transfer) | Lowest | Highest (margin stays) | Medium |
| IP control | Client from day 1 | Client from day 1 | Vendor-managed | Varies |
| Risk profile | Shared, then transferred | All on client | Vendor-managed | Shared |
| Best for | First-time market entrants | Experienced global operators | Short-term, non-core work | Ongoing flexibility |
The critical insight: after transfer, a 100-member GCC in India typically costs 35% to 50% less per year than an equivalent onshore operation in the US. The BOT model gets you to that cost structure without forcing you to figure out Indian entity law and hiring on your own. To model the numbers for your own headcount, try the GCC cost calculator.
Choose a direct captive when the function touches competitive advantage, IP, or sensitive data, and you already have in-country experience. Choose outsourcing for short-term, non-core work where you don't need to own the team. Choose the build operate-transfer model when you want full ownership but lack the local knowledge to get there alone.
For a deeper breakdown, see our GCC vs. outsourcing comparison. If you want to explore whether ongoing partner support (without a transfer event) fits better, read about GCC-as-a-Service. And for how BOT sits alongside captive, hybrid, and EOR structures, see the full guide to GCC models in India.
BOT Model Variants: BOOT, BOO, BTO, and DBFOT
The build operate-transfer model belongs to a family of related structures. Understanding the variants prevents confusion during contract negotiations.
BOOT (Build-Own-Operate-Transfer): Follows the same structure as BOT with one difference: the partner retains ownership of the infrastructure throughout the concession period, not just during the build phase. In practice, the partner finances the initial setup costs and recoups them through operate-phase fees before transferring.
BOO (Build-Own-Operate): No transfer at all. The private party retains ownership indefinitely. This is essentially permanent outsourcing with a custom-built operation.
BTO (Build-Transfer-Operate): Ownership transfers immediately after the build phase, but the provider continues operating the center under a management contract. This gives the client legal ownership from day one while still relying on the partner for stabilization.
DBFOT (Design-Build-Finance-Operate-Transfer): The most comprehensive variant, where the partner handles design, construction, financing, and operation before eventual transfer. This structure is more common in physical infrastructure than IT.
In the IT and GCC context, only BOT and BOOT matter. They are functionally identical in most engagements, with the key distinction being who carries the setup cost on their balance sheet during the operate phase.
Benefits of the Build Operate-Transfer Model
De-risked market entry. The provider absorbs execution risk during the most uncertain phases. If the operation doesn't meet expectations, you can exit before transfer rather than unwinding a fully captive entity.
Capital spread over time. Instead of a large upfront investment for direct captive setup, BOT costs are distributed across 24 to 36 months of operate-phase fees.
Faster hiring. BOT partners with established India networks can hire 30% to 40% faster than a company building its first local recruiting function from scratch.
Proven operation at handover. By the time you take ownership, the center has a delivery track record, established processes, and a stable team. You're not inheriting a startup, you're inheriting a running business.
Exit optionality. If strategic priorities shift during the operate phase, you can renegotiate or wind down without the sunk costs of a captive entity setup.
Risks and Challenges of the BOT Model
Transfer Phase Failures
The transfer phase is where BOT engagements break down. A report from Everest Group found that 42% of BOT failures stemmed from unclear transition planning and mismanaged expectations during the early phases. Businesses that don't explicitly detail transfer terms in their original agreement consistently run into problems with scheduling, costs, and employee retention.
The transfer process itself is substantial. It involves establishing the client's own legal entity in India, transferring all employees, migrating statutory registrations (EPF, ESIC, professional tax), reassigning IT systems, transferring lease agreements and vendor contracts, and completing all financial settlements. Compliance missteps during this process can create lasting problems, which is why governance frameworks need to be designed into the engagement from the start.
Employee Retention: The Real Transfer KPI
Most descriptions of the transfer phase focus on legal and operational mechanics. Practitioners will tell you that the real success metric is employee retention. If more than 5% to 10% of team members leave during transfer, institutional knowledge evaporates.
Employees must be informed early about the change in employer, reassured about benefit continuity, and offered employment on comparable or better terms. A well-managed transfer typically achieves 95%+ employee retention. Practitioners on forums and vendor management blogs emphasize that hiring a senior India-based center head before the transfer, someone with genuine authority, is a prerequisite. A center where all strategic decisions still flow from headquarters isn't a captive. It's a remote team.
Provider Dependency
During the operate phase, knowledge concentration with the provider creates risk. If the relationship sours or the provider underperforms, switching mid-engagement is expensive and disruptive. Clear SLAs, documented processes, and early knowledge-sharing protocols mitigate this.
Tax and Legal Considerations
Transfer pricing is the most consistently significant tax issue for multinational groups using the build operate-transfer model in India. Arm's length pricing must be maintained, and transfer valuation mechanics should be agreed before the BOT arrangement begins, not negotiated during the transfer itself.
If the transfer qualifies as a going concern, it would likely be exempt from GST, but this requires careful structuring. Transfer fees typically range from USD 200,000 to USD 800,000 as a one-time cost, or a multiple of the monthly management fee.
Operate-Phase Cost Premium
The provider's margin is embedded in operate-phase pricing, making it more expensive than running the same team in-house. This is the trade-off for speed and de-risked execution. The premium disappears post-transfer.
How to Choose the Right BOT Partner
Not all build operate-transfer providers are equal. The critical differentiator isn't the build phase (most competent firms can incorporate an entity and lease office space) but the transfer phase. Here's what to evaluate:
Proven transfer experience. Ask specifically how many transfers the partner has completed, not just how many centers they've built. Building is straightforward. Transferring is where expertise matters.
Transfer terms in the contract from day one. The single most important piece of advice from legal practitioners and experienced GCC operators: define transfer mechanics, timelines, fees, and employee treatment in the original agreement. Partners who resist this specificity are protecting their optionality at your expense.
Transparent pricing. Understand whether the model is cost-plus (you see the actual costs and a stated margin) or margin-loaded (a blended rate that obscures the provider's take). Cost-plus models create fewer surprises at transfer.
Cultural integration capability. The center needs to feel like your organization, not the provider's. Look for partners who invest in embedding your values, communication norms, and performance frameworks during the operate phase.
India-based leadership continuity. The center head hired during the operate phase should be someone who stays through and beyond the transfer. Leadership turnover at handover destroys momentum.
Not sure if the BOT model fits your situation? Take a GCC readiness assessment to evaluate your organization's preparedness before committing.
Frequently Asked Questions
How long does a typical build operate-transfer engagement last?
Most BOT engagements run 18 to 30 months total. The build phase takes 1 to 6 months, the operate phase runs 12 to 18 months, and the transfer execution itself takes 3 to 6 months. Organizations with clearer internal ownership readiness are increasingly completing the full cycle in 18 to 24 months.
How much does the BOT model cost?
During the operate phase in India, expect USD 18,000 to USD 35,000 per FTE annually depending on role seniority. Transfer fees typically range from USD 200,000 to USD 800,000 as a lump sum. Post-transfer, a 100-person India GCC costs 35% to 50% less per year than an equivalent US-based team.
What's the difference between BOT and BOOT?
In a standard BOT, the provider doesn't own the infrastructure but manages it for a fee. In a BOOT (Build-Own-Operate-Transfer), the provider retains ownership of the infrastructure throughout the concession period and typically finances the initial setup. In IT and GCC contexts, the two are functionally similar.
What happens to employees during the transfer?
All employees move from the provider's payroll to the client's Indian legal entity. Statutory registrations (EPF, ESIC, professional tax) transfer as well. Employees should be offered comparable or better terms. Well-managed transfers retain 95%+ of the team.
Why do BOT engagements fail?
According to Everest Group, 42% of BOT failures stem from unclear transition planning. The most common problems are undefined transfer terms, unrealistic timelines, poor employee communication, and lack of India-based leadership at the receiving entity.
Is the BOT model only used in India?
While India dominates BOT adoption for GCCs due to its talent density and mature ecosystem, the model is also used for centers in the Philippines, Poland, Mexico, and other nearshore and offshore locations. Everest Group estimates the provider opportunity linked to GCCs exceeds $25 billion across geographies.
Can I start small with a BOT model?
Yes. A growing number of companies begin with a micro GCC of 5 to 15 people, validate the India model, and then scale into a full BOT engagement. This staged approach reduces risk and provides tangible evidence for board-level decisions before committing to a larger operation.
How does AI change the build operate-transfer model?
AI mandates add complexity to every BOT phase. The build phase requires MLOps infrastructure and data platform setup. The operate phase demands model governance and pipeline management. The transfer phase must include AI infrastructure (model registries, training pipelines, responsible AI frameworks) alongside the standard people-and-process handover.
Ready to explore a build operate-transfer model for your India GCC? Talk to NeoIntelli's advisory team about your requirements and timeline.