The build operate transfer model has a partner assemble your offshore team, run it for an agreed period, then hand the whole thing over to you. One contract covers all three stages, and the ownership question waits until a point where you will know far more than you do today.
Most companies think the choice is binary. Outsource it, or build it yourself. That framing is where the trouble starts, because both options force a decision at the moment you have the least information. Before you know the market. Before you have any evidence about attrition, salary drift or how quickly people ramp.
BOT exists because that timing is bad. You get an operating team fast, and you buy yourself two years of watching before committing capital to a permanent structure. The catch is that the model takes more drafting effort than either alternative, and a large share of BOT deals never reach the transfer at all. Sometimes for good reasons.
Кратко:
- A partner builds the team, operates it under their entity, and later transfers people and assets to you.
- The transfer is an option you hold, not an obligation you owe. Write it that way.
- Published timelines contradict each other wildly, which tells you the schedule is negotiated rather than standard.
- In ASEAN the operate phase usually runs through an employer of record, which changes what transfer comes to mean.
- Reaching the transfer and declining it is a legitimate outcome. Plenty of teams are better left where they are.
What Is the Build, Operate, Transfer Model?
Build, operate, transfer is a delivery structure where an external partner sets up an offshore or nearshore team on your behalf, runs it as a managed operation for a defined period, and then transfers ownership to you at the end. You specify the roles and the standards, and you own the work itself. The partner carries the employment relationship and the premises, plus the operational overhead, while the team matures.
It sits between two familiar options. Straight outsourcing never hands you anything, so you carry no local structure and no long-term asset. A captive centre hands you everything on day one, so you carry entity setup, hiring risk and fixed cost before you have any local knowledge to spend it wisely. BOT lets you run the operation first and decide about ownership second. As of 2026 the model appears most often in software delivery, though it applies just as cleanly to finance and analytics, and to customer operations.
What Happens in Each of the Three Phases?
The middle phase carries almost all the value, which is not where most attention goes.
| Phase | What the partner does | What you do | What to watch |
|---|---|---|---|
| Build | Recruits, hires, secures premises, sets up tooling and process | Define roles, standards and target output | Hiring against your bar, not their bench |
| Operate | Employs the team, runs payroll and compliance, manages facilities | Direct the work, set priorities, review performance | Whether the team is genuinely yours in everything but employment |
| Transfer | Moves people, contracts and assets across to your structure | Stand up the receiving structure, absorb the team | The valuation basis, the retention risk, the timing trigger |
A word on timing. Published BOT guides give ranges that flatly contradict each other. One puts the operate phase at 12 to 24 months and the whole thing at 18 to 36. Another says two to three years total with a build phase that could run a full year on its own. They disagree because there is no industry standard here. Read that as good news: the schedule is a term you negotiate, not a default you inherit.
The build phase is shorter than people expect and the operate phase is longer. That asymmetry is the point. You are not buying a fast setup. You are buying time to learn before you commit.
How Does BOT Compare With Outsourcing, a Captive and Staff Augmentation?
These structures differ mainly on who employs the people and who ends up owning the operation.
| Who employs | Who directs the work | Ends in your ownership | Upfront commitment | |
|---|---|---|---|---|
| Outsourcing | Поставщик | Provider, to an agreed output | Нет | Низкий |
| Аутсорсинг персонала | Поставщик | Вы | Нет | Низкий |
| Build, operate, transfer | Provider, then you | Вы | Optional, by agreement | Средний |
| Captive centre | You, from day one | Вы | Yes, immediately | Высокий |
Notice that BOT and staff augmentation look identical during the operate phase. In both, somebody else employs the people and you run them day to day. The difference is entirely in what the contract says happens later. If you want the near-term arrangement without the ownership question attached, the dedicated remote team model does that job with less contractual weight.
For the broader category and where each of these sits, we have published полный разбор аутсорсинга бизнес-процессов and a piece on how enterprises structure delivery across locations.
Weighing BOT against a straight outsourcing deal? Download the operating model comparison checklist.
Why Does BOT Look Different in Southeast Asia?
Malaysia ranked third worldwide in the Kearney Global Services Location Index 2023, behind India and China, ahead of Indonesia in sixth, Vietnam in seventh, the Philippines in twelfth and Singapore in fourteenth. Malaysia’s Digital Investment Office reports that the country hosts close to half of all analytics-based services in ASEAN. Those rankings explain why the region shows up on BOT shortlists at all.
Where the region diverges is the operate phase. In ASEAN it tends to run through an employer of record rather than a partner-owned captive, because an EOR can employ your team legally from day one without anybody registering a company first. So the operate phase starts in weeks instead of quarters, and the transfer turns into a decision about standing up a permanent structure later, once you hold real evidence about the team. Note that the mechanics of establishing that structure sit outside what this article covers, and belong with local advisers.
The English-language market matters here too. Mandarin and Bahasa Malaysia sit alongside English inside the same team, which is difficult to assemble elsewhere at a comparable cost base. And if the transfer never happens, the arrangement simply continues as a managed operation, which is a softer landing than an unwanted captive.
When Should You Not Take the Transfer?
Reaching the end of the operate phase and declining the transfer is a legitimate outcome. It is one of two normal endings, and the industry rarely frames it that way.
Take the transfer where the function is core to how you compete. Take it where you need the people inside your own culture and systems, where headcount justifies a permanent local structure, or where a regulator or a client demands direct employment.
Leave it alone where the function matters without differentiating you. Leave it where the team is small enough that a permanent structure would cost more than it returns. Leave it, too, where the partner runs this work better than you would, which is uncomfortable to say out loud and frequently true.
The mistake is treating the transfer as a milestone you owe somebody. Write it as an option you hold. A contract that obliges you to take the team on a fixed date has removed the entire reason you chose this model.
What Belongs in the Contract Before You Sign?
The ones people skip are the last two.
- The transfer trigger. Date, notice period, and who initiates. Make it your call.
- The valuation basis. How the transfer price is calculated, using a formula rather than a figure agreed later under pressure.
- Intellectual property. Ownership from day one, not at handover. Everything the team produces is yours from the first sprint.
- What moves across. People and contracts. Tooling and documentation. Process assets. Name every one of them.
- Retention through the handover. Transfer is the moment your team is most likely to leave. Agree how people are told, and what they are offered on the day.
- What happens when you decline. Continuation terms, notice, pricing. Nobody drafts this because everybody assumes the transfer happens, and then the awkward conversation arrives without a framework.
At SummitNext the accountability split makes the handover easier to reason about. We hold employment and payroll, plus statutory compliance. You hold operational management from the first day, so the team is already yours in every sense except the employment contract. Transfer moves one thing, not two. Our staff can also work at your premises where that helps, which is the fastest way to move context that no runbook captures. And there is no minimum headcount, so a five person operate phase is a real option rather than an exception.
For the wider picture of what operating in the market involves, see what operating in Malaysia involves, and for the cost and risk side of building versus buying, our piece comparing in-house and outsourced operations.
Часто задаваемые вопросы
What does build operate transfer mean?
Build operate transfer is a contract where a partner sets up an offshore team, runs it as a managed operation for an agreed period, then hands ownership of the people and assets to you. It lets a company defer the ownership decision until it holds real evidence about the market and the team.
How long does a BOT engagement take?
There is no standard. Published guides range from around 18 months to three years in total, and they contradict each other because the schedule is negotiated rather than fixed. Build phases run in months, operate phases in years. Treat the timeline as a contract term you set, not an industry default you inherit.
Is BOT the same as staff augmentation?
During the operate phase they look identical, since a provider employs the people and you direct the work. The difference sits in the contract. Staff augmentation has no ownership path attached. BOT carries an agreed transfer of people and assets to you at a later date.
Do I have to take the transfer?
Not if the contract is written properly. Draft the transfer as an option you hold rather than an obligation you owe, with a trigger you control. A clause that forces the handover on a fixed date removes the flexibility that made the model worth choosing in the first place.
Can BOT work for a small team?
Yes. A five to ten person operate phase is a legitimate starting point, and SummitNext sets no minimum headcount. Small teams often suit the model better, because the cost of taking on a permanent structure for a handful of people is exactly the decision worth deferring until you have evidence.
What is the biggest risk in a BOT contract?
Retention through the handover. Transfer is the point where employment terms change and your team is most exposed to being approached elsewhere. Agree in advance how people are told, and what they are offered on the day. Intellectual property ownership from day one is the second thing to settle.
Итог
Build, operate, transfer buys you time. That is the whole proposition, and it is worth more than most companies realise when they are staring at a build-or-buy decision with no local knowledge to inform it.
Two things decide whether it works. Write the transfer as an option rather than an obligation, and be honest at the end about who ownership really serves. Declining is not defeat.
If you are weighing an ASEAN team and cannot yet tell whether you want to own it, поговорите с нашей командой and we will map the operate phase with you before anybody signs anything.
Русский 
English 
繁體中文