Pilot First: How to Run a 90-Day Contractor-to-EOR Conversion Pilot with 5–10 Staff

 

Author: Martin English — CEO & Founding Partner
Published: November 24, 2025
Updated: November 24, 2025
Disclosure: This article is for informational purposes only and does not constitute legal advice.

 

Audience & Intent

Who this guide is for

• CFOs, COOs, founders, HR/People and Legal leads with 5–10 Filipino freelancers or contractors
• Teams considering a Philippines Employer of Record (EOR) but hesitant to roll it out across the entire workforce
• Leaders who want to test EOR in a controlled 90-day pilot before committing

What you’ll get

• A step-by-step playbook for a 90-day contractor-to-EOR pilot with 5–10 staff
• A clear 30/60/90-day structure: what to do, who owns it, and which risks to watch
• Suggested success metrics (people, ops, finance, risk) and how to track them
• Guidance on how to scale or adjust after the pilot

 

TL;DR: How does a 90-day contractor-to-EOR pilot work?

• Start with a small, high-signal cohort (5–10 Filipino contractors) rather than your entire remote team.
• Use 90 days to test EOR across four dimensions:
  • Compliance and risk (misclassification, DOLE alignment, statutory obligations)
  • People and retention (engagement, acceptance, turnover)
  • Operations (payroll, HR support, timekeeping, SLAs)
  • Finance (cost per FTE, effective hourly cost, FX and fee impact)
• Structure your pilot as:
  • Days 0–30: Design, selection, communication, documentation
  • Days 31–60: Conversion, go-live, stabilisation
  • Days 61–90: Measurement, adjustments, and go/no-go decision for scale

At the end, you should be able to answer:

“Should we move more Filipino contractors to EOR, keep a hybrid model, or pause and redesign our approach?”

 

Why run a 90-day pilot instead of going all-in?

A contractor-to-EOR move touches legal, finance, HR, culture and clients at the same time. Going “big bang” with 30–50 contractors can:

• Overwhelm your ops and HR capacity
• Create noise in metrics (you don’t know what’s working)
• Make it harder to unwind if the EOR vendor or model isn’t a fit

A 5–10 person pilot gives you:

• Signal without chaos — enough data to see patterns, but small enough to manage manually
• A safe space to fix kinks in contracts, payroll, benefits, tools and communication
• Internal proof-of-concept you can show to investors, auditors and your board

Think of it as an MVP for compliance and employment, not just a paperwork exercise.

 

Design principles for a successful pilot

Before you pick anyone, align on these principles:

1. Small, representative, not random
   • Pick 5–10 contractors across one or two functions (e.g., Customer Support + EA/VA, or Finance + Ops), not scattered everywhere.
2. High enough risk to matter
   • Include contractors who look employee-like in practice (full-time hours, core roles, long tenure).
3. High enough value to get attention
   • Choose people who are important to delivery so stakeholders actually care about results.
4. Tightly scoped timebox (90 days)
   • Day 0–30: design and prep
   • Day 31–60: conversion and go-live
   • Day 61–90: review and recommendation
5. Clear success criteria before you start
   • “We will call this pilot a success if X, Y, Z happens by Day 90.”

 

Step 1: Choose your 5–10 pilot staff using the conversion matrix

If you already have a Contractor-to-Employee Conversion Matrix, this step is easy:

• Filter for High Risk – High Value and High Risk – Medium Value profiles.
• From that list, choose 5–10 people who:
  • Are open to structured work and benefits
  • Are in a contained part of the org (e.g., one team or one client)
  • Have managers who are supportive of the pilot

If you don’t have the matrix yet, look for:

• Contractors who work 30–40 hours/week for you
• Tenure of 6+ months
• Access to your tools, email and systems daily
• Roles that are clearly core (support, EA/VA, finance, ops, PM, dev)

The goal: a cohort that actually tests EOR in realistic conditions.

 

Step 2: Align stakeholders and success metrics

Get Finance, HR/People, Legal (or EOR partner) and team leads in the same virtual room.

Agree on:

1. Scope of the pilot

• Headcount: 5–10 Filipino contractors
• Teams: which function(s) or client accounts
• Landing model: EOR in the Philippines, not a mix of EOR plus entity (for the pilot)

2. Success metrics by domain

People / Engagement

• % of pilot contractors who accept the EOR offer
• Retention and absence during the 90 days
• Simple pulse survey (for example: “I feel more secure in my job” scores)

Operations

• On-time and error-free payroll runs
• Time to resolve HR queries
• Visibility into attendance, leave and performance metrics

Finance

• Total monthly cost per FTE (salary + statutory + EOR fee) vs current contractor cost
• Effective hourly cost and cost per unit of output (ticket, case, sprint point, etc.)
• FX and fee impact vs existing approach

Risk & Compliance

• Confidence in misclassification risk reduction
• Clarity around DOLE-aligned employment and PH obligations
• Evidence for investor/auditor conversations

