Published by iValuePlus Services on April 22, 2026

Why "Just Hire Someone in India" Is Riskier Than It Sounds

India is one of the most compelling talent markets in the world for US companies. Deep STEM talent, strong English proficiency, a mature startup and services ecosystem, and salaries that run 50–70% below US equivalents — the value proposition is genuinely hard to argue with.

And yet, US companies make costly mistakes every year by treating offshore hiring in India as simpler than it is. The founders who wire salary to a personal Indian bank account. The startup that “hired a contractor” who has worked exclusively for them, full-time, for two years. The company that didn’t realize their India-based sales lead was creating Permanent Establishment tax exposure. The team that shipped customer data to an offshore team without a Data Processing Agreement.

These aren’t edge cases. They’re common. And they’re entirely avoidable.

This guide gives US companies — founders, COOs, CTOs, HR leaders — a structured pre-hire checklist covering every critical area to verify before building an offshore team in India. Whether you’re hiring your first India-based engineer or scaling from 5 to 50, this is the due diligence framework that keeps you compliant, protected, and operationally set up to succeed.

Check 1: Legal Hiring Structure — Entity, EOR, or Staff Augmentation?

The first question any US company must answer before a single interview is conducted: through what legal structure will these workers be employed?

Indian employment law requires every worker to have a legally registered employer in India. You cannot employ Indian workers directly from the US without an Indian legal entity. You have three primary options:

Option A: Set Up Your Own Indian Entity

You register a Private Limited Company (Pvt. Ltd.) in India — the most common structure for foreign companies with significant India operations. This gives you full control: you hire directly, manage payroll, and own all employment relationships.

This is the right choice when:

You plan to have 20+ employees in India long-term
You want direct brand presence and the ability to sign Indian contracts
You’re prepared for the 3–6 month setup timeline and ongoing compliance obligations (annual filings, audits, director requirements)

This is the wrong choice when:

You need to hire in the next 4–8 weeks
Your India headcount will stay under 15–20 people
You don’t have local legal and accounting resources to manage entity compliance

Option B: Employer of Record (EOR)

An EOR is a licensed Indian company that employs workers on your behalf. The EOR is the legal employer — handling contracts, payroll, statutory contributions, and compliance. You manage the work.

Best for: Companies wanting to hire 1–20 people quickly without entity overhead.

Option C: Staff Augmentation Partner

Similar to EOR but typically more integrated — the staffing partner manages HR, sourcing, and onboarding support in addition to EOR functions. Your team members work embedded in your organization, under your direct management.

Best for: US companies that want a single partner managing talent acquisition and employment compliance, with ongoing HR support.

Can a US company hire in India without setting up a legal entity?

Yes. Through an Employer of Record (EOR) or staff augmentation partner, the Indian partner company serves as the legal employer. The US company manages day-to-day work and direction without needing its own Indian registration. This approach is compliant with Indian labor law, enables hiring within weeks, and is the standard model for US companies building offshore teams of under 20 people.

What to verify before proceeding:

Is your intended EOR or staff augmentation partner actually registered in India with a valid PAN, EPFO registration, and Shops & Establishments Act compliance for their state?
Do they have audited payroll records and compliance history?
Is their MSA (Master Service Agreement) specific about who is the legal employer?

Check 2: Worker Classification — Employee vs. Independent Contractor

This is the compliance failure that catches the most US companies off guard — and carries the most direct legal risk.

The Contractor Temptation

Many US companies, accustomed to engaging US freelancers as 1099 contractors, apply the same thinking to India. They find a talented engineer in Pune, agree on a monthly rate, wire payment to their personal account, and call them a “contractor.” It feels familiar. It’s fast. And in India, it’s frequently illegal misclassification.

How Indian Authorities Evaluate Classification

Indian labor law — particularly under the Code on Wages (2019) and various state-level Shops and Establishments Acts — looks at the substance of the working relationship, not what you call it in a contract. Indicators of an employment relationship include:

Works exclusively (or primarily) for one company
Works full-time hours on an ongoing basis
Follows directions on how work is performed (not just what to deliver)
Uses company-provided tools or systems
Has no independent business or other clients

