US companies exploring how to hire tech talent in Colombia or Mexico quickly run into three overlapping terms: Employer of Record (EOR), staff augmentation, and Build-Operate-Transfer (BOT). Vendors in each category tend to describe their model as the obvious choice, which makes independent comparison difficult to find. This article lays out what each model actually is, where each one is genuinely the right fit, and where the differences matter enough to change your decision without a sales pitch for any single option.
At Cafeto, we operate models that overlap with all three categories, which gives us a reason to be honest about the tradeoffs: the right structure depends entirely on what you’re trying to accomplish, not on which model a given vendor happens to sell.
Employer of record (for): What it actually is
An EOR is a legal employment mechanism. The EOR provider becomes the legal employer of a worker in a foreign country handling payroll, tax withholding, benefits, and labor law compliance while the worker performs their day-to-day job for your company.
EOR is fundamentally a compliance and payroll solution, not a talent sourcing or management solution. In most EOR arrangements, you find and select the candidate yourself (or through a separate recruiting process); the EOR simply handles the legal employment relationship required because you don’t have a local entity.
What EOR is good at:
– Quickly and compliantly employing an individual you’ve already identified, in a country where you have no legal entity
– Managing statutory benefits, local tax withholding, and labor law compliance on an ongoing basis
– Providing a lower-commitment structure for hiring one or two people in a new country, without a full staffing relationship
What EOR doesn’t do:
– Source or vet candidates (in most models, this remains your responsibility)
– Provide backup coverage, bench depth, or the ability to quickly replace someone who doesn’t work out
– Offer institutional knowledge of the local talent market, compensation benchmarks, or cultural fit assessment
– Guarantee retention EOR employees can and do leave, and the EOR provider typically has no stake in preventing that
EOR is best understood as legal infrastructure, not a talent partnership.
Staff augmentation: What it actually is
Staff augmentation is a talent partnership model. The provider sources, vets, and employs engineers, then places them with your team, where they work under your day-to-day direction integrated into your sprints, your codebase, and your engineering culture, while the provider manages the employment relationship, HR, hardware, and compliance in the background.
What staff augmentation is good at:
– Providing vetted, pre-qualified candidates rather than requiring you to run your own recruiting pipeline in a foreign market
– Offering bench depth: if an engagement needs to scale up, or if an individual placement doesn’t work out, a mature provider can typically offer a replacement faster than a fresh recruiting search
– Bundling hardware provisioning, security configuration, HR support, and retention management into the relationship reducing your administrative burden significantly beyond what pure EOR offers
– Providing local market knowledge compensation benchmarks, cultural context, and a track record with comparable placements
What staff augmentation doesn’t inherently do:
– Guarantee project outcomes (unless structured with outcome-based terms specifically)
– Provide a path to legal ownership of the employment relationship, unless paired with a BOT structure
– Necessarily give you a dedicated, single-client team unless specifically negotiated some providers place engineers who also work with other clients over time (verify this specifically before signing)
Build-operate-transfer (bot): What it actually is
BOT is a phased model that starts like staff augmentation the partner sources, employs, and manages a dedicated team on your behalf but includes a structured path to transferring full legal ownership of that team to your own entity, once (and if) you establish one in that country.
What BOT is good at:
– Providing a dedicated team from week one, without the multi-month, five- to six-figure cost of establishing a foreign legal entity upfront
– Preserving optionality: you’re not committing to permanent reliance on the partner, nor to establishing a foreign entity before you’re ready
– Retaining institutional knowledge through the transition the same engineers, not a fresh team, move to your direct employment when you transfer
– Scaling a genuinely long-term country presence, where staff augmentation alone might feel administratively thin at larger team sizes
What BOT requires:
– A longer-term commitment mindset BOT is generally not the right structure for a single short-term engineer or a bounded project
– A partner with genuine legal infrastructure in-country, since the transfer phase depends on their ability to support entity establishment and employment migration
– Patience with a phased decision: many companies operate in the BOT model for two to four years before deciding whether to transfer, and that’s by design, not a delay
A decision framework
Choose EOR if:
– You’ve already identified a specific candidate through your own process
– You need one or two hires in a country, not an ongoing team-building relationship
– You have internal capacity to manage performance, culture integration, and replacement risk yourself
Choose staff augmentation if:
– You need vetted talent sourced for you, with bench depth and replacement capability
– Your internal engineering leadership can direct day-to-day work
– You want a single relationship that also handles HR, hardware, and retention management
– You’re not yet certain you want a long-term dedicated country presence
Choose BOT if:
– You’re planning a genuinely long-term (3+ year) engineering presence in the country
– You want the option not obligation of full legal ownership eventually
– You’re scaling beyond the size where a lighter staff augmentation relationship feels administratively sufficient
– You want continuity of the same team through any eventual ownership transition
Many companies use more than one model simultaneously:
It is entirely reasonable and common in practice to use EOR for a single specialized hire you sourced yourself, staff augmentation for your core ongoing engineering team, and a BOT structure for a strategic, growing country presence, all at the same time, potentially even with the same overall partner if they offer the range of services.
The question that actually differentiate providers within each model
Regardless of which model you choose, ask any provider:
– What is your attrition rate, and how does it compare to the market you operate in?
– Do you provide dedicated hardware and security controls, or rely on personal devices?
– What happens, contractually, on day one after the engagement ends who has access to what?
– Can you show a reference client who has used this exact model with you for 2+ years?
– What is your actual legal entity structure in the country not just a partner network, but direct legal presence?
Conclusion
EOR, staff augmentation, and BOT solve genuinely different problems, and the right answer for your company depends on your timeline, your commitment level, and how much of the talent sourcing and management burden you want to carry yourself. The mistake is not picking the “wrong” model in isolation it’s picking a model because a vendor sells only that one, rather than because it fits your actual situation. A partner who can honestly walk you through all three, and tell you when their own preferred model isn’t the right fit, is worth more than one who has only one structure to offer.
Bibliography
- HireWithNear. (2026). US companies hiring in Latin America: 5 strategic trends for 2026. https://www.hirewithnear.com
- Morgan Stanley. (2026). Technology market trends: The financial logic of build-operate-transfer models in LATAM. Morgan Stanley Equity Research.
- N-iX. (2026). Software development in Latin America: Industry overview and regional hub analysis. N-iX Technical Reports.
- Alcor BPO. (2026). Nearshore software development in Colombia 2026. https://alcor.com
Book a Consultation to learn about engineering operations to Colombia:
https://outlook.office.com/book/[email protected]/?ismsaljsauthenabled
Learn about: The Changing Economics of the H-1B Visa here
