What Should a US Founder Look for in an Indian EOR?

Picking an India EOR is not about picking a logo from a vendor list. US founders often learn this after their second or third hire, when a payroll question sits unanswered for three days, a Form 16 correction stalls, or a state registration gap surfaces during a routine audit.

The headline pitch from most EOR providers sounds identical: legal hiring, compliant payroll, fast onboarding. The differences hide in the operational layer. This guide breaks down the questions that actually separate strong India EORs from weak ones, written for founders who want to evaluate vendors with clear eyes rather than marketing copy.

Does the EOR own its Indian entity, or does it route through local partners?

This is the single most important question to ask any EOR before signing.

There are two structural models in the Indian EOR market. India-native providers own their Indian entity, employ workers directly, and run compliance in-house. Aggregator providers, often large global platforms operating in 100+ countries, sublet to local Indian partners who become the actual legal employer of your team.

The two models look identical on a sales call. They diverge sharply once compliance, support, or dispute resolution enters the picture.

From our experience helping US companies set up teams in India, the aggregator gap stays invisible until a high-pressure moment hits, a contentious exit, a missed statutory filing, or a complaint that escalates to a District Officer. By then, fixing the gap retroactively is expensive and slow.

Ask the provider directly: "Is the legal employer of my Indian worker your company, or a partner?" If the answer involves the words "network," "trusted partners," or "local affiliates," you are looking at an aggregator.

How transparent is the EOR's pricing and FX handling?

Pricing transparency is where most US founders get the worst surprises in year one.

The Indian EOR market has two pricing models. Each has tradeoffs:

• Flat fee per employee per month: Typically $99 to $699 regardless of salary. Predictable, scales cleanly with senior hires.
• Percentage of gross salary: Usually 10 to 20 percent of monthly gross. Looks cheap for junior roles but compounds every time you give a raise.

Headline fees are only half the story. The hidden costs sit in four places:

• FX markup: Large global platforms often add a 3 to 5 percent spread on every USD-to-INR conversion. Over a year of monthly payroll, that compounds into thousands of dollars per employee.
• Setup fees and deposits: Some providers require refundable security deposits equal to one to two months of payroll, with vague return timelines.
• Off-boarding and termination charges: These rarely show up in the sales deck but appear when a worker exits.
• Benefits administration markups: Health insurance, life insurance, and equipment provisioning are often invoiced at a margin rather than at cost.

What good pricing looks like in practice: a flat monthly fee, FX markup under 1 percent (or zero through hold-and-pay structures), no setup or off-boarding charges, and all benefit costs passed through at actual cost with a clear invoice line.

A simple test: ask for a sample invoice for a $50,000 salary engineer, with every line itemized. If the provider hedges or sends a "consolidated" number, the margin is hiding somewhere.

Does the support team operate during Indian business hours?

Support timezone is one of the most under-evaluated factors in EOR selection, and it directly affects whether your Indian hires actually stick around.

India runs roughly 10.5 to 13.5 hours ahead of US time zones. When support is staffed only out of US hours, this is what happens in practice:

• An employee raises a payroll query at 11 AM IST. The US team picks it up around 9 PM IST.
• A generalist support rep asks a clarifying question. The employee sees it the next morning at 9 AM IST.
• A back-and-forth that should take 30 minutes stretches across 48 to 72 hours.

A genuine India-hours support setup includes local payroll specialists who understand PF, ESI, TDS, and professional tax firsthand, a named point of contact for your account, and response times measured in hours during the Indian workday.

From what we have seen, the support gap is invisible during the sales process and painful by month two. The questions that cut through marketing claims:

• Who answers a query submitted at 3 PM IST, and how quickly?
• Is there a named account manager, or only a generic support inbox?
• Does the support team sit in India, or is "India coverage" routed through a regional partner?
• Can my employees reach support directly, or must every query route through my US HR team?

If the answers lean on phrases like "global team" or "24/7 chat" (which usually means a chatbot), the real support model is a US ticket queue.

How does the EOR handle compliance beyond payroll?

Compliance in India is not just payroll plus PF. It is a layered stack of federal and state-level obligations, and the laws that most often trip up foreign employers sit outside the core payroll conversation.

A strong India EOR should own each of the following:

