Reading time: 8 min
Author: ITDS Team
| Short answer: build-operate-transfer (BOT) is a model in which a partner builds an engineering team for you abroad, runs it for an agreed period, typically two to four years, and then transfers it to your own local company. It suits companies that want their own team eventually but can't wait a year to build one from scratch. |
You want your own engineering centre abroad, but you don't want to spend a year setting up a company, learning local employment law and hiring from scratch before anyone writes code. You also don't want to rent a team forever. Build-Operate-Transfer sits between those two options.
This guide explains build-operate-transfer (BOT) for CFOs and CTOs considering a captive centre: what it is, the three phases and how long they take, what transfers and what doesn't, how the cost curve compares with permanent outsourcing, and when BOT is the wrong choice. For how ITDS builds and runs dedicated teams in Portugal and Poland, see our page on nearshore software development.
| In this guide | |
| What BOT is The three phases What transfers |
The cost curve When BOT is wrong FAQ |
What is build-operate-transfer?
Build-operate-transfer is an engagement model in which a partner builds an engineering team for you in another country, runs it for an agreed period, and then hands it over so it becomes your own team, employed by your own local company.
The idea is simple: rent the team, then keep it. You get the speed of working with a partner who already knows the local market, and the long-term control and cost structure of owning the team. The partner's job is to make itself unnecessary on an agreed date.
| Rent the team. Then keep it. |
The three phases of build-operate-transfer and their timelines
Timelines vary with team size and complexity. The ranges below follow those commonly quoted in industry guides to build-operate-transfer. They are typical, not guaranteed.
| Phase | What happens | Typical length |
|---|---|---|
| Build | The partner recruits the first engineers and leads, sets up workplaces and tools, and agrees processes with you | About 4 to 9 months |
| Operate | The partner employs and runs the team. You direct the product work. The team grows and settles into your way of working | Often 2 to 4 years |
| Transfer | You set up or prepare your own local entity, and engineers move to your employment along with processes and knowledge | About 3 to 6 months |
Most of the value comes from the operate phase. It gives you time to prove that the team works, and to decide whether you really want to own it, before you commit to running a company abroad.
What transfers and what doesn't
A good BOT contract spells this out from day one. Typically:
- Usually transfers: the engineers and team leads (through new employment contracts with your entity), the code and IP they created, documentation, processes and working practices, and sometimes equipment or office arrangements.
- Usually doesn't transfer: the partner's recruitment engine, its shared services such as payroll and HR, its tools and know-how built for other clients, and any engineer who chooses not to move.
Two points deserve attention. Engineers can't be transferred like assets; each person decides whether to accept your offer, so retention planning matters. And many BOT contracts include a transfer or conversion fee, which should be agreed up front rather than negotiated at the end.
Employment and corporate law differ by country, so the transfer mechanics should be reviewed by local counsel. This is general information, not legal advice.
The cost curve: BOT vs permanent outsourcing
The chart below shows the general shape of the costs, not real figures.
Permanent outsourcing keeps a steady cost per engineer, which includes the partner's margin, recruitment and management. Building it yourself starts very expensive, with entity setup, legal work, recruitment and slow hiring, and only gets cheaper once the centre runs at scale. BOT starts close to outsourcing, then drops after transfer, when you stop paying the partner's margin but take on the overhead of running the team: HR, payroll, office, legal and recruitment.
The savings after transfer are real only if your team is large enough to absorb that overhead and stable enough to justify it. Model your own numbers before you decide.
| Considering your own team in Portugal or Poland? Talk to us about how to start, and how to keep the option to bring the team in-house later. Discuss your options |
When build-operate-transfer is the wrong choice
- Your team will stay small. For a small team, the overhead of running your own entity often outweighs the savings.
- Your need is uncertain. If you don't know whether you will need the team in two years, keep the flexibility of a partner.
- You don't want to run a company abroad. After transfer, you are the employer, with everything that involves.
- The project is short. BOT pays off over years, not months.
- You need the partner's bench. If you value fast replacement and access to a wider talent pool, permanent partnership may serve you better.
In those cases, a long-term dedicated team with a partner is usually the better model, and it keeps the BOT option open for later.
Build-operate-transfer: FAQ
It is a model in which a partner builds an engineering team for you abroad, operates it for an agreed period and then transfers it to your own local company, so the engineers become your employees.
Typically about 4 to 9 months to build, 2 to 4 years to operate and 3 to 6 months to transfer, depending on team size and complexity.
After transfer, the cost per engineer is often lower because you no longer pay the partner's margin, but you take on HR, payroll, office, legal and recruitment costs. It usually pays off only for larger, stable teams.
They are offered employment with your local company. Each person decides whether to move, so retention planning and fair offers matter. Local employment law applies, so involve local counsel.
When the team will stay small, the need is uncertain, the project is short or you don't want to run a company abroad. A long-term dedicated team is often the better fit in those cases.
Discuss your optionsTell us how big a team you need, for how long and whether you want to own it one day. On a short call, we will tell you how we would build it in Portugal or Poland and which model makes sense today. |