BOT (Build-Operate-Transfer) is the rent-to-own path for an offshore center: a partner builds and runs the team, then hands you the entity, employees, and ops. It wins for 20–100 permanent hires when you want ownership in 18–36 months. It fails under ~15 people, for untested markets, or when you need someone working next week.
If you are still mapping structures, start with the global hiring models overview, then contrast BOOT, TBO, and what is an EOR.
Use BOT when
- You have committed to a market (India, Poland, Mexico, and similar) and want eventual local entity ownership, not a perpetual vendor relationship.
- Target headcount is roughly 20–100+ in one site, so setup and transfer overhead amortizes.
- You can wait 2–4 months to first hire and 18–36 months to full transfer.
- Your HQ cannot staff local HR, facilities, payroll registration, and entity admin during the ramp.
- Leadership wants a captive-like center but will not staff a greenfield DIY build for the first two years.
Not when
- Headcount stays under ~15. Use EOR; BOT fees and transfer logistics do not pay back.
- You are still testing talent quality or product-market fit. EOR or a small ODC trial is cheaper to exit.
- You need people in days, not months. BOT’s build phase cannot compete with EOR onboarding timelines.
- You do not want to run a foreign subsidiary after transfer. BOT’s end state is you owning the center.
- Procurement wants a pure services MSA with no path to ownership. That is staff aug, TBO, or BPO, not BOT.
How BOT works (three phases)
Build (months 1–6). The partner incorporates a local entity or uses its own, leases space, stands up IT, and recruits against your role specs and interview bar. You approve candidates and technical standards. First hires often land in 2–4 months, versus 6–8 months if you incorporate, bank, register payroll, and hire yourself from zero.
Operate (months 6–24). The partner runs HR, payroll, facilities, and local compliance. Your engineering or ops leads run product output. This is where most BOT value sits: you get a full center without building scaffolding. Insist on visibility into attrition, time-to-fill, and employer cost true-ups every month.
Transfer (months 18–36). Entity (or a fresh entity you form), employment contracts, lease, assets, and process docs move to you. Expect 3–6 months of embedded transition support. Employee consent, benefits continuity, and local labor rules (India, Brazil, and similar) decide whether the handoff is clean or a re-hire exercise.
Transfer is where deals succeed or fail. Hard deadlines, delay penalties, IP assignment, and attrition budgets belong in the contract at signature, not at month 22.
Concrete cost scenario: 30 engineers in India over 3 years
Assume average fully loaded cost ~$40,000/year per engineer (salary + statutory). Industry-typical BOT economics:
| Phase | What you pay | Rough range |
|---|---|---|
| Build | Setup (entity, office, recruiting framework) | ~$30,000–$100,000 (sometimes waived for higher operate margin) |
| Operate | Management fee on loaded cost | ~15%–25% (so ~$46,000–$50,000 all-in per person/year at those fees) |
| Transfer | Per-employee or lump sum + your entity legal | ~$0–$5,000/employee, plus ~$5,000–$30,000 entity work |
Year-3 math, simplified: 30 people × $40,000 loaded = $1.2M labor. At a 20% management fee, operate premium is ~$240,000/year during the operate window. Add build once and transfer once. Over a full 3-year cycle, BOT often lands ~10%–20% above a pure DIY captive from day one, in exchange for 3–6 months faster time-to-team and less operational risk.
Compare ongoing EOR at roughly $400–$699/employee/month: for 30 people that is ~$144K–$252K/year forever, with no ownership unless you later set up an entity via EOR vs entity. For broader budget framing, see cost of hiring internationally and the BPO cost guide.
Side-by-side: BOT vs adjacent models
| Factor | BOT | BOOT | TBO | EOR | Captive (DIY entity) | Staff aug |
|---|---|---|---|---|---|---|
| End state | You own center | You buy out partner-owned center | Provider keeps delivery model | EOR stays employer | You always owned it | Vendor keeps workers |
| Sweet spot | 20–100+ | 30–100+, capital constrained | Project / variable skills | 1–20 | 30+ with ops muscle | Short-term capacity |
| Time to first hire | 2–4 months | 3–6 months | Weeks (if bench exists) | Days–weeks | 6–12+ months | Days–weeks |
| Upfront capital | Medium ($30K–$100K+) | Near zero (partner funds) | Low | Near zero | High | Low |
| Ongoing premium | 15%–25% mgmt (temporary) | 20%–35% + buyout | Blended / outcome rates | Flat EOR fee | Internal ops cost | Hourly markup |
| IP path | Contract + transfer clean-up | Same, plus share/asset sale | Commercial assignment | Employment contracts | Direct employment | Vendor contract |
| Best for | Planned permanent center | Same, defer CapEx | Skills flex, not ownership | Speed without entity | Full control from day one | Temporary seats |
Deep comparisons: what is BOOT, what is TBO, EOR vs staffing agency, EOR vs BPO.
BOT vs captive center: when DIY still wins
A captive (your own entity from day one) wins when you already have regional ops leadership, a local counsel relationship, and confidence you will keep 40+ people for 3+ years. You skip partner margin and transfer politics. You also own every miss: bad lease, payroll registration delay, weak first hiring manager.
Practical split used by many scale-ups:
- 0–15 people, unproven market: EOR.
- 15–40 people, committed market, weak local ops: BOT.
- 40+ people, strong local ops bench: captive, optionally with a short EOR bridge during incorporation.
If the captive path is real, read EOR vs entity for crossover math by country before you pay BOT setup fees.
Second scenario: 20-person product team in Poland
Nearshore BOT in Poland often prices higher per seat than India but closer time zones for US/EU product teams. Illustrative path:
- Build: ~$40K–$80K for entity support, Warsaw or Kraków office, and initial recruiting.
- Operate: management fees still cluster around 15%–25% of loaded cost; loaded mid-level eng cost is commonly higher than India, so the absolute fee is higher even at the same percentage.
- Transfer at month 24: budget retention for ~5%–15% attrition and Polish employment continuity paperwork.
If you only need six engineers for an 18-month build, this is usually the wrong tool. Use EOR or TBO for the spike, then revisit BOT only if headcount stays.
Negotiation checklist before you sign
Put these in the MSA, not in a side letter after you are dependent on the center:
- Transfer date with penalties for delay, plus your right to trigger transfer after a stated month.
- Transfer price formula (per seat, lump sum, or asset book value), frozen at signature.
- IP assignment that benefits your company during operate and after transfer, covering past work.
- Named critical roles and notice before substitutions.
- Attrition SLA and retention-bonus funding responsibility during transfer.
- Step-in rights if the partner becomes insolvent or materially breaches.
- Data, credentials, and source-code escrow or continuous delivery obligations.
- Brand and email domain usage during operate so employees do not only know the partner employer.
- Open-book operate costs so “loaded cost” cannot hide unexplained markups.
Key risks (budget these explicitly)
Operate-phase lock-in. The partner earns fees every month of delay. Start transfer planning by month 12, not month 22.
Attrition at transfer. Expect roughly 5%–15% exits when the employer of record changes. Retention bonuses and early communication help; some loss is normal.
Loyalty to the partner brand. If workers feel employed by the BOT firm, not you, transfer becomes recruitment. Prefer arrangements where your brand is visible early (email, tools, career framing).
IP during operate. Code written by partner employees needs assignment that benefits your company, not only the partner. Dual assignment (employee → partner → you, or direct third-party beneficiary language) is standard practice.
Markets with hard labor transfer rules. Brazil, France, Germany, and similar jurisdictions make employee movement between entities slower and more expensive than India-centric BOT playbooks imply. Price local counsel into the transfer budget.
FAQ
Who owns IP during the operate phase, and after transfer?
During operate, default ownership often sits with the partner as employer unless your MSA assigns work product to you. After transfer, re-paper employment IP clauses onto your entity. Require invention assignment covering past and future work, plus escrow or source-code delivery milestones before final payment.
What exit options exist if we abandon the market at month 14?
Most BOT contracts are multi-year. Expect early-termination fees covering unrecovered build costs and notice on the operate team. Negotiate a wind-down schedule, employee notice funding, and lease exit responsibilities up front. If exit optionality matters more than ownership, stay on EOR until the market is proven.
How much are typical transition / transfer fees?
Public practice ranges widely: from included in the MSA to about $2,000–$5,000 per employee, sometimes plus asset book value. Ambiguous formulas are how partners extract premium at month 24. Fix the formula at signature.
Does BOT create contractor misclassification risk?
Usually no if the partner properly employs workers on local employment contracts. Risk rises if the “BOT” is really a body shop of freelancers billed as employees, or if you control workers while they stay on shaky contractor papers. Treat classification the same way you would in any outsourced model; see contractor vs employee (global).
What happens if the BOT partner fails mid-operate?
Employees sit on the partner’s entity. Insist on step-in rights, source-code and access continuity, and a documented path to move people to your entity or a backup EOR on short notice. Ask for audited financials and long-tenure client references before you sign.
BOT vs staff augmentation: which is rent vs rent-to-own?
Staff aug rents capacity with no transfer. BOT builds infrastructure and people with an explicit handoff. If you never want the keys, do not buy BOT. For recruitment-led temp models, see EOR vs staffing agency.
Which markets work best for BOT?
India still dominates because of talent depth and a mature partner ecosystem. Poland, Romania, and Mexico show up often for nearshore BOT. Complex labor markets make transfers harder and should not be sold as copy-paste India deals.
How long should the operate phase be?
Long enough to prove the talent market and stabilize managers, short enough that transfer does not become optional. Many workable deals target transfer readiness around 18–24 months, with planning starting at month 12. Operate phases that drift past 36 months without a hard trigger are usually fee extraction, not stabilization.
Can we run BOT and EOR in the same country?
Yes. Some companies keep executives or scarce specialists on EOR while the bulk center sits in BOT operate. Just avoid duplicate management layers and conflicting IP templates. Document which population transfers when.
Related guides
Related Decision Pages
Was this page helpful?
Tell us or send a correction.