The Builder’s Brief: designing a GCC team from a blank charter
A centre head on the first thirty roles — what they built in-house, what they bought in, and the sequence that made it hold.
Draft. Figures marked like this are illustrative and pending verification against Recruise placement data & Sachith sign-off before publication.
Key takeaways
- Starting from a blank charter, the guest built for ownership before headcount — the first hires had to be able to design the work, not just do it.
- Build, buy, and borrow were decided role by role across the first thirty seats, not set as a single policy.
- The sequence held because the anchor leaders came first and everything else hung off them — order was the real design.
Episode notes: the first thirty roles, in order.
In this Builder’s Brief, a centre head walks us through standing up a GCC team from nothing — no template, no inherited org, a charter and a hiring number. The through-line of the conversation is that the number was the least useful thing they were given. What mattered was sequence: which handful of anchor leaders had to exist first, because every subsequent hire would be recruited, managed, and calibrated by them. Get those wrong and thirty good hires underneath them still don’t add up to a centre.
The guest is candid that the early seats were deliberately senior for the size of the team — more ownership than the day-one work strictly required. That was the point. A blank charter rewards people who can shape the work; hiring only doers into it just recreates a backbone shop under a captive’s banner. They optimised the first hires for judgment and let throughput follow once the shape was set.
“The best answer we heard to ‘how did you build thirty roles?’ was ‘I built the first four, and they built the rest.’ Sequence was the design.”
Sachith Rai · MD & Founder, Recruise
What they built, bought, and borrowed — and why.
The guest resisted a single sourcing policy. Core capability — the judgment the charter was built to own — was built in-house and hired permanent, because renting it would have hollowed out the reason the centre existed. Scarce, one-off expertise needed to get moving was borrowed through partners and contract specialists, deliberately temporary. And a few mature, well-defined functions were bought as ready-made teams where speed mattered more than owning the muscle. The mix was decided seat by seat against what each role was for.
We close the episode on the part most build plans skip: what they got wrong and corrected. The guest is honest about an early role hired too junior for the ambiguity it faced, and about how re-reading the plan each quarter — rather than executing the annual version — let them catch the drift while it was still cheap to fix. Full show notes, chapter markers, and the role-by-role sourcing map are linked with the episode.
One pattern worth knowing, every week.
The Signal is our weekly read on the senior GCC talent market — one chart, one pattern, no noise. Written from live placement data.
More from Recruise Insights.
The capability-deepening playbook most GCCs ignore
There’s a structural decision every GCC past a certain size has to make. Most defer it. The ones who don’t are pulling ahead.
Choosing the operating model before you choose the headcount
Whether the centre runs as a captive, a hub, or a shared-service backbone decides the roles you can even hire. Most plans skip the choice.
Span of control is where GCC org design quietly breaks
Too flat and managers drown; too deep and the centre calcifies. The right span is a hiring decision made a year in advance.