Build-Operate-Transfer (BOT): When It Makes Sense For Engineering Teams

Build-operate-transfer (BOT) is an engagement model where a vendor builds an engineering team for you in another country, runs it for a set period, and then hands it over. At transfer, the engineers become your employees, usually under your own local legal entity.

The model came from infrastructure projects, where private firms built and ran roads or power plants before handing them to governments. In software, the asset being transferred is a working team: people, processes, tooling, and the knowledge they hold about your product.

BOT sits between two common options:

• Staff augmentation gives you engineers fast, with no setup, and a conversion clause lets you hire the best ones directly later.
• Opening your own entity abroad makes them yours from day one, but it takes a year or more of legal, HR, and recruiting work before anyone ships code.

This guide explains how the three BOT phases work, what they cost, how BOT compares with other models, and the signals that tell you whether your team needs it at all.

How The Build-Operate-Transfer Model Works: The 3 Phases

A BOT engagement runs in three phases that usually span two to five years in total. Each phase shifts more control from the vendor to you, and the contract defines what must be true before the next phase starts.

Provider timelines vary. Some LATAM vendors quote 18 to 36 months end to end, while others describe an operate phase of two to five years on its own. The right length depends on team size and how fast your own managers can take over.

Phase 1: Build (Roughly 0–6 Months)

The vendor recruits the team, sets up payroll and compliance, and provides equipment and workspace. You define roles, seniority, the tech stack, and the hiring bar. Your engineering leaders should interview finalists, since these are future employees, not rotating contractors.

The key output of this phase is a written definition of what will transfer:

• Org chart,
• Systems ownership,
• Documentation standards, and
• Target headcount.

The vaguer this definition, the harder the transfer gets.

Phase 2: Operate (Roughly 6–36 Months)

The team works on your roadmap, inside your sprints and tools, while the vendor handles HR, payroll, retention, and local labor law. You direct the technical work; the vendor runs the employment side.

This is also when you prepare to run the team without help. Place your own engineering manager or tech lead in the team early. Move the team onto your HR policies and internal tools step by step, instead of switching everything on transfer day.

Phase 3: Transfer

At a pre-agreed trigger, such as a date or a headcount threshold, the engineers move to your payroll. That usually means opening a local entity, transferring employment contracts, and taking over benefits, equipment, and vendor tooling licenses.

You pay a transfer fee at this point, unless your contract waives it. After the handover, many vendors offer a support period or keep part of the team on a staff augmentation basis.

Transfer is an option, not an obligation. Some companies never trigger it because the vendor arrangement keeps working, and the option alone keeps the vendor accountable on quality and retention.

BOT Vs. Staff Augmentation, Dedicated Teams, And Captive Centers

The real difference between these models is who employs the engineers at the end, and how much setup you take on to get there. Staff augmentation gets you there with the least setup and the most flexibility; BOT is the only one that transfers a whole operation.

Ranges reflect common market terms from BEON.tech’s engagements and published vendor terms (BOT providers commonly ask for a 12-month minimum for hubs of 15 to 100+ FTEs). Your quotes will vary by country and seniority. Which of these team engagement models fits depends on your team size, your horizon, and how much country risk you want to own.

Is BOT The Same As An Employer Of Record (EOR)?

No. An EOR employs people you already found and manage, and it never plans to hand them over. BOT includes recruiting and operations, and it ends with a transfer to your own entity. Many BOT vendors use an EOR structure during the operate phase.

When Does Build-Operate-Transfer Make Sense For An Engineering Team?

BOT makes sense when you plan to own a large team in one country for five years or more, and you have the management layer to run it after transfer. If any of those three conditions is missing, a simpler model will usually cost less and carry less risk.

Signs BOT Is The Right Fit

• You need 15 or more engineers in one location. Below that size, the cost of a local entity, legal counsel, and HR staff rarely pays off.
• Your horizon is five years or longer. Transfer windows usually open between years two and five. You need time after that to recover the transfer fee and entity costs.
• You already validated the region. You have worked with LATAM engineers through staff augmentation or a dedicated team, and you know the time zone, skill depth, and retention work for you.
• Ownership matters for strategic reasons. Examples include IP-heavy work, regulated data, plans to hire local leadership, or a board that wants the team on your balance sheet.
• You have someone to run it. A director or VP who will own the hub, travel to it, and manage local leaders after the vendor steps back.

Signs BOT Is Not The Right Fit

• You need capacity in weeks, not quarters. BOT front-loads recruiting and setup. Staff augmentation puts engineers in your sprints in about three to four weeks.
• Your headcount plan is uncertain. If the roadmap or funding could change in the next 12 months, a multi-year commitment with a transfer clause adds risk instead of removing it.
• You want engineers, not an office. Many teams care about owning the talent relationship, not a legal entity in Mexico or Colombia. Direct conversion of individual engineers solves that with far less overhead.
• No one internal will own country operations. After transfer, you take on local labor law, payroll, benefits, and retention. Without a leader for that work, the team often loses its best people within a year.

