An Employer of Record (EOR) lets a SaaS company employ engineers, product people and customer teams in India without opening an Indian entity. The EOR’s local company employs your team, runs payroll and handles Indian labour law, while your people work in your codebase, your sprints and your customer conversations. For SaaS companies, the details that matter most are intellectual property, security, time-zone overlap and how fast you can add people.
This guide explains how EOR for SaaS works in India, which roles companies typically build there first, how to protect IP and pass customer security reviews, how to structure the team across time zones, and when to move to your own entity. Information was checked against the sources listed at the end on 20 October 2026.
Why SaaS companies build teams in India
- Depth of technology talent. NASSCOM’s Strategic Review 2025 put India’s technology industry workforce at about 5.8 million in FY2025 and projected industry revenue passing $300 billion in FY2026.
- A mature global-team ecosystem. A NASSCOM and Zinnov report cited by Reuters counted 2,117 global capability centres in India in FY2026, with a talent base of 2.36 million. Many engineers have already worked in distributed product teams.
- Product and platform skills. Backend, cloud, data, AI and quality engineering are all well represented, along with product management, design and customer success.
- Follow-the-sun coverage. India’s time zone lets SaaS companies extend support and on-call coverage beyond US or European hours.
How EOR for SaaS works
| You do | The EOR does |
|---|---|
| Choose who to employ and set their compensation | Issues a Labour Code-compliant appointment letter |
| Onboard them to your tools, code and processes | Registers them for PF, ESI where applicable, and tax |
| Manage their work, goals and performance | Runs monthly payroll and statutory filings |
| Decide on raises, promotions and exits | Provides benefits such as health insurance |
| Own the product, the code and customer relationships | Handles leave, exits and final settlements |
You pay the EOR one monthly invoice covering salary, employer contributions and the EOR fee. For the basics, see what is an EOR.
Roles SaaS companies typically build in India first
| Stage | Common first roles | Why |
|---|---|---|
| First 1 to 3 people | Senior backend or full-stack engineers | Add product capacity quickly, with people who can work independently |
| 3 to 8 people | QA or test automation, DevOps or SRE, frontend | Make the India pod self-sufficient across the delivery cycle |
| 8 to 15 people | Engineering manager, data engineering, product manager or designer | Local leadership and end-to-end ownership of product areas |
| Alongside engineering | Customer success, technical support, solutions engineering | Coverage outside home-market hours and closer support for APAC customers |
| As you grow | Finance operations, revenue operations, people operations | Support functions that scale with the business |
Start with senior people. Your first India hires set the culture and standards for everyone who follows, and senior engineers need less real-time support from headquarters. Our city-by-city talent guide covers where each skill set is strongest.
Protecting intellectual property
For a SaaS company, the code is the company. With an EOR, the employing entity is the legal employer, so IP needs to flow to you clearly:
- IP assignment in the appointment letter: all work product created in the course of employment is assigned to your company, not just to the EOR.
- A matching clause in your EOR agreement: the EOR assigns to you any rights it acquires as employer.
- Confidentiality obligations covering source code, customer data and product plans.
- Prior inventions disclosure so you know what the employee brings with them.
- No reliance on post-employment non-competes: they are generally unenforceable in India under Section 27 of the Indian Contract Act. Rely on confidentiality, IP assignment and access controls instead.
If you’ve been paying India engineers as contractors, converting them to employees through an EOR also tidies up IP ownership. See contractor vs employee in India and our guide to IP protection in employment.
Passing customer security reviews
Enterprise customers will ask how you secure engineers and data outside your home country. Prepare for questions about:
- Who employs your India team, and whether a third party has access to their data. See direct vs indirect EOR.
- Background verification for people with production or customer-data access. See background verification in India.
- Device and access controls: device management, encryption, single sign-on and offboarding timelines. See our guide to laptops and security for India EOR employees.
- Security training records.
- Incident response, including the CERT-In directions that require specified incidents in India to be reported within six hours.
- Personal data handling under the DPDP Act and Rules, including where data is stored and who can access it.
Team models that work for SaaS
| Model | How it works | Works best when |
|---|---|---|
| Product pod | A small cross-functional India team owns one product area end to end | You have clear product areas and a strong local lead |
| Platform or infrastructure team | India owns shared services: CI/CD, cloud infrastructure, internal tools | Your product teams need a stable platform underneath them |
| Quality and release team | India runs automated testing and release processes overnight for the home market | You ship frequently and want faster feedback loops |
| Follow-the-sun support | India covers customer support and on-call during the home market’s night | You sell to customers across time zones |
| Mixed teams | India engineers sit inside existing headquarters teams | The team is small and overlap hours are generous |
Many SaaS companies start with mixed teams for the first few hires, then move to pods once there’s a local engineering manager.
Working across time zones
India Standard Time is 10.5 hours ahead of US Eastern standard time, 13.5 hours ahead of US Pacific, and 4.5 to 5.5 hours ahead of the UK depending on the season. SaaS teams that work well across that gap usually:
- Agree two to four hours of daily overlap, typically India’s late afternoon and evening with the US morning.
- Give the India team ownership of whole product areas or services, not tickets passed across the gap. Ownership cuts the number of hand-offs that need real-time discussion.
- Write things down: design docs, decision logs and recorded demos make asynchronous work possible.
- Use the overlap for decisions, not status updates.
- Rotate meeting times so the burden of late or early calls doesn’t fall on one side.
On-call and support coverage
An India team can take on-call or support shifts that cover your home-market night. Plan it carefully:
- Put on-call expectations in the appointment letter, including any allowance and compensatory time off.
- Check working-hours and night-work rules under the Labour Codes and the relevant state law with your EOR before designing shifts.
- Give on-call engineers real authority: runbooks, access and escalation paths, so they can fix problems rather than wait for headquarters.
- Track on-call load, and rotate it fairly across the whole engineering team, not just India.
Compensation and equity for India employees
- Structure salary for the Labour Codes. Under the Labour Codes in force since 21 November 2025, basic pay plus dearness allowance must be at least 50% of total wages. That affects PF and gratuity, so your EOR should design the structure.
- Budget for statutory costs. Employer PF is 12% on wages up to ₹25,000 a month after the September 2026 ceiling increase, plus gratuity accrual. See payroll in India.
- Offer health insurance. It’s expected by experienced engineers and often covers family members.
- Equity. Many SaaS companies want India employees to share in the upside. Options or other equity in a foreign parent granted to Indian residents involve foreign exchange and Indian tax rules, and the tax treatment depends on the plan design. Take legal and tax advice before granting, and tell your EOR so payroll can handle any taxable benefit correctly.
- Review pay regularly. Strong engineers in India receive frequent outside offers, and annual reviews are standard.
Your first 90 days with an India SaaS team
| When | What happens |
|---|---|
| Weeks 1 to 2 before start | Appointment letter signed, background verification complete, laptop and accounts ready |
| Week 1 | Product and architecture walkthrough, development environment set up, first small change shipped |
| Weeks 2 to 4 | Paired work with headquarters engineers during overlap hours; first independent tasks |
| Month 2 | Ownership of a defined area, service or customer segment |
| Month 3 | Participating in planning, code review and on-call rotation; first 90-day review |
Founders who visit Bengaluru, Hyderabad or Pune once in the first quarter often find it pays for itself in trust and speed.
What an EOR costs a SaaS company
Your monthly cost is the employee’s salary, employer statutory contributions and the EOR fee. StratEdge Global’s EOR starts at $349 per employee per month with health insurance included, on month-to-month terms with no deposit. Compare that with the published EOR fees of global platforms, typically $599 to $699 per employee per month before add-ons. Use our EOR cost calculator to estimate a specific role, and see the true cost of employment in India for how CTC is built.
When to move from an EOR to your own entity or a GCC
Most SaaS companies start with an EOR and revisit the decision once the India team is large and stable, often somewhere between 15 and 50 people. Signals it’s time to look at your own entity or a global capability centre:
- The India team is large enough that entity running costs are lower than EOR fees.
- You need an Indian company to sign local customer or partner contracts.
- You want to own office leases, assets or local bank accounts.
- You have, or plan to hire, local HR, finance and legal staff.
Moving later is straightforward if your EOR has no transfer fees and supports the switch. See GCC vs EOR in India and EOR vs entity.
Mistakes SaaS companies make in India
- Starting with contractors and never converting. It creates misclassification risk and unclear IP ownership.
- Hiring juniors first to save money. Without senior anchors, junior engineers need constant support across a 10-hour time difference.
- Sending tickets, not ownership. Teams that only receive tasks can’t make decisions, and good engineers leave.
- Ignoring notice periods. Experienced engineers in India often have 60 to 90 day notice periods. Plan start dates around them; see the notice period guide.
- Treating the team as “offshore”. Separate rituals, channels or recognition create a two-tier culture. Your EOR employees should be treated as your own team.
- Leaving security for later. Customer security reviews will ask about India; it’s easier to build controls from day one.
Checklist: EOR for SaaS in India
- IP assignment and confidentiality in the appointment letter and the EOR agreement.
- Written confirmation of which entity employs your India team.
- Labour Code-compliant salary structure, with health insurance.
- Background verification for roles with production or customer-data access.
- Company-managed laptops with device management and encryption.
- Single sign-on with multi-factor authentication for every tool.
- Agreed overlap hours and clear ownership areas.
- On-call terms, if any, in writing.
- An incident response plan that covers India.
- A path to your own entity, with no exit penalties.
Choosing an EOR for a SaaS team
Beyond price, SaaS companies should check that their EOR can support how product teams actually work:
| Question | What a good answer looks like |
|---|---|
| Will IP be assigned to us, not just to you? | Clauses in both the employee’s appointment letter and your EOR agreement |
| Who employs our team, and who sees their data? | A named Indian entity and a short, disclosed list of data processors |
| Can you support on-call and shift allowances? | Yes, through payroll, with terms written into appointment letters |
| Can you supply and support laptops? | Yes, or a clear process for working with your IT team |
| Can you run background verification? | Yes, with DPDP-compliant consent, completed before the start date |
| How fast can we add the next engineer? | Days after an offer is accepted, not weeks |
| Can we move employees to our own entity later? | Yes, with no transfer fee and a defined process |
Why StratEdge Global: one partner, one platform
StratEdge Global helps SaaS companies build India teams that work like part of headquarters.
- From $349 per employee per month, with health insurance and KnowBe4 security training included. See pricing.
- Laptop, accessories and an office seat in the ENHANCED plan; background verification in ELEVATE.
- India employees employed through StratGrid Private Limited in Bengaluru, with one accountable team.
- Onboarding in as little as 48 hours, and HireEdge recruitment for engineering, product and customer roles. See managed hiring in India.
- Real-time visibility of payroll, leave and documents through EmpleYor.
Planning your India product team? Book a free 30-minute call.
Sources
Official sources
- Ministry of Labour and Employment: four Labour Codes in force from 21 November 2025
- Press Information Bureau: EPF wage ceiling raised to ₹25,000
- Press Information Bureau: Digital Personal Data Protection Rules, 2025
- CERT-In: Directions of 28 April 2022
- India Code: Indian Contract Act, 1872, Section 27
Industry sources
- NASSCOM Strategic Review 2025
- Reuters via Communications Today: NASSCOM-Zinnov GCC figures for FY2026
All sources checked on 20 October 2026.
This guide is general information, not legal, tax or financial advice. Equity, IP and working-hours questions depend on your specific situation; take professional advice.
FAQ
What is EOR for SaaS?
It means using an Employer of Record to employ your SaaS company’s engineers and other staff in a country where you have no entity. The EOR is the legal employer; your team works on your product under your direction.
Can a US SaaS company build an engineering team in India without an entity?
Yes. An Employer of Record employs your team through its Indian entity, so you can start in days and set up your own entity later if it makes sense.
Who owns the code written by EOR employees?
Your company should, through IP assignment clauses in the employee’s appointment letter and in your agreement with the EOR. Check both before anyone starts.
Which roles should a SaaS company employ in India first?
Usually senior backend or full-stack engineers, followed by QA, DevOps and frontend engineers, then an engineering manager and product roles as the team grows.
Can India employees receive stock options?
Often, yes, but options in a foreign parent involve Indian foreign exchange and tax rules. Take legal and tax advice and coordinate with your EOR.
When should a SaaS company move from an EOR to its own Indian entity?
Typically once the India team is large and stable, often between 15 and 50 people, or earlier if you need an Indian company for contracts, assets or local operations.
Do India SaaS employees need to work US hours?
No. Most teams agree two to four hours of daily overlap and give the India team ownership of whole product areas, so most work can happen asynchronously.