Build-Operate-Transfer, or BOT, is an outsourcing model in which a partner builds a dedicated team or operation for a client, runs it for an agreed period, and then transfers it, people, processes and assets, to the client, who takes full ownership. In software it is the middle way between hiring your own offshore team from scratch and outsourcing indefinitely: you get the partner's speed and local knowledge at the start, and your own team at the end. This article, published in 2023 and rewritten in 2026, explains how the BOT model works in software outsourcing, its three phases, the contract points that matter, how it compares with an offshore development centre and with team augmentation, and when it is the right choice.
TL;DR
- BOT has three phases: the partner builds the team and infrastructure, operates it to agreed service levels, and transfers it to the client at a set point.
- It combines the "build" option of insourcing with the "buy" option of outsourcing: the client ends up owning a team it did not have to recruit and set up alone.
- The contract must settle the transfer trigger, the transfer price, intellectual property, employee transfer rules and what happens if the client does not exercise the option.
- Compared with an offshore development centre run by the partner forever, BOT costs more during operation but ends with ownership; compared with team augmentation, it is heavier to set up but builds a lasting capability.
- BOT fits companies that want a permanent engineering presence in a new location but lack the local entity, recruiting network and employer brand to start alone.
What is the Build-Operate-Transfer model?
The BOT model is a contractual arrangement in which a service provider sets up an operation on behalf of a client, runs it for a defined period and then hands it over. It originated in large infrastructure projects, where a private partner builds and operates a facility before transferring it to a public authority, and it is widely used in IT and business process outsourcing to set up dedicated teams in other countries. (en.wikipedia.org)
In software outsourcing the idea is simple. A company wants an engineering team in a country where talent is available and cost is lower, but it has no legal entity there, no recruiting network and no employer brand. A partner that already has all three builds the team, runs it under its own roof and, when the team is stable and the client is ready, transfers it. BOT acts as a hybrid between the "build" option of insourcing operations and the "buy" option of outsourcing them: the client gets to the end state of an owned team without carrying the start-up risk alone.
How do the three phases work?
The three phases are build, operate and transfer, and each has its own deliverables and risks. The build phase is about speed and fit, the operate phase about stability and knowledge, the transfer phase about legal and human continuity.
| Phase | What the partner does | What the client does | Typical duration |
|---|---|---|---|
| Build | Recruits the team to the agreed profiles, sets up office or remote infrastructure, tooling, security and processes; onboards people to the client's domain | Defines profiles, participates in interviews, provides domain knowledge and access | 3–6 months |
| Operate | Runs the team day to day: delivery management, HR, payroll, retention, training, service levels, reporting | Directs the work through its product owners; measures delivery against agreed KPIs | 12–36 months |
| Transfer | Moves people, contracts, assets and documentation to the client's new or existing entity; supports the handover for a defined period | Sets up the receiving entity, accepts the team, takes over HR and administration | 3–6 months |
The operate phase is where most of the value is created and most of the risk sits: if the partner does not invest in retention and knowledge sharing, the client receives a team that leaves or a codebase nobody fully understands. Good BOT contracts therefore tie part of the partner's fee to retention and to documentation delivered.
Which contract points decide whether BOT works?
Five points: the transfer trigger, the transfer price, intellectual property, the rules for transferring employees, and the exit if the client decides not to transfer. Each of them should be written before the build phase starts, because they shape how the partner invests.
- Transfer trigger: a date, a team size, a performance milestone, or the client's option exercised within a window. Options give flexibility; fixed dates give the partner certainty.
- Transfer price: a lump sum, a multiple of monthly fees, or zero if the operate phase was priced to include it. The price should fall as the operate phase lengthens.
- Intellectual property: everything the team produces belongs to the client from day one, with the partner holding only the licences it needs to operate. This should never be left to the transfer phase.
- Employee transfer: in the European Union the transfer of an undertaking generally carries employees with their contracts; outside it, individual consent and re-hiring are the norm. Local employment law decides, and retention bonuses are often part of the plan.
- Exit without transfer: the client may keep the team as an outsourced service, hand it back, or wind it down, with notice periods and fees defined.
A written scope, measurable results and regular communication are what make any outsourcing relationship work, as we argue in our article on choosing a software partner; in a BOT they are also what makes the transfer painless.
How does BOT compare with an offshore development centre and team augmentation?
BOT ends with ownership, an offshore development centre run by the partner does not, and team augmentation never aims at a separate team at all. The right choice depends on whether the client wants a permanent engineering presence it owns, a long-term outsourced capacity, or extra hands inside its existing team.
| Criterion | Build-Operate-Transfer | Offshore development centre (partner-run) | Team augmentation |
|---|---|---|---|
| End state | Client owns the team | Partner keeps running the team | No separate team; individuals join the client's team |
| Set-up effort | High: entity planning, transfer terms | Medium | Low |
| Cost during operation | Partner fee plus salaries, with a margin for the exit | Partner fee plus salaries | Day rates per person |
| Control | Grows over time, full after transfer | Shared, defined by contract | Full, within the client's processes |
| Knowledge | Built to be transferred | Stays with the partner unless contracted | Stays with the client |
| Best for | Permanent presence in a new location | Long-term capacity without ownership | Short-term skills gaps, variable workload |
For most European mid-sized companies the realistic alternatives are a nearshore partner team, which WWG runs across Italy, Poland and Ukraine as described in our article on nearshore development ROI, or team augmentation for specific profiles. BOT becomes attractive when the company has decided it wants its own engineering hub and the volume to justify it, typically from fifteen to twenty people upwards.
When is BOT the right choice, and how does WWG approach it?
BOT is the right choice when a company wants a permanent, owned engineering presence in a location where it has no entity, recruiting network or employer brand, has the volume to justify a dedicated team, and prefers to reach ownership through a partner rather than alone. It is the wrong choice for short projects, small teams or companies that do not actually want to run an operation abroad.
WWG's approach starts from what it already operates: delivery hubs in Italy, Poland and Ukraine, with recruiting, HR and delivery management in place, and experience in training and employing engineers in North Africa. For a client that wants to build an owned team in one of these locations, WWG can build and operate it inside its own structure and transfer it when the client is ready, with the transfer terms written at the start. For a client that is not sure it wants ownership, the same hubs offer a nearshore team or augmentation first, with BOT as a later option; our article on the benefits of IT outsourcing for lean teams covers how to start small. In every case the client's product owners direct the work from day one, intellectual property belongs to the client, and reporting is monthly against agreed KPIs.
Considering your own engineering hub abroad? Talk to a WWG engineer at business@wwg.it.
Sources
FAQ
Frequently Asked Questions
It means a partner builds a dedicated engineering team for a client, operates it for an agreed period under its own roof, and then transfers the team, with its contracts, assets and documentation, to the client, who takes full ownership. It combines the speed of outsourcing at the start with ownership at the end.
Typically two to four years in total: three to six months to build the team, twelve to thirty-six months of operation, and three to six months for the transfer and handover. The operate phase is where the team stabilises and knowledge is built, so it is rarely shorter than a year.
The main risks are attrition during operation, knowledge that stays with the partner, unclear intellectual property, and a transfer that fails for legal or financial reasons. All four are managed in the contract: retention incentives, documentation deliverables, client ownership of IP from day one, and transfer terms and price agreed before the build starts.
Not better, different. Team augmentation adds people to your own team quickly; a nearshore partner team gives long-term capacity without ownership; BOT builds a team you will own. Choose BOT if you want a permanent engineering hub abroad and have the volume to justify it; otherwise start with augmentation or a partner team and keep BOT as an option.