3. Decision thresholds

Examples:

• If ≥80% of pilot staff accept and remain after 90 days
• And no material payroll or HR incidents occur
• And cost per FTE is within a pre-agreed range vs contractor baseline

Then you recommend expanding to the next cohort.

 

Step 3: Design the employment landing zone

Before you talk to contractors, design what you are actually offering.

Define the employment model

• EOR partner: which Philippines EOR you will use
• Entity status: confirm you will not use your own PH entity (for pilot clarity)

Set offers and compensation

For each pilot role:

• Gross monthly salary in PHP or your base currency
• 13th month pay setup (usually accrued monthly)
• Employer contributions (SSS, PhilHealth, Pag-IBIG)
• Any allowances (internet, night shift, equipment)
• Optional benefits (HMO, performance incentives)

Confirm HR processes

• How will leave requests work?
• How will timekeeping and attendance be tracked?
• Who handles disciplinary and performance issues?
• How do you terminate under EOR if needed?

Your EOR partner should help shape this, but your internal team must still own the experience and expectations.

 

Step 4: Build your 90-day pilot timeline (30/60/90 structure)

A simple breakdown:

Days 0–30: Design & Communication

• Finalise pilot cohort (5–10 staff)
• Align on comp bands, benefits and EOR pricing
• Run baseline cost modelling vs current contractor costs
• Prepare communication pack:
  • Announcement email
  • Group call agenda
  • 1:1 talking points
  • Written FAQ
• Conduct pilot kick-off call with contractors
• Collect required KYC and documentation for EOR onboarding

Days 31–60: Conversion & Go-Live

• Issue employment offers via EOR
• Sign contracts, update payroll and HR systems
• First payroll run under EOR model
• Monitor:
  • Contractor reactions and queries
  • Any payroll or HR issues
  • Operational impact on managers

Days 61–90: Stabilise & Review

• Run second and third payroll cycles
• Pulse survey staff and managers on experience
• Compare:
  • Actual cost per FTE vs baseline
  • Any changes in quality, output or continuity
• Prepare a pilot report and recommendation:
  • Continue and scale
  • Adjust (for example: different roles/comp, new processes)
  • Pause and revisit later

 

Step 5: Communicate clearly with your pilot contractors

Use your EOR transition communication pack, adapted for a pilot context.

Core messages:

• “We are testing a more stable, compliant way to work with you.”
• “Same work, same team, more formal status.”
• “This is a pilot, not an experiment on your job security.”

Be explicit about:

• What stays the same: manager, tasks, tools, schedule (subject to normal business needs)
• What improves: payslips, benefits, 13th month, statutory contributions, HR support
• What you expect from them during the pilot: honest feedback, flagging issues early

 

Step 6: Set up tools, data and governance for the pilot

Treat this like a mini-program:

• Pilot owner: often COO or Head of People
• Support roles:
  • HR/People Ops
  • Finance / Payroll
  • Team leads for pilot departments
  • EOR account manager

Set up:

• A simple tracker (sheet or board) with:
  • Pilot cohort list
  • Key dates (offer sent, contract signed, first payroll date)
  • Issues log
  • Metrics snapshot
• A shared Slack/Teams channel or email group to handle:
  • EOR queries
  • Payroll clarifications
  • Quick decisions

This way, you avoid issues being buried in private chats or email threads.

 

Step 7: Track the right metrics during the 90 days

You don’t need a giant dashboard; a compact view is enough.

People metrics

• Pilot headcount at start vs end
• Acceptance rate (offers accepted / offers issued)
• Unplanned exits (who and why)
• Pulse survey results (for example, 1–5 scores on security, clarity, satisfaction)

Operational metrics

• Number of payroll errors or delayed payments
• Time to resolve HR queries
• Changes in SLA/FCR/CSAT (for CS roles) or equivalent output metrics

Financial metrics

• Actual employer cost per FTE under EOR vs contractor baseline
• Effective hourly cost
• Cost per unit of output (ticket, case, project, etc.)

Risk & compliance

• Confirmation that PH statutory contributions are being handled correctly
• Comfort level of Legal/Compliance vs pre-pilot status
• EOR performance on documentation and reporting

 

Step 8: Run a structured Day-90 review and make a clear call

At the end of 90 days, hold a pilot review session with:

• CFO / Finance lead
• COO / Operations
• HR / People
• Team leads
• EOR partner (optional, as a listener/input)

Answer:

1. Did this reduce risk in a meaningful way?
2. Did people respond well to the new model?
3. Are costs acceptable vs contractor baseline?
4. Are operations easier, similar or harder?

Then decide:

• Scale: expand to the next 10–20 contractors using the refined process
• Adjust: change comp, process or EOR partner before scaling
• Pause: hold at 5–10 EOR employees and re-evaluate in 3–6 months

Document:

• What worked
• What broke
• What you will do differently for Wave 2

