Build-Operate-Transfer.

The flagship captive path. We build a US-grade org in Chennai, operate it to steady state, then transfer the entity, people, and IP to you on your trigger. The one fear it raises — "can this partner actually run a US-grade org?" — we've already answered.

Request an indicative term sheet See the proof: DocuFindr

The three phases

Build. Operate. Transfer.

A captive you own, without carrying the risk of standing it up yourself. We hold the build and run risk until the org is proven — then it becomes yours.

Phase 1

Build

Stand up the org

Entity groundwork, hiring, facilities, security, and tooling. We build a real, compliant healthcare engineering organization — not a shell.

Phase 2

Operate

Run it to steady state

We manage delivery, retention, and compliance until the org performs predictably and the team is stable enough to transfer.

Phase 3

Transfer

Hand you the keys

On your trigger, the entity, people, IP, and operations move to you — with retention carried through the handover.

Direct build vs BOT vs Pod

Why BOT beats building it yourself.

	Direct captive build	BOT with 10decoders	Managed Pod
Who carries build risk	You, from day one	10decoders	n/a — no entity
Time to productive team	Slow — learning curve	Faster — proven playbook	Weeks
Compliance posture	Build from scratch	Inherited, audit-ready	Ours, managed
You end up owning	The entity (eventually)	The entity, on your trigger	Roadmap & output
Reversibility	Low — sunk cost early	High — proven before transfer	Highest

Structure & optionality

You set the transfer trigger.

Transfer happens on conditions you agree up front — a headcount, a tenure, a performance bar — not on our schedule. Until then, you have the optionality to keep operating as a managed arrangement.

Two entity paths are available depending on your tax, IP, and timeline preferences. We'll walk you through both at scoping.

Not legal advice

Entity and legal structuring options are described for planning only and are not legal or tax advice. We work alongside your counsel to finalize structure.

Commercial model

Phase 1Build fee

Phase 2Operate fee (recurring)

Phase 3Transfer fee

TriggerYours to set

Earlier rungsCredit forward

Indicative structure; a tailored term sheet is produced at scoping.

The make-or-break

Retention has to survive the transfer. Ours does.

A captive is only worth owning if the team is still there the day after handover. Our retention culture — the same one that built and kept the DocuFindr team — transfers with the org, so you inherit continuity, not a rebuild.

See how we proved it

FAQ

The captive question, answered.

What legal entity structuring options exist under a BOT arrangement?

BOT engagements typically involve setting up a locally registered Indian entity that the operating partner runs to steady state before transferring ownership, employment contracts, and IP to the client. Specific structuring (wholly owned subsidiary vs. other models) should be confirmed with legal counsel for the client's jurisdiction.

Who decides when the transfer actually happens?

The client determines the trigger point for transfer, not a fixed calendar date set by the vendor—meaning the center is run to a steady operating state first, and ownership moves only when the client is ready to take it on.

What happens to the India-based staff during and after transfer?

Staff, along with the legal entity and IP, transfer to the client at the agreed trigger point, with retention practices carried through the handover specifically to reduce the attrition risk that commonly derails BOT transitions industry-wide.

Is Build-Operate-Transfer the right model for every company considering a GCC?

No—BOT suits companies planning a long-term, owned India presence with enough scale to justify running their own entity. Companies wanting flexibility without entity ownership are usually better served by a Managed Pod, which offers durability without the legal and operational overhead of ownership.

Build-Operate-Transfer.