We have watched the same India hiring strategy go wrong in the same eight ways for years now.
The pattern rarely looks like a disaster at the start. It looks like a shortcut that worked. A contractor who shipped fast. An offer that got accepted. A team that grew. Then a year passes, and a tax notice lands, or the best engineer quits, or an acquirer's lawyer asks for records nobody kept.
Across the 300+ companies we have helped build teams in India, the mistakes generally cluster into three buckets – Legal shortcuts, team-shape errors, and a mindset problem that poisons the other two. Here are the eight mistakes US founders and HR leaders make the most, and what to do instead.
Mistake 1: Hiring contractors instead of employees
This is the most expensive mistake on the list, and almost nobody sets out to make it.
It starts sensibly. You need one engineer in India to join your team. Setting up an entity feels like overkill, so you put them on a contractor agreement, wire a monthly amount, and get to work. On paper it is cheaper. No Provident Fund, no ESI, no gratuity. The math holds right up until someone looks closely.
That someone is usually an Indian authority or your own acquirer's lawyer. And here is the thing founders miss: the label on the contract does not decide anything. The facts do. Indian courts apply four tests to figure out the real relationship. Control, over hours, tools, and daily tasks. Integration, whether the person is woven into your org. Economic dependence, whether they rely on you alone and carry no business risk. And mutuality of obligation, whether there is an ongoing duty to offer and accept work. A full-time developer taking your standups, using your systems, working only for you, fails all four.
When that happens, the worker is an employee in substance, and you owe the back-dated bill. Employer PF at 12%, ESI where it applies, gratuity, plus 12% annual interest and damages under the EPF Act. On a senior engineer worked for a couple of years, that catch-up commonly lands between $25,000 and $40,000 per person. Multiply it across a team of five and the number stops being a rounding error.
Then there is the quieter risk. A directed contractor can create Permanent Establishment, meaning your foreign company is treated as doing business in India and becomes taxable here. This almost never surfaces in a raid. It surfaces during funding due diligence, when an acquirer asks for records that were never accrued.
The fix is not complicated. For genuine project work with a clear scope and an end date, contracting is fine. For your core, full-time roles, employ people properly from day one. This is exactly the problem Wisemonk's EOR exists to solve. If you already have contractors who look like staff, we convert them into FTEs, terminating the old agreement and starting a proper employment relationship before the liability builds any further. Not sure where you stand? Our misclassification quiz flags your exposure in a few minutes.
Mistake 2: Waiting for the entity before making the first hire
In India setting up your own private entity can take months. A US startup finds the exact senior engineer they wanted, then tells the candidate to wait while incorporation grinds through. By the time the entity is payroll-ready, that engineer has taken another offer. The role restarts from zero.
An Employer of Record flips the order. Because the EOR already holds the Indian entity, your hire can start in a matter of two days rather than months, and you skip the upfront setup cost entirely.
Having your own entity only starts to pay off once you have a few dozen long-term employees in one place and want your own permanent presence. Start lean, hire the person now, and move to an entity later when the numbers actually flip. Our EOR vs entity breakdown shows exactly where that line sits for your headcount.
Mistake 3: Hiring twenty engineers before one local team lead
A US company hires twenty individual contributors in India, all reporting into a manager sitting in a US timezone.
It works for a quarter. Then the cracks show. Context gets lost across the twelve-hour gap. Nobody on the ground owns escalation, culture, or career growth. The strongest engineers, the ones with options, leave first, because no one local is invested in keeping them. Hire your first India leader early, even before the team feels big enough to justify it. Someone on the ground who owns delivery and people is what turns a group of remote contractors into a team that stays.
Mistake 4: Copying US compensation logic straight across
A US base salary and an Indian CTC are not the same animal, and treating them alike produces offers that quietly underwhelm.
CTC, or cost to company, bundles far more than take-home pay. It splits into fixed and variable components, absorbs employer PF contributions, gratuity provisioning, and allowances like HRA that carry real tax advantages when structured well. There is also a new constraint you cannot design around. Under the 2025 Labour Codes, basic pay plus dearness allowance must be at least 50% of CTC, and that single rule resets how PF, gratuity, and take-home all get calculated. Plenty of older salary structures that leaned on a low basic to trim contributions are now out of line, and the liability accrues whether or not your state has finished notifying its rules.
Copy your US logic across and you get one of two outcomes. Either the headline number looks competitive but the actual in-hand pay is less. Or you misprice the role in your budget and find out later. This is where good CTC structuring earns its keep, shaping the package so it is compliant with the 50% rule, tax-efficient for the employee, and correctly costed for you. It is also one of the things a competent EOR handles as a matter of course.
Mistake 5: Using a generic global contract and skipping compliance setup
The one-size-fits-all employment agreement is a trap. A US-style or pan-global template does not hold up under Indian law, which runs at both central and state level.
In India, you need a compliant offer letter under the applicable state Shops and Establishments Act along with Statutory registrations for PF, ESI, professional tax, and TDS. This is where do-it-yourself hiring quietly goes wrong, and the November 2025 Labour Codes raised the stakes, with substantive provisions already in force while the final rules are due in 2026. An EOR handles contracts drafted under the Indian Contract Act and the right state act, IP and confidentiality clauses built in, and every monthly statutory filing.
Mistake 6: Treating India as cheap labor, not a capability center
This is the mindset error underneath most of the others, and it is the one that costs you the team.
When India is a line item to minimize, everything downstream suffers. Onboarding gets skipped. Ownership stays in the home office. Growth paths never get drawn. People notice, and they leave. The companies that win in India treat it as a capability bet, the same reason 1,800+ multinationals run Global Capability Centers here. Hire for the long term, invest like you mean it, and the retention takes care of itself.
Mistake 7: Skipping background checks and IP protection at hiring
If you are rushing through the offer stage then you’ll end up fixing two things that are painful to fix later.
The first is background verification. Employment history, credentials, and criminal checks are standard practice in India, and waving them through to close faster is a risk that compounds. The second is IP protection. India's defaults surprise foreign founders: copyright in an employee's work usually sits with the employer, but patents do not transfer automatically, and contractors keep what they create unless a written assignment says otherwise. This ties straight back to Mistake 1, since a misclassified contractor may own the very code you paid for. Compliant employment contracts fix this by writing IP assignment and confidentiality in from the start, so what your India team builds belongs to you, and stays yours after they leave.
Facts confirmed, including Wisemonk's own F&F guide. The key hard numbers: no at-will, notice periods 30-90 days (contractual, often longer for seniors), F&F within 2 working days under the Code on Wages, workmen protected under the IR Code with due process and reinstatement risk. Now the 50% wage rule detail is already covered from earlier searches (basic + DA must be at least 50% of CTC, live now, reshapes PF/gratuity/take-home).
Here are the two additions. Both match the established voice, no em-dashes, no double-apostrophed phrases.
Mistake 8: Assuming you can let someone go the way you would in the US
This one blindsides US founders more than any other, because it runs against an assumption they never think to question. There is no at-will employment in India. You cannot simply part ways on two weeks' notice.
Notice periods are contractual and real, commonly 30 to 90 days, and longer for senior roles. If you terminate for cause, you have to follow due process, which for anyone who counts as a "workman" under the Industrial Relations Code means a documented inquiry and a genuine chance to respond. Skip the process and the termination can be ruled illegal, with reinstatement and back wages on the table, no matter how solid your reason was. Then there is the exit itself. The Code on Wages now requires full and final settlement within two working days of the last working day, a sharp tightening from the 30 to 45 days most companies were used to. Miss it and you are exposed to penalties and a complaint to the Labour Commissioner.
None of this means India is a place where you cannot manage performance. It means the offboarding has to be as deliberate as the onboarding.
The thread running through them all
Almost every one of these comes from treating an India hire like a US hire with a currency swap. It is not. Different law, different compensation logic, different reasons the best people stay. Get those right and India becomes one of the strongest bets you can make on talent.
If you want to understand our EOR service in depth, talk to our India experts. We have done this for 300+ global companies, and we can tell you fairly quickly which of the eight you are most exposed to.
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.