The India Expansion Playbook for Startups in 2026: Contractors, EOR or Entity?

You just closed your Series A. The board wants India. Your VP of Engineering has shortlisted five candidates in Bangalore. And somewhere on a VC call last week, someone mentioned "GCC" and you nodded politely without being entirely sure what it means for a company your size.

There are three structural options for hiring in India: contractors, an Employer of Record (EOR), or your own Indian entity. A GCC (Global Capability Centre) is simply the industry term for an entity you own in India, whether it has 20 engineers or 200. The label doesn't change what it is legally. Each option is being pitched as the obvious choice, depending on who's selling it.

There is no single right model for India expansion. The right choice depends on how fast you're growing. What works when you're adding 5 engineers a year gets expensive and rigid when you're adding 30. The setup that feels like overkill at Series A is the one you'll wish you'd started a year earlier by Series C.

The India expansions that go well treat the hiring model as a progression. You start where the math fits your current growth rate, build the team, and move to the next structure when the triggers are clear.

Who this guide is for

• Series A and B founders deciding how to hire in India for the first time (or the second time)

• CTOs and People Ops leads who need to explain the EOR vs entity tradeoff to leadership

• Founders already on EOR who are wondering when to graduate to their own entity

For a detailed cost model across both paths, read EOR vs Entity Cost: What It Takes to Build a 30-Person Team in India. For a day-to-day account of what running a team through a global EOR looks like, read The Reality of Running an India Team Through a Global EOR. This guide focuses on the decision framework: which model, at which growth rate, and how to know when it's time to move.

📌 TL;DR

Three structures to compare: Contractor, EOR, and Entity (your own registered Indian company, i.e. what a GCC is regardless of size). The question is which one fits your current growth rate, and when you'll outgrow it.

• 1–10 hires/year, testing the waters: Contractors for project-based needs, or EOR for a core team. No setup cost, first hire live in 7–14 days.

• 10–25 hires/year with a 2–3 year India roadmap: Start on EOR, incubate your entity in parallel (the EOR-to-GCC path), graduate your team when the entity is ready.

• 50+ hires/year or India as a customer market: Set up your own entity directly, provided your ops team can handle the compliance load.

• Most teams that build a serious India presence move through all of these stages. EOR is where you start. Your own entity is where you end up.

The three structural options

There are three structures for hiring in India. Everything else, including the term "GCC", is a label on top of one of these.

1. Contractors

Contractors are individuals you directly pay on a contract. There’s no employment relationship, and there are no employee benefits (you’re typically covering just the fee + any tools/infra you provide). It’s the fastest way to start, but it’s limited: contractors can’t be managed like employees, and misclassification risk grows as the engagement deepens. This works for very small, project-based needs (often 1–3 people), not for building a core team.

2. Employer of Record (EOR)

An EOR is the legal employer in India; you direct the work. The EOR handles payroll, and other compliances. No entity required on your side. First hire can be live in 7–14 days. This is the standard starting point for Series A and B companies building their first India team.

3. Your own Indian entity (= GCC)

You register a Private Limited Company under the Ministry of Corporate Affairs. You are the legal employer. You own the compliance stack, the contracts, and the entity. A GCC is just the industry term for this structure when it serves a foreign parent company. Whether it has 15 engineers or 500, the legal structure is the same.

The decision that matters is when to move from one to the next, and whether to transition gradually through EOR first or set up your entity directly.

Which situation are you in right now?

One question drives this: how many hires are you planning to add per year in India? Not how many people you have today, but how fast you're growing. That growth rate tells you which structure fits now and when you'll need the next one.

Situation 1: You're adding a handful of hires and testing the waters

You're planning to add 5–15 people over the next year. India is promising but unproven for your company. You need your first hire live in weeks, not months. You don't have a local HR ops team, and you're not ready to commit $20K–$50K to register an entity for a bet that might not pan out.