If your “contractor” checks most of these boxes, they are functionally an employee under Indian law — regardless of what your contract says.

Consequences of Misclassification

Back payment of statutory contributions: PF, ESI, gratuity — potentially years of unpaid contributions
Tax authority penalties on both the worker and the engaging company
Employee rights claims: leave encashment, notice period pay, termination claims
Reputational and legal exposure that can complicate future India operations or entity setup

The Rule of Thumb

Dedicated full-time worker, working for you for more than 3 months? That’s an employment relationship in India. Structure it as one — through an EOR or staff augmentation partner — from day one.

True independent consultants (delivering defined projects, working for multiple clients, setting their own hours and methods) can legitimately be engaged as contractors — but they’re the exception, not the norm for offshore team building.

Check 3: Indian Labor Law — What US Companies Are Actually Liable For

India’s labor law landscape is complex, state-specific, and actively enforced. Even through an EOR, US companies benefit from understanding what protections Indian workers are entitled to — because these shape team management decisions, hiring timelines, and exit processes.

The Four Labour Codes (2020)

India consolidated 29 legacy labor laws into four codes:

Code on Wages — covers minimum wage, overtime, payment of wages
Industrial Relations Code — covers standing orders, dispute resolution, layoffs
Code on Social Security — covers PF, ESI, gratuity, maternity benefit
Occupational Safety, Health and Working Conditions Code — workplace safety standards

Implementation is state-by-state and ongoing as of 2026. Your EOR partner should be operating in compliance with both legacy law and applicable code provisions.

Key Protections US Companies Must Plan Around

Minimum Wage: Each Indian state sets its own minimum wage by skill category. Metro cities (Bangalore, Mumbai, Hyderabad, Pune) have higher minimums. All roles must meet or exceed the applicable minimum wage.

Working Hours: Standard is 8 hours/day, 48 hours/week. Overtime is payable at 2x the ordinary rate. This matters for offshore teams asked to cover US hours — ensure overtime is structured and compensated correctly.

Maternity Benefit Act: Female employees with 80+ days of service are entitled to 26 weeks of fully paid maternity leave. Smaller companies (under 50 employees) are exempt from providing crèche facilities but not from the leave benefit. Budget and plan for this.

Shops and Establishments Act: State-specific regulation of working conditions, leave entitlements, working hours, and employment records. Your EOR must be registered under the applicable state’s act.

Standing Orders (Industrial Employment Act): Companies with 100+ workers must have certified standing orders defining conditions of service. Less relevant for small offshore teams, but important context at scale.

Practical implication for US companies: Indian labor law is protective of workers. This isn’t a problem — it’s a planning input. Your offshore team will expect their statutory rights to be honored. Any EOR or staff augmentation partner worth working with will already be honoring them.

Check 4: Payroll, Statutory Benefits, and Tax Obligations

Even if your EOR handles payroll execution, US companies need to understand what’s being paid — because it affects your total cost model and your team’s experience.

Statutory Contributions — Non-Negotiable

Provident Fund (PF/EPF): Both employer and employee contribute 12% of basic salary. Basic salary is typically set at 40–50% of total CTC. For a worker earning ₹1,00,000/month CTC, this means roughly ₹20,000–₹24,000/month basic, with ₹2,400–₹2,880/month employer PF contribution on top.

EPFO (Employees’ Provident Fund Organisation) filings are mandatory. Non-compliance triggers penalties and interest.

Employee State Insurance (ESI): Applies to workers earning up to ₹21,000/month gross. Employer contributes 3.25% of gross wages; employee contributes 0.75%. Provides medical, maternity, and disability coverage. Register with ESIC (Employees’ State Insurance Corporation).

Gratuity: After 5 years of continuous service, employees are entitled to a gratuity payment equal to 15 days’ salary per year of service. For offshore teams, this is a long-term accruing liability — your EOR should be provisioning for it.

Professional Tax: A small state-level tax (up to ₹2,500/year) deducted from salary and remitted to state government.

TDS (Tax Deducted at Source): Your EOR deducts income tax from salary at applicable rates and remits quarterly. Annual Form 16 is issued to the employee.

Leave Entitlements

