Hiring Employees in India: A Founder's Guide to Entity Setup, EOR, and Contractor Pathways

By Sagar Chainani, Founder, Versatile Club

Q1. Why Is Hiring Employees in India the Highest-Leverage Move for a 2026 Founder?

A US founder messaged me on WhatsApp at 11pm her time, three days before her first India payroll cycle. She had just closed a $7M Series A. She had three Bengaluru engineers signed. And she had no idea why her global EOR's "India PF challan" had not landed in her inbox. That call is not unusual. It is the most common shape of the first India hire in 2026.

The 2026 trigger moment

I see the same pattern across the founders I work with. The round closes. The board approves headcount. US engineering salaries are running $180,000 all-in for a senior IC, and a comparable Bengaluru hire lands closer to $58,000 all-in. India holds roughly 5.95 million tech professionals and the second-largest English-speaking technical workforce in the world. The math is obvious. The execution window is 30 to 60 days. That is the trigger.

Why entity setup is the wrong first move

Setting up an Indian Private Limited subsidiary takes 12 to 18 months of paperwork through MCA (Ministry of Corporate Affairs) SPICe+ filings, FEMA (Foreign Exchange Management Act) FC-GPR reporting, and post-incorporation compliance, with $50,000+ in upfront cost before the first hire. ⏰ For a Series A founder, that timeline kills the round's velocity. So the real choice collapses to three pathways: hire as a contractor, hire through an Employer of Record (EOR), or wait for the entity. Two of the three move in days, not quarters.

What this article gives you on Monday morning

I have spent six years placing engineers, designers, and ops professionals across Bengaluru, Hyderabad, and Pune through Contract-to-Hire (C2H) and now EOR. 💸 What I see most often is the "Burned Founder" pattern: a 3 to 5 percent FX markup hidden inside the global EOR invoice, a partner-aggregator entity the founder did not realize was the actual employer, and a backdated PF (Provident Fund) liability discovered at month four. This guide is the playbook I wish those founders had on day one.

Q2. Entity, EOR, or Contractor: Which Pathway Fits Your Headcount, Capital, and Timeline?

There are exactly three legal pathways to hire someone in India: a wholly-owned Indian entity, an Employer of Record, or an independent contractor. Anything labeled "PEO" by a US vendor is, in my experience, marketing language. US-style co-employment PEO does not legally exist under Indian labour law. You either employ someone, or you do not.

What each pathway actually is

Entity (Pvt Ltd, LLP, or Branch Office)

