GCC and AI CoE: Build, Operate, Transfer
We build the centre, run it, and hand it over on a date in the contract.
India's GCCs are becoming the enterprise's AI command centre. Parents fund a veteran operator to stand up the team, platform, and governance and, in full BOT mode, to run the pod until a scheduled transfer puts people, platform, and playbooks on your side of the ledger.
A fully loaded production CoE is an expensive line on the parent’s books. The difference between a good BOT and a bad one is whether transfer is real: a date in the contract, standards that outlive our involvement, and a pod that ships production work during the operate phase, not after it. The full structure of the mandate is laid out on the Work with us page.
Smaller mandates are welcome too: a blueprint alone, or standards for a CoE you already run. The first proof is often a production agent or factory build already in flight; the CoE conversation follows the evidence.
Engagement shapes
- 01CoE blueprint: operating model, skills matrix, platform, and governance in a fixed design window.
- 02Standards for agents, data, and evaluation that the parent can reuse globally.
- 03Full Build-Operate-Transfer: we hire and run a pod of 8 to 30 people, ship production workflows during the operate phase, then transfer on a contracted date.
- 04Fractional technical leadership after transfer: design authority as a thin overlay.