Build-operate-transfer (BOT) is a sourcing model in which a provider sets up an operation for a client, such as an offshore development team, a help desk or a shared-service center, runs it for an agreed period, and then transfers it to the client’s ownership. The client can get a working operation faster and with less setup risk than building it alone, and usually ends up owning the capability rather than renting it. BOT sits between IT outsourcing (ITO) and building an in-house team.
In public infrastructure, build-operate-transfer also describes projects where a private company builds and runs a facility, such as a toll road, before handing it to a government. This entry covers the IT and services sourcing meaning.
At a glance
- Three phases: the provider builds the operation, runs it, then hands it over.
- The client usually ends up owning the team, and often the entity, assets and processes.
- It reduces the risk and time of entering a new country or labor market.
- Transfer terms, fees and employee rights are the most complex part of the contract.
- It is most common for offshore or nearshore IT, software and shared-service centers.
What problem it solves
A company that wants its own delivery center in another country faces a long list of unfamiliar work: setting up a legal entity, finding premises, hiring in a new labor market, setting up payroll and benefits, and meeting local tax and employment rules. Doing all of that before any work gets done is slow and risky.
Traditional outsourcing avoids the setup but leaves the client dependent on the provider indefinitely. Knowledge and people stay with the provider, and changing providers later can mean losing both. BOT addresses both problems: the provider’s local experience gets the operation running quickly, and the planned transfer gives the client long-term control, its own staff and its own processes.
How it works
Build. The provider sets up the operation to the client’s requirements: entity or hosting arrangements, facilities, recruitment, tools, security controls and processes. The client usually approves key hires and design decisions.
Operate. The provider runs the operation, often under a master services agreement (MSA) with a statement of work (SOW) that sets service levels, reporting and fees. The client directs the work while the provider handles administration and management.
Transfer. When the agreed conditions are met, or when the client exercises its option, the operation moves to the client. Depending on the structure, that may mean buying the provider’s local entity, moving employees to a client-owned entity, assigning leases and supplier contracts, and handing over documentation. The provider may continue to support the client for a period after transfer, similar to a transition services agreement (TSA).
Commercials. Fees typically include setup costs, an operating fee and a transfer or buyout fee, which may decline the longer the operation runs before transfer.
Employee transfers, entity purchases, non-solicitation clauses and intellectual property ownership are governed by the contract and by local law, which varies by country. Have counsel in each relevant jurisdiction review BOT contracts.
When it matters for buyers
- Entering a new market. Building a team in a country where you have no presence is the classic use case.
- Scaling fast. BOT can get a team running faster than recruiting from scratch.
- Long-term capability. When a function is strategic enough that you want to own it eventually, BOT avoids permanent dependence on a provider. It is a middle path in a build vs. buy decision about capability.
- Comparing sourcing models. Weigh BOT against business process outsourcing, a managed service provider (MSP) and a captive center on cost, control and exit risk. Buyers looking at offshore support for a help desk may be offered BOT alongside traditional outsourcing.
Questions to ask vendors
- Which BOT operations have you built and transferred, and can we speak to those clients?
- What exactly will transfer: staff, entity, leases, equipment, contracts, intellectual property?
- How is the transfer fee calculated, and how does it change over time?
- Can we trigger transfer earlier or later than planned, and on what notice?
- How will you handle employee consent, benefits and retention through transfer?
- What support will you provide after transfer, and for how long?
How it differs from IT outsourcing
In IT outsourcing, the provider delivers services with its own people and keeps them; at the end of the contract, the client renews, switches providers or brings the work back in-house, often rebuilding knowledge from scratch. In BOT, transfer to the client is the planned outcome from the start, so the contract is designed around handing over people, processes and assets. BOT usually requires more client involvement during the build and operate phases, because the client is shaping an operation it will later own.