Leave Type	Typical Entitlement	Notes
Earned/Privilege Leave	12–18 days/year	Accrues, encashable on exit
Sick Leave	6–12 days/year	State-specific
Casual Leave	6–12 days/year	Usually non-encashable
National Holidays	3 days (fixed)	Republic Day, Independence Day, Gandhi Jayanti
State + Festival Holidays	7–12 days/year	Varies by state; often includes Diwali, Holi, Eid
Maternity Leave	26 weeks (paid)	Mandatory under Maternity Benefit Act

Total leave days a typical Indian employee takes: 35–45 days/year including all holidays. US companies often underestimate this when projecting offshore team productivity.

Payroll Structure: CTC vs. Take-Home

Indian compensation is expressed as CTC (Cost to Company) — the total annual employer spend. This includes basic salary, allowances (HRA, food, transport, medical), and employer statutory contributions.

Take-home pay is CTC minus employee statutory contributions, TDS, and professional tax. A ₹12 LPA (lakh per annum) CTC translates to roughly ₹75,000–₹85,000 per month in-hand, depending on structure.

What to verify with your EOR partner:

Are statutory contributions included in the quoted CTC, or added on top?
Is gratuity provisioned monthly?
Are TDS returns filed quarterly?
Are Form 16s issued annually?

Check 5: Permanent Establishment (PE) Risk

Permanent Establishment is a tax concept that determines whether a foreign company has sufficient presence in a country to be taxable there. For US companies with India-based offshore teams, PE risk is real — and underappreciated.

What Triggers PE Risk in India

Under the India–US Double Taxation Avoidance Agreement (DTAA) and Indian tax law, a US company may be deemed to have a PE in India if:

India-based employees have the authority to conclude contracts on behalf of the US company
India-based employees habitually exercise that authority
There is a fixed place of business in India used by the US company (an office, even informal)
India-based staff are performing the core income-generating activities of the US company’s business

What Does Not Trigger PE (When Structured Correctly)

India-based employees performing preparatory or auxiliary functions (research, internal development, support)
Workers employed by an EOR or staffing partner — not directly by the US entity
No fixed place of business in India attributable to the US company
No authority to bind the US company in contracts

How do US companies avoid permanent establishment risk when hiring in India?

US companies minimize PE risk by: (1) ensuring India-based staff are employed by an EOR or staffing partner, not directly by the US entity; (2) explicitly prohibiting offshore staff from entering contracts or acting as legal agents on behalf of the US company; (3) avoiding fixed office space in India attributable to the US entity; and (4) structuring offshore roles as internally-facing (development, support, analysis) rather than client-facing commercial roles.

Practical steps:

Include explicit language in your MSA and the worker’s employment agreement that they are not authorized to bind the US company in any contract
Do not provide India-based staff with US company email domains used to solicit or close client business in India (internal team accounts for project work are different)
Consult a cross-border tax advisor before placing client-facing roles in India

Check 6: Intellectual Property Protection

IP is the one area where a single contractual gap can have irreversible consequences.

The Default Position Under Indian Law

India’s Copyright Act (1957) provides that work created by an employee in the course of employment belongs to the employer. However, this applies to a direct employment relationship. When work is created by someone employed by an EOR — where the legal employer is the EOR, not your US company — the automatic assignment to your company is not guaranteed without an explicit contractual clause.

What You Must Have in Writing

In the Client Services Agreement with your EOR/partner:

Explicit IP assignment: all work product, code, designs, data, and inventions created by augmented staff in the scope of their work for you is assigned to your company
Moral rights waiver (where applicable)
Confirmation that the EOR will include equivalent terms in the individual employment contracts

In the individual employment contracts (ask to see a sample):

IP assignment clause covering all work created during the engagement
Obligation to disclose and transfer any work created on company systems or time
Prohibition on using company IP for any other purpose

Additional protections:

Ensure software is not developed using open-source libraries with copyleft licenses (GPL, AGPL) without a clear policy — this can affect your ability to maintain proprietary code
Establish a clear policy on pre-existing IP the worker may bring to the role

Trade Secrets and Confidential Information

India’s trade secret protection relies primarily on contractual law (not a specific Trade Secrets statute, unlike the US). This means your NDA and confidentiality provisions in the employment agreement are your primary protection.

