BOT & Transition · GCC Operations
Build-Operate-Transfer with the transfer designed in from the first month: team, processes, systems, workspace and controls built to hand over, an operate stage measured against readiness criteria, and a staged transition of employees, records, vendors, knowledge and control into your organization.
Most companies that choose Build-Operate-Transfer want the same thing: a center they own, staffed by their people, run under their governance, without having to build every local function before the first team is productive. The risk is not in the build or the operate stage. It is in a transfer that was never designed, arriving at a center that was never built to be handed over.
NeoIntelli builds the operating layer to transfer from the first month, runs it until readiness criteria are met rather than until a date arrives, and moves it into your organization in stages you control.
BOT & Transition is NeoIntelli's Build-Operate-Transfer service for companies that want to own their India GCC but do not want to build every local operating function before the first team is productive. NeoIntelli builds the team, processes, systems, workspace and controls, operates the agreed operating layer until readiness criteria are met, and then transfers employees where applicable, process ownership, vendors, systems, records, governance and operational control into the client's organization. Every process is documented for transfer from day one. Transfer mechanics depend on the contract and entity structure.
Three stages, one design principle: nothing is built in a form that only NeoIntelli can run. Exact transfer mechanics depend on the contract and the entity structure.
Stage 1
Everything is built in the form it will be handed over in: documented, owned, on standard tooling.
Stage 2
NeoIntelli runs the agreed operating layer against service levels while the center's leadership and the client's receiving organization mature.
Stage 3
Defined capability moves into the client's organization by readiness criteria, staged by function, team or location.
The BOT journey
Six steps. The two in the middle, stabilize and transfer readiness, are the ones most BOT arrangements skip, and the ones that decide whether the cutover is a milestone or a crisis.
Team, processes, systems, workspace, controls and operating model, built for handover.
The operating layer runs to service levels. Leadership focuses on the mandate.
Stable performance, documented processes, settled leadership, trusted reporting.
Readiness criteria met and evidenced. Client owners named for every function.
Employees, records, vendors, systems and control move on a planned date, staged where needed.
The client operates the center directly. NeoIntelli supports on request.
Readiness criteria are agreed at the start and evidenced before cutover. They replace the calendar as the trigger for transfer.
A checklist for the transfer plan. Each item has a client owner, a source, a destination and a reconciliation step.
Note: Third-party contracts transfer only where the contract allows it and any required consent is obtained. Where consent is not available, a replacement arrangement is planned and in place before cutover. NeoIntelli does not promise the transfer of third-party contracts it does not control.
People are the most important thing that moves, and the area where a general promise is least useful. The transition plan covers each of these areas explicitly for the specific structure in use.
Note: Treatment of tenure, gratuity, equity, tax and benefit continuity depends on the employment structure, the contract and applicable law. NeoIntelli plans the operating side of the transition and does not make universal claims about these outcomes. Legal, tax and regulatory interpretations should be validated with qualified advisers. NeoIntelli can coordinate the operating implementation of agreed requirements.
The day-to-day employee lifecycle before and after transfer is covered under People & HR Operations.
The test of a BOT-ready operating model is simple: could the client's organization run it tomorrow with the documentation, systems and records it has access to today? If the answer depends on NeoIntelli-only processes, undocumented knowledge or partner-only tooling, the model is not ready, whatever the contract says.
NeoIntelli designs around documented processes, defined ownership, service levels, standard tooling, employee and vendor records in transferable systems, controls with evidence, knowledge transfer during the operate stage, transition governance and clear commercial obligations. The full list is on the GCC Operations overview.
The models are often confused because the operate stage can look similar from the outside. The end state and the obligations are different.
| Factor | Build-Operate-Transfer | Captive from day one | EOR | Managed services |
|---|---|---|---|---|
| Who operates local functions | Partner, until transfer | Client, from day one | Employer of record, limited scope | Partner, for as long as agreed |
| Employment vehicle | Per contract and entity structure, with planned transfer | Client's India entity | Third-party employer | Client's India entity |
| End state | Client-owned and operated center | Client-owned and operated center | No built-in path to a center | Client-owned, partner-operated |
| Transfer obligation | Yes, planned from the start | Not applicable | No | No, optional later |
| Best for | Companies that want to own the center but are not yet ready to run it | Companies with an India operations organization already in place | Small pilot teams before an entity exists | Companies that want to keep leadership on the mandate long term |
Comparing a GCC with outsourcing altogether? Read GCC vs Outsourcing. Weighing entity timing and cost? Use the GCC Cost Calculator.
Buyer questions
Legal, tax and regulatory interpretations should be validated with qualified advisers. NeoIntelli can coordinate the operating implementation of agreed requirements.
A Build-Operate-Transfer model is an arrangement where a partner builds the center's team, processes, systems, workspace and controls, operates the agreed operating layer for a period, and then transfers defined capability into the client's organization. The client owns the intended end state from the start. The partner is accountable for getting the center to a transferable condition.
In India, BOT typically involves the partner recruiting and operating the team under an agreed employment and entity structure, running local operations and governance, and then transferring employees, processes, vendors, records and operating control to the client's India entity once readiness criteria are met. The legal mechanics depend on the entity structure, employment arrangements and contract, and should be confirmed with qualified advisers.
BOT fits when a company wants to own its India center but cannot yet run every local function itself, wants to start before its own organization is ready, or wants to reduce the risk of a first-time build. It fits less well when the company already has a strong India operations team or wants managed operations long term.
Long enough for the center to reach stable performance, documented processes, settled leadership and a client organization ready to receive it. That is determined by readiness criteria agreed at the start rather than by a fixed calendar. Ending the operate stage on a date rather than on readiness is the most common cause of a difficult transfer.
Employees move into the client's organization under a planned transition that covers employment documentation, continuity of service where applicable, benefits and payroll cutover, leave balances, statutory records, policy changes, communication and manager continuity. The specific treatment of tenure, benefits and any equity or tax matters depends on the structure and must be confirmed with legal and tax advisers.
The client should own the intellectual property created by the center throughout the arrangement, not only after transfer. This should be established in the engagement contract and in employment and vendor agreements from day one, with assignment provisions that do not depend on the transfer happening. NeoIntelli does not claim ownership of client IP.
Yes. Transfer can be staged by function, by team or by location, with each stage having its own readiness criteria and cutover plan. Gradual transfer reduces disruption and lets the client's organization build capacity at a sustainable pace. The sequence should be agreed in the transition plan rather than improvised.
A captive built directly gives the client full control from day one but requires the organization to run every local function immediately. BOT reaches the same end state through a partner-operated period, trading some early control for lower execution risk and a faster start. The right choice depends on how ready the client's own organization is to operate in India.
An employer-of-record arrangement provides an employment vehicle for a small team, usually with limited operating support and no built-in path to a client-owned center. BOT builds and operates a complete operating layer with transfer as the intended outcome. EOR can be a short first step. BOT is a route to ownership.
Managed services run agreed operating functions for as long as the client wants them, with no obligation to transfer. BOT includes a planned transfer of capability into the client's organization. The operating layer can look similar during the operate stage. The commercial terms, the documentation standard and the end state are different.
BOT Transition
A working session on your intended end state, entity timing, readiness criteria and how employees, vendors, systems and control would move.
One partner, five connected services