If you are a CTO or founder evaluating India for an Offshore Development Centre (ODC), you have probably encountered two types of advice: breathless marketing from outsourcing firms promising effortless scale, and horror stories from founders who got burned by vendors delivering subpar work. Neither is useful. What you actually need is a clear-eyed, detail-oriented breakdown of the legal structures, compliance obligations, infrastructure requirements, and realistic cost models involved in setting up an engineering team in India.
This guide is that breakdown. No abstractions, no hand-waving — just the specifics you need to make an informed decision.
Why India: The Case in Numbers
India produces roughly 1.5 million engineering graduates annually. The active software developer population exceeds 5.4 million, making it the second-largest developer talent pool globally behind the United States. But raw numbers alone do not explain why India dominates as an ODC destination. Three structural advantages matter:
English proficiency at scale. India is the world's second-largest English-speaking country. For engineering teams, this means documentation, code reviews, Slack discussions, and sprint ceremonies happen in English by default — not as a trained overlay on a non-English-speaking workforce.
Timezone overlap with both US and EU. India Standard Time (UTC+5:30) creates a natural 3–4 hour overlap with US Eastern Time in the mornings (8:00–11:30 AM IST overlaps with US evening, and Indian afternoon overlaps with early US hours) and a 3–4 hour overlap with Central European Time in the afternoons. This makes synchronous collaboration practical without requiring engineers to work graveyard shifts.
Depth of senior talent. The presence of engineering centres for Google, Microsoft, Amazon, Flipkart, Razorpay, and hundreds of well-funded startups means India has a deep bench of engineers with 8–15 years of experience designing distributed systems, running production infrastructure, and making architecture decisions — not just writing code to spec.
Entity Structure Options: A Comparative Matrix
Before hiring a single engineer, you need to decide how you will operate in India. This is the most consequential decision you will make, and it is often under-analyzed. Here are your five options:
| Structure | Setup Time | Setup Cost | Monthly Overhead | IP Ownership | Compliance Burden | Control Level | Exit Complexity |
|---|---|---|---|---|---|---|---|
| Private Limited Subsidiary | 4–6 months | $60K–$100K | $12K–$20K/month | Direct (you own the entity) | High — you handle all labor law, tax, audit | Full | 12–18 months to wind down |
| Branch Office | 3–5 months | $40K–$70K | $10K–$15K/month | Parent company | High — plus RBI reporting | Full | 6–12 months |
| Liaison Office | 2–4 months | $25K–$40K | $5K–$8K/month | Parent company | Moderate — but cannot generate revenue in India | Limited (no commercial activity) | 3–6 months |
| Employer of Record (EOR) | 1–2 weeks | $0 | $500–$700/person/month | Via contract (weaker) | Low — EOR handles payroll/compliance | Low (no physical office, no team cohesion) | Immediate |
| ODC Partner | 1–4 weeks | $0–$5K | Included in per-person rate | Via contract (strong, with proper MSA) | Low — partner handles compliance | High (you direct the team, partner handles admin) | 30–90 days |
Each option has legitimate use cases. If you are a 500-person company planning to hire 100+ engineers in India over 3 years, a subsidiary makes sense — you will amortize the setup cost and want direct control. If you need 3–5 engineers quickly to validate whether offshore delivery works for your product, an EOR or ODC partner is the rational choice.
Subsidiary vs. ODC Partner: The Decision Framework
For most companies in the 20–200 employee range evaluating their first offshore team, the real decision comes down to two options: set up your own subsidiary, or partner with an established ODC provider.
Setting up a subsidiary requires:
- ✓Engaging a law firm in India for incorporation (Companies Act 2013 compliance)
- ✓Registering with the Registrar of Companies (ROC), obtaining PAN, TAN, GST registration
- ✓Opening a corporate bank account (which alone can take 4–8 weeks)
- ✓Leasing office space, procuring furniture, IT infrastructure, ISP connections
- ✓Hiring an HR team or outsourcing payroll, PF registration, ESIC registration
- ✓Engaging a statutory auditor (mandatory for all Indian companies)
- ✓Filing annual returns with the Ministry of Corporate Affairs
This is not hard, but it is time-consuming and capital-intensive. The total cost to get to "first engineer seated and working" is typically 4–6 months and $60K–$100K.
Working with an ODC partner means the partner already has:
- ✓A registered legal entity with all compliance in place
- ✓Office space with infrastructure (desks, monitors, network, power backup)
- ✓HR processes for hiring, onboarding, payroll, statutory compliance
- ✓A management layer that handles day-to-day operational issues
Your engineers are employed by the partner entity, but they work exclusively for you. You direct their work, set priorities, run standups, and own all work product via a well-structured Master Services Agreement (MSA) with IP assignment clauses.
Legal Considerations You Cannot Ignore
The IT Act 2000 and Amendments
India's Information Technology Act 2000 (amended 2008) governs electronic contracts, digital signatures, and cybercrime. For ODCs, the relevant provisions are:
- ✓Section 43A: Any company handling sensitive personal data must implement "reasonable security practices." The standard referenced is IS/ISO/IEC 27001.
- ✓Section 72A: Disclosure of personal information in breach of a lawful contract is punishable with imprisonment up to 3 years or fine up to ₹5 lakhs.
If your product handles user data (which it almost certainly does), your Indian entity or partner must comply with these provisions.
Digital Personal Data Protection Act 2023 (DPDP Act)
India's DPDP Act, passed in August 2023, is India's equivalent of GDPR. Key provisions affecting ODCs:
- ✓Data Fiduciary obligations: If your Indian team processes personal data of Indian citizens (e.g., an Indian SaaS product), you are a Data Fiduciary and must appoint a Data Protection Officer.
- ✓Cross-border data transfer: The DPDP Act allows transfer of personal data to countries not on the government's restricted list. As of 2026, the restricted list has not been published, meaning transfers to most countries are currently permitted — but this could change.
- ✓Consent management: Processing requires explicit, informed consent. This applies to your product's users, not to your employees (employee data processing has separate provisions under labor law).
- ✓Data retention limits: You cannot retain personal data beyond the purpose for which it was collected.
State-Specific Labor Laws
India's labor law framework is a patchwork of central and state legislation. The four new Labour Codes (2019–2020) — the Code on Wages, Industrial Relations Code, Social Security Code, and Occupational Safety Code — are enacted but not yet universally notified by all states. In practice, this means:
- ✓Uttar Pradesh (where Noida is located) has specific Shops and Commercial Establishments rules governing working hours (9 hours/day, 48 hours/week), overtime, and leave.
- ✓Karnataka (Bangalore) has its own Karnataka Shops and Commercial Establishments Act.
- ✓Telangana (Hyderabad) and Maharashtra (Pune) each have state-specific variations.
Your entity (or your ODC partner's entity) must comply with the state-specific laws of where the office is located, not just central legislation.
Termination Norms
Termination in India is not at-will. For non-workman employees (which covers most software engineers):
- ✓Notice periods of 30–90 days are standard and contractually binding in both directions.
- ✓Many companies include a "notice period buyout" clause allowing either party to pay salary in lieu of notice.
- ✓Termination for cause requires documentation. Wrongful termination claims can be pursued under the Industrial Disputes Act (for workmen) or through civil courts.
- ✓Garden leave clauses are enforceable if they are reasonable in duration and scope.
IP Protection: Getting This Right
Indian Copyright Act 1957
Under Section 17(c) of the Indian Copyright Act, the employer is the first owner of copyright for works created during the course of employment. This is similar to the "work for hire" doctrine in the US. However, there is a critical nuance: this applies to employees, not contractors.
If your Indian engineers are employed by an ODC partner (not by you directly), you need an explicit IP assignment chain:
- ✓Employment agreement between the ODC partner and the engineer must contain an IP assignment clause, assigning all work product IP to the ODC partner.
- ✓MSA/SOW between you and the ODC partner must contain an IP assignment clause, assigning all work product IP from the partner to you.
Without both links in this chain, you have a gap. This is the single most common legal oversight in ODC arrangements.
Trade Secret Protection
India does not have a standalone trade secrets statute. Trade secret protection is enforced through:
- ✓Non-disclosure agreements (contractually enforceable)
- ✓The Indian Contract Act 1872 (breach of confidentiality obligations)
- ✓Common law principles of equity
Practical measures matter more than legal theory: restrict repository access, use VPN with audit logging, enforce endpoint security policies, and include non-solicitation clauses in employment agreements.
HR Compliance: Statutory Obligations
Indian employment comes with mandatory statutory contributions that significantly affect your cost model:
| Statutory Obligation | Employer Contribution | Employee Contribution | Applicability |
|---|---|---|---|
| Provident Fund (PF) | 12% of basic salary (capped at ₹15,000 basic) | 12% of basic salary | All employees earning basic ≤ ₹15,000/month, or all employees if establishment is covered |
| Employee State Insurance (ESIC) | 3.25% of gross salary | 0.75% of gross salary | Employees earning gross ≤ ₹21,000/month |
| Gratuity | ~4.81% of basic salary (accrual) | None | Payable after 5 years of continuous service |
| Professional Tax | Varies by state (max ₹2,500/year) | Deducted from salary | State-specific |
| Labour Welfare Fund | Varies by state | Varies by state | State-specific |
Notice periods in the Indian IT industry are typically:
- ✓Junior engineers (0–3 years experience): 30 days
- ✓Mid-level engineers (3–7 years): 60 days
- ✓Senior engineers (7+ years): 90 days
This has a direct impact on hiring timelines. When you make an offer to a candidate currently employed, you should expect a 30–90 day wait before they join. Some candidates negotiate early release, but do not count on it.
Leave policies are governed by state Shops and Establishments Acts. Typical minimums:
- ✓12–18 days of earned/privilege leave per year
- ✓12 days of sick/casual leave per year
- ✓National and state-specific public holidays: 10–15 days per year
Infrastructure: What an ODC Office Actually Requires
Office Space by City
| City | Grade A Office Rent (per seat/month) | Talent Density | Key Advantage | Key Risk |
|---|---|---|---|---|
| Noida (NCR) | $80–$130 | High (proximity to Delhi talent pool) | Cost-effective, strong infra in Sector 62/63 | Traffic congestion (mitigated by metro) |
| Gurugram (NCR) | $120–$180 | Very High | Dense tech ecosystem, MNC presence | Higher cost, power reliability issues in some areas |
| Bangalore | $130–$200 | Highest | Deepest talent pool in India | Most expensive, highest attrition rates |
| Hyderabad | $90–$140 | High | Growing tech hub, good infra, lower cost | Slightly smaller senior talent pool |
| Pune | $85–$130 | Moderate-High | Good quality of life, strong engineering culture | Smaller scale than Bangalore/Hyderabad |
Technical Infrastructure
A production-grade ODC office requires:
- ✓Dual ISP connections with automatic failover (typically one fiber + one leased line). Minimum 100 Mbps per 20 engineers.
- ✓Power backup: UPS for immediate failover + diesel generator for extended outages. Indian power grids have improved significantly, but 2–4 hour outages per month are still common in some areas.
- ✓Physical security: Biometric access control, CCTV monitoring, visitor management system. Required for SOC 2 Type II compliance if your clients require it.
- ✓Endpoint management: Company-provisioned laptops with MDM (Mobile Device Management), disk encryption, and remote wipe capability.
- ✓Network security: Hardware firewall, VPN concentrator, network segmentation between teams (important if the facility hosts multiple client teams).
Realistic Cost Breakdown: Fully Loaded Cost Per Engineer
This is where most analyses get it wrong — they quote base salaries and ignore the 40–60% overhead on top. Here is a realistic fully loaded cost model for engineers working in an ODC in India:
| Component | Junior (0–3 yrs) | Mid-Level (3–7 yrs) | Senior (7–12 yrs) | Lead/Architect (12+ yrs) |
|---|---|---|---|---|
| Base Salary (annual) | $8K–$14K | $16K–$28K | $30K–$48K | $48K–$72K |
| Statutory Benefits (PF, ESIC, Gratuity, Bonus) | 18–22% of base | 18–22% of base | 15–20% of base | 15–20% of base |
| Health Insurance (group policy) | $300–$500/yr | $400–$600/yr | $500–$800/yr | $600–$1,000/yr |
| Office Seat + Infrastructure | $100–$180/month | $100–$180/month | $100–$180/month | $100–$180/month |
| Equipment (laptop, monitors, amortized) | $50–$80/month | $60–$100/month | $80–$120/month | $100–$150/month |
| Management/HR/Admin overhead | $150–$300/month | $150–$300/month | $150–$300/month | $150–$300/month |
| Fully Loaded Monthly Cost | $1,200–$2,200 | $2,400–$4,000 | $4,200–$6,500 | $6,500–$9,500 |
These numbers assume Noida/Pune/Hyderabad pricing. Bangalore costs run 15–25% higher due to higher salaries and office rents. The "fully loaded" figure includes everything: salary, benefits, office, infrastructure, equipment, HR, admin, and a management layer.
Timezone Strategies That Actually Work
The 4-Hour Overlap Model
The most common and practical approach. Indian engineers work 11:00 AM – 8:00 PM IST, which creates:
- ✓4-hour overlap with US Eastern: 10:30 AM – 2:30 PM EST (roughly)
- ✓3.5-hour overlap with US Pacific: 7:30 AM – 11:00 AM PST (roughly)
This window is used for standups, design discussions, PR reviews, and ad-hoc pairing. The remaining Indian working hours (before and after the overlap) are used for heads-down development, testing, and async collaboration.
The Follow-the-Sun Model
Works well for DevOps, SRE, and support teams. The Indian team handles the daytime shift (IST), then hands off to a US or EU team. This gives you near-24-hour coverage without anyone working nights. Requires disciplined handoff processes: shared runbooks, incident logs, and async communication via structured Slack channels or ticketing systems.
Flex Hours
Some teams allow Indian engineers to choose their own schedule as long as they are available during the overlap window. This improves retention (engineers value flexibility) but requires strong async communication culture and clear documentation practices.
Scaling Cadence: Setting Realistic Expectations
Hiring in India is competitive. The top 10% of candidates have multiple offers. Realistic scaling timelines:
- ✓Month 1: 1–2 engineers (sourcing, interviewing, offer acceptance, notice period serving)
- ✓Month 2–3: 2–4 engineers per month (pipeline matures, referrals start flowing)
- ✓Month 4–6: 3–6 engineers per month (with dedicated recruiting effort)
If someone promises you a 10-person team in 2 weeks, they are either pulling from a bench (which means you are getting whoever is available, not the best fit) or they are overcommitting. The exception is an established ODC partner with an active bench and pre-vetted candidates — in which case 3–5 engineers in 2–4 weeks is achievable for common skill sets.
Risks and Mitigations
Attrition
India's IT industry attrition rate is 18–22% annually. For ODC teams, you can reduce this to 8–12% with:
- ✓Retention bonuses: Annual or biannual bonuses tied to tenure (common: 10–15% of annual salary after 12 months).
- ✓Career growth paths: Engineers need to see a trajectory — from developer to senior developer to tech lead to architect. If your offshore team is stuck executing tickets with no growth, they will leave.
- ✓Interesting work: This matters more than money for senior engineers. Give them architecture problems, not just CRUD tasks.
- ✓Team culture: Build a real team identity — team offsites, learning budgets, conference attendance, internal tech talks.
Quality
- ✓Code reviews: Every PR reviewed by at least one senior engineer. Enforce this in your Git workflow.
- ✓Pair programming: Especially during onboarding and for complex features. Cross-timezone pairing during the overlap window.
- ✓Automated quality gates: CI pipelines with linting, type checking, test coverage thresholds, and security scanning. Do not rely on human discipline alone.
Communication
- ✓Structured async updates: Daily written standups (async) in addition to synchronous standups during the overlap window.
- ✓Decision logs: All architecture and product decisions documented in writing (ADRs, RFCs, or even just Slack threads summarized in Notion/Confluence).
- ✓Escalation paths: Clear process for when someone is blocked — do not let blockers sit for 12+ hours because of timezone gaps.
How an ODC Partner Model Works in Practice
Stripe Systems, a software development company based in Noida, India, founded by Anant Agrawal, is one example of how the ODC partner model operates. Their structure addresses the specific pain points described above:
- ✓Infrastructure ownership: The partner maintains office space with dual ISP connections, power backup, biometric access, and endpoint management — so the client does not need to procure or manage any of this.
- ✓HR and compliance: All statutory compliance (PF, ESIC, gratuity, professional tax, labor law compliance) is handled by the partner. Engineers are employed by the partner entity, with IP assignment flowing to the client via the MSA.
- ✓Management layer: A dedicated delivery manager coordinates between the client and the team, handles day-to-day operational issues (leave management, infrastructure problems, HR queries), and ensures the client team can focus on product and engineering decisions.
- ✓Client ownership of the team: Despite being employed by the partner, the engineers work exclusively for the client. The client directs their work, sets priorities, conducts standups, and has full visibility into code, commits, and delivery metrics. The team functions as an extension of the client's engineering organization.
This model gives clients the speed and simplicity of a partner arrangement with the control and integration of an internal team.
Case Study: A Canadian SaaS Company Evaluates Its Options
Company profile: A 40-person Canadian SaaS company (Series A, $8M ARR) building a B2B project management platform. The engineering team is 14 people, all based in Toronto. The VP of Engineering needs to add 10 engineers (4 backend, 3 frontend, 2 QA, 1 DevOps) within 6 months without blowing through the remaining runway.
Options Evaluated
The company evaluated three approaches:
Option A: Own Subsidiary in India
- ✓Engage an Indian law firm for incorporation under the Companies Act 2013
- ✓Register a Private Limited company, obtain PAN, TAN, GST registration
- ✓Open a corporate bank account
- ✓Lease office space in Noida (1,500 sq ft for 10 engineers)
- ✓Hire an HR/admin coordinator locally
- ✓Begin recruiting
Option B: Employer of Record (EOR) via Remote/Deel
- ✓Sign up with an EOR platform
- ✓Hire engineers as EOR employees
- ✓Engineers work from home or co-working spaces
- ✓EOR handles payroll, compliance, and benefits
Option C: ODC Partner
- ✓Sign MSA with an established ODC partner
- ✓Define role requirements and tech stack
- ✓The partner sources, screens, and presents candidates
- ✓Client conducts final interviews and selects engineers
- ✓Engineers are onboarded at the partner's office in Noida
Cost Comparison (10 Engineers, First 12 Months)
| Cost Component | Own Subsidiary | EOR (Remote/Deel) | ODC Partner |
|---|---|---|---|
| Incorporation/Setup | $80,000 | $0 | $0 |
| Office Lease + Fitout | $45,000 (year 1) | $0 (remote only) | Included |
| IT Infrastructure | $25,000 | $0 (engineers use own equipment) | Included |
| Monthly Admin/HR/Compliance | $15,000/month | $500–$700/person/month ($5K–$7K total) | Included |
| Recruiting Costs | $30,000–$50,000 (agencies) | $10,000–$20,000 | Included |
| Engineer Salaries + Benefits | $35,000–$45,000/month (fully loaded) | $35,000–$45,000/month + EOR fees | $45,000–$65,000/month (all-inclusive) |
| Total Year 1 Cost | $620K–$770K | $540K–$660K | $540K–$780K |
| Ongoing Monthly Cost (Year 2+) | $50K–$60K/month | $40K–$52K/month | $45K–$65K/month |
Timeline Comparison
| Milestone | Own Subsidiary | EOR | ODC Partner |
|---|---|---|---|
| Legal entity ready | 4–6 months | Immediate (not needed) | Immediate (partner's entity) |
| Office operational | 2–3 months after entity | N/A (remote) | 1–2 weeks |
| First engineer starts | 6–8 months from decision | 4–8 weeks (notice period) | 3–6 weeks |
| Full team (10 engineers) | 10–14 months | 4–7 months | 3–6 months |
| Fully productive | 14–18 months | 6–9 months | 5–8 months |
Why the ODC Model Was Chosen
The company chose the ODC partner model for three reasons:
- ✓
Speed to productivity. The first 3 engineers were seated and writing code within 4 weeks — working from the Stripe Systems office in Noida. The subsidiary option would have had them still dealing with incorporation paperwork at that point. For a Series A company, time-to-value is existential.
- ✓
Operational simplicity. The VP of Engineering did not want to become an expert in Indian labor law, PF compliance, or office lease negotiations. With the ODC model, all of that was handled by the partner. The VP's involvement was limited to defining role requirements, interviewing candidates, and managing the team's technical output.
- ✓
Physical office and team cohesion. The EOR option was cheaper on paper, but engineers would be fully remote and distributed across different cities. The company wanted a co-located team that could whiteboard together, pair program in person, and build team cohesion. The ODC model provided this without requiring the company to set up and manage its own office.
- ✓
Risk mitigation. If the offshore experiment failed, the company could wind down the engagement in 60–90 days with no stranded assets (office lease, equipment, legal entity). With a subsidiary, unwinding would take 12–18 months and cost $30K–$50K in legal and accounting fees.
Outcome (12 Months Later)
After 12 months, the team reached full strength at 10 engineers. Sprint velocity had stabilized, the team owned two full microservices end-to-end, and attrition was zero (helped by strong onboarding, interesting work, and the cohesion of a co-located team). The fully loaded cost was approximately $55,000/month for 10 engineers — roughly 65% less than hiring equivalent talent in Toronto.
Conclusion
Setting up an ODC in India is not complicated, but it is detail-intensive. The entity structure decision, IP protection chain, HR compliance obligations, and infrastructure requirements all need to be addressed deliberately. For most companies in the 20–200 employee range making their first move into India, partnering with an established ODC provider is the fastest, lowest-risk path to a productive engineering team. The key is to choose a partner that gives you operational simplicity without sacrificing your control over the team's technical direction, work output, and engineering culture.
The specifics matter. Get them right, and you will build a team that delivers real engineering value. Get them wrong, and you will spend your time fighting operational fires instead of building product.
Ready to discuss your project?
Get in Touch →