• PF, ESI, TDS, gratuity, professional tax: The baseline. Every EOR claims this. Ask for sample monthly filing receipts from the last quarter.
• Shops and Establishments Act registration in every state where you hire: This is state law, not central law. A Karnataka registration does not cover a remote employee working from Tamil Nadu. If your team is spread across five states, the EOR should hold five active registrations.
• POSH Act compliance: The Sexual Harassment of Women at Workplace Act applies the moment your EOR has 10 or more workers across all clients, which is essentially always. The provider must maintain a formally constituted Internal Complaints Committee, run annual training, and file annual compliance reports with the District Officer by January 31 each year.
• The 2026 labor codes: India's four labor codes were notified on November 21, 2025, with central rules rolling out around April 1, 2026. The biggest operational shift is the 50 percent wages rule, where basic salary plus dearness allowance must equal at least half of total CTC. Strong EORs have already restructured payroll setups to comply.
• DPDP Act obligations: India's data protection law was notified in November 2025, with phased rollout through 2027. Your EOR should be handling employee consent for HR data processing, breach notification protocols, and Data Fiduciary obligations.

Companies often underestimate POSH and S&E in particular. Both carry penalties that escalate quickly, and both are areas where aggregator EORs visibly fall short.

How does the EOR shield you from permanent establishment risk?

Permanent establishment (PE) is the biggest tax risk most US companies face when hiring in India. Under Article 5 of the US-India tax treaty, your company can become taxable in India if it maintains a "fixed place of business" in the country or if a "dependent agent" regularly concludes contracts on its behalf.

A properly structured EOR engagement avoids both triggers:

• The employee works remotely or from a co-working space the EOR provides, so your company does not own or lease premises in India.
• The EOR is an independent third party, not an agent acting on your behalf.
• The employee's role is internal (engineering, marketing, support), not commercial deal-making that binds your company to Indian customers.

What can break the shield:

• Giving an India-based hire a title like "Country Manager" with authority to close enterprise deals with Indian clients.
• Leasing office space in India under your US entity's name.
• Letting the employee sign customer contracts on your behalf.

In many cases, global employers assume PE protection is automatic once they sign with an EOR. It is not. The role design and contract structure have to match the legal framework. A capable EOR will flag these issues during onboarding rather than waiting for an Indian tax notice to surface them.

How flexible is the payroll and benefits setup?

Standard EOR setups in India tend to be rigid. Salaries are denominated in INR, payroll runs monthly, benefits come from a fixed catalog, and the structure is whatever the provider's template says it is.

That works for junior hires. It breaks for senior talent.

Where flexibility actually matters:

• Currency denomination. Some providers can denominate salaries in your local currency (USD, GBP, EUR) rather than forcing everything into INR. This matters when you are hiring against a global compensation band.
• Payroll frequency. Indian payroll defaults to monthly, but some clients need fortnightly or weekly cycles to match their global payroll calendar.
• Customized salary structure. Senior Indian hires often come from companies where their previous CTC was structured a specific way (LTA, NPS, food coupons, car lease). A flexible EOR can replicate that structure rather than force a flat template.
• Customizable benefits. Standard EOR health insurance plans cover ₹3 lakh to ₹5 lakh sum insured. Senior hires often expect ₹15 lakh to ₹25 lakh, plus executive benefits like extended life cover, OPD coverage, and parental health insurance. Most EORs cannot accommodate this. The ones that can stand out fast.
• Equity and RSUs. US C-Corps issuing RSUs to Indian EOR employees need to handle FEMA, perquisite taxation, and ESPP-style structures. The EOR should know how to administer this end-to-end, not just point at the legal team.

If the provider's answer to any of the above is "that's not how we do it," you have a vendor, not a partner.

Can the EOR support contractor payments and Contractor of Record use cases?

Most US companies in India end up with a mix of full-time EOR employees and contractors. Treating the contractor side as an afterthought is a common mistake.

A strong India EOR should also operate as a Contractor of Record, handling the full freelancer payment lifecycle end-to-end:

• Compliant contracts that hold up under Indian misclassification tests.
• Invoicing and payment tracking inside a single system.
• Foreign remittance agreements (FIRA / FIRC) for every cross-border transaction, which Indian banks require for tax purposes.
• GST handling where applicable (contractors above ₹20 lakh annual turnover must register).
• TDS deduction under Section 194J or 194C, depending on the service type.
• FEMA compliance on foreign currency inflows.
• Bulk payment support for teams managing 20+ contractors.

The risk of getting contractor payments wrong is real. Indian tax authorities apply a supervision-and-control test that often reclassifies long-term contractors as employees, retroactively triggering PF, ESI, gratuity, and TDS obligations plus penalties.

