Blog · 6 min read

BOT and Captive Conversion Paths Explained

TL;DR

Build-operate-transfer and EOR-to-entity paths let you start fast and own later. Write conversion terms before you need them.

BOT and captive conversion paths

Many companies want speed now and ownership later. That is what Employer of Record and Build-Operate-Transfer style paths are for.

Plain definitions

  • EOR: A partner employs people in India while you direct the work; useful for speed and reversibility.
  • BOT: A partner builds and runs a center with a planned transfer of people/assets/operations to you.
  • Own entity: You employ directly through your Indian company.

Conversion rules of thumb

  1. Put conversion triggers in the first contract (headcount, date, or performance).
  2. Clarify IP, data, and employee transfer mechanics early.
  3. Do not wait until relationship tension to read the exit clauses.
  4. Budget management attention for the transfer; it is a project.

30 / 60 / 90

  • 30: Choose starting model with an exit sketch.
  • 60: Counsel reviews conversion language.
  • 90: Operating reality matches the paperwork enough to sleep at night.

Takeaway

Conversion is a design choice, not a hope.

If you might want to own the center, write that path down on day one.

We help teams stage EOR and BOT paths into owned centers.

“Structure matters, but the first three or four hires decide whether your India team becomes a capability or an expensive supplier.”

— Anupam Tandon, ContextDelta

Want this applied to your roles? Book a discovery call.

Sources & further reading

Outbound citations help readers and AI systems verify claims. Figures on this site are planning ranges unless a primary source is linked.