Wisemonk Team
Written By
Category Workplace and Legal Compliance
Read time 9 min read
Last updated June 30, 2026

India Employment Laws SaaS Founders Should Know Before Hiring

India Employment Laws SaaS Founders Should Know
TL;DR
  • India consolidated 29 employment laws into four Labour Codes that became effective on November 21, 2025. SaaS founders hiring in India need to understand this new framework before they extend their first offer.
  • Indian employment law is decided at two levels. Central laws like PF, ESI, Gratuity, and the new Labour Codes apply nationally. State-level laws like Shops and Establishments and Professional Tax change every time you hire in a new city.
  • Classification matters more than the contract. India determines whether someone is an employee or a contractor by how they actually work, not by what the paperwork says. Misclassifying a contractor as a freelancer can trigger back PF, ESI, and gratuity going years back.
  • Statutory thresholds are headcount-triggered. ESI kicks in at 10 employees, PF at 20, and a POSH Internal Complaints Committee at 10. The new wage definition under the Code on Wages applies from your first hire.
  • Most SaaS founders should hire through an EOR for the first phase. It removes Permanent Establishment risk, handles every statutory filing, and means your India team can start in days rather than weeks.

Before a SaaS founder hires their first engineer in India, they need to understand the legal scaffolding that sits underneath every Indian employment relationship. We've seen too many global SaaS teams treat their India hire like a remote US contractor, only to discover six months in that they owe back contributions, missed a state registration, or have a contract that wouldn't hold up in an Indian tribunal. Wisemonk works with foreign SaaS companies on exactly this problem, and the patterns repeat across every client.

This article walks through the laws that actually matter when you hire in India, what's changed under the new Labour Codes, and what specifically a SaaS founder should set up before extending an offer.

Why are India's employment laws different from what SaaS founders expect?

India's employment law is layered, federal, and trigger-based. The country has central laws that apply nationally, state laws that vary by region, and statutory thresholds that activate as your team grows. SaaS founders coming from a US or UK at-will employment model often underestimate how much structure Indian law requires from day one.

Three things tend to surprise founders the most:

  • Written contracts are mandatory. A verbal offer or a casual email doesn't qualify. Under the new Labour Codes, every worker must receive a written appointment letter.
  • Classification is determined by behavior, not by the document. If a contractor works fixed hours, takes direction from you, and works exclusively for your company, Indian law treats them as an employee no matter what the agreement says.
  • State law layers on top of central law. Every state has its own Shops and Establishments Act and most have their own Professional Tax rules. Hiring across Bangalore, Pune, and Delhi means three sets of state filings.

From our experience helping foreign companies hire their first India team, the founders who treat compliance as an afterthought spend the next year cleaning up. The ones who set the structure correctly at hire one rarely think about compliance again.

What are the new Indian Labour Codes and how do they affect SaaS hiring?

The Government of India notified all four Labour Codes effective November 21, 2025. They consolidate 29 older central laws into a single, modernized framework. Every SaaS founder hiring in India after this date is operating under the new framework, even though some state-level rules are still being finalized.

The four codes are:

The four Labour Codes effective November 21, 2025
CodeWhat it coversKey change for SaaS founders
Code on Wages, 2019Minimum wages, payment of wages, bonus, equal remunerationNew universal wage definition (50 percent basic pay rule)
Code on Social Security, 2020PF, ESI, gratuity, maternity benefit, gig worker coverageESI coverage extended PAN-India, gratuity after one year for fixed-term staff
Industrial Relations Code, 2020Trade unions, standing orders, dispute resolutionFormal recognition of fixed-term employment with benefit parity
Occupational Safety, Health and Working Conditions Code, 2020Workplace safety, working hours, leave, contract laborMandatory written appointment letters, digital record-keeping

The single biggest change SaaS founders should know is the new wage definition. Under the Code on Wages, basic pay plus dearness allowance plus retaining allowance must make up at least 50 percent of total compensation. If allowances exceed 50 percent of total pay, the excess is added back to the wage base for calculating PF, ESI, gratuity, and bonus.

This closes the loophole most Indian employers used for years, where they kept basic salary artificially low to minimize PF and gratuity contributions. For SaaS founders, this means your offer letter and CTC structure need to be designed with the new wage floor in mind from day one.

How does the 50 percent wage rule change CTC design?

In the old model, many companies set basic salary at 30 to 40 percent of CTC and loaded the rest into HRA, special allowance, and other components. Under the new rule, that structure no longer works for statutory calculations. Even if your offer letter shows 30 percent basic, the law will treat 50 percent of CTC as the wage base for PF and gratuity.

