Micro Global Capability Center (GCC) Playbook
A micro global capability center is a small, owned engineering team, typically five to fifteen engineers, that a company stands up in a location like India to do ongoing work as its own people rather than as a vendor's. It is the fastest-growing corner of the global capability center world, and almost everything written about GCCs assumes two hundred seats and a multi-year program, which is exactly why mid-market companies think this is not for them. It is. This playbook covers what a micro GCC actually is, what you stand up first, the economics by seat count, and the honest line where staff augmentation is the better call.
I spend my days talking to mid-market buyers about exactly this, so I will write it the way those conversations actually go: what convinces a real decision-maker, including the part where the honest answer is not a center at all. The long form matters here, because GCC gets confused with other things; throughout this piece it means global capability center, nothing else.
What counts as a micro global capability center?
A micro global capability center is a small owned team, on the order of five to fifteen engineers, that does continuing work for a company as its own staff in an offshore or nearshore location. The two words that separate it from everything nearby are owned and ongoing. Owned means the team is yours: your knowledge, your roadmap, your people, even if a partner helps you run it. Ongoing means the work is continuing capability, not a project with an end date. Strip either one away and you are describing something else, a vendor engagement or a temporary team, that deserves a different structure.
Size is the least interesting part of the definition, which is why leading with headcount misleads people. What makes a center a center is that a group is large enough to hold a domain, cover for each other, and accumulate institutional knowledge that stays with you. That is usually true from around five engineers and clearly true by fifteen. The reason the micro label matters is that it breaks the assumption baked into most GCC writing, that you need hundreds of seats to justify the model, which quietly excludes the companies this model now serves best.
Why the smallest segment is growing fastest
The smallest segment is growing fastest because the model finally fits mid-market economics, and the numbers bear it out. India hosts 583 mid-market GCCs per the Zinnov-Nasscom GCC Landscape FY2026 report, and mid-sized GCCs are growing at roughly 6.2% CAGR, outpacing the broader market's roughly 4.5% growth per Inductus GCC data. That is not a rounding difference; it is the smaller end of the market pulling ahead of the whole.
The reason is straightforward once you stop assuming GCCs are only for giants. The operating knowledge for running an owned offshore team, which used to be a large-enterprise capability, is now available to mid-market companies through partners and proven models, so the setup cost and risk that once demanded hundreds of seats to justify have come down. A company that could never contemplate a two-hundred-person center can absolutely contemplate a ten-person one, and increasingly does, because the same benefits, owned talent, retained knowledge, cost structure, now arrive at a size it can actually staff and manage.
The five-person start: what you stand up first
The first version of a micro global capability center is smaller and simpler than people fear, and getting the first five right matters more than any later decision. You are not standing up a department; you are standing up a team that can own a slice of real work end to end. That means picking one domain the team will genuinely own, not scattering five people across five unrelated tasks, and staffing it with enough range to cover for each other. A five-person team that owns one domain well is worth far more than five individuals renting out hours on five different things.
Governance at this size is light but real. You need clear ownership of what the team is responsible for, a simple cadence for how work flows and gets reviewed, and the framing, from day one, that this is one team, not a pool of vendors. That one-team framing is the whole game, because it is what turns five people in another country into your engineers rather than someone you outsource to. The centers that thrive treat the first five as founders of a small real team; the ones that struggle treat them as a cheaper way to get tasks done, and never get the ownership that makes a center worth having.
The economics at 5, 10, and 15 seats
The economics of a micro global capability center are best understood as a shape rather than a single number, because the actual figures depend on location, seniority, and how you run it. At five seats, your cost is dominated by the team itself plus a thin layer of the fixed overhead any owned team carries, entity, workspace, and operations, which is why the smallest centers lean on a partner to keep that overhead from swamping the value. At ten, the same fixed overhead spreads across more people, so the per-seat economics improve and the center starts to feel efficient rather than marginal. At fifteen, you have a genuinely self-justifying unit that can own multiple domains while the fixed costs sit as a small share of the whole.
The through-line is that fixed overhead is the enemy of the smallest centers and the friend of slightly larger ones, which is why the model rewards a clear growth path from five toward fifteen. I am deliberately not quoting per-seat figures here, because honest numbers depend on your specifics and stale numbers do more harm than good; our GCC cost in Ahmedabad guide is where the actual cost structure lives. The point for planning is the curve, not a quote: micro centers get more efficient as they grow toward the middle of the five-to-fifteen band, and the plan should assume that trajectory rather than freeze at five.
Micro GCC versus staff augmentation: the honest threshold
Here is the line I hold in every one of these conversations, including when it costs us the bigger engagement: if your work is temporary, bounded, or uncertain, do not build a center, use staff augmentation. A center earns its setup only when the work is ongoing and central enough that owning the team and its knowledge pays back over years. When that is not true, an owned center is overhead you do not need, and flexible staffing is the honest, cheaper answer.
The threshold is duration and ownership, not headcount. If you will still want this capability in three years and you want the knowledge to compound inside your own team, a micro GCC is right even at five people. If you need capacity now and flexibility more than continuity, our hire developers staff-augmentation model fits better, and our comparison of GCC versus outsourcing walks through where each one wins. Telling a buyer to choose the smaller commitment when it fits them better is not a lost sale; it is the reason the next, bigger conversation happens at all.
The growth path: micro to mid without rebuilding
The best reason to start small is that you do not have to stay small, and a well-designed micro center grows into a mid-sized one without being re-founded. The mechanism that makes this clean is build-operate-transfer: a partner stands up and runs the center while you focus on the work, and ownership transfers to you on a schedule you control, so you get speed early and full ownership later without a disruptive rebuild in between. A micro center set up this way is a scaled-down real center, which means adding seats and domains is growth, not reconstruction.
The centers that cannot scale are the ones set up as a temporary-feeling arrangement that later has to be turned into a real one, which is a rebuild dressed up as growth. Starting with real ownership, light governance, and a model built for expansion avoids that trap. Our piece on what actually transfers in a build-operate-transfer exit covers the mechanics, and if you are thinking about geography as you grow, adding a second GCC city is the next decision after this one. The playbook is simple: start small, but start real.
Mistakes that kill small centers
Small centers usually fail for a short list of avoidable reasons, and naming them is cheaper than learning them. The first is treating the team as vendors instead of your own people, which starves it of the ownership that makes a center worth more than contractors. The second is scattering a tiny team across too many unrelated responsibilities, so no one owns anything well and the knowledge never compounds. The third is carrying heavy-center overhead onto a light-center headcount, which makes the economics look bad for reasons that have nothing to do with the team.
The fourth, and quietest, is setting the center up as a stopgap and then being surprised when it cannot grow. Every one of these is a design choice made at the start, which is the good news: a micro global capability center that is set up as a small, owned, real team with a growth path avoids all four. If you want to pressure-test whether a micro GCC or staff augmentation fits your situation, our global capability center team has this conversation honestly, and you can talk to us to get a straight answer, including when the answer is not to build one yet.
