A large GCC can absorb some ambiguity. If a 2,000-person centre has an unclear decision-rights structure in one department, the other departments carry the organization while someone eventually sorts it out.
A nano or micro team doesn't have that luxury. When your entire India presence is 6 people on an EOR arrangement, or 15 people in a freshly registered entity, there's no redundancy to absorb an unclear mandate. It doesn't get diluted anywhere. It becomes the whole team's daily experience, immediately, from the first week.
That's exactly why the companies getting the most out of a small India team treat one decision as inseparable from the hiring plan itself: before the first person joins, decide exactly what that person, or the small leadership layer above them, can actually decide without checking in on every call.
Why size doesn't reduce the stakes, it raises them.
It's tempting to assume a 6-person EOR team or a 15-person micro GCC needs less structure than a large captive centre, simply because there's less to organize. The opposite is closer to true. A large centre has layers: if the top of the structure is a little unclear, there's usually someone two levels down who can still make the call the business needs made that day.
A nano team has no layers. If the senior hire who's meant to be running things has to route every real decision back to headquarters, there's no one else in the room to absorb that latency. It shows up in every decision, not just the important ones. The smaller the team, the more precisely the mandate needs to be defined, not less, which is the part that gets missed most often, because it feels backwards.
What good mandate design looks like at this scale.
The companies doing this well tend to settle three specific things before anyone is hired, not after. First, they write down what the senior person on the ground can decide, hiring within a defined budget, vendor selection below a certain threshold, day-to-day technical or process calls, and what genuinely needs to go back to headquarters. Not a general statement of trust. A short, specific list, because a 6-person team doesn't need an elaborate governance document, it needs clarity.
Second, they decide this before choosing between EOR and a micro-GCC entity, not after, because the two structures change what "local authority" even means in practice. An EOR-employed team lead is directing work but isn't the legal employer of record, so decisions about compensation changes or role structure may need to route through the EOR provider as well as headquarters. A micro-GCC entity puts that authority genuinely local, if the mandate is written to reflect it. Skipping this step means discovering the gap the first time it actually matters, usually at an inconvenient moment.
Third, they treat the first hire as a leadership decision, not a staffing one, even at this scale. The first person into a 6-person team sets the operating norms for everyone who follows: how decisions get made, how much initiative is expected, whether "I'll check and get back to you" becomes the default response to anything unfamiliar.
What this looks like in practice.
Picture two companies, each building a 12-person data-engineering team in India, one through an EOR, one through a freshly registered micro-GCC entity, both hiring from the same talent pool. Company A hires its senior lead first and spends the next two months figuring out, decision by decision, what that person can actually approve without escalating. A tooling choice gets picked and then reversed three weeks later on a call the lead wasn't part of. By month four, the lead has learned that the safest move is to ask before doing almost anything, and the team's pace has slowed to match.
Company B writes the decision map before the search even opens: a budget threshold the lead owns outright, technical architecture decisions that stay local, and a short, explicit list of the few things that need sign-off. The lead walks in already knowing the shape of the role. Four months in, that team has shipped meaningfully more, not because the people are different, but because nobody on it is spending energy managing expectations in two directions instead of doing the work.
A team that spends its first three months routing everything upward doesn't become confident once it grows. It becomes a larger team with the same habit.
The part that surprises companies most is how durable the early pattern turns out to be. Later hires learn the norm from the earlier ones. The mandate decision made in week one is effectively setting the operating culture for however large the team eventually becomes.
Which is why the growth path itself needs designing, not improvising.
Getting the mandate right at 6 or 12 people only pays off if the team's growth from there follows a plan rather than a series of reactive decisions. The companies that handle this well treat the whole journey, EOR, to micro GCC, to whatever comes next, as one continuous plan with three stages, not three separate decisions made independently.
<strong>Phase one validates.</strong> Hire a small team, typically 2 to 10 people, through an EOR. Near-zero upfront capital, operational in weeks, no entity to unwind if the answer turns out to be no. The goal isn't cost savings, it's finding out, with real people doing real work, whether the capability belongs in India at all.
<strong>Phase two commits at a sustainable scale.</strong> Once the answer is yes, move to a nano or micro GCC, typically 10 to 25 FTEs, or a build-operate-transfer structure if you want a partner to carry the operational load a little longer. Entity registration can often run in parallel with continued EOR hiring, so the team doesn't sit idle waiting for paperwork. This is where retention and depth become the design priority, not just speed.
<strong>Phase three scales on your own terms.</strong> If the growth goal justifies it, the centre grows into a fuller captive operation, with the leadership mandate, hiring plan, and scope that a genuinely strategic capability deserves. Plenty of companies stop happily at phase two, running a lean, senior-heavy centre indefinitely. The point of phasing isn't to push everyone toward the biggest possible structure, it's to make sure the structure at every stage matches what's actually been proven true.
The signal that it's time to move between phases is rarely a revenue number. It's usually one of a few concrete things: the team has grown past the point where per-head EOR fees cost more than running your own lean entity; you're losing people you wanted to keep because an EOR arrangement can't offer the equity or career path a real local entity can; or the work has shifted from a contained pilot into something core enough that direct control over how it's built and led actually matters.
A few common questions.
Is the mandate different for an EOR-employed team versus a micro-GCC entity? The two structures change who else sits inside certain decisions, which means the mandate can't be copied from one to the other without real thought about your specific setup. This is one of the places a generic template does more harm than good.
What's the earliest sign a mandate wasn't defined clearly enough? A senior hire who quietly stops proposing things after their first decision gets reversed. It's visible within the first month or two to anyone who knows what to look for, usually well before it shows up in any report you'd actually see.
What's the biggest risk in the phased approach? Treating each phase as a separate decision instead of one plan. Exactly where the transition triggers should sit, headcount, retention, scope, depends on your specific growth trajectory and risk tolerance, which isn't something a general answer can responsibly cover.
This is the specific layer Espresso Shot Consulting works through with companies building a nano or micro team in India, designing the mandate and the phased growth path together, so the first hire walks into clarity, and the team scales on a plan instead of a scramble.