Ensure:

All offshore team members sign NDAs before accessing any proprietary information
NDAs are governed by Indian law (for enforceability in India) with a dispute resolution mechanism
NDAs cover not just “trade secrets” but also source code, customer data, product roadmaps, financial information, and business strategies

Check 7: Data Security and Privacy Compliance

Data security is a growing concern for US companies with offshore teams — both from a client obligation standpoint and from India’s evolving regulatory landscape.

India’s Digital Personal Data Protection Act (DPDP Act, 2023)

India’s DPDP Act came into force in 2023 and imposes obligations on any entity processing personal data of Indian residents. If your offshore team in India handles personal data of Indian users (common for consumer tech companies, fintech, healthtech), you must:

Identify and document your data processing activities
Ensure a lawful basis for processing personal data
Implement data minimization and purpose limitation
Honor data principal (user) rights (access, correction, erasure)
Report data breaches to the Data Protection Board within prescribed timelines

For US companies: Even if your primary compliance focus is GDPR or CCPA, your offshore team’s processing of Indian user data must also comply with DPDP Act requirements.

Cross-Border Data Transfer Obligations

Your offshore team in India will inevitably access US-side systems, customer databases, and potentially HIPAA-regulated or SOC 2-governed data. Before giving access:

Conduct a data inventory: what data will offshore team members access, process, or store?
Implement role-based access controls — offshore team should only access data necessary for their role
Execute Data Processing Agreements (DPAs) with your EOR/staffing partner covering data handling obligations
Ensure offshore systems meet your security standards: encryption at rest and in transit, MFA, VPN access policies, endpoint security

Practical Security Baseline

Security Control	Minimum Standard
Access management	Role-based access; MFA on all systems
Device policy	Managed devices or BYOD policy with MDM enrollment
Data transfer	Encrypted channels only; no personal email for work data
Offboarding	Immediate access revocation on exit
Background checks	Criminal record verification at minimum; identity verification
NDA and data handling agreements	Signed before any system access

Check 8: Notice Periods and Exit Obligations

US companies frequently underestimate how notice periods and exit processes work in India — and it creates hiring timeline surprises and exit management friction.

Notice Periods: Longer Than You Expect

Most Indian employment contracts at mid-to-senior level specify 30–90 days notice. This is not a formality — it is legally binding, and “gardening leave” (working the notice period) is common.

What this means for your hiring timeline:

If you interview and select a candidate in Week 1, and they have a 60-day notice period, they join in Week 9 at the earliest
Negotiated early releases happen, but are not guaranteed and depend on the outgoing employer’s willingness
Build 30–60 day notice periods into your hiring timeline as the default, not the exception

What this means for exits:

When you need to let go of an offshore team member, your EOR must follow the contractual notice period
Paying in lieu of notice is an option but must be specified in the contract
For terminations for cause, specific documentation and process requirements apply under Indian labor law — do not treat these as at-will terminations

Retrenchment Compensation

Under the Industrial Disputes Act (and its successor code), companies with more than 100 workers must obtain government permission before retrenching workers — and must pay retrenchment compensation (15 days’ wages per year of service) to retrenched employees. This threshold matters if your India offshore team grows large.

For teams under 100, retrenchment compensation is still good practice and may be contractually required.

Statutory Dues on Exit

Any employee exit must be managed to ensure full and timely payment of:

Earned leave encashment (any accrued, unused earned leave)
Gratuity (if 5+ years of service)
PF settlement (employee and employer contributions)
Final salary for the notice period worked
Experience/relieving letter (a formal document certifying employment — expected by departing employees and their next employers)

Your EOR handles all of this. But understand what’s required so exit timelines are realistic.

Check 9: Offshore Partner Due Diligence

Choosing the wrong offshore staffing or EOR partner is the single highest-leverage mistake a US company can make. A noncompliant partner doesn’t just create operational friction — it transfers legal risk to you.

What to Verify About Any Partner

Legal and compliance registration:

Registered Indian company (can verify on MCA21 portal)
EPFO and ESIC registration numbers (verifiable on respective government portals)
Valid PAN and GST registration
Shops & Establishments Act registration for their state