This creates an internal playbook and precedent you can reuse.

 

Example 90-Day Pilot Snapshot (for your board or investors)

You can summarise the pilot like this:

Area	Before (Contractors)	After 90-Day EOR Pilot
Headcount	5–10 Filipino contractors	5–10 PH EOR employees
Risk	High misclassification exposure	Materially reduced, aligned to PH laws
People	No payslips, limited benefits	Payslips, 13th month, contributions
Cost	$X/month total	$Y/month (salary + EOR fee + statutory)
Operations	Ad hoc HR and payroll	Structured payroll and HR workflows
Decision	Unclear if we should scale contractors	Clear go/no-go on EOR expansion

This is the story stakeholders want to hear: we tested, measured and decided — not “we guessed and hoped”.

 

Related resources

This 90-day pilot guide sits SOS’ other PH-focused resources:

• Contractor vs Employee in the Philippines (2025): Tests, Red Flags & Fixes via EOR
  Use it to justify why you need a conversion pilot in the first place.
• Are Your Filipino Freelancers Actually Employees? 10-Question Self-Audit Checklist
  Use it to choose the high-risk profiles for your 5–10 pilot cohort.
• When Should You Convert Filipino Contractors to Employees? (Headcount, Tenure, Risk & Cost Triggers)
  Use it to prove that the timing for a pilot is now, not “someday”.
• Contractor-to-Employee Conversion Matrix for Philippines Teams (2025)
  Use it to prioritise who goes into Pilot Wave 1.
• From Hourly Freelancers to Salaried Employees in the Philippines: Cost Modelling Playbook for CFOs
  Use it for baseline vs pilot cost comparisons.
• Communication Pack: How to Explain an EOR Transition to Your Filipino Freelancers & Contractors
  Use it to run the people side of the pilot without causing panic.

Together, these give you a full stack:

Diagnose → Prioritise → Pilot (this article) → Model → Communicate → Scale

 

FAQs: 90-Day Contractor-to-EOR Conversion Pilots

1. Why start with only 5–10 Filipino contractors?
   Because 5–10 is big enough to surface real issues, but small enough that your HR, finance and ops teams can handle problems manually. It’s the fastest way to get signal without committing your entire contractor base.
2. How do I pick the right people for the pilot?
   Prioritise contractors who are both high-risk and high-value: they work near full-time hours, sit in core roles and have been with you for at least a few months. Use your Contractor-to-Employee Conversion Matrix and self-audit checklist to shortlist them.
3. Do we need to convert pilot staff permanently after 90 days?
   Not automatically. The pilot is a test, not a trap. If it clearly doesn’t work for your business or for specific individuals, you can pause or adjust. The important thing is that expectations are clear from the start and any changes are handled properly and respectfully.
4. What if some contractors don’t want to join the EOR pilot?
   That’s normal. Some contractors will prefer flexibility or worry about change. You can either keep them as contractors for now, or substitute other suitable profiles into the pilot cohort. Their feedback is still useful input for your broader conversion strategy.
5. How much extra admin should we expect during the pilot?
   Expect a short spike: more questions, more checks and some teething issues in the first 1–2 payroll cycles. With only 5–10 staff, this should be manageable, especially if you have a dedicated internal owner and a responsive EOR account manager.
6. Is a 90-day period enough to evaluate EOR?
   For most teams, yes. In 90 days you can see at least two or three payroll cycles, a full onboarding experience and initial sentiment from staff and managers. If you need deeper data (for example seasonal volumes), you can extend the evaluation while still using the same structure.
7. Can we run a pilot if we already have some employees in the Philippines?
   Yes. The pilot is really about testing the EOR model against your existing contractor setup, not whether you have zero employees today. You can still compare risk, cost and operations across contractors, EOR employees and any in-entity hires.
8. Do we need legal advice before launching the pilot?
   The pilot framework here is a practical guide, not legal advice. For higher headcount, sensitive cases or complex contract histories, you should review your plan with local counsel and your EOR provider to make sure the transition path is compliant and fair.

 

Next steps: Start your 90-Day Contractor-to-EOR Pilot

If you’re looking at your roster of Filipino contractors and thinking:

“We probably need to fix this at some point, but I don’t know where to start…”

a focused 90-day pilot with 5–10 staff is usually the safest, smartest move.

Here’s what you can do next:

1. Map your current contractors into a conversion matrix
   • Use the Contractor-to-Employee Conversion Matrix template to score risk and value
   • Shortlist the 5–10 best candidates for a pilot cohort
2. Run a quick cost and risk scan with your leadership team
   • Compare current contractor costs vs a simple EOR model
   • Align CFO, COO, HR and Legal on pilot scope and success metrics
3. Book a 30-minute Contractor-to-EOR Pilot Planning Call
   • Walk through your current PH contractor setup
   • Choose a realistic 5–10 person pilot cohort
   • Sketch a 30/60/90-day timeline and decision criteria