A Quick Rule Of Thumb

If you would answer “yes” to team size, horizon, and internal ownership, ask vendors for BOT proposals. If you answer “no” to any of them, start with staff augmentation and keep the option to hire engineers directly later.

How Much Does A Build-Operate-Transfer Engagement Cost?

A BOT engagement has three cost layers: the monthly rate during build and operate, the transfer fee, and the cost of running the team yourself afterward. Most vendor pages show only the first one, which makes BOT look cheaper than it is.

Monthly Rate During Build And Operate

During the first two phases you pay a monthly rate per engineer, similar to staff augmentation. In LATAM, all-in rates for senior engineers commonly run between $7,500 and $10,000 per month, depending on stack and country. Some vendors bill cost-plus instead:

• Salary,
• Statutory employer costs, and
• A separate management fee.

Transfer Fee

The transfer fee compensates the vendor for the recruiting, retention, and margin it gives up. Vendors price it as a multiple of monthly run-rate, a fixed amount per engineer, or a schedule that declines the longer the team stays. Get the formula in writing at signing; negotiating it later, when the vendor controls the team, puts you in a weak position.

Costs After Transfer

Once the team is yours, you absorb what the monthly rate used to cover:

• Legal entity setup and annual compliance, plus local accounting and legal counsel.
• Statutory employer contributions, which in some LATAM countries reach 50% to 100% of gross salary.
• Benefits, equipment, office or coworking space, and payroll software.
• Local HR and recruiting staff to replace people who leave.
• Severance exposure under local labor law if you downsize later.

Model these numbers for three years after transfer before you sign. For smaller teams, fixed costs like counsel, accounting, and HR staff spread over fewer engineers, and the post-transfer cost per head can end up close to the vendor rate you paid before.

What Should A BOT Contract Include?

The contract decides whether BOT protects you or locks you in. Settle these five terms before signing, while you still have leverage:

1. Transfer trigger and formula. The date window or headcount that allows transfer, and the exact fee calculation. Add the right to transfer early or to extend the operate phase.
2. Asset definition. What moves at transfer: people, documentation, repositories, tooling licenses, and vendor-built internal tools.
3. Key-person and non-solicitation terms. Team leads and managers must transfer with the team, not move to other vendor accounts before the handover.
4. Employment-transfer mechanics. How contracts move to your entity without triggering severance or acquired-rights claims. In Mexico, for example, this often runs through an employer-substitution scheme. Hire local counsel from day one, not in year three.
5. Exit without transfer. Your right to end the engagement with notice and no transfer fee if the team does not meet agreed quality or retention benchmarks.

Common BOT Risks And How To Reduce Them

BOT projects tend to fail in three predictable ways, and each one is easier to prevent at signing than to fix at transfer.

• Attrition at handover. Engineers may leave if the move to your payroll lowers pay, benefits, or perceived stability. Match or improve their conditions, and tell them about the transfer plan early.
• Culture and process shock. A team that ran on the vendor’s management systems can stall when it moves to yours. Align tools, rituals, and HR policies during the operate phase.
• Scope creep in the build phase. Adding roles or functions faster than planned breaks the assumptions behind the transfer formula. Use change control on the asset definition.

An Alternative To BOT: A Long-Term Staff Augmentation Team

Most US engineering teams between 50 and 500 people want the outcome of BOT without the entity: stable engineers who know the product, low turnover, and a team that works as part of their own. Long-term staff augmentation delivers that with far less setup, and you can scale up or down every month.

Here is how that path works with BEON.tech:

1. Start with staff augmentation. Add one engineer or a full squad; if you need a self-managed unit, the same terms apply to a dedicated team. Engineers join your sprints in about three to four weeks, on a monthly rate that covers salary, benefits, equipment, and payroll. You can scale with 30 days’ notice.
2. Run the team as your own. You set the backlog, rituals, and standards. BEON handles retention, career coaching, and replacements if someone leaves.
3. Keep the team stable for years, not months. Retention is part of the service: talent coaches, regular performance reviews, and no-cost replacements keep product knowledge inside your team, without you taking on local HR or labor law.
4. Grow without new overhead. A new engineer, a second squad, or a different stack runs through the same contract and the same onboarding. There is no entity to open, no transfer fee to negotiate, and no handover to plan.

This approach gives you what BOT promises from the first month: a stable team that works like part of yours, without a multi-year commitment or a transfer to manage.

Choosing The Right Path For Your Engineering Team

BOT is a strong option for companies that plan to own a large engineering hub in one country and have leaders ready to run it. For most growing teams, it is a commitment that arrives before the evidence does, and staff augmentation gives you that evidence first.

If you want long-term LATAM engineers who work like part of your team, with the option to hire them directly later, talk to BEON.tech about staff augmentation. We will help you size the team, set the conversion terms, and have engineers in your sprints within a month.

FAQs