What UAE finance and ops leaders ask before they outsource — answered straight.

A fully loaded in-house seat in Dubai or Abu Dhabi carries a set of costs that never show up in the job offer: visa and Emirates ID processing, mandatory health insurance, end-of-service gratuity accrual, desk space and utilities in a free zone or mainland office, telephony and CRM licensing, recruitment and training amortised over the role's tenure, and a share of team-lead, QA and workforce-planning overhead. Individually small, together they typically run close to what the salary itself costs.

The comparison that matters isn't salary-to-salary — it's fully-loaded-seat to fully-loaded-seat. Once you add the items on the left, an offshore seat quoted at a single flat rate usually comes out well under half the in-house figure, even before accounting for the flexibility of scaling seats up or down without severance exposure.

Offshore agents are employed by the vendor, in another country, under that country's labour law. They never appear on your UAE payroll and never count toward your MOHRE headcount, which means they sit outside your Emiratisation calculation entirely — they neither help nor hurt your Nitaqat or Emiratisation band.

The practical pattern most companies land on:

• Keep the roles your quota requires onshore — the skilled, customer-facing, or regulated positions that count toward your target stay staffed with UAE-based employees.
• Offshore the overflow and out-of-hours volume — after-hours coverage, weekend spikes, seasonal surges and repetitive back-office work move to the managed team.
• Treat the two as separate headcount pools from the start, so your quota planning and your support capacity planning don't collide at renewal time.

Delivery for a managed programme happens at the offshore hub — typically Cairo, Amman, Delhi or Kolkata — so this is, by definition, a cross-border personal data transfer under UAE Federal Decree-Law No. 45 of 2021 (the PDPL). If your entity sits inside DIFC or ADGM, a separate free-zone data regime applies on top of the federal law, with its own transfer conditions.

Four things should be confirmed and documented before a vendor is contracted, not after:

• Lawful basis for transfer — consent, contractual necessity, or another basis recognised under the applicable regime.
• Hosting jurisdiction, named explicitly — which country the data is processed and stored in, in writing.
• A signed data processing agreement (DPA) — setting out the vendor's obligations, breach notification terms and sub-processor rules.
• Current security certification — ISO 27001 and SOC 2 evidence that's actually current, not an expired certificate screenshot.

Sector-specific rules stack on top of the general PDPL requirements where relevant — SAMA rules for banking and payments data, CBUAE requirements for financial institutions, and DoH requirements for health data. If your data falls under one of these, the vendor screening needs to reflect the stricter regime, not just the baseline PDPL.

An offshore outsourcing contract is typically treated as an imported service. Rather than the vendor charging VAT, the receiving company self-accounts for it through the reverse-charge mechanism — reporting both the output and input VAT on its own return, so in most fully taxable businesses the net cash impact is nil, though the transaction still needs to be correctly reported.

• UAE: standard VAT rate of 5% applies to the reverse-charge entry.
• Saudi Arabia: standard VAT rate of 15% applies under the equivalent mechanism.
• Treatment depends on registration status and where the service is deemed to be supplied, which can vary by contract structure.

Every rate quoted by a properly screened vendor should be stated exclusive of VAT, so there's no ambiguity about what's being reverse-charged versus what's a straight cost.

Most GCC support programmes end up split across two hubs rather than concentrated in one, because Arabic capability and high-volume English/Hindi capability tend to live in different places.

A common split for a Gulf-facing programme: Arabic-first voice and complaints handled from Cairo or Amman, high-volume English/Hindi chat and back office from Delhi or Kolkata, and Malayalam coverage from Kochi where the customer base calls for it. The mix is decided during scoping, not guessed at afterward.