The build-operate-transfer (BOT) model in software development is a deal where a provider builds an engineering team in another country, runs it for an agreed period, and then transfers the people, and often the legal entity, to you. You end up owning an offshore or nearshore engineering center without having set one up from zero.
It's a good model at the right size. For most startups, that size is a long way off.
Key Takeaways
- Build operate transfer has three phases: the provider recruits and sets up the team, operates it under its own entity, then hands the team and usually the entity to you.
- There's no standard length for the operate phase or standard transfer fee. Vendor figures vary widely, so everything is negotiated.
- BOT makes sense when you're confident you'll want a large, permanent team in one country. Below that size, the setup work and the transfer fee are hard to justify.
- Staff augmentation with a conversion option is the lighter version: you can hire individual engineers directly later without taking on an entity.
How Build Operate Transfer Works, Phase by Phase
Build. The provider recruits engineers to your spec, sets up an office or remote-work setup, handles payroll, and, if the plan is a full transfer, may set up a local legal entity designed to become yours.
Operate. The team works on your product, usually full-time and dedicated. The provider remains the employer and handles HR, payroll, compliance, and retention. You pay a monthly fee that covers salaries plus the provider's charge for running the operation.
Transfer. At an agreed point, the engineers move to your payroll, or the entity itself transfers to you with the employees inside it. Contracts, equipment, office leases, and sometimes key managers move over.
Industry analysts mention the model mostly in passing. Everest Group, for example, refers to "build-and-transfer" options in the context of global capability center setups (Everest Group). There is no standard contract. Phase lengths and fees vary so widely across vendors that any number you read online should be treated as one vendor's opinion.
| Phase | Who employs the engineers | Who you pay | What you get |
|---|---|---|---|
| Build | Provider | Setup + recruiting fees | A hired team |
| Operate | Provider | Monthly operating fee | A working team, provider runs HR |
| Transfer | You | Transfer fee | The team, and often the entity |
How Transfer Fees Are Usually Structured
Since there's no market standard for the number, focus on the structure. Three common shapes:
- Flat transfer fee. One amount at transfer, fixed in the contract on day one. Easy to budget, but it doesn't care whether you transfer 8 people or 30.
- Per-head fee. A fee per engineer who moves. This scales with the value you're taking.
- Amortized fee. The transfer cost is built into the monthly operate fee, so it shrinks or disappears the longer you stay in the operate phase.
The clauses that matter more than the fee itself: what happens if you want to transfer early, whether you can transfer part of the team, who owns the entity's liabilities at the moment of transfer, and whether the provider's non-solicit applies to engineers who decline to move.
When BOT Makes Sense
BOT fits a company that has already decided to own a large engineering presence in one country and wants someone else to absorb the early mistakes. That usually means a few things are true. You're confident the team will grow well beyond ten people and stay for years. You have, or will hire, someone to run it locally after the transfer. And your finance and legal teams are ready to own a foreign entity, with its payroll, tax filings, and labor law.
If those aren't true yet, you're paying to build something you won't be ready to own.
A Concrete Version
Here's an illustrative comparison. Every number below is an assumption for the arithmetic, not a market figure.
A Series B company wants 20 engineers in Mexico, long term.
Option A, BOT. Assume the operate fee runs $8,000 per engineer per month for 24 months: 20 x $8,000 x 24 = $3,840,000. Then an assumed flat transfer fee of $150,000. After transfer, the company carries the engineers at its own cost, which it estimates at $6,500 per engineer per month including entity overhead, plus a local HR lead.
Option B, staff augmentation, converting selectively. Assume $7,500 per engineer per month for 24 months: 20 x $7,500 x 24 = $3,600,000. At month 24, the company converts the 8 engineers it most wants to keep through the provider's conversion option and keeps the rest augmented.
Two-year totals: Option A is $3,840,000 + $150,000 = $3,990,000. Option B is $3,600,000 plus whatever the 8 conversions cost, so B stays cheaper as long as those fees come in under the $390,000 gap, and the company avoids owning an entity until it has proven it needs one.
After month 24 the picture flips. Option A's team costs $6,500 per head against $7,500 augmented: $1,000 x 20 = $20,000 a month, or $240,000 a year (before the HR lead's salary). If B had kept all 20 augmented, A would win back its $390,000 head start in about 20 months. So Option A wins if the company is certain about the full 20-person team and plans to run it for years after transfer. Change the assumptions and the answer changes, which is the point. Run your own numbers before believing anyone's sales deck, including ours.
The Honest Counterpoint
Staff augmentation has a ceiling too. At 30 or 40 engineers in one country, paying a provider's rate on every head is real money, and owning the team through BOT or your own entity is cheaper over a long horizon. We say this openly in staff augmentation vs building an offshore team.
There's also culture. A BOT team becomes yours: your employer brand, your equity plan, your managers. Augmented engineers are excellent contributors but they're still engaged through someone else. For some companies that difference matters more than the cost.
Frequently Asked Questions
How long is the operate phase in build operate transfer?
There's no standard. Vendors quote very different ranges, and it depends on the team size and how ready you are to take over. Negotiate the earliest date you can trigger a transfer and what it costs to do so early.
Is build operate transfer the same as an offshore development center?
They overlap. An offshore development center is a dedicated team abroad, and BOT is one way to end up owning one. Many dedicated-center contracts never include a transfer.
Can I do a small BOT with five engineers?
You can, but the entity setup and transfer cost are spread over very few people. At that size, augmentation with a conversion option usually gets you the same people for less overhead. See how contract-to-hire works.
The Bottom Line
BOT is a good model for companies that already know they want to own a big team in one country. If you aren't there yet, start with augmented engineers and convert the ones you want to keep. Ruzora's agreements include a conversion option with a fee that steps down the longer an engineer has worked with you. Request a shortlist to see who's available, and read staff augmentation in Mexico if that's your target country.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