Payroll compliance track record:

Ask for a sample payslip structure (redacted)
Ask how TDS returns are filed and when
Ask about their process for handling statutory audits
Ask for references from US clients who have been through an employee exit with them

Talent capabilities:

Do they have a pre-vetted talent bench, or do they post to Naukri/LinkedIn and wait?
What is their average time-to-shortlist for a role similar to yours?
What is their vetting process? (technical tests, English communication screening, background checks)
What is their replacement policy if a hire doesn’t work out in the first 60–90 days?

Contract terms to scrutinize:

IP assignment — explicit, comprehensive, covers all work product
Exclusivity of the worker’s time (are they billing the same person to multiple clients?)
Data protection and confidentiality obligations
Exit and replacement provisions
Markup transparency (CTC vs. service fee clearly separated)

Red flags to walk away from:

Vague answers about compliance registration
“All-in” pricing with no breakdown between CTC and fee
No sample employment contract available for review
No references from US clients
Offshore workers not receiving payslips or Form 16

Check 10: Contracts, NDAs, and Confidentiality Infrastructure

A comprehensive contract stack is not optional — it is the foundational protection layer for your US company’s interests across IP, confidentiality, non-competition, and dispute resolution.

The Contract Stack You Need

1. Master Service Agreement (MSA) with your EOR/partner Governs the entire relationship between your US company and the staffing partner. Must include:

Scope of services and deliverables
IP assignment (all work product to your company)
Confidentiality and data protection obligations
Representations on labor law compliance
Indemnification (partner indemnifies you for their employment compliance failures)
Governing law and dispute resolution
Termination provisions (notice, cure periods)

2. Statement of Work (SOW) per engagement Role-specific addendum: job title, responsibilities, reporting structure, duration, fees.

3. Individual employment agreements (between EOR and worker) Your EOR uses these. You should review a template to confirm:

IP assignment to your company (not just to the EOR)
Non-disclosure obligations covering your confidential information
Non-solicitation clause (prevents the worker from poaching your clients or other team members post-engagement)
Notice period terms
Governing law: Indian law, jurisdiction: relevant Indian state

4. Non-Disclosure Agreements Even if the employment contract contains confidentiality clauses, a standalone NDA signed by each team member before accessing your systems adds a layer of protection and clearly documents consent.

5. Non-Compete Clauses — A Nuance Under Indian contract law (Contract Act, 1872, Section 27), post-employment non-compete clauses are generally unenforceable as restraints of trade. Non-solicitation clauses (which are narrower) and in-employment non-competes are generally enforceable. Structure your contracts accordingly — rely on IP assignment and NDA, not post-employment non-compete, for core protection.

Check 11: Time Zone, Communication, and Infrastructure Readiness

Compliance protects you legally. But operational readiness is what determines whether your offshore team actually performs.

Time Zone Math

India has a single timezone: IST (Indian Standard Time), UTC+5:30. There is no daylight saving adjustment.

The practical implication: There is limited natural overlap between standard US and India working hours. Most US companies running offshore teams in India use one of three models:

Model A — Async-first: Offshore team works standard IST hours (9am–6pm IST). Work is handed off, reviewed asynchronously. Daily standups happen at the edge of the India workday (3pm–5pm IST = 9:30am–11:30am ET). Works well for development, data, content, and back-office roles.

Model B — Shifted India hours: Offshore team members work afternoon/evening IST hours (1pm–10pm IST or similar) to overlap with US morning. Works for customer success, real-time collaboration roles, or US teams that need daily sync. Commands a 10–20% salary premium for candidates willing to work shifted hours.

Model C — Follow-the-sun: Teams hand off work at end of each day to the other timezone, enabling near-continuous progress. Requires strong documentation discipline.

Before hiring, decide and document your model. Be explicit with candidates about expected hours — don’t hire someone on standard IST hours and then expect them to be on a 9am PT standup.

Communication Infrastructure Checklist

Before your first offshore team member starts:

Documented async communication norms (response time expectations, channels for different urgency levels)
Video meeting platform and license (Zoom, Google Meet, Teams)
Asynchronous documentation tools (Confluence, Notion, Linear)
Project/task management system (Jira, Asana, Linear, Shortcut)
Version control and CI/CD access provisioned
Secure communication channels (Slack with appropriate access controls)
VPN policy and implementation (required if accessing US systems)

Hardware and Equipment Policy

Decide before hiring: Do you provide equipment (shipped to India or procured locally) or do you use BYOD (Bring Your Own Device) with MDM enrollment?

Laptop procurement in India: Your EOR can procure and asset-manage hardware locally, which avoids customs complications. Budget ₹80,000–₹1,50,000 ($950–$1,800) per laptop depending on spec.

Check 12: Cultural Integration and Team Cohesion

This is the check that many companies skip because it feels “soft” — and then struggle with because it affects performance, retention, and team morale.

Communication Style Differences

Indian professional culture tends toward:

Indirect communication: Problems, disagreements, and “I don’t know” are often communicated indirectly. A team member saying “we can try” may mean “this is very difficult.” Training managers to ask specific questions and create psychological safety for direct feedback is important.
Hierarchical deference: Team members may be reluctant to push back on a manager’s decision even when they have valuable insight. Explicitly invite dissent and critical thinking.
Formality: Especially in early-stage relationships, Indian professionals tend to be more formal than US startup culture. A deliberate “we’re informal here, please call me [first name]” goes a long way.

Festivals and Holidays

India has a large number of national and regional holidays — and they vary significantly by state and religion. A Bangalore-based team will observe Kannada Rajyotsava and certain South Indian festivals; a Pune team will observe different regional holidays. Build a shared holiday calendar that accommodates this without requiring Indian team members to “use personal leave” for major cultural festivals.

Retention and Belonging

Offshore team members who feel like “outsiders” or “just contractors” have lower engagement and higher attrition. Practices that improve retention:

Include offshore team members in all-hands meetings
Recognize work publicly in company channels
Send welcome packages for new joiners (even shipped internationally)
Run virtual team events that include India-based team members (not just US-team happy hours on US-morning time)
Create career progression paths — make clear that offshore roles are not a dead end

Manager Readiness

If the US-side manager has never managed across cultures or timezones, invest in a short cultural briefing before the offshore team member starts. This doesn’t need to be elaborate — even a 2-hour workshop covering communication norms, feedback styles, and timezone etiquette dramatically improves the first 90 days.

Checklist: What US Companies Must Verify Before Hiring an Offshore Team in India

#	Check	Key Question
1	Legal hiring structure	Entity, EOR, or staff augmentation — which fits your situation?
2	Worker classification	Are roles structured as employment (not contractor)?
3	Indian labor law	Does your EOR comply with all applicable codes and acts?
4	Payroll and statutory benefits	Is PF, ESI, gratuity, TDS, and leave correctly structured?
5	Permanent establishment risk	Are offshore staff restricted from acting as business agents?
6	IP protection	Is there an explicit IP assignment clause in all contracts?
7	Data security and privacy	Are DPAs in place? Is data access scoped and secured?
8	Notice periods and exits	Are notice period timelines factored into hiring and exit plans?
9	Partner due diligence	Is your EOR/partner compliant, referenced, and transparent?
10	Contracts and NDAs	Is the full contract stack in place before system access?
11	Time zone and infrastructure	Is your communication model defined and tooling ready?
12	Cultural integration	Are managers briefed and integration practices in place?

FAQ

Q: Can a US company hire employees in India without setting up an Indian entity?

Yes — through an Employer of Record (EOR) or staff augmentation partner. The partner’s Indian entity serves as the legal employer, handling all compliance, payroll, and statutory obligations. The US company directs the work. This is the standard approach for US companies building offshore teams of under 20 people in India.

Q: What is the difference between hiring a contractor and an employee in India?

In India, an independent contractor is someone who works independently for multiple clients, sets their own methods, and delivers defined outputs. An employee works under an employer’s direction, typically full-time and exclusively. If a worker is dedicated full-time to your company and follows your direction, Indian law likely treats them as an employee — regardless of what the contract says. Misclassification creates liability for back contributions, penalties, and employment claims.

Q: What are the biggest compliance risks when hiring offshore in India?

