- A Series A changes your capacity to act, more cash, more runway, a headcount plan and board expectations, but it does not change the core math of a per-head EOR fee against the fixed annual cost of running your own India entity.
- Keeping your India team on an EOR after a raise is a deliberate staging strategy, not a failure. A hybrid, your own entity plus an EOR for later or satellite hires, can be a permanent setup rather than a stopgap.
- Your break-even is a formula, not a single headline number: your entity's fixed annual cost divided by the annual EOR fee per employee. Transfer pricing is the India cost most founders forget to include.
- For an AI startup, employment vests copyright work in the employer by default, but patents are different and need an express assignment. Series A diligence checks that chain, so decide IP on purpose.
- Legal employer liability, permanent establishment exposure and your team's gratuity and provident fund continuity all move with the model, so weigh them before you switch from an EOR to your own entity.
Deciding whether to keep your India team on an EOR after your Series A? Talk to an expert!
Discover how Wisemonk creates impactful and reliable content.
Knowing when to move your India team off an EOR after a Series A is a decision about timing and cost, not a box your raise ticks automatically. We run India teams for 300+ global companies on our EOR, and we model this exact crossover with founders every month. The honest answer is that a Series A changes what you can afford, not the arithmetic that should drive the call.
When should a post-Series-A startup switch from an EOR to its own India entity?
Not automatically. A Series A is a prompt to decide on purpose, not a signal to switch. The raise changes your capacity, more cash, longer runway, a headcount plan and board expectations, but it leaves the underlying math untouched. Staying on an EOR after the round is a legitimate staged choice for a startup, not a sign you fell behind.
This is the pattern we see across the companies we support at Wisemonk: a raise creates pressure to "look permanent," and the India entity gets framed as the grown-up option. It is one option, but it is a cost-and-liability decision that should turn on signals you can measure, not on the fact that the round closed.
What a raise actually changes
A Series A changes four things, and all four are about capacity rather than cost structure. You have more cash in the bank, a longer runway, a board that expects a credible hiring plan, and a headcount target for the next 18 to 24 months. Those shape how fast and how many you hire. None of them changes what each model costs per head.
What it does not change
What the raise does not touch is the arithmetic. An EOR charges a per-head fee; your own entity carries a fixed annual cost whether you employ three people or thirty. The relationship between those two numbers is the only thing that decides which is cheaper, and a bank balance does not move it.
Why staying on an EOR is a deliberate stage, not a failure
We treat the EOR as a staging strategy. It lets you hire and run a compliant India team now, test the market, and keep optionality while the headcount plan proves out. Moving to your own entity is a later, planned step, and for some companies the right end state is a hybrid: an owned entity for the core team and an EOR for satellite or later hires.
| Signal | Keep on an EOR | Move to your own entity |
|---|---|---|
| India headcount vs your break-even | Below your calculated crossover | At or above your calculated crossover, with more hiring planned |
| Permanence of the India presence | Still testing the market or the team | A long-term, core function you intend to own |
| Need for a registered local presence | None; you only need to employ people | You need a licence, government contracts, or a registered Indian presence an EOR cannot hold |
| Appetite to run payroll and compliance in-house | You want that off your plate | You have, or will hire, the finance and HR capacity to carry it |
| Speed of your next hires | You need people in seats in days | You can absorb a multi-month entity setup before the next hires start |
If you want the India-specific side-by-side first, check out EOR vs entity in India.
At what headcount does your own India entity become cheaper than an EOR?
There is no single headcount that fits every company, because the answer is a formula, not a number. Your break-even is your entity's fixed annual cost divided by the annual EOR fee per employee. Below that number the EOR is cheaper; above it your own entity is. The inputs, not a rule of thumb, decide where you land.
The crossover formula
Write it out and the decision stops being a guess:
N = entity annual fixed cost / annual EOR fee per employee
Salary is paid under either model, so it drops out. What is left is EOR platform fees against the entity's fixed overhead. At our published rate of from $99 per employee per month, the annual EOR fee is about $1,188 per person.
Your entity's fixed annual cost is the other half of the fraction, and it is the number most founders under-count. For the full sensitivity band at different overhead levels, work through our detailed EOR versus own entity comparison rather than relying on one figure.
You can also plug your own numbers into the EOR vs entity calculator.
Why a single headline number misleads
The crossover depends entirely on your entity's fixed overhead, so it can land anywhere from the low dozens to beyond a hundred people. The moment someone quotes a flat "switch at X," they have hidden the inputs that actually move it. A different overhead assumption shifts the answer by years of hiring. Treat any single number as a starting point to pressure-test with your own costs, and work through the comparison linked above for the full sensitivity band.
To size the per-head side of the formula for your own team, check out what an India hire really costs.
| Stage | Where your India team usually sits | Sensible default | What to pressure-test |
|---|---|---|---|
| Seed / pre-Series-A | First few hires, still testing | Stay on an EOR | Whether India is even the long-term location |
| Series A | A growing pod, plan firming up | Decide on purpose; often keep the EOR, sometimes start planning the entity | Your real entity overhead, including transfer pricing |
| Series B and later | An established, core function | Entity or a hybrid, once the math turns | Whether satellite hires still belong on an EOR |
Transfer pricing, the India cost most founders leave out
When your Indian entity does work for your foreign parent, Indian transfer-pricing rules treat that as a related-party transaction that has to be priced at arm's length and documented. That means a local transfer-pricing study, a benchmarking analysis, and an accountant's certification each year. The annual compliance cost is real and recurring, and leaving it out of the fixed-cost side of the formula is what makes an entity look cheaper than it is. For the line items, see our guide to India transfer pricing for US companies.
For the wider cost picture around that overhead, check out the true cost of employment in India.
Who owns your AI startup's IP and model work under each model?
Under either model you can own the IP your India team produces, because ownership comes from the contract, not from whether you use an EOR or your own entity. The important nuance for an AI company is that copyright and patents behave differently in India by default, so the question to settle is what your contracts actually assign.
The copyright-versus-patent split
For work created by an employee in the course of employment, Indian copyright law makes the employer the first owner by default, absent any agreement to the contrary (Copyright Act 1957, Section 17, proviso (c)). Patents do not work the same way. Indian patent law has no equivalent provision that vests an invention in the employer automatically, so an employment relationship alone does not assign a patentable invention; you need an express assignment in the contract (Patents Act 1970). The IP chain for India developers walks through how that assignment is built.
For the contract-side checklist, check out protecting IP when hiring in India.
What diligence checks
Series A and later diligence does not ask which employment model you used. It traces the assignment chain: can you show, for every contributor, that the rights in their work sit with your company? Under an EOR, that means the employment contracts route IP to you; under your own entity, the same contractual assignment has to be in place. A gap in the chain is a diligence problem regardless of structure.
What it means for model weights, pipelines and patentable methods
For an AI startup, the practical question is not a legal label on model weights. It is whether your contracts assign the full range of what your team produces, data pipelines, model artifacts, and any patentable methods, to your company. Because patents need an explicit assignment in India and copyright-style work does not, the clean move is to decide this up front and have the assignment language cover inventions expressly. Treat this as a question of what the contract assigns, and get it reviewed rather than assumed.
To see where those assignment clauses sit in the paperwork, check out employment agreements in India.
Does staying on an EOR limit your equity, control, or business activities?
No. Staying on an EOR does not cost you control. You keep every people decision, hiring, compensation, performance, promotions and exits, while the EOR holds legal employer liability and the statutory registrations that go with it. The real Series-A question is narrower than "do we lose control": it is which entity's name sits on an option grant.
Control stays with you
In practice the division is clean. You choose who to hire, set pay and performance expectations, run promotions, and decide exits. The EOR executes the employment, payroll, benefits and filings compliantly as the legal employer. You direct the work; they carry the employer obligations.
Which entity's name is on an ESOP grant
The one place the model genuinely shows up is equity. An option grant is made by a specific legal entity, and under an EOR your team is employed by the EOR, not by a local company you own. That is a structuring question to settle deliberately with your counsel, because the Indian tax and reporting treatment of employee equity is involved and fact-specific. The point for this decision is simply to raise it on purpose, not to copy a number off a blog. Our guide to granting ESOPs to India employees covers the mechanics.
For the wider range of equity structures, check out equity compensation in India.
Owned-entity EOR versus partner-model EOR
Not all EORs are built the same, and it matters for your diligence. Some run on their own registered Indian entity; others operate through a local partner. The questions to ask are who actually holds the employment contract and who holds any licence your work depends on. India recognizes a single legal employer per worker, so frame this as "who is the legal employer," not as co-employment, which is not how the India model works.
If you want to confirm the legal footing of the model itself, check out is an EOR legal in India.
What legal and compliance risk sits with each model?
The variable that actually differs between the two models is who holds legal employer liability, and speed and cost follow from that. Under an EOR, the provider carries the statutory employer obligations. When you register your own entity, that liability, and the filings, registrations and exposure that come with it, moves onto you.
Legal employer liability
India recognizes one legal employer per worker. Under an EOR that is the provider, which carries payroll, statutory registrations and filings. Own the entity and you become the employer of record for your team, which means you take on those registrations and the ongoing compliance calendar directly.
To see what that legal-employer role involves, check out legal requirements for hiring employees in India.
Permanent establishment risk, reduced not eliminated
An EOR reduces permanent establishment (PE) exposure but does not eliminate it. PE turns on the facts of how your business operates in India, assessed through the business-connection rules under the Income-tax Act 2025 (in force from April 1, 2026) read with Article 5 of the applicable tax treaty. Owning an entity changes the analysis rather than removing the question, so treat PE as something to manage under either model, not a box an EOR ticks for you. Our explainer on permanent establishment risk in India goes deeper.
Owning an entity also brings foreign-exchange and corporate obligations onto you. Foreign investment into an Indian company generally follows the automatic route, which needs no prior government approval, but still requires a post-investment filing (Form FC-GPR) within the prescribed window of 30 days. Contraventions carry penalties of up to three times the amount involved under the foreign-exchange law (FEMA, Section 13). And if a company stops operating, it can be struck off for non-operation, which is a corporate housekeeping provision (Companies Act 2013, Section 248), not a foreign-exchange penalty. These are the kinds of obligations an EOR carries today and your entity would carry tomorrow.
Before you decide, take the permanent establishment risk quiz to see where your own setup lands.
Statutory benefit continuity on a move
When people move from the EOR onto your entity, their statutory benefits do not all behave the same way, and this catches teams out. Gratuity eligibility is built on continuous service, and a structure that terminates with one employer and rehires with another can reset that clock.
Provident fund is different: the employee's universal account number (UAN) is permanent and portable, so the PF record carries across employers rather than resetting. Plan the move so you protect continuity on purpose.
For the full list of statutory contributions your team carries, check out PF, ESI and gratuity obligations for US startups in India.
Can you move from an EOR to your own entity later, and how hard is it?
Yes. Moving from an EOR to your own entity is a planned transition, not a toggle you flip. Your people move across on continuous service, the entity stands up over a few months, and you run both models in parallel during the handover. For many companies the hybrid that results is a legitimate end state rather than a halfway house.
The transition is a project, not a toggle
The move has moving parts: registering the entity, setting up payroll and statutory registrations, transferring employment, and protecting benefit continuity. It is sequenced work, which is why starting it on purpose after a raise beats reacting to a deadline. For the step-by-step mechanics, see our dedicated guide on moving from an EOR to a legal entity.
If you are also weighing how the entity itself gets built, check out how to set up a legal entity.
Timeline: entity setup in 3 to 6 months
Standing up an Indian entity typically takes about 3 to 6 months from decision to being ready to employ. That lead time is exactly why the EOR is useful during the transition: your existing India team keeps running on it while the entity is built, so there is no gap in employment and no pause in hiring. If you want the registration route itself, see registering a company in India.
For how teams keep hiring while that clock runs, check out hiring without a local entity.
The hybrid as a permanent answer
The end state does not have to be "all entity." A common, durable setup is an owned entity for your core India function plus an EOR for later, satellite or short-term hires. That keeps the flexibility of the EOR where it helps and the ownership of an entity where the headcount justifies it. It is a deliberate operating model, not a compromise. At larger scale, the same logic shows up in setting up a GCC in India.
To compare the other employment routes alongside the hybrid, check out choosing an employment model in India.
How does Wisemonk support your India team through this decision?
Wisemonk is an India-native Employer of Record (EOR) that helps global companies hire, pay, and manage employees in India without setting up a local entity.
We support 300+ global clients, manage 2,000+ employees and process over $20M in annual payroll, with a 4.8/5 rating on G2, and EOR pricing from $99 per employee per month.
- Compliant employment from day one: we become the legal employer in India so your team is hired and paid while you decide on an entity.
- A clear cost comparison: we model the per-head fee against your own entity's fixed cost so your break-even is a number you can see.
- IP and equity handled up front: contracts that assign work to your company and keep your option grants clean for investor diligence.
- A staged path to your own entity: stay on our EOR now and move to your own entity when the headcount math turns, with no break in employment.
- One partner across the lifecycle: hiring, payroll, benefits, equipment and background checks under a single point of contact.
We provide EOR services in India, and we are expanding rapidly into the US and UK markets.
Not sure whether to keep your India team on an EOR?
Talk to our India experts and get a clear read on the EOR-versus-entity decision for your stage.
I highly recommend them. Wisemonk helped us tap into the vibrant and top-notch Indian talent market and hire our first couple of founding engineers in record time. We've been able to accelerate our roadmap and deliver terrific value to our customers thanks to Wisemonk's efforts. They are easy to work with and very transparent about the process. I highly recommend them to any company looking for talent located in India.
Krishna Ramachandran, Co-founder at Onform, USA
Frequently asked questions
Is an EOR a temporary solution?
No. An EOR is a deliberate staging strategy, not a stopgap you are meant to outgrow. Many teams stay on one indefinitely, and a hybrid, your own entity plus an EOR for later or satellite hires, is a legitimate permanent setup rather than a transitional compromise.
Does an EOR restrict our business activities in India?
No. You direct the work, set strategy and manage the team, while the EOR holds legal employer liability. The one caveat is regulated activity: some licensed work needs a licence the EOR may not hold, so confirm licensing before you assume an EOR covers it.
Can we hire in India before our own entity is ready?
Yes, and it is the core reason companies use an EOR. You can hire, pay and onboard Indian employees compliantly within days, with no local entity, then keep that team running as a compliant bridge while your own entity is registered over the following months.
Is opening a local entity more cost-effective at scale?
Not automatically. It depends on your entity's fixed annual overhead against the per-head EOR fee, so the honest answer is a formula, not a number. Run your own figures through the crossover calculation before assuming that scale alone makes an entity cheaper.
Who is the legal employer of our India team under an EOR?
The EOR is. India recognizes one legal employer per worker, so there is no co-employment: the EOR carries statutory registration, payroll and filings while you direct day-to-day work. When you move your India team off an EOR, that liability transfers to your own entity.
Does raising a Series A mean we should set up our own India entity now?
No. A Series A changes your capacity, more cash, runway and board expectations, but not the arithmetic that decides the call. Treat the raise as a prompt to decide on purpose, then move your India team off an EOR only when the math actually turns.
How can Wisemonk help us choose between an EOR and our own entity?
We run your India team on our EOR today and model the crossover with you, so your break-even is a number you can see. When the headcount math turns, we handle the move to your own entity with no break in your team's employment.
Related Blogs
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.
