A CRM worth calling.
The list is the job everywhere. The UAE simply charges more for it — and most tools quote the price before they've read the market.
Why the UAE makes it hard
A current, targeted contact database is the spine of outbound. Building one here runs into five things at once:
- The market moves. One of the world's highest expatriate turnovers — a number or a title that was right six months ago is a coin-flip today.
- The registries are fragmented. JAFZA, DIFC, DMCC and dozens of free zones each keep their own records; global databases surface them unevenly.
- The names don't reconcile. A company sits under its English trade name in one source and its Arabic legal name in another. Dedupe is a real piece of work, not a checkbox.
- The mobiles are gatekept. Verified GCC direct dials are the hardest, most guarded data — and the higher the seat, the harder it gets.
- The law has teeth. PDPL governs personal data. An enriched mobile used carelessly is exposure, not an asset.
Two ways in
You reach the list from one of two places. The engine works from either, and ends both in the same place — a record worth a call.
Contacts without context. The engine returns who they are — company · title · LinkedIn — so the next touch is personal, not cold. This is how a tired CRM is made useful again.
A definition without the names — company, seniority, function. The engine returns the matching decision-makers as full records — name · title · company · tel · email · LinkedIn — ready to load. This is how a CRM is built from nothing.
The pipeline — paid step last
The discipline that makes it cheap: free legs first, paid leg last, verification before any send. You never pay to enrich a row you haven't already decided to contact.
- Source (free). Apollo people-search, Firecrawl scrape, Serper SERP — name, title, company, LinkedIn from public and database surfaces. Bound the universe before spending a credit.
- Map (free). Account and committee map, switchboard attached.
- Prioritise. ICP-score, decide who is worth a paid reveal. Most rows never need one.
- Reveal (paid, last). Apollo or waterfall enrichment — verified email and direct phone, only on prioritised rows. ~1 credit per record.
- Verify. Reacher gates email deliverability before anything is sent. Unverified rows are never contacted.
- Load. Push to the CRM — HubSpot, Airtable, Salesforce, Pipedrive.
Tools & status
What's wired, what's keyed, what's a phone call away.
| Tool | Role in the engine | Status | Cost |
|---|---|---|---|
| People + company search and per-record enrich. The census engine. | ● Live · paid | ~1 credit / revealed record | |
| Public-web scrape + search — free leg. | ● Live | credit-cheap | |
| Google SERP as JSON — free-leg search + LinkedIn slug lookup. | ● Live | credit-cheap | |
| Sales Nav list export + email/phone reveal. | ◐ Keyed · 0 API credits | API needs paid credits; free tier 20 email / 5 phone | |
| Sales Nav search → clean CSV + emails (Chrome extension). | Option | ~$50 / 1,000 leads | |
| API enrich + reverse-phone match. Pipeline-grade. | Not keyed | ~$98/mo · weak GCC mobiles | |
| True reverse-phone → person + LinkedIn (phone-in). | Not keyed | credit-based | |
| Budget waterfall, 20+ sources, email + phone. | Not keyed | $15/mo · 200 credits | |
| Phone-verified mobiles, GDPR-defensible. European-led; UAE depth modest. | Not keyed | $15–25k/yr + seats | |
| Self-hosted email verification — deliverability gate before send. | Free / self-host | $0 | |
| Orchestration — normalise, dedupe, route, write to CRM. | ● In stack | self-host |
The live test — Apollo, 20 Jun 2026
Probe against a single UAE conglomerate domain to prove the engine end-to-end.
Search-level data (titles, company, masked names) is near-free. The job is to spend credits only on prioritised rows, never the whole pull.
Lots of tools promise. Here's the reality.
Every vendor's landing page promises the whole list at a click — every contact, verified mobiles, no misses. In the UAE that promise meets the market above. Here is what actually comes back, and the limits to read before you quote anyone a number.
| Field | Realistic hit-rate | Note |
|---|---|---|
| Name · title · company · LinkedIn | 85–95% | strongest layer; free-to-cheap |
| Verified email | 60–75% | corporate; verify before send |
| UAE direct mobile | 25–45% | the ceiling — vCard-assist lifts to 50–60%; gatekept at C-suite |
Limitations — read before quoting a number
| Limit | What it means |
|---|---|
| UAE mobile ceiling | No tool beats 25–45% on verified UAE direct mobiles, whatever the landing page claims. GCC mobiles are the hardest, most gatekept data. Plan for switchboard + LinkedIn at the top tier. |
| Masked until enrich | Search returns masked names and "available" flags. Email/phone cost a credit each to reveal. Budget the reveal, not the search. |
| Freshness / churn | UAE expat turnover staletes data fast; titles drift. No single database stays current — the waterfall beats any standalone. |
| LinkedIn ToS / ban | Scraping on your own account risks a ban; safe rate ~60–80 profiles/day. Proxycurl was sued and shut down in 2025 — never put a scraper-reseller on the critical path. |
| PDPL / GDPR | Enriched personal mobiles used for cold outreach carry UAE data-protection exposure, sharper at C-suite. The licensed-provider route is the defensible posture. |
| Verify before send | One bounce off a target domain burns sender reputation. Reacher gates every row first. |
Free legs first, paid leg last, verify before send.
The engine's value is not the data vendors — it is the discipline that spends a credit only on a row already worth contacting, and never ships a number it hasn't verified.