Employ
Recruit
A US fintech wants its customer support handled in Manila. They have two real options that look the same on a P&L line — and the choice fits inside a broader global recruitment strategy:
- Pay an Employer of Record to hire 12 specific support agents as employees who work under fintech’s direction.
- Pay a Manila-based BPO to deliver “tier-1 customer support” — they staff it, train it, replace it, you don’t care who’s actually answering the phone.
Both cost roughly $480K/year. Both put the work in Manila. Both produce the same KPI dashboard.
They are not the same thing. The first is EOR. The second is outsourcing. Picking the wrong one costs more than the headline price gap — control, IP, talent retention, and exit flexibility all play out differently. This guide walks through when each model wins, the cost math at scale, and the decision framework we use with clients facing this choice.
Need an Employer of Record to hire your own people compliantly across 150+ countries? Or a Contractor of Record for freelancers? We do both.
The 30-Second Answer
- Employer of Record (EOR): you hire your own employee in another country. The EOR is the legal employer (handles payroll, taxes, statutory benefits, compliance). You direct the day-to-day, the worker reports to your team, and the relationship is yours.
- Outsourcing (BPO/KPO/ITO): you buy a deliverable from a vendor. The vendor employs whoever does the work. You don’t hire, manage, or even necessarily know the individuals. You pay for the outcome.
If the worker should feel like part of your team, it’s EOR. If you’re buying a service and don’t care who delivers it, it’s outsourcing.
The 8 Key Differences
| Dimension | Employer of Record | Outsourcing | Why it matters |
|---|---|---|---|
| Who employs the worker | EOR (your worker, contracted by EOR) | The outsourcing vendor (their employee) | Defines liability, IP, and continuity |
| Who manages day-to-day | You (your manager, your tools, your priorities) | The vendor’s manager | Control vs hands-off trade-off |
| What you pay for | Person-based: salary + employer load + EOR fee | Outcome-based: SLA, ticket volume, hours, output | Determines pricing flexibility |
| Worker loyalty | To your company | To the vendor | Retention math is very different |
| IP ownership | Strong by default (employment contract assigns it) | Whatever the SOW says — often vendor-owned by default | Critical for software, content, R&D |
| Scalability | Linear: 1 person costs 1 person | Step-function: vendor can flex up/down faster | Outsourcing wins at burst capacity |
| Knowledge retention | Stays with your worker | Vendor can replace the person any time | EOR wins for institutional knowledge |
| Exit cost | Standard severance + notice | End the contract per SOW; people aren’t yours to keep | Outsourcing exits cleaner; EOR retains people |
What is an Employer of Record?
An Employer of Record is a third party that legally employs your worker on your behalf in countries where you don’t have a legal entity. The EOR signs the local employment contract, runs payroll, withholds taxes, pays statutory benefits, and handles termination compliance. You manage the work; the EOR handles the legal-employer paperwork.
The worker has a real employment contract under their country’s labor law. They get statutory benefits (vacation, sick leave, severance accrual). They feel like — and legally are — an employee, just one whose paystub is issued by the EOR rather than your parent company.
If you’re still weighing whether an EOR is the right move, we’ve put together a full breakdown of the pros and cons of using an Employer of Record — covering cost, compliance, flexibility, and the scenarios where it makes sense versus where it doesn’t.
What is Outsourcing?
Outsourcing means hiring a third-party company to perform a business function. You don’t engage individuals — you engage a vendor that staffs and delivers the function. Three flavors:
BPO (Business Process Outsourcing)
Customer support, accounting, HR admin, content moderation. The Philippines, India, Costa Rica, Bulgaria are major hubs.
KPO (Knowledge Process Outsourcing)
Legal research, financial analysis, market research, medical coding. Higher skill than BPO.
ITO (IT Outsourcing)
Software development, infrastructure, helpdesk. India and Eastern Europe dominate.
The outsourcing vendor is the legal employer of every person doing the work. You sign a Master Services Agreement and Statement of Work, set SLAs (response time, ticket close rates, output quality), and the vendor delivers. You can have 50 outsourced support agents on a contract and never know any of their names.
Cost Math: What Each Really Costs
The headline rates look similar. The all-in cost diverges.
EOR cost build-up (hire 12 support agents in the Philippines, $1,600/month each)
| Component | Annual cost |
|---|---|
| Base salary × 12 | $230,400 |
| Employer load (SSS, PhilHealth, Pag-IBIG, 13th-month, leaves: ~25%) | $57,600 |
| EOR fee (~$400/employee/month × 12) | $57,600 |
| Equipment (laptops, headsets — optional) | $12,000 |
| Software licenses, your tools | $24,000 |
| Recruitment (one-time) | $10,000 |
| Total Year 1 | ~$391,600 |
| Total Year 2 onward (no recruitment) | ~$382,000 |
Outsourcing cost build-up (12 FTEs equivalent at a Manila BPO at $35/hour blended)
| Component | Annual cost |
|---|---|
| 12 FTEs × 2,080 hours × $35/hour | $873,600 |
| Setup / transition (one-time) | $25,000 |
| Volume discount at this scale (typical 10-15%) | -$95,000 |
| Total Year 1 | ~$803,600 |
| Total Year 2 | ~$778,000 |
On this scenario, EOR is roughly half the cost of BPO outsourcing. That’s not unusual — outsourcing markups on people-time are 80-150% over the underlying labor cost, because you’re paying for the vendor’s overhead, account management, training, attrition replacement, and margin.
When does outsourcing actually win on price?
- Burst / seasonal workloads where you’d otherwise overhire and lay off
- Functions where you need 200+ FTEs and vendor scale economies kick in
- Low-skill, high-volume work where vendor process discipline beats individual hires
- Markets where setting up EOR is hard (Russia, Iran, North Korea — niche)
When does EOR win?
- Skilled work where you want to retain institutional knowledge
- Long-term roles (24+ months — outsourcing markup compounds)
- Anything touching your core product — IP defaults matter
- Smaller teams (under 50 FTEs in a country)
📖 Mini-story
A US SaaS company outsourced their entire customer-success function to a Manila BPO at $42/hour for two years. They paid ~$2M/year for 24 FTEs. Then a board member asked the obvious question: “What if we just hired them ourselves?” Conversion to EOR-employed-direct hires landed at ~$840K/year for the same 24 people, who all chose to switch (better benefits, employer-of-record statutory protections). The two-year savings paid for an entire engineering team.
The Control Axis: Who Runs the Day
This is the single biggest functional difference, and the one most companies underweight.
EOR: Full Operational Control
- You set hours and shifts
- You assign work and priorities
- You define performance standards and review the worker yourself
- You build the relationship (1:1s, team rituals, career development)
- The worker sits in your Slack, your project tracker, your team org chart
The EOR is invisible to the worker beyond payday and benefits enrollment. The relationship is between you and them.
Outsourcing: Arms-Length Control
- The vendor sets the day-to-day; you set SLAs and priorities at the engagement level
- You don’t review individuals; you review aggregate performance
- You don’t know who’s there next quarter; turnover is the vendor’s problem
- The relationship is between you and the vendor’s account manager
Some sophisticated outsourcing engagements blur this — “dedicated team” models where named individuals work full-time on your account and you have access to them. These are halfway between BPO and EOR, with most BPO drawbacks and reduced cost benefits.
IP and Confidentiality
EOR: IP Defaults to You (Mostly)
Standard EOR employment contracts include “work-for-hire” provisions that assign all IP created by the worker during the employment to the client. Treat it like hiring an employee at home: assignments are clean. A few countries (Germany, parts of EU) have stricter rules where employees retain certain moral rights or compensation rights for inventions. The EOR contract must explicitly assign IP to the client, not the EOR.
Outsourcing: IP Belongs to Whoever the SOW Says
Default in most BPO contracts: the vendor retains IP. They created it; they own it. To get IP rights you specifically negotiate them in the SOW, often with extra cost. This is fine for routine work (a customer-support ticket reply isn’t IP). It’s a problem when the outsourced work touches code, content, designs, customer data, or process documentation that’s strategically valuable. For ITO especially — outsourced software development — every line of code and architectural decision is potential IP. Negotiate hard or use EOR for anything proprietary.
Compliance and Risk
Both models reduce direct compliance exposure compared to setting up your own foreign entity, but they distribute the risk differently.
EOR Risk Picture
- You’re not the legal employer. Worker complaints, wrongful termination claims, and labor-court actions go to the EOR. They’re indemnified to handle them.
- Permanent establishment risk is the main residual concern: does the worker’s activity create a tax presence for your parent company? Manageable with a properly structured EOR engagement. See our glossary entry on permanent establishment.
- Misclassification risk is removed because the worker is properly employed (vs the contractor route — see our EOR vs Independent Contractor guide).
Outsourcing Risk Picture
- You’re not the employer at all. Vendor takes 100% of employer-side liability.
- Joint employer risk is real if you direct the work too closely. US NLRB and EU equivalents have found “joint employer” relationships when client control of workers is high.
- Data protection under GDPR, HIPAA, etc. is more complicated — you’re sending personal data to a vendor, who may sub-process it. Data Processing Agreements are mandatory.
- Vendor lock-in risk: if you’ve outsourced your customer database to a BPO using their tools, leaving is painful and slow.
Decision Framework
- Is the work tied to your core product or sensitive IP? YES → Lean EOR. NO → Continue.
- Will the function need to scale up and down by 2-3x quickly? YES → Lean outsourcing. NO → Continue.
- How long will you need the function? <12 months → Outsourcing. 12-36 months → EOR usually cheaper. 36+ months → EOR or eventually your own legal entity.
- How many people in the country? <10 → EOR. 10-50 → EOR with potential entity build-out planned. 50+ → Consider local entity; outsourcing for non-core scale.
- Do you want to own the relationship with the workers? YES → EOR. NO (just want the outcome) → Outsourcing.
Most companies land on EOR for engineering, product, design, key support, finance, and senior roles. Outsourcing wins for tier-1 customer support, content moderation, data entry, accounting back-office, and 24/7 helpdesk.
Use our misclassification risk tool to check whether your current “contractor” arrangements are actually disguised employment — that’s the third option people often try, and it’s usually a mistake.
Hybrid Models: When to Use Both
Real distributed teams typically use both models for different functions:
| Model | Use case |
|---|---|
| EOR | 8-person engineering team in Buenos Aires — core product, long-term, IP-heavy |
| Outsourcing | 24/7 tier-1 support overflow — burst capacity, deliverable-based, low-skill-routing, replaceable |
| Direct entity | 80-person sales operation in Mexico — long-term, scaled, regional revenue |
The trap is treating these as one-size-fits-all. Different functions have different optimal engagement models. The mature playbook is comfortable using all three.
How to Switch From Outsourcing to EOR
If you’ve outsourced something for 18+ months, the EOR economics often look much better. But the conversion has nuance:
- Audit the current vendor’s IP and data terms. Make sure you have rights to migrate (or can negotiate them out).
- Identify which of the vendor’s people you’d want to retain. Most of the time, BPO workers will happily switch to EOR-direct employment — the benefits package is usually substantially better.
- Negotiate with the vendor. Tell them you’re considering insourcing via EOR. Many will counter with a discount; some will help facilitate the transition (for a fee).
- Run them in parallel for 60-90 days. Onboard the EOR-employed team while the vendor still owns delivery. Knowledge transfer is the riskiest part.
- Cut the vendor over and recover any setup fees, security deposits, or data.
A typical conversion takes 3-6 months and pays for itself in 12-18 months at the cost gaps we usually see.
Common Mistakes
- Treating EOR like outsourcing. Companies hire EOR-employed workers and then never integrate them — no team rituals, no career conversations, no recognition. The worker churns within a year. EOR is direct hiring; treat it like one.
- Outsourcing core IP work. “It’s just internal tooling” — until that internal tooling becomes a product. Get IP assignments in writing for anything that touches code or content.
- Mid-size BPO contracts that should be EOR. The sweet spot for outsourcing is either very small (under 5 FTEs, where vendor process beats DIY) or very large (50+ FTEs, where scale economics matter). The middle (10-30 FTEs) is usually cheaper via EOR with similar quality.
- Joint employer creep. Outsourcing engagements where the client manages individual vendor staff like employees — directing their work, evaluating them, even disciplining them — invite reclassification. Either go full outsourcing (arms-length, SLA-managed) or convert to EOR.
- Forgetting permanent establishment. A 30-person outsourcing operation can sometimes create PE for the client even though they’re not the employer. Get tax advice before scaling deep into a single market.
The Bottom Line
EOR and outsourcing solve different problems. EOR is for hiring your own people in countries where you don’t have an entity. Outsourcing is for buying outcomes without caring who delivers them.
For most knowledge-work functions — engineering, design, product, marketing, key customer-success, finance — EOR wins on cost, control, IP, and retention. For high-volume, low-skill, burst-driven work — tier-1 support, content moderation, basic helpdesk — outsourcing wins on flex and process.
The mature distributed-company playbook uses both, matched to the function. The wrong choice doesn’t blow up immediately, but it compounds: a year into a $2M outsourcing contract that should have been a $900K EOR engagement is a year of pure waste, plus the difficulty of unwinding the vendor relationship.
If you’re not sure which model fits, the smell test is: do you want to know who’s doing the work? If yes — and most companies do for most functions — that’s EOR.
NOT SURE WHICH MODEL FITS?
See EOR pricing for your countries or book a 20-minute call — we’ll model both scenarios honestly and tell you which one fits, even if it’s outsourcing.
Frequently Asked Questions
For knowledge work and skilled roles in most countries: yes, often by 30-50%. Outsourcing markups on people-time are typically 80-150% over labor cost. EOR adds ~$400-700/employee/month plus actual employer load (~25-30% over base salary). For low-skill, high-volume work at large scale, outsourcing economics can win via vendor process and scale discounts.
No. Offshoring means moving work to another country regardless of how (you can offshore via your own entity, EOR, or an outsourcer). Outsourcing means using a third party. You can outsource onshore (US BPO serving US clients) or offshore (Manila BPO serving US clients).
By default, the vendor — they created it. To get IP rights, you specifically assign them in the Master Services Agreement and SOW. Always negotiate IP assignments for anything proprietary or product-related.
The client (you), via the EOR’s standard employment contract assignment language. Always read the EOR contract to confirm — some EORs use generic templates that assign IP to themselves, not the client. A reputable EOR will provide a contract that clearly assigns work-product IP to the client.
Operationally you can, but legally you shouldn’t. Heavy client direction of individual vendor staff invites “joint employer” findings under US NLRB and EU labor law, plus potential misclassification claims. Stay arms-length: manage the SLA, not the people. If you want direct control, switch to EOR.
Yes — and many companies do once outsourcing volumes pass 12-15 FTEs in a country and stay there 12+ months. Standard conversion timeline is 3-6 months with parallel running. Most BPO workers happily move to EOR-direct employment because benefits and protections improve.
A halfway model where the BPO assigns named individuals exclusively to your account, full-time, often working in your tools and rituals. Most BPO drawbacks plus reduced cost benefits. Usually a sign you should just be on EOR.
No. A staffing agency finds and supplies workers (often short-term). An EOR legally employs your hires (long-term, in countries you don’t have an entity in). See EOR vs Staffing Agency for the full comparison.
ITO is its own category. The big risks are IP (always negotiate), code quality (set technical SLAs), and lock-in (require source-code escrow). For long-term core product development, most distributed-tech companies prefer EOR-employed engineers over ITO contracts after the first 12-18 months.
Outsourcing has high overhead per engagement — onboarding, account management, SLA setup. Below 3 FTEs, the per-person cost of outsourcing is often higher than direct hire (via EOR or contractor). The sweet spot is 5-50 FTEs of repeatable, deliverable-based work.