For very early-stage or project-based needs (1–3 people, short-term engagements), contractors may be sufficient. But the moment you're building a core team (with onboarding, performance management, and retention goals), an EOR is the right structure.

With an EOR, there is no setup cost. First hire onboarded in 7–14 days and subsequently in 1-2 days. Compliance (PF, ESI, TDS, gratuity, state-level filings) sits with the provider, not your founding team. And if India doesn't work out, you scale down without spending two years dissolving a legal entity.

Use this phase to test what actually matters: candidate quality, onboarding speed, retention, how well your India team integrates with the rest of the org. If those check out, you have your India signal. The structure conversation comes after.

But not all EORs are the same. The standard compliance-and-payroll model works until an engineer's laptop doesn't arrive, their PF paperwork has an error, or they need a home loan letter from their employer. At that point, a compliance-only EOR has nothing left to offer. Read The Reality of Running an India Team Through a Global EOR to see what that looks like in practice.

Situation 2: You're growing steadily and want your own entity, but need a smooth transition

You're planning to add 10–25 hires per year over the next 2–3 years. India has moved from "let's try this" to "this is a core part of our org." At this point, there are real reasons you might already know you want your own entity: you need local billing/GST later, you want to build your own employer brand in India, you want direct control over ESOPs and IP/contracting, or your leadership team has built India entities before and knows the playbook. The catch is: jumping straight to a full entity setup right now can still be premature.

Registration takes 4–6 months. Setup costs run $20K–$50K. And the ongoing compliance overhead (more on that in Situation 3).

The better move is a EOR-to-GCC path. You begin hiring on EOR immediately. Your team starts growing with zero delay. In parallel, your entity incubation runs in the background: CA registration, resident director appointment, and statutory registrations are all being set up. When the entity is ready (typically in 6–9 months), your team migrates from EOR contracts to direct entity employment. Your team keeps getting paid, compliance stays clean, and hiring doesn't stop during the transition.

What the EOR-to-GCC path looks like in practice:

• Immediate EOR employment for new hires (zero delay while entity incubates)

• Managed co-working or dedicated office setup

• Entity registration, resident director appointment, and statutory registrations running in the background

• A clear graduation trigger (typically 6–9 months or a specific strategic milestone)

• Clean handoff from EOR contracts to direct entity employment, with no payroll gap

EOR-to-entity move is usually delayed due to the operational continuity. Employee contracts, payroll systems, compliance registrations, HR processes: all of it needs to transfer without a gap. On the EOR-to-GCC path, that transition gets planned from Month 1. Not scrambled together when headcount pressure forces your hand.

Who the EOR-to-GCC path is built for:

• Post-Series A/B founders planning to add 10–25 India hires per year over 2–3 years

• Engineering-led companies where India is a core function, not a cost play

• Teams that want to own their India presence but aren't ready to build the full ops stack today

• Companies that don't want to pause hiring while setting up an entity

Situation 3: You have the scale and commitment to set up your own entity directly

You're planning to add 50+ hires per year. India is already or is about to become a customer market for you. You need GST registration, local billing, and inter-company transfers. You want direct control over ESOP grants, IP assignment, and employer branding from Day 1. And critically, you have (or are ready to hire) a dedicated India ops lead who can manage the compliance stack.

Setting up an Indian entity (typically a Private Limited Company registered under the Ministry of Corporate Affairs) gives you full legal ownership, the ability to bill Indian clients, and direct control over HR and compliance.

You end up with the same thing as the EOR-to-GCC path: your own registered entity, your own GCC. You're just going there directly, skipping the EOR transition phase. This makes sense when you have the operational capacity to absorb a 4–6 month setup period before your first hire is live, and the commitment to own the compliance workload from Day 1.

The tradeoff is real. Registration takes 4–6 months, costs $20K–$50K upfront, and carries an ongoing annual overhead of $25,000–$40,000 for a 20–30 person team. For a full breakdown, see EOR vs Entity Cost: What It Takes to Build a 30-Person Team in India.

