Build Operate Transfer is the model agencies ask about once they have decided a captive center is too much commitment and a vendor is too little control. A partner recruits and runs the team, then transfers it to you at an agreed point.
It is a legitimate model. It is also an ownership decision wearing the costume of a staffing decision, and most agencies who ask about it do not actually want to own anything.
What BOT Actually Is
Three phases. Build: the partner recruits, onboards, and sets up infrastructure under their entity. Operate: they run the team, usually one to three years, while it delivers for you. Transfer: the team, and sometimes the entity, moves to you at a pre-agreed price.
The transfer clause is the whole model. Without it this is just a managed service with extra paperwork.
Why It Appeals to Agencies
It looks like the best of both. You skip the eighteen months of entity setup, compliance, and first hires. Someone experienced absorbs the early risk, when attrition and mis-hires are most likely. And you keep the option to own the team once it is proven.
That option is the appeal. Agencies like reversibility, and BOT sells it.
The Problem It Solves, and the One It Does Not
It solves setup risk genuinely well. The first six months of any offshore build are where most failures happen, and buying an operator through that window is worth real money.
What it does not solve is the reason most agencies should not own an offshore team in the first place. After transfer you own the entity, the compliance, the payroll, the local leadership hire, and the attrition. The costs you avoided did not disappear, they were deferred to a date you agreed in advance.
Agencies that sign BOT deals without a concrete plan for who runs the team post-transfer usually extend the operate phase indefinitely, which means they paid a premium for an option they never exercise.
When BOT Genuinely Fits
Three situations, and they are narrower than the pitch suggests.
You are planning to be much larger. If you are heading for 40 or more offshore seats, fixed setup starts to amortise and ownership starts to pay. BOT gets you there without learning entity setup yourself.
You are planning to sell. An owned delivery capability is an asset a buyer can value. A vendor relationship is not, and it is a risk they will discount for.
Your work cannot leave your control for compliance reasons. Some client contracts require it. That is a real constraint and ownership is the answer.
Outside those, the option you are paying for is one you probably will not use.
The Terms That Decide Whether It Works
If you do it, four clauses matter more than the rate.
Transfer price and how it is calculated. Agree it upfront, in writing, with a formula rather than a valuation at the time. A transfer price set later is a negotiation you will enter from a weak position, because the team already knows your accounts.
Who owns the knowledge. Documentation, process, and account history should be yours from day one, not transferred at the end. If it lives only in the partner systems, the transfer is far less valuable than it looks.
What happens if you do not transfer. Most BOT deals quietly become permanent managed services. Know what the terms revert to, and price the deal on the assumption that this is the likely outcome.
Attrition during the operate phase. If the partner is measured on cost rather than continuity, you can inherit a team that has turned over twice. Tie something to retention.
The short version: BOT is worth paying for if you have a specific reason to own the team later. If you cannot name that reason in a sentence, you are buying an option you will not exercise, and a managed pod gets you the same delivery for less.
Part of: The GCC Model for Marketing Agencies, covering how agencies get offshore economics without building a center.