From 1 to 10 India Hires: A US Founder's Compliance Roadmap

If you're a US founder scaling India hires, the compliance roadmap looks simple at hire 1 and gets harder fast. Most founders think the real rules start at 20 employees. They actually start at hire 1. The biggest cliff is hire #10, where three laws activate at once. This article walks through each stage in order.

We've helped 300+ global companies hire 2,000+ employees in India and processed $20M+ in annual payroll. Below is the stage-by-stage playbook for US founders scaling from 1 to 10 hires, what triggers when, and where teams get tripped up.

Why does India break the US hiring playbook?

The mental model that works for remote US hires fails on three counts in India. Classification is decided by how someone actually works, not what the contract says. Central labor laws activate at headcount thresholds most founders don't see coming. And state laws stack on top of central laws, multiplying every time you hire in a new city.

Three patterns we see again and again with US founders:

• W-2-ish thinking. Treating an India hire like a US W-2 with different paperwork. The offer letter you used in San Francisco won't work in Bangalore. India-compliant offers need a specific CTC structure, a basic salary at least 50% of total comp, gratuity language, and a 30 to 90 day notice period.
• Contractor-default. "We'll just hire them as a 1099" is the most common opening move and the most expensive one. It works for two months. It breaks the moment the contractor asks for benefits, equity, or full-time status, because India determines classification by working relationship, not contract language. Misclassification penalties start at ₹50,000 per worker, plus back-dated PF and ESI.
• Late compliance. "We'll set things up properly at 20 people." Indian compliance doesn't wait. POSH policy, Shops & Establishments registration, and written contracts apply from hire 1. ESI, the POSH Internal Complaints Committee, and the Gratuity Act all activate at hire 10. By the time you reach 20, you're already 10 hires past the biggest cliff.

India isn’t just another remote hiring destination. It’s a $315.4 billion IT-BPM ecosystem employing approximately 5.95 million professionals. That scale is exactly why compliance behaves differently here. (Source: Wisemonk India IT Services Report 2026)

The roadmap below is sequenced by hire number, not by topic. Each stage covers what changes, what you set up, and what you personally sign off on. By the end, you'll know exactly which laws apply to you today, what activates next, and where the breakeven sits between EOR and your own entity.

For most founders, the real challenge is understanding how India’s complex compliance structure, business structure differences, and early-stage decisions shape long-term growth and scale.

What do you set up before hire #1?

Three things, in this order: pick your structure (contractor, EOR, or entity), assess your Permanent Establishment risk, and lock down your IP and contract templates. Most founders skip step 1 and go straight to "let's just hire someone." That's where the cost trap starts.

The decision matrix below covers when each structure fits.

For most US founders making hire 1 to 10, the answer is EOR. Contractor works only when the work is genuinely project-based and the person works for other clients. Entity setup makes sense at scale, not at hire 1.

What is Permanent Establishment risk and when does it trigger?

Permanent Establishment (PE) is a tax concept where your India activities create enough presence to make your US C-corp owe Indian corporate tax. It triggers when your India workers create a "fixed place of business" or routinely sign contracts on your behalf.

A US founder with two India contractors signing client deals from a co-working space has a PE problem. The same founder hiring through an EOR doesn't, because the EOR is the legal employer, not your US entity.

PE exposure is the silent risk most founders don't price in. It's not about employee count. It's about what those employees actually do and where the legal employment relationship sits. EOR structures specifically isolate this risk. Contractor and direct-employment models can amplify it, especially when the contractor has authority to bind your company.

Read more: What is Permanent Establishment Risk & How to Avoid It?

Why contractor misclassification is the #1 cost trap

India determines classification by working relationship, not contract language. If you set hours, assign ongoing work, and they work only for you, they're an employee under Indian law no matter what the agreement says. The penalties are not abstract. Misclassification triggers ₹50,000+ per worker in fines, plus retrospective PF, ESI, and gratuity assessments going back to the original start date.

A founder we recently spoke with had two contractors in India for 18 months, both working full-time, both reporting only to them. When they tried to convert to full-time, the legal review surfaced ₹4.2 lakh in retroactive PF alone, plus ESI back-pay. The contractor structure they thought was saving money cost them more than 18 months of EOR fees would have.

Misclassification creates hidden penalties, compliance exposure, and financial risk, making it critical for founders to structure hiring correctly from the start and avoid costly mistakes.

Get those three right and hire #1 moves smoothly. Get them wrong and you're cleaning up paperwork at hire 4.

Read more: Contractor Misclassification Risk in India Explained

Setting the right structure early, whether EOR, pvt ltd, or contractor, ensures founders prepare for compliance, protect equity, and build a scalable foundation for their India hiring journey.

What does hire #1 actually look like?