The top compliance risks are: worker misclassification (contractor vs. employee), failure to pay statutory contributions (PF, ESI, TDS), Permanent Establishment tax exposure, missing IP assignment provisions, and inadequate data security agreements. Most are preventable with the right EOR partner and properly drafted contracts.

Q: How long does it take to hire and onboard an offshore team member in India?

Typically 4–7 weeks: 1–2 weeks for sourcing and interviews, then 30–60 days notice period at the candidate’s current employer, then onboarding. If candidates are immediately available, this compresses to 2–3 weeks. Build notice period timelines into your hiring plan as the default expectation.

Q: How do I protect my company’s intellectual property when working with an offshore team in India?

Use explicit IP assignment clauses in both your Master Service Agreement with the EOR partner and in the individual employment contracts. These clauses should specifically assign all work product, code, designs, and inventions to your company. Also use NDAs covering source code, customer data, and business strategy. Post-employment non-competes are generally unenforceable in India — rely on IP assignment and NDA for protection.

Q: What taxes and statutory contributions are required for offshore employees in India?

Mandatory contributions include: Employer PF (12% of basic salary), ESI (3.25% of gross wages for eligible employees), Professional Tax (state-level, up to ₹2,500/year), and TDS deduction and remittance. After 5 years, gratuity (15 days’ salary per year of service) becomes payable. Your EOR handles all of these — but they affect total cost and must be factored into your budget.

Q: What is Permanent Establishment risk and how does it affect US companies hiring in India?

PE risk means Indian tax authorities could deem your US company to have a taxable business presence in India, making a portion of your global revenue subject to Indian corporate tax. This risk is triggered when India-based employees have authority to sign contracts on your behalf, conduct core income-generating activities, or when your company has a fixed business location in India. Structure offshore roles as internally-facing and ensure staff are employed through an EOR (not directly by your US entity) to significantly reduce PE exposure.

Q: Do US companies need to follow Indian data privacy laws when hiring an offshore team?

Yes, where relevant. India’s DPDP Act (2023) applies to processing of personal data of Indian residents. If your offshore team handles Indian user data, you must comply with the Act’s requirements on data processing, breach notification, and data principal rights. Separately, cross-border data transfers to your offshore team require appropriate data processing agreements and security controls regardless of jurisdiction.

Q: How do US companies manage time zone differences with offshore teams in India?

Most effective teams adopt one of three models: async-first (minimal required overlap, strong documentation discipline), shifted India hours (offshore team works afternoon/evening IST to overlap with US morning — common for collaboration-heavy roles), or follow-the-sun (work handed off at end of each day). Define your model before hiring and communicate expected hours clearly to candidates.

Q: What should I look for when choosing an offshore staffing or EOR partner in India?

Key criteria: verified compliance registration (EPFO, ESIC, PAN, GST); transparent pricing with CTC and service fee separated; IP assignment terms in standard contracts; US client references; clear talent vetting process; replacement guarantee if a hire doesn’t work out; and a track record of managing employee exits correctly.

Ready to Build Your Offshore Team the Right Way?

iValuePlus helps US companies hire compliant, high-performing offshore teams in India — without the legal risk, compliance complexity, or operational headaches.

We handle:

Employer of Record and staff augmentation services
End-to-end payroll, statutory benefits, and compliance
Talent sourcing, vetting, and onboarding
Ongoing HR support and manager enablement

Get in touch with us today!

BOT Model for Software Development Teams: A Practical Guide for CTOs

Learn how the BOT Model for Software Development Teams helps...

Offshore Development Team for Startups: Benefits, Risks & Costs

Should your startup hire an offshore development team? Explore real...

Staff Augmentation for Startups: Can You Hire 2–3 Developers Without Setting Up an Office?

Hire 2–3 offshore developers from India without setting up an...

iValuePlus Services

iValuePlus is a one-stop solution to address all your needs to access, build and grow your business in the Indian market which is cost-effective & has a huge talent pool. Established in 2019 as a ‘Business Solution provider', our team has delivered successful growth projects in the international market. Our services include setting up ODC (offshore development center), Staff Augmentation, Talent Acquisition, Digital Marketing, in the IT/ITES domain.