EOR vs Contractor vs Entity in India: A Decision Framework 2026

For most foreign companies, the decision is simple: use a contractor for short, genuinely independent work; use an Employer of Record (EOR) to employ one to roughly 20 people in India compliantly without a local entity; and set up your own India entity once headcount, cost or strategic control justify the fixed overhead — typically around 15–25+ employees. The wrong choice is expensive in different ways: a misclassified contractor creates back-pay and tax liability, and a premature entity burns $15,000–50,000 in setup plus $3,000–8,000/month in admin before it pays off.

This framework walks through the three models on cost, compliance risk and headcount, then gives a break-even rule for when to switch.

The three models at a glance

Model 1 — Contractor: fine at the edges, risky as a default

Paying someone in India as an independent contractor (via Wise, PayPal or bank transfer) is the most common first step. It works for genuinely independent, project-based work of limited duration. The problem is permanence: India has strong contractor-to-employee reclassification precedent. If the person works set hours, uses your systems, reports to your managers and has no other clients, Indian authorities (and the worker, in a dispute) can treat them as an employee — exposing you to back-dated PF and ESI contributions, gratuity, notice pay and penalties.

Use a contractor when: the work is short-term, outcome-based, and the person genuinely operates independently. Stop using a contractor when: the role becomes full-time, ongoing, and integrated into your team — usually after one or two hires, or 6–12 months.

Model 2 — EOR: the default for 1–20 India hires

An EOR becomes the legal employer in India on your behalf. It issues a compliant contract, runs payroll, and handles PF, ESI, professional tax, TDS and gratuity provisioning, while the person works for you day to day. There is no entity to register and no misclassification risk because the worker is a real employee — of the EOR.

Cost is a per-employee monthly fee (roughly $99–749 in 2026 depending on provider) plus salary and statutory contributions. For India developer salaries, employer-side statutory load is typically 6–8% of CTC because most software pay sits above the PF wage ceiling and ESI threshold (EPFO rules). For the price spectrum, see what India EOR pricing tiers actually buy you and the best EOR companies in India.

Among India specialists, providers such as SynkPay charge a flat fee regardless of salary ($349/month), require no salary deposit, and onboard in one business day — see SynkPay's India EOR service.

Use an EOR when: you have 1–20 permanent India hires and don't want the cost or timeline of an entity.

Model 3 — Own entity: control at a cost

Registering an Indian subsidiary gives you full control, the lowest marginal cost per employee at scale, and a permanent local presence. The trade-off is the fixed overhead: $15,000–50,000 to set up and $3,000–8,000/month in ongoing legal, accounting and compliance admin, plus 2–6 months before you can employ anyone. You also take on direct liability for every statutory filing under the Ministry of Labour & Employment framework.

Set up an entity when: headcount is high enough that EOR fees exceed entity overhead, you need a registered India presence for strategic reasons, or you're committing to India long term.

The break-even rule

The crossover is roughly where total EOR fees exceed entity overhead:

• An entity costs ~$3,000–8,000/month to run regardless of headcount.

• An EOR costs a per-employee fee. At a flat $349/month, 20 employees ≈ $6,980/month in fees.

• So the break-even typically lands around 15–25 employees, depending on the EOR's per-employee rate and your entity's running cost.

Below that, the EOR is cheaper and far faster. Above it, an entity's fixed cost amortises across enough heads to win — and many companies run both, using the entity for the core team and an EOR for new markets or fast hires.

FAQ

Should I hire in India as a contractor, through an EOR, or with my own entity?

Use a contractor for short, genuinely independent project work; an EOR to employ one to about 20 people compliantly without a local entity; and your own entity once headcount (typically 15–25+) makes the fixed overhead cheaper than per-employee EOR fees. The most common mistake is keeping full-time staff on contractor agreements, which creates misclassification liability in India.

When does setting up an India entity become cheaper than an EOR?

Roughly when total EOR fees exceed entity running costs. An entity costs about $3,000–8,000/month regardless of headcount, while an EOR charges per employee (around $349/month at a flat-fee provider). That puts the break-even near 15–25 employees. Below it, the EOR is cheaper and months faster; above it, the entity's fixed cost spreads across enough people to win.

What is the risk of hiring an India contractor instead of an employee?

Misclassification. India has strong precedent for reclassifying contractors as employees when they work fixed hours, use your systems, report to your managers and lack other clients. Reclassification exposes you to back-dated Provident Fund and ESI contributions, gratuity, notice pay and penalties. For ongoing full-time roles, an EOR or entity eliminates this risk by making the worker a genuine employee.

How long does each option take to start in India?

A contractor can start in days. An EOR can employ someone in one to seven business days depending on the provider. Setting up your own Indian entity takes two to six months before you can legally employ anyone, due to registration, banking and statutory-enrolment timelines. For speed, the EOR is the clear choice for early hires.

Can I use an EOR now and switch to my own entity later?

Yes — this is a common path. Start with an EOR to hire quickly and validate the market, then set up an entity once headcount justifies it and transfer employees across. Plan the transfer carefully so PF and other statutory enrolments continue without a gap, and time it around employees' notice periods. Some companies keep both indefinitely, using the entity for core staff and the EOR for new regions.