US SaaS Startup With 8 India Contractors: Entity vs EOR

If your US SaaS startup has 8 contractors in India doing full-time work on your core product, the honest starting point is that most of them are employees under Indian law, no matter what the agreement calls them. That means the choice is not really contractors versus something formal. It is between two compliant structures: opening your own Indian entity, or using an Employer of Record (EOR). For a team of eight, an EOR is almost always the faster and lower-risk move, and an entity starts to make sense later, once the team is much larger and clearly permanent.

This guide walks through how to make that decision with real numbers, timelines, and the risk you are carrying right now.

Why are 8 India contractors a compliance problem?

Because Indian authorities look at how the work actually happens, not at what your contract says. Eight people working full-time and exclusively for you, on your tools, inside your standups and sprint cycles, look like employees to the EPFO, the ESIC, and a tax officer, even if every agreement says independent contractor.

This is worker misclassification, and it is the most common and most expensive mistake foreign companies make in India. The tests that matter are control, integration, and economic dependence. Do you set their hours and tasks? Are they part of your team rather than an outside vendor? Do they earn most of their income from you? The more of these that apply, the weaker your contractor position becomes. We cover the full breakdown in our guide to contractor misclassification risk in India.

From our experience helping foreign companies formalize India teams, the pattern is consistent. Contractor setups feel clean for the first year or two, then a funding round, an acquisition, or a disgruntled leaver forces the question, and by then the exposure has been compounding month over month across all eight people.

What does misclassification actually cost per contractor?

If contractors are reclassified as employees, the liability is retrospective and applies for the entire engagement period, not just going forward. That is what makes eight contractors a meaningful number rather than a rounding error.

The clawback typically includes:

• Provident Fund arrears, covering both the employer and employee share, plus interest and damages of up to 25 percent of the arrears.
• Employee State Insurance arrears where the worker earned within the eligibility threshold.
• Gratuity and leave encashment that a contractor was never paid.
• Missed TDS and professional tax, with penalties and interest attached.

There is also permanent establishment risk. A team of full-time people operating in India can create a taxable presence for your US parent, which pulls a share of your profits into the Indian tax net. Not having an Indian entity does not protect you here. It usually makes enforcement messier and more expensive to untangle.

Multiply a single reclassification across eight people and you are looking at a serious backdated bill before any legal fees. This is the number founders should weigh against the cost of formalizing, because it is the cost of doing nothing.

What changed with India's Labour Codes in 2025?

On November 21, 2025, India's four new Labour Codes came into force, consolidating 29 separate laws. Two changes matter directly for anyone running contractors.

First, gratuity now accrues from year one for fixed-term workers, down from the old five-year threshold. So if a long-running contractor is reclassified, the gratuity exposure builds far faster than it used to.

Second, basic salary must now be at least 50 percent of total compensation. This raises the base used to calculate PF, gratuity, and other benefits, which means larger backdated liabilities on reclassification and a need to rebuild older salary structures. The EPFO also ran an enrolment amnesty for misclassified workers that closed on April 30, 2026, and scrutiny has tightened since. In short, contractor arrangements that felt safe a year ago carry more risk today.

What does setting up an Indian entity involve?

An Indian subsidiary makes your startup a real employer in India, with its own payroll, bank account, and statutory registrations. It is the right long-term structure once your India team is large and permanent, but it is a commitment, not a quick fix.

For a foreign company, the practical realities are:

• Setup timeline of roughly four to eight weeks, since foreign director paperwork needs apostille and notarization, and RBI or FEMA filings apply to the foreign investment.
• A resident director requirement. At least one director must have stayed in India for 182 days or more in the year, which founders usually cover through a nominee until they have local presence.
• Ongoing annual compliance: statutory audit, ROC filings such as AOC-4 and MGT-7, corporate tax returns, GST returns, and monthly PF, ESI, TDS, and professional tax filings.
• A retained chartered accountant or compliance firm to keep all of this on schedule, since missed filings trigger penalties automatically rather than reminders.

None of this is a reason to avoid an entity forever. It is a reason not to rush into one for eight people when a faster option exists.

How does an EOR solve this for a team of 8?

An Employer of Record already has an Indian entity and legally employs your eight people on compliant local contracts. You keep full day-to-day control of the team, direction, priorities, and performance, while the employer obligations sit with the EOR.

The EOR handles compliant appointment letters that meet the Labour Code rules, PF and ESI registration and monthly filings, TDS and professional tax, gratuity provisioning, insurance, and a clean full and final settlement when someone leaves. For your existing eight, it terminates the contractor agreements and starts fresh employment relationships, which closes the misclassification gap cleanly rather than leaving it open.

The onboarding is measured in days, not weeks, and there is no entity to register or wind down. If you later decide to open your own subsidiary, you can transition the team across. This is why most companies in your position hire employees in India through an EOR first and revisit the entity question once the team is much larger.

Here is how the two compliant paths compare for a team of eight.

At what point should a startup switch to its own entity?

When the India team is large enough and permanent enough that the fixed cost of running an entity is lower per head than paying an EOR fee on every employee. That crossover is about scale and certainty, not a fixed date.

A few signals that the entity conversation is worth having:

• Your India headcount has grown well past a couple dozen and keeps climbing, so the flat EOR fee per person adds up to more than an entity's fixed compliance cost.
• India is clearly a long-term base, not an experiment, and you want direct ownership of contracts, IP, and local banking.
• You have the internal or outsourced capacity to run Indian payroll and statutory compliance reliably every month.

For a company with eight contractors today, that moment is usually still ahead. The immediate priority is getting all eight onto a compliant footing, and an EOR does that now. When the scale case arrives, you can run the numbers properly, and our team can help you compare the full cost of an EOR in India against running your own entity.

How Wisemonk helps US SaaS startups formalize India teams

This is the exact situation we handle every week. Wisemonk is an India-native EOR, which means we own our compliance infrastructure in India rather than routing your team through a third-party partner. For a US SaaS startup with eight contractors, we can bring the whole team onto compliant employment quickly, close the misclassification and PF exposure that has been building, and give you clean, employment-grade IP assignment that holds up in fundraising and acquisition diligence.

Practically, that covers compliant appointment letters under the current Labour Codes, PF, ESI, TDS, gratuity, and professional tax handled end to end, and a structured conversion so your engineers see the move as an upgrade rather than disruption. If you want to see how a specific contractor-to-employee conversion would work for your team, or how the numbers shift as you grow, we can map it out with you. Managing India contractors and full-time hires under one compliant structure is what we do.