Build-operate-transfer is how mid-market and enterprise tech companies launch a nearshore engineering team today and own it outright tomorrow, without committing upfront capital to a foreign subsidiary. A partner builds the team, runs it under your governance, then transfers full ownership once operational benchmarks are met. Everest Group reports that the share of GCCs set up through the BOT model climbed from under 10% to nearly 40%, and rises above 90% once assisted-transfer variants are included.
The BOT model explained in one sentence for you
The BOT model in IT turns a service provider into a temporary operator of your nearshore team, with a contractual obligation to transfer the entity, employees, and assets to your company at a predefined milestone. Ownership usually transitions on a fixed schedule, often around three years.
Everest Group describes the structure as a way to avoid upfront capital investment, reduce operational risk, and accelerate speed-to-market, while keeping the long-term option to internalize the team. The transfer premium pays for that optionality. You stop renting and start owning.
How BOT works: the three phases to understand
Phase 1 (Build, months 0 to 6). The partner registers the legal entity, leases space, recruits the first engineering cohort, and sets up payroll, equipment, and local compliance. You define role specifications, target architecture, and governance from day one.
Phase 2 (Operate, months 6 to 36). The partner runs HR, payroll, benefits, retention, and labor compliance. Your engineering leaders direct the work, own all code and IP, and set sprint priorities. Productivity and attrition KPIs track from week one.
Phase 3 (Transfer, months 30 to 36). The partner refines workflows and runs the centre while compliance is managed, then hands over ownership once the agreed benchmarks are reached. Transfer fees and tax structure are negotiated in the original contract, not at the milestone.
BOT vs. outsourcing vs. staff augmentation vs. subsidiary
| Model | Ownership | Setup time | Best for |
| Outsourcing (BPO) | Vendor | 4 to 8 weeks | Defined projects, variable demand |
| Staff augmentation | Vendor | 2 to 6 weeks | Short-term skill gaps |
| BOT | Vendor to client | 3 to 6 months | 3+ year horizon, eventual ownership |
| De novo subsidiary | Client | 9 to 18 months | Mature global ops, full risk appetite |
BOT vs outsourcing trades faster setup for permanent vendor dependence. Staff augmentation rents skills. A subsidiary buys total control at maximum cost. BOT sits between the last two, designed for companies that want a captive team without bearing early setup risk.
This is when BOT makes sense (and when it doesn’t)
BOT fits when your team will exceed 30 to 50 engineers, your offshore commitment is at least three years, and your work involves IP, regulated data, or domain knowledge worth protecting long-term. Companies with mature engineering leadership benefit most, since the transfer phase demands internal managers ready to absorb the team.
BOT is the wrong tool for short pilots, variable workloads, or unproven nearshore strategies. If you cannot yet articulate a five-year roadmap or absorb local employment liability, validate the model first with a lighter setup. Náez does exactly that for US and Canadian tech companies, handling recruitment, hiring, and remote contracting so you can stand up a small Colombian team, prove it works, and revisit BOT once the case is clear. See the EOR services guide for how that entry path works.
Let’s talk about costs and financial structure of a BOT engagement
Three cost layers define a BOT agreement in tech: build fees (one-time, covering entity setup and recruiting), operate fees (monthly per-FTE rate with management markup), and transfer fees (one-time, calculated against annual run-rate). According to Accelerance’s 2025 Global Software Outsourcing Rates and Trends Guide, hourly rates for software development across Latin America typically range from $23 to $90, depending on role and experience.
Industry benchmarks place total savings versus US in-house hiring between 40% and 60% once management premium, retention, and infrastructure are loaded in. Documented BOT engagements have cut operating costs by around 40% while enabling rapid scaling.
Timeline: from first conversation to team transfer
Initial scoping and partner selection takes 6 to 10 weeks. Contract negotiation and entity setup runs 8 to 12 weeks in parallel. The first engineer onboards by month 4 to 6. A steady-state team of 25 to 50 engineers lands by month 12 to 18.
Compressing this only adds risk. Rushing the build phase pushes attrition into year two. Extending operations beyond 48 months erodes the financial logic, since you pay a management premium on a team you could already run yourself.
IP protection and legal considerations to have in mind
The transfer clause is where most BOT deals fail. Define which IP assignments cover engineer contracts from day one, which entities hold code repositories, and how trade secrets migrate at the milestone. Local labor law in Latin America treats employees as locally protected, so contract transfer requires explicit consent procedures.
US tech companies should layer three protections: NDA and IP assignment in every engineer contract, a master services agreement that holds the provider liable for IP leakage, and a transfer protocol audited by independent counsel. For HIPAA, SOC 2, or PCI DSS workloads, build compliance scaffolding before the first hire.
How to choose a BOT partner in Latin America?
Filter on three signals: documented prior transfers (ask for case references where ownership actually moved), local employment infrastructure (their own legal entity, not a chain of subcontractors), and engineering management depth (technical leads on payroll, not only recruiters).
Pricing transparency matters more than headline rates. A partner unwilling to itemize build, operate, and transfer fees in writing will cost you in surprises later. Weight reference calls over sales decks, and make sure the partner can show ownership transfers that actually closed.
Colombia as a BOT destination: advantages
For nearshore BOT in Colombia, the country produces over 13,000 engineering graduates a year, works in Eastern and Central US time zones, and offers free trade zone benefits including a 20% income tax rate versus the 35% standard. Bogotá, Medellín, and Barranquilla host concentrated tech ecosystems with senior engineers in cloud, data, and product roles.
ProColombia reports that the BPO sector has grown at a 12% CAGR since 2018. For US companies that prioritize real-time collaboration and bilingual delivery, Colombia beats Asian offshore alternatives on latency and cultural fit while delivering 30% to 50% cost savings versus US hiring.
Some doubts that have already been mentioned to us
Typically 30 to 36 months from kickoff to transfer. Larger teams extend to 48 months.
Industry benchmarks place fully-loaded savings at 40% to 60%, depending on role mix and seniority.
Your company. IP assignment is written into every engineer contract from day one.
Yes, but cancellation triggers exit fees and may convert the engagement into a long-term managed service contract.
A GCC is the destination. BOT is one of several paths to build one, alongside de novo setup, assisted setup, and managed services.
An EOR handles employment compliance for individual hires with no entity transfer. BOT builds an entity designed to migrate to you. If you want to validate your nearshore team before committing to BOT, that EOR path is where Náez starts. See the EOR services guide.
Contracts migrate to your new entity under local labor law, preserving seniority, benefits, and accrued vacation.
Colombia offers lower cost and free trade zone incentives. Mexico offers USMCA trade benefits and closer time zones.
Start by proving the model. Náez recruits, hires, and onboards remote engineering teams in Colombia and across Latin America for US and Canadian tech companies, so you can validate your nearshore strategy before building an entity. Book a 15-minute call with Náez to scope your first hires.