You incorporate an Indian company under the Companies Act 2013 via the MCA SPICe+ form, file FC-GPR with the RBI under FEMA for inbound capital, and obtain PF (Provident Fund), ESIC (Employees' State Insurance Corporation), Shops & Establishments (S&E), and GST registrations. Setup runs 12 to 18 months and $50,000 plus annual compliance overhead. You are the legal employer. You own everything, including liability. rippling

Employer of Record (EOR)

A licensed Indian entity employs the person on your behalf. ✅ At Versatile Club, we operate through our own registered Indian entity, with PF, ESIC, and S&E licenses across all 28 states and 8 union territories. The employee works for you. The entity holds the contract, runs payroll, files statutory returns, and absorbs PE-risk shielding for the foreign parent. Onboarding moves in 5 business days under our contractual SLA.

Independent Contractor

The individual invoices you as a service provider, manages their own taxes, and receives no statutory benefits. Cheap on paper. Legally fragile if the relationship looks like employment under India's tests of control, exclusivity, and integration.

The contrarian piece: PEO is a myth in India

⚠️ Any vendor pitching you an "India PEO" is selling you an EOR with US branding. The Code on Wages 2019 and the Industrial Relations Code 2020 recognize a single legal employer per worker. There is no co-employment register. So when you read "PEO India" on a global generalist's site, translate it as "EOR with shallower depth." remote

The decision rule (keep it boring)

Headcount band	Default pathway	Why
1 to 10 hires	EOR	Speed, no capex, PE risk shielded
10 to 30 hires	EOR with active GCC roadmap	Unit economics still favor EOR; start entity prep
30+ hires or India leadership in place	Owned entity	Break-even on entity overhead, IP control

The 6-axis pathway comparator

Axis	Owned Entity	EOR	Contractor
Setup time	12 to 18 months	5 business days (Versatile Club SLA)	1 to 3 days
Capex	$50,000+	$0 (first month free at Versatile Club)	$0
Compliance owner	You	EOR entity	The contractor
IP control	Strongest, direct assignment	Strong, contractually assigned to client	Weakest, requires watertight MSA
PE risk for foreign parent	Highest, parent owns subsidiary	Shielded if no commercial authority	High if contractor is integrated
Ideal headcount band	30+	1 to 30	1 to 5, project-bounded

In our placements, the unit economics flip toward an owned entity at roughly 25 heads, and only when there is real India leadership on the ground to run governance. Below that, an EOR is the cheaper, faster, lower-risk move.

Q3. What Does It Actually Cost to Hire Employees in India in 2026 (Total-Cost Calculator)?

The honest number for a senior software engineer in Bengaluru is about $58,000 all-in per year through an India-native EOR, against roughly $220,000 in San Francisco for the same role. That is a $162,000 saving per seat. The hidden complexity sits in how you arrive at the $58,000.

The components that make up the all-in cost

💰 Every India hire breaks into the same buckets. Most founders only see Base. CFOs see all of it.

• Base salary, the annual cash figure on the offer letter
• Provident Fund (PF), 12% employer contribution on Basic + DA under the EPFO scheme husys
• Employees' State Insurance (ESI), 3.25% employer and 0.75% employee, applicable for monthly wages up to ₹21,000 safeguardglobal
• Gratuity, accrued at 4.81% of Basic + DA from month one under the Payment of Gratuity Act, 1972 paybooks
• Bonus, statutory under the Payment of Bonus Act, 1965 for eligible wage bands
• Professional Tax (PT) and Labour Welfare Fund (LWF), state-specific, capped at ₹2,500 per year per state
• Health insurance, group cover for employees outside the ESI threshold
• EOR fee, charged per employee per month

Worked example: $80,000 senior engineer in Bengaluru

Line item	Versatile Club	Global generalist (typical)
Base salary (annualized)	$80,000	$80,000
Statutory load (PF, ESI where applicable, gratuity, PT)	~13% of Basic + DA husys	~13% of Basic + DA husys
EOR fee per employee per month	$149	$599
Setup fee	$0	$299 to $500
Exit fee	$0	1 month notice fee
First month free	Yes	No
FX markup on USD-to-INR	0%, USD invoiced direct from our Indian entity	3% to 5% reported on global platforms
Annual EOR fee delta	$1,788	$7,188
Hidden FX delta on $80k	$0	~$2,400 to $4,000

What the global generalist invoice quietly does

A global EOR routes payroll through a local partner entity in India and bills you in USD that has been converted from INR with a markup. ❌ The 3 to 5 percent FX line is not labeled "FX markup." It is buried inside an exchange rate that does not match the RBI mid-market reference rate. ✅ Our model is structurally different: we invoice USD directly from our owned Indian entity, with the mid-market rate published on every invoice, and the C2H placement fee charged only after the hire completes day 90.

The reason this matters on Monday morning: a CFO running a 10-person India team on a global generalist is overspending roughly $50,000 per year on EOR fees alone, before counting FX. That is a full additional engineer.

Q4. Which Statutory Contributions and Multi-State Filings Must You Get Right from Day One?

India statutory compliance is not abstract. It is a monthly cycle of challans, returns, and filings under specific acts, with specific deadlines, in specific states. Get it wrong, and the liability accrues quietly until an audit or diligence cycle surfaces it. Get it right, and it becomes invisible infrastructure.

The central layer: PF, ESI, gratuity, bonus, TDS

Provident Fund (PF) under the EPFO

Every employer with 20 or more employees registers under the Employees' Provident Funds and Miscellaneous Provisions Act, 1952. The employer contributes 12% of Basic + DA, the employee contributes 12%, and contributions are remitted by the 15th of the following month via electronic challan-cum-return (ECR) on the EPFO portal. We hold our own PF establishment code, so challans clear under our PAN, not a partner's. husys

Employees' State Insurance (ESI) under ESIC

For employees with monthly wages up to ₹21,000, the employer contributes 3.25% and the employee contributes 0.75%, deposited by the 15th of the following month under the ESI Act, 1948. Above the threshold, group health insurance replaces ESI as a benefit. safeguardglobal

Gratuity, bonus, and TDS

Gratuity accrues at 4.81% of Basic + DA from month one under the Payment of Gratuity Act, 1972, payable on exit after 5 years of continuous service. The Payment of Bonus Act, 1965 mandates 8.33% to 20% statutory bonus for eligible wage bands. TDS on salaries is deducted under Section 192 of the Income-tax Act and deposited by the 7th of the following month, with quarterly returns and annual Form 16 issued by 31 May. paybooks

The 2026 Code on Wages anchor

⚠️ Once the Code on Wages is fully notified, Basic + DA must be at least 50% of total CTC. This raises PF, gratuity, and leave-encashment outflows for any employer running a low-Basic structure today. We re-modeled all our offer letters for the 50% rule before EOR launch.

The state layer: S&E, PT, and LWF

S&E (Shops and Establishments) registration is per state, not per company. If you have one engineer in Bengaluru and one in Pune, you need two registrations. Professional Tax slabs and Labour Welfare Fund cycles are also state-specific. Most global generalists handle the top 4 to 6 metros only. We run payroll across all 28 states and 8 UTs.

State	S&E filing	Professional Tax	LWF	Common founder trip-up
Maharashtra	Annual	Monthly, dual PTRC + PTEC registration	Half-yearly	Missing PTEC enrollment for the company itself, not just employees
Karnataka	Annual renewal, enrollment within 30 days of joining	Monthly	Half-yearly	Late S&E enrollment past the 30-day window
Tamil Nadu	Half-yearly returns	Biannual (June and December)	Annual	Missing the June and December PT cycle
Telangana	Annual	Monthly remittance	Half-yearly	PTRC enrollment delays
Delhi	Strict S&E inspection regime	No PT	Half-yearly	Assuming "no PT" means "no state filings"
West Bengal	Annual	Monthly slabs, frequent rule changes	Half-yearly	Missing rule-change updates

What this looks like inside a live payroll cycle

✅ Each month, a clean India payroll cycle produces five artifacts: a payroll summary with gross, deductions, and net per employee; PF and ESI challan confirmations; TDS deposit receipts; a PT and LWF filing log per state; and a compliance status report flagging upcoming deadlines. If your current vendor cannot produce all five, you have a paper-trail gap that will surface at the next diligence cycle.

The Maharashtra dual-registration trap

The single most common founder mistake I see: a US company hires its first Pune engineer through a global EOR and registers for PTRC (Professional Tax Registration Certificate, employee-side). Maharashtra also requires PTEC (Professional Tax Enrollment Certificate, company-side) under the Maharashtra State Tax on Professions, Trades, Callings and Employments Act, 1975. Miss PTEC, and the penalty compounds monthly. Across the 12+ states we run payroll in, this is the trip-up I flag most often on a first diligence call.

Q5. What Changes in 2026: Code on Wages, DPDP Act, and Income Tax Act 2025 Forms?

A Series B People Ops VP forwarded me her existing offer letter template last month and asked one question: "Will this still work in 2026?" The Basic salary line read 30% of CTC. The data-protection clause was a one-line GDPR reference. The TDS section pointed to Form 24Q. Three changes, all wrong for 2026. This section is the re-modeling I sent her back.

The Code on Wages 50% rule and the take-home shock

⚠️ Once the Code on Wages 2019 is fully notified through 2026, Basic + DA must be at least 50% of total wages, replacing the legacy "Basic at 30 to 40%" structure that most India offer letters still use. PF (Provident Fund) is calculated on Basic + DA. So the moment Basic rises, the 12% PF outflow rises with it. Gratuity accrual at 4.81% of Basic + DA also rises.

Before-and-after offer-letter worksheet

Line item	Legacy structure (Basic 30%)	2026 structure (Basic 50%)
Annual CTC	₹20,00,000	₹20,00,000
Basic + DA	₹6,00,000	₹10,00,000
Employer PF (12% of Basic + DA) rippling	₹72,000	₹1,20,000
Gratuity accrual (4.81% of Basic + DA)	₹28,860	₹48,100
Net take-home impact	Higher cash	Lower cash, higher PF + gratuity

The Monday morning action: re-model your offer template to a 50% Basic anchor and warn the candidate that headline take-home will drop slightly while long-term retirement and gratuity balances rise. We re-modeled all our offer letters before our 2026 EOR launch. remote

DPDP Act 2023 and the offer-letter clauses you cannot skip

The Digital Personal Data Protection Act 2023, with Rules notified in 2025, governs how you collect, store, and transfer Indian employee data. ❌ A US HRIS pushing employee PII into a Salesforce instance in Virginia is not automatically compliant. The offer letter and employment contract must carry four specific clauses. husys

DPDP offer-letter clause checklist

• A clear notice describing what personal data you collect and the purpose of processing husys
• An explicit consent mechanism, with the right to withdraw consent
• A cross-border transfer clause naming the jurisdictions data flows to (US, UK, EU)
• The name and contact of a Data Protection Officer or grievance officer for the employee

We bundle these four clauses into the standard contract for every EOR hire so the founder is not redrafting paperwork mid-cycle. remote

Income Tax Act 2025 and the new TDS forms

The Income-tax Act 2025 replaces the 1961 Act effective 1 April 2026 and introduces revised return and certificate forms. ✅ The forms that matter for payroll: safeguardglobal

• Form 130, replacing salary TDS deposit linkages under earlier Section 192 procedures
• Form 131, the revised quarterly TDS return for salaried employees
• Form 138, replacing the legacy Form 24Q quarterly statement

The action item: confirm with your payroll vendor that Form 138 quarterly filings are live in their stack for the April to June 2026 quarter, and that Form 16 issuance for FY 2025-26 maps to the new schedules. If the answer is "we are still testing," that is the answer. safeguardglobal

Q6. How Do You Pass the Misclassification Test Before Calling Anyone a "Contractor"?

A US founder once told me she had "12 contractors in India" on a Zoom call. Twenty minutes in, I had counted eight she could not legally call contractors. Misclassification in India is not a soft risk. The back-pay exposure on a single misclassified worker runs $25,000 to $40,000 once you add backdated PF, ESI, gratuity, leave, and statutory bonus. Across 12 heads, that is real money. paybooks

The 7-question diagnostic I run

Use this on every "contractor" you have in India. Each yes pushes you closer to employment.

1. Control. Do you direct what they work on, when, and how? Yes means employee-like control. paybooks
2. Exclusivity. Do they work only for your company? Exclusivity is a strong employment signal.
3. Tools and equipment. Do you provide the laptop, software, and email domain? Provided tools push toward employment.
4. Fixed hours. Are they expected to be online during specific hours? Fixed hours read as employment.
5. Integration. Do they appear on the org chart, attend standups, and have a manager? Integration is the strongest signal.
6. Payment regularity. Are they paid the same monthly amount on the same date? Salary-shaped payments read as employment.
7. Equity or stock options. Have you granted them equity? Equity grants almost always indicate employment.

What to do with the score

⚠️ Three or more "yes" answers, and you are running misclassification risk. Five or more, and the worker is functionally an employee in the eyes of the Provident Fund Inspectorate, ESIC, or a labour court. rippling

The cleanest legal way to test a hire on real work is Contract-to-Hire (C2H), structured so the contractor relationship has a defined end date and a documented evaluation gate, then converts to full-time employment under a single legal employer. We built our C2H product around exactly this gap. The 6-month replacement guarantee on placements means the founder is not paying twice if the conversion does not work out. remote

Q7. When Does an India Hire Trigger Permanent Establishment Risk for the Foreign Parent?

Permanent Establishment (PE) is the single most expensive India risk most founders never think about. A US parent with a single India "contractor" who signs commercial contracts can become subject to Indian corporate tax on a portion of its global revenue under Indian PE rules and the relevant Double Taxation Avoidance Agreement. This is not a payroll question. It is a corporate tax question that lives or dies on what one person does on a given Tuesday. wisemonk

The dependent-agent test

Under Section 9 of the Income-tax Act and the OECD-aligned DTAA framework India follows, PE is triggered when an India-based person "habitually concludes contracts" or "habitually plays the principal role leading to the conclusion of contracts" on behalf of the foreign enterprise. Read that twice. The line is commercial authority, not job title. wisemonk

When EOR shields PE and when it does not

✅ An EOR shields PE for engineers, designers, ops, and individual contributors who do not conclude contracts. The legal employer is the EOR's Indian entity, the worker has no commercial authority, and the foreign parent is insulated. ❌ An EOR does not shield PE for a "Country Head," "VP Sales India," or "BD Lead" who signs customer contracts, sets pricing, or commits the foreign parent to deals. wisemonk

The PE decision tree

The hire's role	Right pathway	Why
Engineer, designer, ops, or IC with no signing authority	EOR or C2H	No PE trigger, fastest setup
Customer-facing role with no contract authority (SDR, AE under quota review)	EOR with care	Document authority limits in writing
Country Head, VP Sales, BD Lead with signing authority	Owned Indian entity	EOR does not shield PE
Project-bounded specialist, no integration	Independent contractor	Confirm misclassification test passes

The Monday morning action: any hire with revenue, pricing, or contract authority should never sit as a contractor and should not sit on an EOR either. They belong on a fully owned Indian entity with their own corporate-tax footprint. This is the most-missed risk I see across my WhatsApp inbox. wisemonk

Q8. What Salary Benchmarks Should You Anchor To in Bengaluru, Hyderabad, and Pune?

Salary benchmarks are useful only if you read them as ranges, not points. India CTC numbers compress on the offer letter and expand on counter-offers. ⏰ A senior engineer in Bengaluru with two competing offers can move 20% on counter, then add a 25% notice-period buyout on top.

How to read these numbers

CTC is the gross headline. Net take-home runs roughly 75 to 85% of CTC after PF, professional tax, and TDS deductions. Joining bonuses run 1 to 3 months of CTC for senior engineering hires in Bengaluru. Notice-period buyouts of 60 to 90 days are increasingly the norm at Series B and above. ✅ Across the placements we have made over six years, the 50 behavioral parameters in our culture-fit framework predict retention better than salary alone. skuad

City nuance behind the table

Bengaluru carries the engineering premium and the highest counter-offer culture. Hyderabad runs about 10 to 15% lower on senior engineering CTC, with strong GCC compression effects. Pune punches above its weight in product design, embedded systems, and infrastructure roles, with notably better retention than Bengaluru in our experience.

2026 CTC benchmark table (annual, INR Lakhs)

Role and level	Bengaluru	Hyderabad	Pune
Software Engineer (3 to 5 yrs)	₹20 to 35L	₹18 to 30L	₹16 to 28L
Senior Software Engineer (5 to 8 yrs)	₹35 to 60L	₹30 to 50L	₹28 to 48L
Staff / Principal Engineer (8 to 12 yrs)	₹60 to 1.1Cr	₹50 to 90L	₹48 to 85L
Engineering Manager	₹50 to 90L	₹45 to 75L	₹42 to 72L
Product Designer (4 to 7 yrs)	₹25 to 45L	₹22 to 38L	₹22 to 40L
Product Manager (5 to 8 yrs)	₹40 to 70L	₹35 to 60L	₹32 to 58L
Ops / People Ops Lead	₹20 to 35L	₹18 to 30L	₹18 to 32L

Convert to USD at roughly ₹83 to ₹85 per dollar to model employer all-in cost.

What I tell founders to do with this table

Pick the role and level. Anchor the offer at the 60th percentile of the band. Hold counter-offer discipline at the 75th percentile, and only beyond if the candidate is a top-decile fit on the behavioral parameters. The headline CTC is the easy part. The retention math is what decides whether the hire pays back.

Q9. How Do You Manage an India Team Across the Cultural Gap (High Power Distance, High-Context)?

A Vancouver-based engineering manager once emailed three Bengaluru engineers directly asking for a release-readiness update. He got nothing back for two days. He assumed the team was disengaged. The team was waiting for their local lead to authorize the disclosure to a senior they did not know personally. That single incident is the most useful cultural lesson I have to offer. India scores 77 on Hofstede's Power Distance Index, against 40 for the United States. That gap is not abstract. It changes how requests should travel through your team.

Read the room, route through the lead

⚠️ The Monday morning rule: for the first 90 days, route non-trivial requests through the India lead, not directly to ICs. It feels indirect to a US manager. It is how trust is built in a high power distance culture. Once the relationship is established, the routing relaxes naturally. ✅ Across the placements we have made over six years, the teams that adopt this pattern in the first quarter retain better than the ones that do not.

The wedding hint and high-context signals

An Indian team lead once shared extensive wedding planning details with his US boss across three weekly one-on-ones. The boss heard "casual chat." The lead was signaling a looming three-week schedule conflict. India operates closer to high-context communication than the US or UK does. The message often sits in what is not said. A lack of an enthusiastic "yes" is, in practice, a polite "no." rippling

The action: when you ask "can you ship this by Friday?" listen for the shape of the answer, not just the words. A neutral "we will try" is a yellow flag. A long pause followed by "I will check with the team" is usually a red flag. Direct disagreement to a senior in a public forum is culturally rare, not a sign of agreement.

Trust as insurance, paid in advance

Indian business culture is relationship-based. Trust is built before the business need surfaces, not after. A 15-minute personal check-in once a week, separate from standups, pays back compounding interest at the next deadline crunch. ✅ Our 90-day Success Coach exists exactly for this gap. The Coach checks in with the hire, the hiring manager, and the founder weekly, and surfaces signals that a Slack standup never will. Compliance is the floor. Retention is the ceiling. Culture is what carries you between them.

Q10. What Does a Realistic 90-Day Launch Timeline Look Like (Days 0–14, 15–45, 46–90)?

When we onboarded our first EOR employee under our 5-day SLA, the agreement was signed on a Tuesday in San Francisco and the engineer was payroll-live by Monday morning IST. That is the speed possible with an India-native EOR (Employer of Record) on an owned entity. The harder question is not Day 1. It is Day 90. Here is the realistic sequence I run with founders making their first India hire.

Days 0 to 14: agreement to payroll-live

⏰ The first two weeks compress the legal, compliance, and onboarding work into a single sprint.

• Day 1. Service agreement signed between client and Versatile Club.
• Day 2. India-compliant, DPDP-ready offer letter issued to the candidate, including the four mandatory clauses on notice, consent, cross-border transfer, and grievance officer. remote
• Day 3. Employment contract executed, documents collected, BGV (Background Verification) initiated. Express BGV matters because nearly 30% of India IT-sector resumes contain discrepancies. husys
• Day 4. Statutory registrations initiated under PF (Provident Fund) and ESI (Employees' State Insurance) for the new hire. safeguardglobal
• Day 5. Employee active on payroll.

Days 15 to 45: first payroll cycle and Success Coach kickoff

The second phase is where most global EOR onboardings start to leak.

• First USD invoice issued with line-item breakdown of gross, deductions, and net per employee.
• PF and ESI challan confirmations and TDS deposit receipts shared with the client's finance team. paybooks
• Equipment delivered to the home address, set up, and inventoried.
• 90-day Success Coach kickoff: weekly check-ins with the hire, the hiring manager, and the founder.
• POSH (Prevention of Sexual Harassment) policy acknowledgement and Internal Committee orientation completed. wisemonk

Days 46 to 90: retention signals and the conversion gate

The final phase decides whether the hire pays back.

• Performance check-in at Day 60 with documented goals against the offer-letter scope.
• Retention signals reviewed: workload, manager fit, compensation alignment against the 60th percentile band.
• For C2H (Contract-to-Hire) starts, the Day 90 gate triggers conversion to full-time employment under the same legal employer, with no entity migration.
• 6-month replacement guarantee window stays active on C2H placements.
• ✅ No setup fee, no exit fee, first month free across the EOR engagement.

The 90-day timeline is not aspirational. It is the operating cadence we have run across placements in Bengaluru, Hyderabad, and Pune for six years.

Q11. How Should You Choose Between Versatile, Wisemonk, and Global Generalists Like Deel or G-P?

A People Ops VP at a 60-person Series B told me on a 30-minute Zoom that her India team had grown from 4 to 22 in nine months on a global EOR platform, and the Q2 audit had surfaced three multi-state Professional Tax registrations she had no idea were missing. She was not paying for the wrong category. She was paying the wrong vendor inside the right category. The vendor question is six axes wide, not one.

The six axes that actually matter

When I sit with a founder or People Ops leader on WhatsApp, these are the questions I push them to ask every shortlisted vendor.

1. Owned entity, not a partner shell. Is the legal employer the vendor's own Indian entity, or a third-party local partner? Liability traceability lives or dies here.
2. FX transparency. USD invoiced direct from India at mid-market, or USD converted from INR with a 3 to 5% markup buried inside the rate?
3. Founder accessibility. Direct WhatsApp to the founder, a named CSM, a ticket queue, or a chatbot first?
4. C2H-to-FTE pathway. Can you start the hire as Contract-to-Hire and convert to FTE on the same legal employer with zero entity migration?
5. Retention guarantee. Is there a published 6-month replacement guarantee on placements?
6. India-only depth. All 28 states and 8 UTs covered with state-specific S&E, PT, and LWF, or top-6 metros only?

The 6-axis comparator

Axis	Versatile Club	Wisemonk	Deel	G-P	Multiplier	Skuad
Owned Indian entity	Yes	Yes skuad	Local-partner model in India skuad	Hybrid, partner in many markets skuad	Hybrid skuad	Hybrid skuad
FX transparency	USD invoiced direct from India, mid-market rate published skuad	No FX markup stated skuad	3 to 5% markup reported skuad	15% of salary, USD 1,500/mo minimum skuad	Not disclosed skuad	Not disclosed skuad
Support model	Founder on WhatsApp	Named HRBP per account skuad	Chatbot-first skuad	Mixed skuad	Mixed skuad	Mixed skuad
C2H-to-FTE on same entity	Yes, native pathway	Not a published service skuad	Not offered skuad	Not offered skuad	Not offered skuad	Not offered skuad
Retention guarantee	6-month replacement on C2H	None published skuad	None skuad	None skuad	None skuad	None skuad
India-only depth	All 28 states + 8 UTs	All 28 states + 8 UTs skuad	Top metros via partner skuad	Top metros via partner skuad	Top metros via partner skuad	Top metros via partner skuad
Monthly EOR fee per employee	$149, no setup, no exit, first month free	$99 to $399 skuad	$599 skuad	15% of salary, USD 1,500/mo min skuad	$400 skuad	$400 skuad
Onboarding speed	5 business days, contractual SLA	24 to 72 hours, stated skuad	7 to 14 days skuad	7 to 14 days skuad	24 to 72 hours skuad	48 to 72 hours skuad

When a global generalist is the right call

✅ If you are rolling out 20 hires across 5 countries in 60 days, Deel or Remote is the right tool. Their global breadth is real. ❌ If India is one of those five countries and the depth there matters, the typical pattern is "Deel for the rest of the world, India-specialist for India." That split-vendor pattern is now common at the Series B and C level.

When India-only depth wins

If India is your primary or only offshore market, an India-native EOR with an owned entity wins on liability traceability, multi-state compliance, and support latency. ⚠️ Versatile Club is not the right vendor for everyone. We do not serve companies that need EOR in 5+ countries simultaneously, enterprise 100+ India teams that require SOC 2 or ISO 27001 as a procurement prerequisite, or B2C consumer hiring. Naming the Anti-ICP openly is part of the trust contract.

What I'm Thinking About Next

What I think shifts in the next two years is that India stops being "a country on the global EOR map" and becomes a specialist category. As the Code on Wages enforcement tightens through 2026 and the DPDP Rules go live, compliance liability becomes traceable to a specific entity, on a specific PAN, with a specific challan trail. The local-partner-aggregator EOR model gets harder to defend in a diligence room. Owned-entity India specialists eat the global generalists' India revenue, not because they are cheaper, but because they are accountable. The question I am sitting with is whether US founders making their first India hire will price that liability shift correctly, or whether they will keep optimizing for the lowest sticker on the comparison table. If you are deciding right now, my WhatsApp is open. remote