A compliant week. The 7 days before you extend the offer set up your structure, contract, and IP. The 7 days after the offer is signed cover payroll, benefits, and statutory filings. Done right, hire #1 takes about 14 days end to end. Done wrong, you're rewriting the offer letter at hire 3.

Here's the founder's pre-offer checklist:

1. Lock your structure (EOR, contractor, or entity). For most founders, this is EOR.
2. Confirm IP assignment language. US "work for hire" doesn't carry over. You need explicit India assignment clauses.
3. Pull an India-compliant offer letter template, not a US one with the salary swapped.
4. Decide on CTC structure (basic salary, allowances, voluntary PF).
5. Set notice period (30 to 90 days is standard, not 2 weeks).

What goes in an India-compliant offer letter?

An India offer letter has structural requirements a US offer letter doesn't. The CTC (Cost to Company) is the headline number, but how it's split matters legally. Basic salary must be at least 50% of total CTC. Allowances (HRA, special allowance, others) make up the rest. Get this split wrong and your PF, gratuity, and bonus calculations are off from day one.

To understand where these costs come from, see how India salary structures work or run your numbers with the India salary calculator.

Below is a sample CTC breakdown for a senior software engineer in Bangalore at ₹35,00,000 (~$42,000) annual CTC:

Beyond CTC structure, the offer must include notice period (30, 60, or 90 days), termination terms with payment-in-lieu language, gratuity entitlement after 5 years of service, leave policy aligned with the relevant state's Shops & Establishments Act, and explicit IP assignment for work created during employment.

Want a quick cost breakdown? Check out our blog on “How Much Does it Cost to Hire Developers in India?”.

What statutory rules apply at headcount 1?