One pattern we have consistently noticed: US founders start with "we'll just wire them in USD" and discover six months later that the contractor has no FIRC documents, the payments are sitting in a FEMA grey zone, and the contractor cannot file their Indian tax return cleanly.

How fast does onboarding actually happen?

Speed is a real differentiator, but "fast onboarding" claims vary widely in practice.

The realistic benchmarks:

• Strong India-native EORs: 24 to 48 hours from offer acceptance to fully compliant onboarding.
• Average global EOR platforms: 5 to 10 business days.
• Aggregator models routed through local partners: 2 to 3 weeks.

What slows things down in practice:

• KYC and background verification that the EOR outsources rather than handles in-house.
• State-specific registration delays when the EOR has not pre-registered in the employee's state.
• Bank account opening for the employee, where some EORs require waiting for an Indian salary account before processing the first payroll.
• Contract drafting that gets sent to a US legal team for review on US business hours.

Ask the provider: "If I accept a candidate's offer at 10 AM IST tomorrow, when can they be on payroll?" The honest answer should be a specific number of hours, not "we'll work as fast as we can."

Does the EOR support an eventual transition to your own entity?

Most US companies start with an EOR and graduate to their own Indian subsidiary once headcount crosses 15 to 20 FTE in one location. The economics flip around there, and the operational reasons (custom benefits, office leases, brand presence, control) start mattering more.

The transition is where a lot of vendors quietly fall short.

What a good entity transition looks like:

• The EOR actively supports subsidiary planning, including guidance on incorporation structure, state of registration, and FEMA capital infusion.
• Employee contracts can be migrated to your new entity without resignation and rehire, preserving continuity of service for gratuity, leave balances, and PF accumulation.
• The handover happens on a clear timeline, with statutory contributions, ongoing leave balances, and benefits transferred cleanly.
• The EOR does not lock you in with contractual penalties for moving employees off the platform.

Based on our extensive experience supporting international teams hiring in India, this is where buyers wish they had asked harder questions at the start. The cost of switching EORs midstream is high, but the cost of an EOR that fights your entity transition is higher.

Before signing, ask: "What does your transition support look like when I set up my own entity? Are there fees, lock-in periods, or restrictions on moving employees?"

What does the dashboard and employee experience look like?

The platform itself matters more than founders expect.

A modern EOR dashboard should give your US team:

• A clean view of every Indian hire, their status, contracts, payroll details, and compliance state.
• Self-serve onboarding flows that do not require a 30-minute Zoom call for every new hire.
• One-click payroll approval with full visibility into gross, deductions, and net.
• Itemized invoices with FX rates disclosed at the transaction level.
• Document generation for offer letters, employment contracts, payslips, and Form 16.

For your Indian employees, the experience should include a mobile-friendly app for payslips, leave requests, attendance, expense reimbursements, and tax declarations. If your engineers in Bengaluru are emailing PDFs back and forth to your US HR team for routine requests, the EOR's platform is failing.

The combination that matters most is platform plus human support. Software alone leaves Indian employees stuck on context-specific questions. Human support alone leaves your US team without visibility. The best EORs invest in both.

Why Wisemonk is built for US founders hiring in India

Wisemonk is an India-native EOR, which means we own our Indian entity, employ your team directly, and run every compliance function in-house. There is no aggregator gap, no partner network, and no ambiguity about who is responsible when something needs to be filed, renewed, or escalated.

For US founders specifically, this translates into a few practical things:

• Onboarding in 24 to 48 hours with KYC, background verification, and contract generation handled internally.
• Full compliance ownership across PF, ESI, TDS, gratuity, professional tax, POSH, S&E Act, the 2026 labor codes, and DPDP obligations.
• Pricing transparency with flat per-employee fees starting at $99 per month, FX markup under 1 percent, no setup fees, and itemized invoices.
• India-hours support staffed in India during Indian business hours, with named account managers for client companies.
• Customizable salary and benefits including USD-denominated salaries, flexible payroll frequencies, executive-level health insurance, and RSU administration for US C-Corps.
• Contractor of Record support with full FEMA, GST, and TDS handling, plus foreign remittance documentation for every transaction.
• Entity transition support when you are ready to move from EOR to your own subsidiary, with employee continuity preserved.

The goal is to take India off your founder's plate as an operational problem and let your team focus on hiring great people rather than chasing statutory deadlines.