Philippines EOR vs. Subsidiary: Which Structure Scales to 100 Hires

There is no Philippine law that requires you to open a subsidiary at 50 employees. None. The “50-hire rule” is a cost-of-EOR math heuristic that got repeated enough times in outsourcing forums that it started sounding like regulation. It isn't. Understanding that distinction is the difference between a $12,000 premature entity setup and a compliance structure that actually fits your growth stage.

For most companies hiring under 100 Filipinos, a properly structured EOR is cheaper, faster, and legally cleaner than a subsidiary. Three specific scenarios break that rule — and knowing exactly which three will save you from building a hollow Philippine entity that costs $60,000 a year to maintain.

The 50-Hire Rule Is a Myth — Here's What Actually Triggers the Switch

The headcount heuristic exists because EOR fees are per-employee. At some point, multiplying $249 by your headcount exceeds the annualized cost of running your own entity. That crossover is real — but it's a CFO calculation, not a legal threshold.

The actual triggers for reconsidering your structure are operational: payroll complexity at scale, IP ownership exposure, regulated-industry licensing requirements, and the specific DOLE risk that comes from directing Filipino workers without a clear employer of record. None of those are headcount-gated. A 15-person fintech engineering team building core product IP has a stronger case for a subsidiary than a 90-person CX operation with stable, predictable headcount and no government contract requirements.

The thesis here is specific: EOR wins on cost, speed, and compliance clarity below 100 hires in the majority of cases. The exceptions are real but narrow, and most companies invoking them are rationalizing a decision they've already made for the wrong reasons.

What Philippine Law Actually Requires: DO 174, DOLE Registration, and the Contractor Trap

Department Order 174 is the compliance mechanism most EOR comparisons skip entirely. DO 174 governs labor-only contracting — the arrangement where a third party supplies workers but the actual employer is directing their work. If DOLE audits your arrangement and determines that your foreign company is controlling Filipino workers while a separate entity holds the employment contract, DOLE can pierce the structure and declare an employer-employee relationship with your company directly.

This is the real exposure in badly structured freelance and contractor arrangements. A company paying 20 Filipino contractors through Upwork, issuing them daily task lists, and treating them operationally as employees has more DOLE risk than either an EOR or a subsidiary client — because neither the contractor nor the platform is absorbing the compliance burden.

EOR resolves this cleanly. The EOR provider is the Philippine employer of record. They file SSS, PhilHealth, and Pag-IBIG contributions. They issue payslips. They handle 13th month pay, separation pay calculations, and DOLE registration. Your company has a service agreement with the EOR provider, not an employment relationship with the workers. That structural separation is the compliance product you're buying.

A Philippine subsidiary resolves it differently: you become the employer, which means you own every compliance obligation directly — BIR registration, DOLE registration, mandatory benefits remittance, annual independent audit. Neither structure eliminates Philippine labor law. The question is who carries it.

The Real Cost Comparison: EOR Fees vs. Entity Overhead at 10, 50, and 100 Hires

Entity setup in the Philippines — SEC registration, BIR registration, DOLE registration, local bank account — typically runs 4–6 months and $8,000–$15,000 in legal and filing fees before you hire a single person. That's the entry cost. The ongoing cost is what most projections undercount.

At 10 hires, EOR wins on every dimension — cost, speed, and compliance clarity. At 50 hires, the math gets closer, but entity overhead (a local HR manager alone runs ₱600,000–₱900,000 annually, plus payroll software, a legal retainer for DOLE and BIR queries, and a mandatory annual independent audit) keeps EOR cheaper in total cost of compliance for most companies. At 100 hires, the crossover can happen — but only if your entity overhead is efficiently managed and your headcount is stable enough to justify the fixed cost.

Budget $40,000–$80,000 per year for a properly run Philippine entity at 50–100 headcount. That number is rarely in the spreadsheet when the “go entity at 50” recommendation gets made.

Three Scenarios Where a Philippine Subsidiary Actually Makes Sense

Scenario 1 — IP-intensive engineering teams. Philippine IP law assigns ownership to the employer of record. If your EOR provider holds that role, IP assignment flows through your service agreement with the EOR — a contractual relay that works in practice but carries challenge risk if the relationship ever sours or the EOR provider goes under. A subsidiary makes your company the direct employer and the unambiguous IP owner. For a 15-person team building core product, that risk premium is worth paying.

Scenario 2 — Government contracts and regulated-industry licenses. BSP-supervised fintech operations, DOH-registered health data processors, and certain Philippine government procurement contracts require a locally registered entity as the contracting party. An EOR provider cannot stand in for your company in those relationships. If your Philippine team's work touches any of these, the entity isn't optional regardless of headcount.

Scenario 3 — 80–120+ stable hires with predictable headcount. If you're projecting headcount that won't fluctuate more than 10–15% quarterly and you're above the EOR-entity cost crossover, the subsidiary math works. The break-even is typically 80–120 employees depending on your EOR rate and how efficiently you run entity overhead. Below that range, or with volatile headcount, EOR remains cheaper in total cost.

What does not justify a subsidiary: wanting “more control” over workers (operational control is available through a well-structured EOR), assuming candidates prefer a direct employer (Philippine workers understand EOR arrangements and care far more about salary, benefits, and management quality), or believing it signals legitimacy to enterprise clients (it doesn't — a CCAP-accredited EOR partner signals more operational credibility than a shell SEC registration).

The Hybrid Path Most Companies Ignore: EOR to Bridge, Subsidiary to Scale

If you're planning 100+ hires over 24 months, the practical move is to start on EOR and run entity setup in parallel from month 6. You hire and operate before committing to permanent entity overhead, validate the Philippine team model, and migrate employees to the subsidiary once it's operational — typically around month 10–12.

EOR-to-subsidiary migration is not automatic. Employees sign new contracts with the subsidiary as employer. Statutory benefits histories transfer in principle, but payroll systems don't migrate themselves. DOLE registration of the new entity must precede any transfer. The BIR TIN situation for employees requires careful handling to avoid duplicate registrations.

A managed EOR provider should own the migration mechanics — contract novation, benefits continuity documentation, coordination with your incoming local HR team. If your EOR provider can't walk you through that process in a pre-sales conversation, that's a meaningful signal about their operational depth.

A Decision Framework You Can Run Today

Four gates. Work through them in order.

1. Gate 1: Are you hiring fewer than 50 people in the next 12 months? Use EOR. The entity math doesn't work at this scale, and the compliance burden isn't worth taking on prematurely. Stop here.
2. Gate 2: Does your work require direct Philippine government contracts or BSP/DOH licensing? An entity is required regardless of headcount. EOR cannot substitute as the contracting party in these relationships.
3. Gate 3: Is the IP created by your Philippine team core to your product? Get a Philippine IP attorney's opinion on your specific EOR contract before deciding. This is a $500 opinion that could protect a material asset. It may still point to EOR — but verify, don't assume.
4. Gate 4: Are you projecting 80+ stable hires within 18 months? Model the break-even with your actual EOR rate and realistic entity overhead — not an optimistic estimate. If EOR is still cheaper in year two at your projected headcount, stay on EOR and revisit at 18 months.

The companies that get this wrong don't usually fail on the legal structure itself. They fail because they set up an entity at 40 hires based on a forum recommendation, underestimated the compliance overhead, and ended up with a Philippine subsidiary that costs $60,000 a year to maintain, requires a local HR manager they didn't budget for, and creates more DOLE exposure than the EOR arrangement they left — because now they own every compliance obligation directly and don't have the operational infrastructure to handle it.

The structure should follow the business model, not precede it.