EOR vs Captive Entity Cost India: Why SaaS Firms Overpay 40%

The 40% cost delta nobody puts in the spreadsheet

A US B2B analytics founder came to Expante Global Consulting with a straightforward brief: stand up a 30-engineer team in Delhi, own the IP cleanly, and keep per-seat cost below $2,500 a month all-in. The initial model his finance team had built assumed salaries, statutory contributions, a small office and recruiting fees. On paper the captive entity route looked cheaper than the EOR quotes he had collected, which averaged $2,100 per seat fully loaded.

When we rebuilt the cost model line by line, the captive structure landed at $3,200 per engineer per month by month twelve. The EOR model stayed flat at $2,100. The 40% gap was not a rounding error or a consulting mark-up. It was the sum of fourteen expense categories that do not appear in a salary-only model but become real cash outflows the moment you incorporate a private limited entity in India and hire your first employee.

This article walks through where that delta hides, which line items catch US and EU operators by surprise, and how to model build versus EOR decisions when the goal is predictable unit economics rather than theoretical control.

Why founders assume captive is cheaper

Most US SaaS operators build their India cost model by Googling median salaries for React developers in Bangalore, applying a 1.15x multiplier for PF and ESI, adding $150 per seat for co-working space, and calling it done. The resulting number is typically 50 to 60% below a comparable US hire, so the business case feels obvious.

The EOR quote, by contrast, arrives as a single bundled rate: $2,000 or $2,200 per month per employee, everything included. It looks expensive against the salary-only captive math, and the founder's instinct is that paying someone else to handle payroll cannot possibly justify a 35% premium.

What that comparison misses is that the captive model requires you to hire and pay for every function the EOR is bundling into their rate: HR manager, payroll processor, statutory auditor, GST consultant, legal retainer, recruiting coordinator, office manager, and often a part-time finance lead to close the books each month under Indian GAAP. These are not engineering seats. They do not write code or ship features. They exist to keep the entity compliant, the payroll accurate, and the team operational. In a 30-person team the overhead ratio can reach six or seven non-engineering FTEs, each carrying salary, benefits, and their own onboarding cost.

The fourteen line items that add 40%

When we model captive entity costs for clients we break the structure into three buckets: people costs, infrastructure and fixed overheads, and compliance and professional services. Here is where the gap opens:

People costs beyond salary

• Provident Fund, ESI, gratuity accrual, and professional tax add roughly 14 to 16% on top of gross salary, not the 10% many operators assume.
• Notice period payouts and earned leave encashment create a balance sheet liability that grows every quarter. By year two this can represent 8% of annual payroll.
• Recruiting agency fees in Indian metro markets run 8.33 to 10% of first-year salary per hire. A 30-person team turning over 18% annually means 5.4 replacement hires, or $35,000 in agency fees.
• Onboarding equipment (laptop, monitor, peripherals) costs $1,100 per seat if you want performance on par with US-issued hardware.

Infrastructure and fixed overheads

• Office lease deposits in Bangalore, Pune, or Gurgaon equal three to six months' rent, paid upfront. For a 35-seat space that is $18,000 to $36,000 locked as a deposit, not an expense, but it is cash out of the business on day one.
• Payroll software, HRIS, attendance tracking, and benefits administration platforms add $90 to $140 per employee per year if bought separately. EOR providers amortise these across hundreds of clients; you carry the full subscription.
• Facilities management, internet, utilities, and cleaning services run $40 to $65 per seat per month in a managed office.

Compliance and professional services

• Statutory audit fees for a private limited company range from $3,500 to $6,000 annually depending on turnover and complexity.
• GST return filing, TDS reconciliation, and transfer pricing documentation (if you recharge the Indian entity from the US parent) require a part-time CA on retainer, typically $800 to $1,200 per month.
• Legal retainer for employment contracts, IP assignment templates, non-competes, and contractor agreements runs $1,500 to $2,500 per quarter.
• Corporate secretarial work (board resolutions, ROC filings, annual return, DIN updates) costs another $1,800 to $2,400 per year.

When you sum these categories across a 30-engineer team and spread them monthly, the delta between gross payroll and true all-in cost per seat is $900 to $1,100. That is the 40%.

What the EOR rate includes that founders miss

The EOR model bundles every item listed above into a single per-seat-per-month rate. You do not hire an HR manager, because the EOR's in-country HR team processes onboarding, maintains the personnel files, and handles terminations. You do not engage a CA, because statutory compliance, TDS filing, and audit coordination are part of the service. You do not lease office space or buy HRIS software, because the EOR either provides co-working credits or expects remote work and already runs enterprise payroll infrastructure.

The trade is control. Under an EOR model the employees are on the EOR's Indian entity payroll, not yours. You direct the work, set priorities, and own the output through a service agreement and an IP assignment clause, but you do not appear as the employer on the appointment letter. For many US SaaS companies that trade is worth $396,000 a year on a 30-person team because it eliminates fourteen expense categories, removes compliance risk, and lets the US finance team model India headcount as a variable cost with a predictable unit rate.

When build makes sense despite the premium

There are scenarios where the captive model is the right call even when it costs 30 to 40% more. We have set up full ODCs for clients in three situations:

• Headcount above 80 to 100 seats. At that scale the fixed overhead of an HR manager, office lease, and compliance function spreads across enough engineers that per-seat cost approaches EOR pricing. The breakeven is typically 75 to 90 seats depending on metro market and turnover rate.
• Planned India revenue or customer base. If the SaaS platform will serve Indian enterprises and require local invoicing, GST registration, and rupee billing, you need an Indian entity anyway. Adding payroll to that entity has near-zero marginal cost.
• Complex IP or regulated verticals. Healthcare SaaS, fintech, or defence-adjacent platforms sometimes require that all engineers sit on a wholly owned subsidiary for audit or certification purposes. EOR structures can create ambiguity in those contexts.

Outside these three cases the EOR model delivers better unit economics for the first 24 months and eliminates the distraction of standing up back-office infrastructure while the product is still finding fit.

What this means for your team

If you are a US or EU SaaS operator evaluating an India delivery team, the key question is not whether captive or EOR is cheaper in theory. It is which model gives you predictable cost, minimal compliance distraction, and the ability to scale or wind down without sunk costs.

Expante Global Consulting has set up both structures for 60-plus clients. We model the breakeven for your specific headcount plan, turnover assumption, and metro preference, then help you choose the setup that aligns with how you want your finance team to manage the India P&L: as a variable cost line or as a subsidiary with its own balance sheet.

The operators who get this right do not start with an ideology about control or ownership. They start with a spreadsheet that includes all fourteen cost categories, a three-year hiring curve, and a clear answer to whether they want to manage Indian statutory compliance or pay someone else to make it disappear.

Which model does your current headcount plan actually support, and have you modelled the non-engineering overhead that comes with the captive route?