Key Summary
- The Build Operate Transfer (BOT) model was originally designed for large enterprises expanding IT operations offshore, primarily into India in the 2000s.
- The model declined in the early 2010s as execution complexity outpaced its promise, and many companies chose to stay in managed service relationships rather than complete the transfer.
- A second wave of BOT adoption began after 2020, driven by talent shortages, distributed work normalization, and the need for mid-market companies to build owned offshore capabilities without enterprise-scale capital.
- In 2026, BOT is being used by finance, healthcare, and operations teams at companies with 50 to 500 employees, not just enterprise IT departments.
- The shift that matters most is not the model itself but who is using it and why: ownership, control, and risk mitigation have replaced pure cost arbitrage as the primary drivers.
A Model With a History – And a New Chapter
If you have been researching offshore staffing options and come across Build Operate Transfer for the first time, it might feel like a new idea. It is not. BOT has existed as a formal offshore model since the late 1990s, and it had its first major wave of adoption in the mid-2000s when large enterprises began building offshore delivery centers, primarily in India.
But the version of BOT that is gaining traction in 2026 looks meaningfully different from its first iteration. According to Deloitte’s analysis of the current BOT wave, the renewed interest in BOT is no longer focused on labor arbitrage and cost reduction alone. It is focused on accessing global talent, building long-term capability, and maintaining control in an environment where domestic hiring has become genuinely difficult across a wide range of functions.
Understanding how BOT evolved, and why the model is being adopted by a fundamentally different buyer profile than it was a decade ago, matters before you decide whether it is the right structure for your company.
Wave One: Enterprise IT, India, and the Arbitrage Era
The first wave of BOT adoption was driven by a very specific business case. According to Torry Harris’s historical analysis of the model, from the mid-2000s through the early 2010s, companies were looking to establish operations overseas primarily to reduce labor costs. The destination of choice was India, which offered a large English-proficient engineering workforce at a fraction of domestic salary rates.
The logic was straightforward: a service provider would set up an offshore development center, run it for an agreed period, and then hand it over to the client as a fully operational, company-owned facility. This allowed enterprises to gain offshore capability without building the entire legal, HR, and infrastructure stack from scratch in an unfamiliar country.
The buyer at this stage was almost exclusively a large enterprise, typically a Fortune 500 company or a multinational with the legal infrastructure and capital reserves to absorb a complex international entity setup. The function was almost always IT: software development, application support, data processing, or systems management.
BOT in its first wave was, in practice, an enterprise IT instrument. Mid-market companies, non-tech functions, and smaller teams were largely excluded from the model by cost, complexity, and the assumption that offshore operations required significant organizational scale to manage.
Why the First Wave Stalled
By the early 2010s, interest in BOT had declined sharply. Deloitte’s review of this period identifies the core problem: execution complexity outpaced the promise. When a BOT engagement was working well during the Operate phase, clients had little incentive to go through the difficult legal and operational process of completing the transfer. The service relationship was delivering results. The transfer was costly and disruptive. So, most clients stayed.
At the same time, many large enterprises had already established global delivery centers independently, either through in-house offshore subsidiaries or through long-term relationships with major service providers. The gap that BOT was designed to fill began to close for the organizations that had driven the first wave of adoption.
The model did not disappear. But it became a niche instrument used in specific situations rather than a mainstream offshore strategy.
The lesson from the first wave is important for any company evaluating BOT today: the transfer is an option, not an obligation. Many successful BOT engagements never reach the formal transfer phase because the Operate phase delivers exactly what the client needs. The value of BOT is not contingent on completing the transfer.
What Triggered the Second Wave
The renewal of BOT as a mainstream offshore model was not driven by a single event. It was the convergence of several structural shifts that changed both those who needed BOT and who could realistically use it.
The talent shortage became a genuine operational problem
The ManpowerGroup 2026 Talent Shortage Survey found that 72 percent of employers report difficulty filling roles. This is not a temporary gap. In functions like finance operations, healthcare billing and coding, and customer experience support, domestic hiring pipelines have become structurally inadequate. Companies that had previously considered offshoring as optional began treating it as necessary.
Distributed work became normal
The COVID-19 pandemic forced the normalization of remote management on a scale. By 2022, most mid-market companies had developed the internal processes, communication tools, and management discipline required to direct teams they could not physically oversee. This removed one of the primary practical barriers to BOT for smaller companies: the assumption that managing an offshore team required physical proximity or enterprise-scale operations infrastructure.
The capital barrier dropped
BOT’s original cost structure was weighted toward the transfer phase, which required significant capital to complete the legal entity setup and infrastructure acquisition. As noted by Aalpha’s 2026 analysis of BOT in outsourcing, modern BOT partners have restructured their engagement models to shift more of the setup burden to the provider during the Build phase, reducing the upfront capital commitment for clients and making the model accessible to companies that could not previously absorb the entry cost.
Ownership became the goal, not just cost reduction
The original BOT value proposition was cost arbitrage. The 2026 value proposition is controlled. Carbon Remote’s analysis of the current BOT market notes that companies adopting BOT today are primarily motivated by the desire to build owned offshore capability — teams that operate within their culture, report to their leadership, and carry their institutional knowledge — rather than simply reducing the cost of a function they do not want to manage directly.
How the BOT Buyer Profile Has Shifted: Then vs. Now
The following table maps the evolution of BOT adoption from its original enterprise IT context to its current mid-market application across multiple functions.
| Era | Who Used BOT | Primary Purpose | Typical Functions |
| 2000s | Large enterprises only | Labor arbitrage and cost reduction | IT development, call centers |
| Early 2010s | Enterprise + first movers | Global delivery footprint | Software, back-office, data processing |
| Post-2020 | Enterprise + mid-market | Talent access and resilience | Tech, finance, operations, healthcare |
| 2025 onward | Mid-market mainstream | Ownership with lower risk | Finance, healthcare, customer experience, back-office |
This shift is reflected in adoption data. Industry research cited by Carbon Remote shows that 50 percent of global companies are already using BOT or hybrid BOT models for their offshore operations, with over 70 percent actively considering it. These numbers would have been unthinkable during the first wave, when BOT was the exclusive domain of large enterprise IT departments.
The Functions That Have Changed the Most
The clearest evidence of BOT’s evolution is the range of functions now being built through this model. Where the first wave was almost entirely defined by software development and IT infrastructure, the second wave is being driven by three functional areas that were largely absent from the original BOT playbook.
Finance Operations
Accounts payable, accounts receivable, payroll processing, financial reporting, and reconciliation work are among the most frequently offshored functions in 2026, and BOT has become a natural structure for companies that want to build dedicated finance teams rather than hand the function to a managed service provider. The work is rule-based, measurable, and well-suited to dedicated offshore teams managed directly by the client’s finance leadership. For more on how Connext structures offshore financial services teams, see our finance solutions page.
Healthcare Billing and Revenue Cycle
Healthcare is one of the fastest-growing areas of BOT adoption outside of IT. As Aalpha’s analysis notes, healthcare faces strict compliance obligations, including HIPAA in the US, that make ownership and control of offshore teams a significant operational concern. BOT addresses this directly: the client maintains management control of the team throughout the Operate phase, the provider handles local HR and compliance infrastructure, and the client retains full visibility over how patient data is handled. Revenue cycle management, prior authorization, medical billing, and coding are all functions where BOT-structured teams are actively being built. Healthcare finance data from CommerceHealthcare shows that labor costs are the primary financial stressor for healthcare organizations in 2026, making offshore staffing through structured models like BOT an increasingly strategic response. Connext’s healthcare staffing capabilities are built specifically to support this type of engagement.
Customer Experience and Back-Office Operations
Customer service, back-office administration, and operations support roles are the third major functional area driving the second wave of BOT adoption. These functions share key characteristics that make BOT well-suited to them: high volume, repeatable processes, clear performance metrics, and the need for a stable dedicated team rather than a shared service arrangement. Connext’s customer experience and back-office outsourcing capabilities are structured to support companies building these teams through a BOT-aligned engagement model.
BOT Function Fit Guide: Which Offshore Roles Work Best in 2026
The following table reflects current market practice for which functions are most viable in a BOT offshore structure for mid-market US companies.
| Function | BOT Fit | Why It Works Offshore |
| Accounts Payable / AR | Strong | High volume, rule-based, measurable output daily |
| Payroll Processing | Strong | Repeatable workflow, clear compliance metrics |
| Financial Reporting | Strong | Structured deliverables, time-zone advantage for overnight runs |
| Healthcare Billing / RCM | Strong | Deep talent pool in Philippines, HIPAA-trainable |
| Prior Authorization | Strong | Process-driven, scalable, shortage role domestically |
| Customer Service | Strong | English proficiency, round-the-clock coverage |
| Back-Office Admin | Strong | High volume, lower complexity, fast to onboard |
| IT Help Desk / Support | Moderate | Works well for Tier 1 and 2 support roles |
| Strategic Finance (CFO advisory) | Low | Requires deep organizational context and senior judgment |
What Has Not Changed: The Core Logic Still Holds
Despite the evolution in who uses BOT and why, the structural logic of the model is the same as it was in 2005. A specialist partner builds the team, manages the operational and compliance infrastructure, and the client directs the work directly. Ownership transfers when the client is ready.
What has changed is that the specialist partner no longer needs to be a large enterprise IT services firm operating at global scale. Mid-market offshore staffing companies can now deliver the same Build and Operate infrastructure that was previously accessible only to enterprise clients, and they can do it for teams of five to fifty people rather than five hundred.
As Article One’s analysis of the current BOT services market notes, BOT services have moved from a niche instrument to a mainstream market entry strategy, and partners are now being selected for domain expertise in the specific function being built, not just for administrative and legal capability in the destination country.
This is the change that matters most for mid-market companies evaluating BOT today. The question is no longer whether you are large enough to use this model. The question is whether you have the right partner to execute it for the specific functions you want to build.
The Role of Co-Management in Modern BOT
One of the structural differences between first-wave BOT and the model being used by mid-market companies today is the management architecture during the Operate phase. In the original enterprise IT model, the service provider typically maintained significant management control over the offshore team, with the client interfacing primarily through project managers and delivery leads rather than direct day-to-day oversight.
The second wave of BOT is built on a different principle. Connext’s co-management model keeps your leadership in direct control of your team’s work from day one of the Operate phase. Connext handles the local HR, payroll, compliance, and operational infrastructure. Your management handles the actual work priorities, quality standards, and team culture. This structure means the team is already functioning as an extension of your company before any transfer decision is made, which significantly reduces the operational risk of the transfer itself and, in many cases, makes the formal transfer less necessary because the management model is already delivering the outcomes of ownership.
What This Means for You
If you have read this far, you now understand something that many companies still get wrong: BOT is not an enterprise-only model; it was never purely about cost, and the transfer itself has never been the point.
The real value of BOT is that it gives you a structured path to build an offshore team you own and manage, without having to build the legal, HR, and operational infrastructure from scratch in a country you are not yet operating in. That path is now accessible to companies with 50 employees, not just 5,000.
The shift in who is using BOT, and why, reflects a broader change in how mid-market companies think about their workforce. Talent access has replaced cost reduction as the primary driver. Ownership has replaced delegation as the preferred model. And the assumption that offshore operations require enterprise-scale resources to manage has been replaced by the reality that most mid-market leadership teams are already managing distributed teams effectively.
What has not changed is the importance of choosing the right partner. The Build and Operate phases succeed or fail based on whether your partner understands the specific function you are building, not just the administrative mechanics of offshore entity management.
If you are evaluating whether a BOT-structured offshore engagement is the right model for your finance, healthcare, or operations team, we are happy to walk through what that looks like in practice for your company size and function.
Get in touch with Connext to start the conversation.
Frequently Asked Questions
No. While IT functions drove the first wave of BOT adoption, the second wave is being led by finance operations, healthcare billing, customer experience, and back-office roles. These functions now represent the fastest-growing segment of mid-market BOT engagements, particularly for US companies building teams in the Philippines and Colombia.
There is no fixed minimum, but BOT engagements typically require the client to have at least one internal manager with capacity to direct the offshore team during the Operate phase. For most mid-market companies, this means BOT becomes viable when the offshore team will have five or more members and the function being built is strategic enough to warrant dedicated management attention. See our co-management service page for more on how management is structured during an engagement.
Traditional outsourcing places a function with a vendor indefinitely. The vendor manages the team, owns the processes, and controls quality. Modern BOT keeps the client under management control throughout the Operate phase, builds the team’s institutional knowledge within the client’s culture and systems, and preserves the option to take full legal ownership at a defined point. The structural difference is not cosmetics. It changes who the team reports to, whose standards they operate under, and who owns the relationship with every member of the team.
No. Transfer is an option embedded in the contract, not a mandatory outcome. Many companies that begin with BOT intent find that the Operate phase delivers the control, quality, and cost outcomes they need without the overhead of establishing a foreign legal entity. The option to transfer always remains. Whether to exercise it is a strategic business decision made at the end of the Operate phase, not a contractual obligation.
The Philippines remains the strongest single destination for non-IT BOT engagements, particularly for finance operations, healthcare billing, and customer experience roles. English proficiency, time-zone compatibility with US business hours for early morning overlap, and a well-established offshore infrastructure make it the default choice for many mid-market companies. Colombia is the leading nearshore alternative for companies that want full US time-zone alignment and Spanish-English bilingual capacity. See Outsource to the Philippines and Colombia for regional detail.