To make those numbers concrete: here is the actual scope of work from a real Indian entity we support (a US-headquartered tech company). Their ongoing finance and compliance operations cover two distinct workstreams.

Workstream 1: Accounting, finance, and payroll (with a fractional CFO)

• Accounts payable, accounts receivable, and general ledger (ongoing)

• Expense management and employee reimbursements (fortnightly)

• Month-end closing and financial reporting (monthly)

• FP&A, budgeting, and forecasting (as needed)

• Statutory audit coordination (annual)

• Board and management reporting (monthly)

• Treasury, banking, and cash management (ongoing)

Workstream 2: Annual audits, transfer pricing, and local tax filings

• Statutory audit, local tax audit, and transfer pricing audit (annual)

• Statutory certifications for each of the above (as needed)

💸 Transfer pricing: the hidden cost most founders miss

Under India's Income Tax Act (Section 92C), intercompany transactions between your Indian subsidiary and foreign parent must be priced at arm's length. In practice, your Indian entity must charge the parent a cost-plus markup. This could be typically around 15% or more of total operational India costs, depending on the nature of services and applicable CBDT Safe Harbour Rules. This is mandatory, not optional: non-compliance triggers transfer pricing audits, penalties, and potential double taxation. Most founders budget for salaries, office, and CA fees but miss that transfer pricing alone adds a significant layer on top of the entire India cost base. On EOR, this cost doesn't exist as the provider's fee structure already accounts for it.

This is not a one-person job. It takes a fractional CFO, a local CA firm, and an audit partner, each with their own timelines, portals, and documentation requirements. When your VP of Engineering or India Site Lead ends up owning any piece of this by default, you lose engineering hours to compliance admin. That's the real cost behind the overhead number.

For a detailed picture of entity operations after the first year, read EOR vs. Entity in India: What's the Right Choice for Expanding Your Tech Team?

What you get at this stage:

At high headcount, entity running costs are typically lower than cumulative EOR fees. The math flips, and it stays flipped as you grow.

However, with the Transfer Pricing, EOR cost is typically under 10% whereas with own entity it is around 25%.

A registered Indian entity also signals to candidates, clients, and partners that India is not an experiment for you. It's a second headquarters. Senior engineers in India notice whether there's a real local presence or just a third-party payroll arrangement. Your own entity changes how you show up in the talent market.

Contractor vs EOR vs own entity: the 2026 comparison

The progression: how successful India teams move through all stages

India expansion isn't a "pick one model" decision. It's a "what stage am I at" question. Most teams that build a serious India presence move through these stages as their hiring velocity picks up.

Stage 1: Contractors → EOR (adding 1–10 hires/year)

Start here. Contractors for project-based needs, EOR when you're building a core team. No setup cost, compliance handled, first hire live in days. Validate the India model (candidate quality, onboarding, retention) before committing to a permanent structure. This stage builds the operational foundation that makes the later stages work.

Stage 2: EOR-to-GCC path (adding 10–25 hires/year, over 18–36 months)

When your hiring rate crosses 10+ per year and you have a confirmed 2–3 year India roadmap, don't rush into setting up your own entity. Up to 50 hires per year, stay on EOR. A good EOR scales with you: compliance, HR, hardware, engagement, all handled. Your team keeps growing without the overhead of entity registration, CA coordination, or statutory filings.

Stage 3: Own entity / full GCC (adding 50+ hires/year)

At this growth rate, the EOR fee math has typically flipped. Running your own entity costs less than the cumulative EOR fee. India stops looking like a remote team and starts looking like a second HQ. You get cost efficiency, market recognition, and full operational control. Whether you arrived here through the EOR-to-GCC path or set up directly, the entity is yours. What changes is which problems you own.

When to move to the next stage:

• Contractors to EOR: When you're building a core team (not just project-based), need employment-grade compliance, or plan to retain hires long-term

