When a client asks you to build a GCC, they are not leaving. They are graduating.
The question is whether the partner graduates with the work — or is replaced by it. Four parts on the reframe, the asset, the trap, and what the relationship becomes after the handover.
The GCC is the client compressing execution. Everything that does not compress is the services company's ground.
Graduation. Asset. Trap. Maturity.
Each part opens on a recognisable scene from the executive's chair — names the misread, gives the distinction, makes the structural argument, closes on the turn. Diagnosis throughout: the structure is indicted, never the seat.
A long-standing client asks for help exploring a GCC. The stomach drops. The defensive reflex — resist, or quietly monetise the exit — is the response of someone who has misread the request. The work has graduated. The corporation builds a captive when a body of work has become too strategic to leave fully outside.
Two proposals on the table. One prices the GCC as a project — entity, hiring, transition, done. The other prices it as a capability transfer. The real asset moving across is operating knowledge: how the work is actually done. Priced as logistics, it should be priced as inheritance. "Transfer" is the most underpriced word in the contract.
The transfer completes. The client thanks the partner and reduces the contract. The cruelty: competence at the task is what springs the trap. The discipline is choosing what to surrender — give up the compressible work deliberately, and hold the ambiguous, cross-domain, surge, and net-new work the captive will never internalise. The series turns here.
Five years on. The GCC is the client's crown jewel — and the services company is still there, doing something it never did before the captive existed. The relationship did not survive the GCC by resisting it; it matured because of it. There is always work the GCC has not internalised yet. As the captive matures, the business generates the next frontier.
The technology services executive who has just been asked to help a long-standing client build a GCC — and who must decide what that request means for the relationship, the revenue, and the work.
Parts publish as they are ready.
Each part is published directly on this site as it is completed. No gate, no email required. The argument unfolds one move at a time.
25+ years inside technology services engagements — including the GCC conversations this series describes. Frontier is drawn from the same place the work was.
Full storyThe executive who can tell the difference between losing an account and graduating with the work never had to choose between the client and the revenue.