Expanding to MENA
Build, EOR, or specialist?
Three routes for UK and Irish businesses expanding into MENA. Each has a different commitment level, cost profile, and compliance posture. This page lays out which fits when — without trying to sell you the one that pays us.
UK and Irish businesses expanding into MENA typically choose between three routes: Build (open your own entity in the target market), EOR (use an Employer of Record for the legal employment relationship), or Specialist (contract a UK-registered MENA payroll specialist for the operating layer). Build amortises best at scale and long horizons; EOR fits first hires and short-term engagements; Specialist fits ongoing multi-market operations once you have an entity. Most operators run a hybrid across markets.
The three routes
What each route is, and what it isn't
Each route has a fit window. Outside it, the maths or the operating reality stops working.
Build
Open your own entity in each MENA market
Scaling beyond ~25 employees in one market with a 2+ year horizon. The cost of entity setup amortises across enough payroll cycles to make sense.
Highest fixed cost. Entity setup, registered agent, ongoing accounting, statutory filings — per market.
Months. Saudi RHQ programme can run 6–9 months end-to-end. UAE mainland or free zone, 2–4 months. Egypt, 3–6 months.
You hold all compliance directly. Mistakes are yours to remediate; protections are yours to design.
First hires. Testing the market. Anything under ~10 employees per market. Anywhere you need to be operating in under 3 months.
EOR
Employer of Record holds the contract
First 1–3 hires per market. Testing the market. Short-term engagements. Project-based hires you'd contract back through your own entity once the market scales.
Per-employee monthly fee plus statutory pass-through. Low fixed cost; cost-per-head higher than entity ownership beyond a threshold.
Weeks. Most MENA EOR onboarding is 2–6 weeks depending on visa pathway.
EOR holds the legal employment relationship and absorbs the compliance surface. You direct the work; the EOR handles the registrations.
High-headcount markets where your per-employee EOR cost exceeds entity-overhead-amortised cost. Very long-term engagements where building IP into your own entity is part of the strategy.
Specialist
Contract a UK-registered MENA payroll specialist
You have your own entity (or you're moving toward one) and you want the operating layer handled — calculations, statutory files, audit trail — without building MENA payroll capability in-house. Multi-market MENA is the sweet spot.
Management fee per cycle (sterling on request). Statutory pass-through at cycle rate. Cheaper than building MENA payroll capability internally; competitive with EOR once headcount grows.
Two to three cycles to handover from an incumbent provider, or one cycle to start fresh on a new entity.
You keep the legal employer relationship and the registrations; the specialist handles the calculation and reporting. UK contract law applies to the supplier relationship.
Single-employee, single-market engagements where the management fee doesn't amortise. Very short-term (under 6 months) operations.
Compare
Side by side
The dimensions UK and Irish CFOs use to make this call.
| Dimension | Build | EOR | Specialist |
|---|---|---|---|
| Time to first hire | 3–9 months (entity setup) | 2–6 weeks | 1–3 cycles (depending on entity readiness) |
| Fixed setup cost | High (per market) | Low | Low (your entity is the fixed cost, not the specialist) |
| Per-employee cost at scale | Lowest beyond ~10 employees | Higher per head; predictable | Competitive with build at moderate scale; better than EOR over time |
| Compliance burden | All on you | All on the EOR (within their scope) | Calculation + reporting on the specialist; submission and registration on you |
| Best fit horizon | 2+ years per market | Months to a year | Long-term operating layer for multi-market MENA |
| Multi-market efficiency | Each market is its own setup | Each EOR engagement is its own contract | One operating layer across all eleven MENA markets |
In practice
Most UK and Irish operators run a hybrid
Build in the highest-headcount market — often Saudi Arabia or the UAE, where headcount supports the entity overhead. EOR in markets where you have one or two hires and aren't ready to commit. Specialist as the operating layer once you have an entity, taking calculation, statutory file generation, and audit trail off your team's plate. The three routes are not mutually exclusive.
- Saudi Arabia: Build + Specialist (entity established for RHQ or scale; specialist runs the cycle)
- UAE: Build or EOR depending on headcount (federal-vs-DIFC + WPS reality)
- Egypt, Morocco, Jordan: EOR for first hires, Build once headcount supports it
- Lebanon, Algeria: Country-specific operational treatment — talk to us
FAQ
Common questions on the build / EOR / specialist call
Do I have to pick one route across all MENA?
No. Most operators run a hybrid. Build in your highest-headcount market (often Saudi or UAE), run EOR in markets where you have one or two hires, and contract a specialist for the operating layer once the entity is in place. Switching between models for a given market is a configuration change, not a re-onboarding.
When does Build stop making sense?
Below ~10 employees per market the entity overhead doesn't amortise — entity setup, registered agent, statutory filings, accounting overhead, and ongoing director liabilities all cost the same whether you have 2 employees or 200. EOR or Specialist usually wins at that scale. Above ~10 employees, the maths flips.
Why a Specialist rather than a generic global EOR or global payroll platform?
Generic global vendors handle MENA as another row in a spreadsheet. Mudad, WPS, GPSSA on the federal-vs-DIFC split, ILOE, Egyptian progressive brackets, the EOSB rules that vary country by country — these are the calculation surfaces where generic platforms fall short. A specialist runs only MENA. One engine. One audit trail. Eleven countries.
What does the Specialist relationship look like for UK and Irish CFOs?
Contracting party is Global Kinect Ltd, a UK company (Companies House 16852789, registered in England and Wales, VAT GB513719302). Management fee invoices in sterling on request under standard UK B2B place-of-supply rules. Statutory pass-through is denominated in local currency at cycle rate, passed through at cost. Per-cycle reporting maps cleanly to UK GAAP cost categories.
How does the Saudi RHQ programme change the calculus?
RHQ status changes the regulatory context for businesses headquartering their MENA regional operation in Saudi Arabia. From a payroll perspective, RHQ employees are treated as standard Saudi-entity employees by the engine — no special configuration. Where RHQ matters most is in the Build calculus: it tilts the case toward establishing a Saudi entity rather than running EOR for Saudi hires.