SERVICES / BUILD-OPERATE-TRANSFER
BUILD-OPERATE-TRANSFER
The BOT model is now the mainstream mid-market path to a captive AI GCC. FlywheelTech's entire business is designed around executing it correctly.
The Build-Operate-Transfer engagement solves the entry problem for mid-market firms: you do not need to have the operational playbook to start. You engage a partner who does, let them build and operate through to maturity, and take full ownership when the capability is ready to run independently.
BOT has grown from under 10% of new GCC setups a few years ago to approximately 40% today. It is the mainstream path for mid-market BFSI companies that need AI capability without the infrastructure burden of building a captive GCC from scratch.
THE ENGAGEMENT MODEL
BOT Launchpad. BOT Growth. BOT Stable. Each defined by activities and outcomes.
Establishes your initial AI capability — the first team, first production workloads, first governance architecture, first HITL framework. This is the tier for companies entering the GCC model for the first time. The outcome: a functioning, staffed AI operations core, capable of running its first production AI workloads under your governance standards.
Scales the capability. Additional AI operational domains are added. The team expands to match the growing workload. The governance and knowledge infrastructure matures. The outcome: a multi-domain AI GCC operating at scale and building the institutional knowledge required for independent operation.
Brings the GCC to full operating maturity. All required AI operational domains are functional. The institutional knowledge is documented and embedded. The organisation is ready to be transferred and run independently. This is the transfer-ready state — and the end of the BOT engagement.
Note: Managed services persist post-transfer. The BOT timeline ends, but the infrastructure layer continues as a separate engagement.
THE TRANSFER
The transfer is not a handover of headcount. It is a handover of institutional AI capability.
When the BOT engagement reaches the Stable tier, FlywheelTech executes a structured transfer of full ownership to the client:
Every team member is already on your payroll. The transfer formalises your direct operational relationship — FlywheelTech exits the management chain.
All models, fine-tuned weights, training data pipelines, and proprietary AI assets are fully client-owned from the point of creation. Transfer documents and confirms this ownership.
The full operating model — decision escalation protocols, HITL governance, model refresh cadences, audit documentation — is handed over as a complete operational manual.
The architecture decisions, the lessons learned, the cultural and operational context — documented and embedded in the team that remains with you.
After transfer, FlywheelTech steps away from the capability. Managed infrastructure and corporate services continue as a separate engagement.
IMPORTANT DISTINCTION
The BOT timeline ends. The infrastructure layer does not.
A common misconception about the BOT model is that everything transitions to the client at transfer. The AI capability — people, models, IP, governance — does. The infrastructure and corporate services layer does not.
FlywheelTech's managed services — facilities, legal and statutory compliance, finance and accounting, IT infrastructure, HR and payroll operations — continue as a long-term operating layer after the BOT transfer. This is not a transitional arrangement. It is a permanent operational layer that allows your organisation to focus on AI capability development rather than entity management in a jurisdiction where you do not have direct operating experience.
The two layers run on separate timelines. The BOT timeline has an end. The managed infrastructure timeline does not — unless you choose to bring it in-house.
Start with a conversation about your situation. No commitment required.
Talk to Us →