• EOR to GCC path: Hiring rate consistently above 10/year, confirmed 18+ month India roadmap, India positioned as a strategic function (not just cost savings)

• to full entity: Entity incubation complete, compliance infrastructure ready, and the cost math has flipped or India is entering customer/GTM mode

Common mistakes at each stage

Setting up an entity too early

The most expensive India expansion mistake we see. $20K–$50K in legal and setup costs before a single hire is live. Four to six months of founder time going into MCA filings, bank accounts, and CA coordination instead of product and customers. And if India doesn't work out, dissolving an entity takes up to two years. Start on EOR, validate the India model, then move to entity when your growth rate justifies it.

Choosing a compliance-only EOR

Payroll and PF filings are the bare minimum. If your EOR can't source engineers, manage hardware delivery, or support an employee whose background check has stalled, you'll feel that gap within 60 days. The hidden cost of a compliance-only EOR is the coordination load that bounces back to your team. The right EOR grows with you from Stage 1 through entity graduation.

Skipping the graduation plan

Most EOR clients eventually want their own entity. The mistake is waiting until headcount pressure forces the transition instead of planning it from the start. A rushed EOR-to-entity move means contract disruption, payroll migration risk, and compliance gaps that take months to close. The EOR-to-GCC path exists to avoid exactly this. Transitions go smoother when the next stage is mapped early.

How TeemGenie supports the full journey

TeemGenie is built to take you from first hire to your own entity, with no handoff at any transition.

• EOR phase: Talent acquisition from a 10,000+ deep-tech candidate database, payroll and full statutory compliance, hardware procurement, HR support on Slack, employee engagement, home loan assistance

• EOR-to-GCC phase: Everything above, plus entity incubation (CA setup, resident director appointment, statutory registrations) and co-working or office management

• Entity phase: Clean employee contract transition, no payroll migration gap, no compliance disruption. Your team stays intact and fully operational

Wherever you are today, we can map the next step. Book a 30-minute call and we'll plan the right path for your growth rate and timeline.

FAQ

Can a US startup hire in India without setting up a local company?

Yes. Through an Employer of Record (EOR), a US company can hire full-time employees in India without registering an Indian entity. The EOR is the legal employer in India; the US startup directs the work. This is the most common starting point for Series A and B founders building their first India team. For more, read EOR vs. Entity in India: What's the Right Choice for Expanding Your Tech Team?.

What's the difference between a contractor and an EOR in India?

With a contractor, there is no employment relationship. You engage someone on a service agreement. With an EOR, the individual is a full-time employee (of the EOR entity), with all statutory benefits (PF, ESI, gratuity, etc.) and employment protections. Contractors work for short-term, project-based needs. EOR is for building a core team with retention and compliance in place. Contractors don’t provide group insurance but an EOR does as your contribution will be full-time.

When should a startup transition from EOR to its own entity in India?

When your hiring rate is consistently above 10–25 per year, when India becomes a customer market needing local billing or GST registration, or when you need direct control over equity grants, IP assignment, and intercompany transfers. The Starter GCC path lets you start that transition without pausing hiring. Your entity incubates while your team keeps growing on EOR.

What does it cost to set up an Indian entity?

$20,000–$50,000 upfront for MCA incorporation, labor license registrations, statutory setup, and a resident director appointment. Ongoing annual overhead for a 20–30 person team typically runs $25,000–$40,000, covering CA retainer, statutory audits, payroll management, and GST compliance. For a full side-by-side model, read EOR vs Entity Cost: What It Takes to Build a 30-Person Team in India.

How do India's new Labour Codes affect EOR hiring in 2026?

India's four new Labour Codes, effective November 2025, consolidated 29 legacy laws. The biggest change for EOR clients is the 50% wage rule: at least half of an employee's CTC must be classified as basic wages, which directly affects PF contributions and in-hand salary calculations. A compliant EOR should have already restructured payroll and CTC templates. If yours hasn't, ask them.