Setting up a Philippine entity for a 15-person ops team costs between $15,000 and $30,000 in legal fees, takes four to six months, and leaves you with SEC filings, a resident agent obligation, and a local HR function to staff — before you've hired a single person. At 10 to 30 Filipino hires, that path is a trap. So is the other default: a traditional BPO contract that hands you output metrics while burying your team inside someone else's org chart.
Most comparisons frame this as BPO versus entity, or EOR versus in-house. That's the wrong frame for this headcount. The actual decision is between a traditional BPO contract and a bundled EOR plus managed team — and the criteria that determine the right answer are almost entirely different from what those other comparisons measure.
For 10 to 30 Filipino hires, a bundled EOR plus managed team beats a traditional BPO contract in three of four scenarios. The one exception is clearly defined below. Here's how to think through it.
- Traditional BPO contracts create legal exposure most clients don't discover until there's a DOLE dispute.
- EOR makes the employer relationship explicit and separation pay calculable before you hire.
- The managed team layer eliminates the need for a Philippine country manager at this headcount.
- Entity dissolution at 15 seats can cost more than the EOR fees you were trying to avoid.
The 10-Person Threshold Is Where Both Default Options Break
Below 10 hires, a traditional BPO contract is defensible — the operational complexity is low enough that the opacity doesn't kill you. Above 50 hires, a Philippine entity starts making financial sense. Between 10 and 30, you're in a gap that neither model was designed for.
A BPO contract at this headcount gives you less control than you think and more legal exposure than you're told. An entity gives you full control but front-loads costs that won't break even against EOR fees until you're at 50 to 80 employees, depending on salary levels. The companies that get this right aren't choosing between BPO and entity — they're choosing a third path that didn't exist five years ago: EOR-backed managed teams that let you own the employment relationship without owning the infrastructure.
What a Traditional BPO Contract Actually Does to Your Legal Exposure
Under a traditional BPO arrangement, the BPO is nominally the employer of record. In practice, the contract rarely specifies what happens when a worker files a DOLE complaint, claims regularization after six months of probation, or is terminated for cause. You end up with de facto control over a worker — setting their tasks, tools, and schedule — without a documented employer-of-record relationship. That's the worst possible position under Philippine labor law.
Philippine law grants workers regularization rights after a probationary period, typically six months. If your BPO contract doesn't explicitly address this, and your team has been working under your direct supervision for that long, you may have created an implied regular employment relationship without the documentation to manage it.
The sharper risk: DOLE Department Order 174 governs legitimate contracting arrangements in the Philippines. If your BPO subcontracts labor in a way that doesn't meet DO 174's requirements — sufficient capitalization, genuine independent operation, no labor-only contracting — you as the principal can be held jointly liable for labor violations. Most clients don't learn this until there's an actual complaint. By then, the BPO's lawyers are protecting the BPO, not you.
A proper EOR arrangement makes the employer relationship explicit from day one: the EOR is the legal employer, the employment contracts are DO 174-compliant, and your liability is contractually bounded. That's not a minor administrative difference — it's the difference between a defensible position and an improvised one.
Cost Per Seat: The Number Most Comparisons Get Wrong
| Model | Setup Cost | Monthly Per-Seat Cost (EOR/admin fee only) | Management Overhead | Exit Cost |
|---|---|---|---|---|
| Traditional BPO contract | Low / negotiated | Opaque — bundled into seat rate | Moderate — you manage output, BPO manages people | 90–180 day notice + penalty clauses |
| EOR-only (Deel / Remote) | Low | ~$599/month | High — you own all local HR and management | 30-day notice + statutory separation pay |
| EOR-only (Splace) | Low | ~$249/month | High — same as above | 30-day notice + statutory separation pay |
| EOR + Managed Team (Ops Pod) | Low | EOR fee + team lead/management layer | Low — local team lead handles daily ops and HR escalations | 30-day notice + statutory separation pay |
| Philippine entity (ROHQ) | $15K–$30K+ | Absorbed into entity overhead | High — you own all HR, payroll, SEC filings | 12–24 months to dissolve; BIR and SEC clearance required |
The hidden cost in a traditional BPO arrangement is salary opacity. You pay a bundled seat rate and rarely know what the worker actually earns. When workers discover the gap — and they do, because Davao's BPO community is not large — you get attrition. EOR makes the salary line visible to both you and the worker, which changes the retention dynamic entirely.
At 10 employees, the difference between a $249 and $599 monthly EOR fee is $3,600 per year. That's a part-time team lead. The entity math is starker: a Philippine ROHQ that costs $20,000 to establish and requires ongoing local HR doesn't break even against EOR fees until somewhere between 50 and 80 employees, and that's before you account for dissolution costs if you ever need to exit.
Management Control: The Axis That Actually Decides the Choice
Traditional BPO gives you output metrics — tickets closed, calls handled, SLA percentages. It doesn't give you control over who gets hired, how they're trained, what tools they use, or what the team culture looks like. The BPO's operational layer sits between you and your people. For commodity CX at 100+ seats, that trade-off is acceptable. At 15 seats doing finance ops or sales support, it means your team's institutional knowledge lives inside someone else's org chart.
EOR-only gives you full operational control — hiring criteria, training content, tooling, scheduling. You own all of it. The problem: without a local management layer, a 10-person team in Davao needs someone on your side who understands Philippine employment norms, can handle HR escalations in timezone, and can enforce performance standards without you being online at 2 a.m. Most US and AU companies underestimate this cost until the first performance issue surfaces and they realize their remote manager has never navigated a Philippine regularization conversation.
An Ops Pod — EOR plus an embedded local team lead — splits the responsibility cleanly. You set objectives and own output standards. The local lead handles daily management, HR touchpoints, and compliance escalations. This is the model that scales from 10 to 50 without requiring you to hire a Philippine country manager.
The decision rule is straightforward: if your team does highly specialized, IP-sensitive work and you have a dedicated remote manager with Philippine employment experience, EOR-only works. If your team is doing CX, finance ops, or sales support at any meaningful volume, the managed layer pays for itself in reduced management overhead within the first quarter.
Exit Flexibility: What Happens When Headcount Drops
Philippine labor law requires separation pay for involuntary termination — typically 0.5 to 1 month per year of service, depending on grounds. Under a traditional BPO contract, this liability is theoretically the BPO's. Check your contract for clawback provisions that pass it back to you. They exist more often than clients expect.
Under EOR, separation pay is explicit, calculated in advance, and funded by the EOR. You know the exit cost before you make the hire. Under a Philippine entity, exit is the worst outcome: SEC approval, BIR clearance, and a process that routinely runs 12 to 24 months. Companies that opened entities for 15 people and then downsized have paid more in dissolution costs than they saved on EOR fees over the entire operating period.
Consider an e-commerce ops team that scales to 20 for peak season and contracts to 12 post-Q4. Under EOR, that's a 30-day notice process for each departure, with known separation pay obligations. Under a BPO contract with a minimum seat commitment, you're paying for eight seats you're not using, or you're triggering penalty clauses. The flexibility gap at this headcount is not theoretical — it's a cash flow decision every year.
Four Scenarios, One Clear Answer Each
| Scenario | Recommended Model | Why | Red Flag to Watch |
|---|---|---|---|
| 10–15 hires, CX or ops function, 18-month horizon | EOR + Managed Team | You lack local management infrastructure; BPO contract gives less control than advertised | BPO contracts with minimum seat commitments and 180-day exit clauses |
| 10–15 hires, specialized or IP-sensitive work, dedicated remote manager in place | EOR-only | Direct control over process and tooling; manager can handle local HR with EOR support | Remote manager without Philippine employment experience — add managed layer if absent |
| 25–30 hires, mixed functions, FinTech or HealthTech vertical | EOR + Managed Team with explicit compliance documentation | Regulated verticals need audit trails; BPO contracts won't produce the workspace and data handling evidence your legal team requires | Any provider who can't show a network segmentation diagram and a recent security audit |
| 30+ hires, clear 3-year growth trajectory | Start EOR; model entity breakeven at month 18 | Use the EOR period to build local HR capability before you own it; transition to entity only when math is confirmed | Opening an entity before you have a local HR lead — you'll own the compliance burden without the infrastructure |
The one scenario where a traditional BPO contract wins outright: pure volume CX at 100 or more seats, commodity function, no IP sensitivity, price as the only variable. Below 50 seats, the control and compliance trade-offs don't justify the opacity. That's not a close call — it's a structural mismatch between what the BPO model was designed for and what a 10 to 30-person team actually needs.
What to Verify Before You Sign Anything
Three contract clauses determine whether your arrangement actually protects you. First: explicit employer-of-record designation and a DO 174 compliance statement. If the contract doesn't name who the legal employer is and confirm DO 174 compliance, you're exposed. Second: separation pay liability — who funds it, how it's calculated, and whether there are clawback provisions. Third: data handling and workspace compliance documentation, specifically if you're in a regulated vertical.
Ask any EOR or BPO provider: “Show me a sample employment contract you issue to workers in our function.” If they can't produce one within 24 hours, that's your answer about their operational readiness.
For FinTech and HealthTech teams: ask for a network segmentation diagram of the workspace and a copy of the most recent security audit. A provider with ISO 27001 certification in progress and documentation to show for it is acceptable. A provider with no documentation at all is not — regardless of what their sales deck says.
One forward-looking point worth sitting with: the Philippine labor market for skilled ops roles is tightening. Tenure in Davao BPO seats is running shorter as experienced workers gain leverage and options. The companies that will retain talent at the 10 to 30 headcount range are the ones offering transparent compensation — visible under EOR, hidden under a BPO markup — and genuine career infrastructure. A managed team model with a real local lead, a clear org structure, and visible salary is a retention advantage. A bundled BPO seat rate is not.
