I think about that GCC often, because the reasons it never crossed into commercial identity were not reasons of capability. They were reasons of decision. Nobody ever explicitly decided not to build a business inside it. The default simply won, year after year, because nobody made the deliberate counter-decision required to change course.

The Default That Wins by Doing Nothing

A GCC exists to deliver a defined scope of work to its parent organisation, reliably, at a predictable cost. That mandate is clear, measurable, and safe. Building a commercial offering on top of that mandate is none of those things — at least not initially. It requires identifying a market, finding a client willing to pay for work the GCC hasn’t been resourced or governed to sell, and accepting a period where the metrics look worse before they look better.

Faced with that asymmetry, the rational short-term choice for almost any GCC leader is to keep doing what the mandate already rewards. The capability accumulates. The opportunity sits there, visible to anyone who looks closely, monetised by nobody, because the cost of looking closely and acting on it falls entirely on the person who would have to make the case upward, defend the resourcing shift, and accept the early-stage messiness that any new revenue line requires.

This is not a story about lack of ambition. The people inside these GCCs are often more capable than the commercial teams at the parent firm who would, in theory, be the ones to monetise what the GCC builds. The constraint is structural, not personal.

Nobody decides not to build a business inside a GCC. The default just wins, year after year, because changing it requires someone to actively choose against the safest available option.

What the Decision Actually Requires

I want to be precise about what “the decision” means here, because it is not a single dramatic moment. It is a sequence of smaller decisions that compound, each one requiring someone with enough standing to absorb the early cost.

First, the decision to name the capability as a product, not a function. A research team becomes a research practice the moment someone gives it a name, a value proposition, and a person accountable for selling it — not just delivering it. That sounds cosmetic. It is not. Naming something changes how it is resourced, reviewed, and protected.

Second, the decision to find an anchor client willing to pay — even a small, internal, low-stakes first client — before the infrastructure exists to serve a large one. This is the step most GCC leaders skip, because waiting until the offering is “ready” feels safer than testing it against a real, paying expectation early.

Third, the decision to protect the new initiative’s early metrics from the parent organisation’s existing performance management system. A nascent revenue line evaluated against the same cost-efficiency metrics as a mature delivery function will look like a failure for at least a year, possibly two. Without explicit protection from a sponsor with enough authority to grant it, the initiative gets quietly deprioritised before it has a chance to prove itself.

What Crossing the Line Actually Changes

I’ve now watched this decision get made — deliberately, not by accident — in a handful of organisations. The change that follows is not incremental. It is categorical.

A GCC that crosses into commercial identity stops competing for budget allocation and starts competing for market share. That shift changes how leadership thinks about investment in the function — not “how do we keep this cost contained” but “how do we grow this faster than the market opportunity is closing.” It changes how the best people inside the organisation think about their careers — staying becomes a bet on upside, not a holding pattern. And it changes how the parent organisation values the GCC itself, from a line item to a strategic asset.

None of that requires new capability. The capability was already there. It requires the decision — and someone willing to be the first to make it, knowing the first eighteen months will look worse on paper than doing nothing would have.

I didn’t make that decision in time, in the GCC I’m describing. Someone else eventually did, in a different organisation, with a similar starting capability — and built a business that the original GCC could have built two years earlier with less effort, because the capability was already there waiting.

The lesson I took from it wasn’t about strategy. It was about timing, and about the cost of the default that wins by doing nothing. That lesson is the foundation of how I think about every GCC conversation I have now.

An anchor client is not your biggest prospect. It is the smallest one whose expectations are real enough to force the offering into shape — early, while the cost of being wrong is still low.

Choose the first client for the discipline it imposes, not the revenue it brings.

The first mandate does three things at once: it names the offering, it sets the standard, and it gives the rest of the organisation a reason to take the initiative seriously. Skip it, and you are building in a vacuum that no amount of internal conviction can fill.

Sponsor air cover is the most valuable and least durable asset a new initiative has. It buys time against the parent organisation's metrics — right up until the sponsor is promoted, reorganised, or gone.

The practices that survive the handover are the ones that used the protected window to manufacture their own evidence: a paying client, a defensible margin, a story the next sponsor can adopt without having to believe in it on faith.

Adoption is not downstream of the build; it is part of it. Incentives, air cover, talent design, and the path of least resistance for the user all decide whether a genuinely good tool ever gets picked up.

A capability nobody adopts is indistinguishable, on the balance sheet, from one that never existed.

Treat adoption as a first-class design constraint and the build changes shape. Treat it as someone else's problem and the best work quietly goes unused.