BOOT (Build-Own-Operate-Transfer) is BOT with financing: the partner funds and owns the center, runs it, then sells it to you. It wins for a 30–100+ person hub when you want ownership but will not put ~$150K–$500K CapEx on the board yet. It fails below ~25 people, when you can fund setup yourself, or when you need hires in weeks.
Map the wider menu in the global hiring models overview, then read BOT and EOR vs entity before you accept a multi-year BOOT MSA. If a salesperson leads with BOOT before asking about headcount and CapEx appetite, treat that as a product pitch, not discovery.
Use BOOT when
- Board or treasury will not fund entity, office, and equipment until the center shows ROI.
- Planned scale is ~30–100+ in one market (India remains the deepest BOOT ecosystem; Philippines, Poland, and Romania appear less often).
- You accept higher total cost (often ~15%–30% above standard BOT) in exchange for near-zero upfront capital.
- You can live with an 18–36+ month operate window before buyout.
- Finance prefers opex-heavy structures over CapEx during the ramp, even if IRR looks worse later.
Not when
- You can write the CapEx check. Standard BOT or a DIY captive usually costs less over the full cycle.
- Team stays under ~25. Overhead, buyout math, and transfer complexity do not amortize. Use EOR.
- You need people next month. BOOT build to first hire is commonly 3–6 months.
- Strategy may pivot within 3 years. BOOT locks you into a market, partner, and buyout path.
- Legal wants a simple services agreement. BOOT is closer to project finance plus employment ops than to staff aug.
How BOOT works (four phases)
Build (months 1–6). Partner incorporates, leases, equips, and recruits. They write the checks. You set roles, interview bars, and tooling standards.
Own (overlaps build/operate, often months 1–24). Partner carries the entity on its balance sheet. Underperformance, attrition spikes, and empty seats hit their P&L first. That risk transfer is why BOOT costs more than BOT.
Operate (months 6–30). Partner runs HR, payroll, facilities, and compliance. Your leads run delivery. Operate windows run longer than typical BOT because the partner needs time to earn back CapEx through management fees. Demand monthly P&L transparency for the center, not only a blended invoice.
Transfer (months 24–36+). Share or asset sale, employee re-papering, license and bank transitions. Budget 3–6 months for legal and regulatory work alone in markets like India (share transfer, board resolutions, ROC filings). Align early with remote hiring compliance controls so access, devices, and data residency do not become transfer blockers.
Concrete cost scenario: 40 developers in India
Assume ~$40,000 loaded cost per developer/year.
| Layer | Typical public-practice range | What it means for 40 people |
|---|---|---|
| Partner CapEx (their money) | ~$150,000–$500,000 | You avoid this cash outlay |
| Operate management fee | ~20%–35% of loaded cost | ~$320,000–$560,000/year at those rates |
| Transfer / buyout | ~$3,000–$8,000 per employee + asset book value | ~$120,000–$320,000 before assets |
| Versus BOT | Often 15%–30% higher full-cycle cost | Premium = capital preservation |
| Versus EOR | EOR ~$400–$699 × 40/month = ~$192K–$336K/year ongoing | BOOT ends after buyout; EOR does not |
Cash-flow framing for a CFO: year 1 BOOT may look “cheap” because CapEx is off your balance sheet, while cumulative years 1–3 often exceed BOT. Model both NPV and peak cash. If your real question is when to leave EOR, tie timing to headcount and entity readiness via how to choose an EOR, not fee fatigue alone.
Side-by-side: BOOT vs adjacent models
| Factor | BOOT | BOT | EOR | Captive DIY | Staff aug | TBO |
|---|---|---|---|---|---|---|
| Who funds build | Partner | Shared / you often pay setup | N/A | You | Vendor | Provider |
| Who owns entity mid-cycle | Partner | Varies | EOR | You | Vendor | Provider |
| Upfront cash from you | Near zero | Medium | Near zero | High | Low | Low |
| Full-cycle cost | Highest of transfer models | Mid | High if large and permanent | Lowest if you execute well | High markup, no ownership | Project-shaped |
| Time to first hire | 3–6 months | 2–4 months | Days–weeks | 6–12+ months | Days–weeks | Weeks |
| Exit difficulty | Hard (buyout + multi-year MSA) | Hard | Easier (notice) | Entity wind-down | Notice / conversion | Notice / KT fees |
| Best for | Scale + CapEx deferral | Scale + willing to fund setup | Small teams / tests | Ops-ready enterprises | Temporary seats | Variable skills |
Also contrast what is TBO and what is ODC if ownership is not the goal.
When finance pushes BOOT and product should push back
CFOs like BOOT because CapEx stays off the balance sheet in year 1. Product and People leaders should push back when:
- The roadmap needs stable senior owners who identify with your company, not a partner brand, for 24 months.
- You already have cash for a standard BOT build and the BOOT premium is pure financing cost at a bad implied rate.
- The “center” is really eight people. BOOT infrastructure for a squad is theater.
Run a simple implied-financing check: take the extra full-cycle cost versus BOT (often 15%–30%) and divide by CapEx avoided. If you are paying the equivalent of a very expensive loan to defer $200K of spend, treasury should say so out loud.
Second scenario: Series C fintech, 60-person India hub
Board wants the hub in 18 months but blocks CapEx until NPS and gross margin prove out.
- Partner funds ~$300K build (office, kit, entity).
- Operate at ~25% management fee on a $40K loaded average: 60 × $40K × 25% ≈ $600K/year partner fee layer during operate.
- Buyout at month 30 at ~$5,000/seat ≈ $300K, plus asset book value.
- Alternative: stay on EOR for the first 20 people (~$400–$699/seat/month), then decide BOT vs BOOT once the market is proven.
BOOT is coherent if the board truly will not fund CapEx and the 60-person plan is real. It is incoherent as a way to avoid making a market decision.
Contract terms that decide whether BOOT works
- Unilateral transfer trigger after a fixed month, with delay liquidated damages.
- Buyout formula fixed at signature (per seat band, multiple of unrecovered CapEx, or book value plus capped premium).
- Audit rights on CapEx and operate-cost true-ups so “investment recovery” cannot inflate silently.
- Employee non-solicit carve-outs that still let you hire the team at transfer without a second ransom fee.
- Change-of-control continuity for tools, IP, and customer data on day one of ownership.
- Financial covenants / step-in if partner credit deteriorates.
- Hire approval rights so the partner cannot pad headcount to inflate fees and buyout base.
- Security and privacy schedules that survive transfer (SOC reports, subprocessors, breach notice).
Without those, “24-month transfer” becomes a slogan.
Key risks
Incentive to delay transfer. Every extra operate month pays the partner. Hard triggers beat goodwill.
Buyout disputes. Multiple of investment vs fixed per seat vs book value plus premium: pick one formula at signature. Negotiating price when you already depend on the center is how deals go sideways.
Higher transfer attrition. Because the partner owned the brand, expect roughly 10%–20% exits in the transfer window, often worse than standard BOT. Fund retention early and communicate the buyer brand months ahead.
Single-partner concentration for 3–5 years. Diligence financials, delivery references, and substitution rights harder than for short EOR pilots.
Regulatory friction at change of control. Licenses, banks, tax IDs, and labor continuity rules can add quarters, not weeks. See also EOR compliance risks for how messy employment transitions get when paperwork lags.
Shadow IT and SaaS sprawl. During own/operate, the partner may subscribe to tools on its entity. Inventory every SaaS seat and admin credential before transfer or you inherit orphaned systems and surprise renewals.
FAQ
How is BOOT different from BOT in one sentence?
BOOT makes partner ownership and financing explicit; BOT is build/operate/transfer without requiring the partner to carry CapEx and balance-sheet risk the same way.
Who owns IP before we buy the center?
Usually the partner’s employment stack unless your MSA assigns work product to you as customer. Require continuous IP assignment, moral-rights waivers where relevant, and a transfer schedule that re-assigns historical work to your post-buyout entity.
What do exit and early-termination fees look like?
Expect repayment of unrecovered CapEx, remaining operate minimums, and sometimes a break fee. Soft exit is not BOOT’s strength; use EOR until the market is proven if optionality matters.
Are transfer / buyout fees negotiable?
Yes, and they should be fixed in the MSA. Leaving “fair market value at transfer” undefined is a classic failure mode. Per-employee bands around $3,000–$8,000 plus assets are a planning anchor, not a quote.
Misclassification: is BOOT safer than freelancers?
If workers are on proper local employment with the partner, classification risk is generally lower than contractor body-shopping. It is not zero if the partner mislabels staff. See contractor vs employee (global).
What happens to benefits at transfer?
Employees usually move from partner benefit schemes to yours. In many jurisdictions you must avoid coverage gaps and may need to honor accrued leave or settle it. Treat benefits continuity as a transfer workstream with local counsel, not an HR afterthought.
Is BOOT common outside India?
India dominates because of talent depth, partner density, and relatively workable private-company transfer mechanics. Elsewhere, teams more often use BOT, EOR-to-entity, or a captive. Do not assume a BOOT product exists in every market a salesperson mentions.
How do we diligence a BOOT partner’s CapEx claims?
Require itemized CapEx budgets, invoices or asset registers, and audit rights before transfer. CapEx that cannot be evidenced should not inflate buyout. Treat unverifiable “sunk investment” stories as a red flag equal to fuzzy transfer dates.
Should we ever combine BOOT with a short EOR bridge?
Sometimes. Hire the first five critical people on EOR to start delivery while the BOOT build runs, then fold them into the center only if conversion terms are pre-negotiated. Without conversion terms, you create two orphan populations and a messier IP map.
Related guides
Related Decision Pages
Was this page helpful?
Tell us or send a correction.