Three practical effects:

  • Employer PF contributions rise. Higher basic means higher 12 percent employer match.
  • Gratuity exposure rises. The exit payout is calculated on the new, higher wage base.
  • Employee take-home may drop slightly, even when CTC is unchanged.

Read more: New Labour Code in India: A Complete Guide

What statutory benefits must SaaS founders provide in India?

Indian law mandates several statutory benefits that aren't optional, regardless of how your offer letter is worded. SaaS founders often discover these obligations after the fact, which is the most expensive way to learn them.

The core statutory benefits are:

Statutory benefits SaaS founders must plan for
BenefitThresholdEmployer cost
Provident Fund (PF)Mandatory at 20+ employees; voluntary below12 percent of basic pay (employer share)
Employee State Insurance (ESI)10+ employees; covers staff earning up to ₹21,000/month3.25 percent of gross wages (employer share)
Gratuity10+ employees once triggered, then permanent; payable after 5 years of service (1 year for fixed-term)About 4.81 percent of basic provisioned monthly
Paid leaveSet by state Shops and Establishments ActTypically 12 to 21 days annual leave plus sick leave
Maternity leaveAll establishments with 10+ employees26 weeks of paid leave (employer cost)
Statutory bonusEmployees earning up to ₹21,000/month8.33 percent to 20 percent of basic, paid annually

On top of these, the Labour Codes added a few obligations that founders often miss. Free annual health checkups for workers above 40 years of age. Mandatory ESIC coverage extended PAN-India even for establishments outside notified areas. And under the OSH Code, even a single worker engaged in hazardous processes triggers safety compliance obligations.

For most SaaS teams hiring engineers, designers, or marketers, the practical statutory load is PF, ESI (registration only, since most staff earn above the threshold), gratuity provisioning, paid leave, maternity benefit, and TDS withholding.

In India, classification is decided by the substance of the working relationship, not the label on the contract. If someone works fixed hours under your direction, uses your tools, and works only for you, they're an employee under Indian law. Calling them a contractor doesn't change that, and the penalties for getting it wrong are severe.

The main classification tests Indian authorities apply:

  • Control test: Do you set their hours and how they do the work?
  • Integration test: Are they integrated into your team and processes?
  • Exclusivity: Do they work for other clients, or only for you?
  • Tools and equipment: Do you provide laptops, software, and infrastructure?
  • Duration and continuity: Is the engagement open-ended or project-based?

Companies often underestimate contractor misclassification risk because the cost only surfaces later. When a misclassified contractor leaves and files a claim, the company can be ordered to pay back PF, ESI, gratuity, and bonus going back to the original start date, plus penalties and interest.

If you're hiring someone full-time, you should hire them as an employee from the start, either through your own entity or through an EOR.

What is Permanent Establishment risk and why should SaaS founders care?

Permanent Establishment (PE) is a tax concept where your India activities create enough presence to make your US, UK, or other foreign company liable for Indian corporate tax. For SaaS founders, PE risk typically gets triggered in two ways: a fixed place of business in India, or employees in India who routinely sign contracts on your behalf.

A SaaS founder with two engineers in Bangalore working from a coworking space, building product, and not signing customer deals usually does not have a PE problem. The same founder with sales reps in Mumbai closing Indian customers does. The activity matters more than the headcount.

EOR structures specifically isolate this risk because the EOR is the legal employer in India, not your foreign company. Direct contractor relationships or branch operations can amplify PE exposure, especially if the contractor has authority to commit your company to deals.

Read more: Understanding the Risks of Permanent Establishment

Which employment law thresholds activate as SaaS teams scale?

Indian employment obligations are not flat. They activate at specific headcount thresholds, and missing the activation point creates retroactive liability. Here's the threshold map most SaaS founders should mark on a wall:

Headcount-triggered compliance milestones
HeadcountWhat activatesRisk if missed
1Written contract, POSH policy, Shops and Establishments registration, written appointment letterContract unenforceable, state penalty
10ESI registration, POSH Internal Complaints Committee, Gratuity Act applicability (permanent once triggered)Back ESI contributions, ₹50,000+ per POSH violation
20PF mandatory (if not opted in voluntarily), filing of returns under multiple actsBack PF plus 12 percent interest plus damages
50Creche facility (Maternity Benefit Act), additional state-level filingsCompliance notices, penalties
100Standing Orders applicable (Industrial Relations Code)Operational disruption, statutory penalties

From what we've seen, hire 10 is the cliff that catches founders by surprise. ESI, POSH, and Gratuity Act applicability all activate at the same time, and once Gratuity Act applies it stays applicable for life, even if your headcount drops back below 10.

What should SaaS founders set up before extending an India offer?