Three things are non-negotiable from hire 1: a written employment contract (verbal offers don't count), a POSH (Prevention of Sexual Harassment) policy in writing, and Shops & Establishments registration in the state where the employee works.

Everything else is either later or optional at this stage. PF is technically optional below 20 employees, though most founders opt in voluntarily from hire 1. ESI doesn't trigger until hire 10. Gratuity is payable to the employee after 5 years of service, but the company's obligation begins the day they start. TDS withholding and Professional Tax registration are payroll mechanics your EOR handles automatically.

If you're using an EOR, most of this is invisible to you. The EOR files registrations, issues the contract, runs payroll, and tracks every cadence. Your job is to sign off, not to run it. If you're going direct, plan for 12 to 15 hours of founder time on hire 1 alone.

A structured hire #1 process ensures compliance, aligns compensation structure, and helps founders focus on building their team while setting the tone for future hiring success.

Hires 2 through 9 don't add new central-law triggers, but they multiply state-level complexity in ways most founders don't see coming.

For a deeper look, read the full guides on legal requirements for hiring in India, payroll compliance in India, and HR policies in India.

What changes between hires 2 and 9?

Not much at the central-law level. Almost everything at the state level. Between hires 2 and 9, no new central statute activates. But every time you hire in a new Indian state, your compliance footprint grows. Most founders miss this because remote-first thinking treats location as irrelevant. Indian law treats it as everything.

How does multi-state hiring change your obligations?

Two things change in every new state: a new Shops & Establishments registration and a new Professional Tax registration (in states that levy it). Both happen before the first salary in that state goes out. Miss them and you're filing late with penalties that scale by months delayed.

Professional Tax rates and slabs vary by state. Here's a snapshot of what you'd owe per employee per month at a ₹50,000 monthly salary in 4 common hiring states:

Delhi doesn't levy Professional Tax. Karnataka has a flat slab above ₹15,000. Maharashtra has an annual structure with a February top-up. Tamil Nadu uses half-yearly slabs. None of this is intuitive, none of it is documented in one place, and your payroll has to handle each one differently.

Should you opt into voluntary PF before hitting 20 employees?

Usually yes. Employer contribution is 12% of basic salary, and most founders are already paying that as part of total comp. Opting in formalizes it as PF rather than higher take-home, which is tax-advantaged for the employee and a meaningful retention signal. India's talent market expects PF. Candidates comparing two offers will pick the one with PF, even if total comp is the same.

By hire 9, your state filings, registers, and payroll cadence should be running cleanly. If they're not, hire 10 is going to break the system.

As founders expand across states, compliance complexity increases, requiring attention to structure, filings, and processes that impact business growth and operational scale.

Why is hire #10 the biggest milestone?

Because three Indian statutes activate at the same time, and one of them stays with you forever. ESI becomes mandatory. The POSH Internal Complaints Committee becomes mandatory. The Gratuity Act becomes permanently applicable to your company. Hit 10 employees without registering and you're not just behind, you're accruing back-payments and exposed to penalties that can run into six figures USD.

We've watched 300+ companies cross this milestone. The ones that planned 2-3 hires in advance sailed through. The ones that crossed silently spent the next 6 months cleaning up retroactive filings.

What is ESI and how do you register?

ESI (Employee State Insurance) is India's mandatory social security health insurance for employees earning ₹21,000 per month or less. Once you hit 10 employees, you must register with ESIC within 15 days. Employer contribution is 3.25% of gross salary; employee contribution is 0.75%. Filings are monthly.

The catch: ESI applies even if all 10 of your employees earn above the ₹21,000 threshold. Coverage is only for employees below the threshold, but registration is triggered by headcount. Most US founders hire engineers earning well above ₹21,000 and assume ESI doesn't apply. Registration still does. Penalty for non-registration is 12% interest per year on unpaid contributions plus damages up to 25% of dues.

Recommended read: Minimum Wage in India 2026 in INR & USD: Employer Guide

How do you set up a POSH Internal Complaints Committee?

The POSH (Prevention of Sexual Harassment) Act requires every employer with 10 or more employees to set up an Internal Complaints Committee (ICC) at each office location. Minimum composition: a presiding officer (a senior woman employee), at least 2 employee members, and at least 1 external member from an NGO or with expertise in women's issues.

The ICC isn't a paperwork exercise. Members need annual training, and the company files an annual POSH return with the District Officer. Non-compliance penalties start at ₹50,000 and escalate to license cancellation for repeat offenses.

Why does the Gratuity Act become permanent at 10?

The Payment of Gratuity Act applies to any company that has employed 10 or more people on any single day in the past 12 months. Once triggered, it stays applicable forever, even if your headcount later drops below 10.

No employee at hire 10 has yet vested (gratuity requires 5 years of service), but the company's obligation to provision starts the moment you cross the threshold. Most founders treat gratuity as a future problem and discover at year 5 that they should have been provisioning monthly.

Combined back-payment and penalty exposure for crossing hire 10 silently and registering 12 months late can run $50,000 to $200,000 USD depending on salary base and delay. None of it is hypothetical.

Most founders realize this after it costs them. See the complete guide to India’s labor laws before your next hire.

BPO/ITES hiring surged 21.7% year-on-year as of February 2026, marking 11 straight months of sustained hiring growth. (Source: Wisemonk India IT Services Report 2026)

Once you've cleared hire 10, the next strategic question gets sharper: do you keep scaling on EOR, or is it time to set up your own India entity?

EOR or your own entity: how do you decide?

By the math first, then by the signals. Most founders ask "when do I switch to entity?" and get a vague "around 15-20 employees." That's the wrong frame. The real question has two parts. At what headcount does an entity cost less than EOR fees plus the overhead of running it? And which non-cost signals push you to switch even when the math hasn't flipped?

Across 300+ companies, the transition usually happens between hire 15 and hire 25. Some clients move at hire 12 for IP reasons. Others stay on EOR through hire 30 because they're remote-first and the math still favors EOR.

What is the actual breakeven point between EOR and entity?

Three numbers decide this: EOR fees, entity setup cost, and ongoing entity overhead.

• EOR fees. $99 to $199 per employee per month at India-focused providers. At 10 employees, that's $12,000 to $24,000 per year.
• Entity setup. $15,000 to $50,000 one-time. Covers incorporation, GST registration, PF/ESI registration, bank accounts, and policy drafting. Adds 4 to 6 weeks before you can hire.
• Ongoing entity overhead. $5,000 to $10,000 per year in compliance fees (audits, ROC filings, payroll vendor, accounting). Plus 0.5 to 1 FTE of finance and HR time. Plus your own attention.

Here's the rough breakeven curve:

Setup cost amortized over 3 years, plus annual overhead.

Pure-cost breakeven sits around hire 12 to 15. But cost is only half the decision.

When you're ready to scale, explore the EOR to entity transition, compare EOR vs entity, and run your numbers with the EOR vs entity calculator.

When does an India entity become non-negotiable?

Five signals push you to entity even when the math hasn't flipped:

• Physical office. If your India team needs a real office, not co-working, an entity is cleaner.
• IP-sensitive R&D. If your India team builds core product, IP should sit with a single legal entity. The standard structure is an Indian subsidiary owned by your US parent.
• India market revenue. Selling to Indian customers means you need a local entity to invoice in INR and handle GST.
• M&A optics. Acquirers prefer clean entity structures. EOR-only India presence raises diligence questions.
• Hiring above 20. At 20+ employees, EOR fees compound fast and entity overhead is justified by scale.

The hybrid path most founders should consider: stay on EOR through hire 10. Set up the entity in parallel between hire 8 and 15. Migrate employees once the entity is fully compliant. Switching too early burns cash on overhead. Switching too late means EOR fees stack up while you delay.

With the EOR-vs-entity decision framed, the last operational piece is the compliance rhythm. What does staying compliant actually look like month to month?

What's the monthly compliance rhythm?

Predictable, if you've set up right. Once you cross hire 10, your compliance work falls into three cadences: monthly, quarterly, and annual. The monthly cadence is what fails first when founders try to run this themselves. Miss two TDS deposits and the interest plus penalty math starts compounding. Miss a POSH return and you're explaining yourself to the District Officer. The good news: the calendar doesn't change much month to month, so once it's running, it runs.

Here's what each cadence looks like.

Monthly (every month, on fixed dates):

• TDS deposit by the 7th of the following month
• Professional Tax payment in states that levy it (deadlines vary by state)
• Salary slips issued to every employee
• Attendance and leave registers updated
• PF and ESI filings with monthly contributions (post-hire 10 for ESI, post-hire 20 or voluntary opt-in for PF)
• Salary disbursement on a fixed pay date (most companies pick the 1st or last working day)

Quarterly (every three months):

• TDS returns filed (Form 24Q for salary TDS)
• POSH compliance review (post-hire 10)
• State-level filings vary by state
• Employee headcount and structure review against threshold triggers (PF at 20, voluntary PF reassessment)

Annual (once per year):

• Form 16 issued to every employee by June 15 (the India tax year ends March 31)
• Gratuity provisioning reviewed and reflected in financials
• Statutory bonus calculation and disbursement (applies to employees earning under ₹21,000/month)
• POSH annual return filed with the District Officer
• Statutory audit prep
• Any state-specific annual returns

The documentation rule: if it isn't documented, it didn't happen. Indian audits rely on your registers, payslips, and filings, not your statements. Missing records become retrospective liability.

Most founders shouldn't run this themselves past hire 5. By hire 10, the work adds up to a part-time hire. Either you build the function in-house (and an entity often follows), or your EOR runs it.

Your founder dashboard each month: TDS confirmed, payroll on time, compliance flags, headcount changes, thresholds approached. Five lines in a Notion doc, reviewed monthly. That's your actual job here.

Once the rhythm is running, the only question left is whether you keep doing this with an EOR partner or pull it in-house. The next section covers how Wisemonk fits at each stage.

How does Wisemonk help US founders scale 1 to 10 India hires?

Wisemonk is an India-native EOR built for global companies hiring in India, including Series A startups making their first or tenth India hire. We're not a generalist global platform with India as one of 90 countries. India is the only country we work in, which is why our compliance, payroll, and HR support go deeper than the alternatives.

Across 300+ companies and 2,000+ employees managed, we've processed $20M+ in annual payroll and onboarded across every Indian state. The roadmap above is what we've watched work.

What this looks like for a US founder scaling from hire 1 to hire 10:

• Pricing built for runway math: we start at $99 per employee per month with no setup fees, no enterprise minimums, and no long contracts. At a 10-person India team, that's $48K-$60K cheaper per year than Deel or Remote.
• One human contact, not a ticket queue: we assign a dedicated HR manager who knows your team. You'll talk to humans, including our founder Aditya when needed. No chatbots, no rotating agents.
• 24-48 hour onboarding: we get your hire live within two business days of offer-accept, while most global EORs take a week or longer. Critical when you're racing notice-period clocks.
• End-to-end compliance: we handle PF, ESI, gratuity, TDS, Professional Tax, POSH, and the new labor codes across every Indian state. State-level variations are our default, not an upsell.
• India-specific IP assignment: our contracts use India-compliant IP language, so the code your engineer ships actually belongs to you.
• Path to your own entity later: we help you transition from EOR to your own entity when headcount crosses 15 to 25 and the math flips.

If you're a US founder hiring your first 1 to 10 people in India, this is built for you.

Voices from Our Clients

"The Wisemonk team played a key role in helping us hire for specialized B2B SaaS marketing skills. We were able to build the team within four months, and hire experienced professionals from Tier 1/major B2B SaaS brands. This includes SEO, digital marketing, business development, product marketing, content marketing, and GTM roles. They are a great partner providing integrated services for EOR and recruitment/hiring and I’d recommend them to any B2B SaaS vendor." - Saurabh Sharma, Co-founder & CEO at Onereach, USA

"I'm very Happy that I discovered Wisemonk. They have been a pure pleasure to work with, and their attention to detail is impressive. They helped us understand their pricing model, find top-qualified individuals, interview them, and then onboard them. I gave them criteria for the type of people we sought, and they delivered. The individuals they were able to find have been some of the best engineers I have ever worked with. I recommend Wisemonk to anyone who is in need of staffing assistance." - Dan Sampson, Head of Engineering at Cobu, USA