BOT GCC India — Build-Operate-Transfer for Nano, Micro & Scaled Teams
BOT is a transition pathway, not only a large-GCC model. BOT can apply to Nano GCC, Micro GCC, and scaled GCC teams. Inaac builds and operates the India team — on your Indian entity payroll or on Inaac-managed payroll/EOR — then transfers people, processes, documentation, governance cadence, vendor relationships, and operating controls to you at agreed milestones.
The BOT Pathway
Build Phase
Inaac sets up the India team — entity incorporation (if needed), hiring, onboarding, payroll, compliance, workplace, and operating processes. The team operates on your entity payroll or Inaac-managed EOR.
Operate Phase
Inaac manages day-to-day operations — payroll, compliance, HR, finance, vendor management, and governance cadence. You retain strategic direction and business oversight.
Transfer Phase
At agreed milestones, Inaac transfers people, processes, documentation, governance cadence, vendor relationships, and operating controls to your organisation. The transition is structured, not abrupt.
What Gets Transferred
GCC Model Comparison
| Model | Typical Team Size | Employment Structure | Best For | BOT Pathway |
|---|---|---|---|---|
| EOR / Inaac Payroll | 1–20 | Inaac-managed payroll/EOR | First hires, pilot teams, quick start | Yes |
| Nano GCC | 1–20 | Client entity payroll or Inaac-managed payroll/EOR | Controlled India entry | Yes |
| Micro GCC | 20–50 | Client entity payroll or Inaac-managed payroll/EOR | Dedicated functional team | Yes |
| Scaled GCC | 50+ | Usually client entity payroll | Mature India capability center | Yes |
| BOT | Applies across models | Transition from Inaac-operated to client-owned | Ownership transfer over time | Core pathway |
Frequently Asked Questions
Is BOT only for large GCCs with 50+ people?
No. BOT is a transition pathway, not a size model. BOT can apply to Nano GCC (1–20 people), Micro GCC (20–50 people), and scaled GCC teams. The BOT structure is the same regardless of team size — Inaac builds and operates the team, then transfers ownership at agreed milestones.
What is transferred in a BOT transition?
We transfer people (employment contracts, HR records, statutory registrations), processes (SOPs, compliance calendars), documentation (entity documents, statutory registers), governance cadence (board meetings, MIS reporting), vendor relationships (IT, facilities, payroll), and operating controls (finance controls, HR policies).
Does BOT require the client to have an Indian entity?
Not necessarily. The India team can be operated on Inaac-managed payroll/EOR during the Build and Operate phases. If the client does not have an Indian entity, we can incorporate one as part of the BOT process, with the team transitioning to the client entity payroll at the Transfer milestone.
How long does a BOT transition take?
BOT timelines vary based on team size, complexity, and client readiness. A Nano GCC BOT transition may take 6–12 months. A Micro GCC BOT may take 12–18 months. Milestones and timelines are agreed upfront and reviewed at each phase.
What happens if the client is not ready to take ownership at the agreed milestone?
BOT milestones are designed to be flexible. If the client needs more time to build internal capability before taking ownership, we can extend the Operate phase. The goal is a smooth, successful transfer — not a forced handover.
Design Your BOT Roadmap
Speak with Inaac Advisors about BOT pathways for Nano GCC, Micro GCC, and scaled India teams.
Book India Entry Consultation