Five things, in this order:

  1. Decide your hiring structure. Contractor, EOR, or your own Indian entity. For most SaaS founders making the first one to ten India hires, an EOR is the right answer.
  2. Confirm IP assignment language. US 'work for hire' doctrine doesn't carry over. You need explicit India-compliant IP assignment clauses in the employment contract.
  3. Use an India-compliant offer letter template. CTC structure, basic salary at least 50 percent of CTC, gratuity entitlement, notice period of 30 to 90 days, leave policy aligned with the relevant state.
  4. Plan for statutory withholdings. TDS (income tax deducted at source), PF, ESI, and Professional Tax all flow through payroll. Build this into your offer math, not as an afterthought.
  5. Set up a POSH policy in writing. Even at hire one, the policy is mandatory. The Internal Complaints Committee becomes mandatory at hire 10, but the policy itself is required from day one.

Companies that go through this checklist before extending an offer rarely have compliance problems later. The ones that skip it usually find out at hire five or six when something breaks. Wisemonk's EOR service handles every item on this list as part of onboarding.

How does Wisemonk help SaaS founders navigate India employment law?

We've helped over 300 global companies hire and manage more than 2,000 employees in India. The questions SaaS founders ask us the most are the ones in this article, and the answers are the same every time: get the structure right at hire one, hire through an EOR until you have a clear reason to set up an entity, and treat compliance as a system rather than a one-time setup.

Practically, here's what working with Wisemonk looks like for a SaaS founder making their first India hire:

  • We act as the legal employer in India, removing PE risk for your foreign entity.
  • We draft India-compliant offer letters and contracts with the correct CTC structure under the new wage rules.
  • We handle PF, ESI, gratuity provisioning, TDS, Professional Tax, and POSH compliance across every Indian state.
  • We onboard your hire in 24 to 48 hours after offer acceptance, not the week or longer that global platforms typically take.
  • We give you a dedicated HR manager who knows your team, so you're not routing every question through a ticket queue.

If you're ready to hire your first or tenth India employee and want to do it without taking on PE risk or running multi-state compliance yourself, the next step is a 20-minute call with our India hiring team.

Hiring in India? Set it up right from day one.

Get help structuring contracts, payroll, and statutory compliance under India's new Labour Codes.

Frequently asked questions

Do US SaaS companies need a legal entity in India to hire employees?

No. SaaS companies can hire full-time India employees through an Employer of Record without setting up an Indian entity. The EOR is the legal employer, handles all statutory compliance, and removes Permanent Establishment risk. Most founders use this model until they have 15 to 25 India hires.

Which Indian employment laws apply to a remote engineer working from home?

All central laws (PF, ESI, gratuity, Labour Codes, POSH) apply based on headcount thresholds. State laws apply based on where the employee lives and works. A remote engineer in Bangalore triggers Karnataka Shops and Establishments and Karnataka Professional Tax. The same role in Delhi triggers different state rules.

Can I hire my first India employee as a contractor to keep things simple?

You can hire contractors if the work is genuinely project-based and the person works for multiple clients. If they work full-time hours under your direction, Indian law treats them as an employee regardless of the contract. Misclassification triggers back PF, ESI, and penalties, so most SaaS founders use an EOR for full-time hires.

What changed for SaaS employers when the Labour Codes came into force?

Three big changes: a universal wage definition that requires basic pay to be at least 50 percent of total compensation, mandatory written appointment letters for every worker, and a two working day rule for full and final settlement after exit. State rules are still being finalized, but central provisions are in force from November 21, 2025.

How much does it cost to hire a SaaS engineer in India compliantly?

A senior engineer in Bangalore typically costs $35,000 to $60,000 fully loaded annually, including statutory contributions like PF, ESI, and gratuity. Compare that with the same role in San Francisco at $200,000+. EOR fees add roughly $99 to $199 per employee per month. See our EOR cost guide for a full breakdown.

What's the legal notice period for India employees?

India doesn't have a statutory notice period for white-collar employees. It's set by contract and typically ranges from 30 to 90 days for full-time staff. Most SaaS hires sign 60 or 90 day notice clauses, which protects continuity. Companies coming from at-will US employment often underestimate this and lose months when a key hire resigns.

Does Permanent Establishment risk apply if I only have one or two India employees?

PE risk depends on what the employees do, not just headcount. One employee signing customer deals from India can create PE exposure. Three engineers building product without customer-facing authority usually do not. Hiring through an EOR isolates this risk because the EOR is the legal employer. Read more on PE risk in India.

Ready to build your India team?

Tell us who you're looking to hire. We'll walk you through exactly how the setup works for your company, your timeline, and your budget.

The India'logue

Everything you need for building & scaling remote teams in India

You wire money to workers in India — this newsletter covers everything that comes with it. Tax, GST, IP, ESOPs, cross-border compliance, worker classification, and every regulation in between.

Know more