Markets · India
Indian firms, export pipelines
Every engagement we have published was run from Kochi into an export market. Same time zone as you, INR invoicing, GST handled correctly.
Markets · UAE and the GCC
A Gulf list has to be read, not exported.
The GCC is six states with different corporate structures, and a job title that means one thing in Dubai can mean another in Riyadh. Two published engagements mapped hospitals, labs, pharma firms and payments companies across the UAE and Saudi Arabia on that basis.
2 delivered engagements · 390 verified leads · 100 companies mapped
- 92%+
- Deliverability target
- Stated guarantee · 2026
- 750
- Verified leads, Pilot
- 250 companies · 3 contacts each · 2026
- 5–7d
- Turnaround
- From a confirmed brief · 2026
Delivered work
Two engagements, published in full.
This is a market we research into, on a client’s behalf. Our clients are IT companies; the Gulf organisations below are theirs to sell to.
Each row is a project that shipped, named by the territory it was briefed on. A market page with nothing behind it would be a claim rather than a capability, so this table is generated from the engagements — not written.
| Territory | Sector researched | Turnaround | Companies | Verified leads |
|---|---|---|---|---|
| UAE and the wider GCC | Healthcare and pharma | Growth standard, 10–14 days | 60 | 240 |
| Dubai and Saudi Arabia | Fintech and payments | Growth standard, 10–14 days | 40 | 150 |
A market we research into — see how the markets differ.
What the brief locks here
Geography is the first field, not the last.
It is locked before titles, volume or timeline, because it decides compliance, time zones and the window your outreach can run in. These are the fields that differ in this market.
- Granularity
- Named emirates, cities or states — the UAE and Saudi Arabia have both been briefed separately
- Account type
- Set per project. Published work covers hospital groups, labs, pharma firms, BNPL providers and payments enablers
- Buying centre
- CIO · VP Automation · Director of IT · Head of Digital · VP Product
- Qualifier
- An active digitisation or automation programme, evidenced before the account qualifies
- Working window
- Kochi is 1.5 hours ahead of the UAE, so a brief raised in the morning is answered the same day
The compliance basis
The UAE PDPL equivalent, stated rather than implied.
Gulf procurement asks where the data was produced and under which jurisdiction, and most vendors selling contact data do not answer. We answer with an address in Kochi, a legal entity, and five named analysts — which is the same answer a DPA needs.
- Lawful basis
- Legitimate interest under GDPR Article 6(1)(f), with equivalents under the UAE PDPL and CCPA. Sources are auditable on request.
- Where the work happens
- One office in Kaloor, Kochi. No offshore delivery arm behind the Indian one and no subcontracted data supplier.
- DPA
- Signed for any engagement where we handle records you already hold. Ask on the Project Brief and we send it for signature.
The full position, with every policy and the date it last changed, is on the data and compliance page.
How we verify
Four stages. A person at every one.
| Stage | What happens | Artifact produced |
|---|---|---|
| 01 Brief | A 30-minute Project Brief call with a senior analyst — not an SDR — to scope the ICP, territory, titles, volume and timeline. Ten fields, all required before research begins. If the brief shows we are not a fit, we say so before any work starts. | The signed research brief |
| 02 Source | Analysts map the territory across twenty-plus sources — ZoomInfo, Apollo, Clay, LinkedIn Sales Navigator, Cognism, Lusha, Crunchbase, PitchBook and company websites — triangulated rather than exported. Accounts outside the brief are dropped here. | The raw master source sheet |
| 03 Verify | Every contact is cross-checked by a person against LinkedIn and the company website: current role confirmed, employer matched, email format validated. The date of that check is recorded on the row. SMTP-only verification is the floor, not the ceiling. | The LinkedIn cross-check log |
| 04 QA and deliver | A 10% spot-check by a second person, with zero QA failures permitted — anything that fails goes back to the analyst. Records that cannot be confirmed are removed, not shipped as Pending. Then a CRM-ready XLSX and CSV with a count summary. | The QA spot-check sheet |
What buyers ask first
Three trade-offs we do not make.
Gulf data is always out of date.
Exports are. People are not
A regional database ages faster than a US one and corrects slower, which is an argument for a person opening the profile rather than against researching the market at all. Anything we cannot confirm is removed before delivery, and the count you get is the count that survived.
We need the whole GCC.
Name the states
One published engagement covered the UAE and the wider Gulf; the other ran Dubai and Saudi Arabia. Those are different briefs with different structures behind them. Buying "the GCC" as one filter produces a list that is wrong in five of six states.
Can you reach the people who actually sign?
The ones we can confirm
Published engagements mapped CIOs, VPs of Automation, Directors of IT, Heads of Digital and VPs of Product. Procurement and finance titles can be added to the brief. What we will not do is ship a title we could not confirm against a live profile and the organisation’s own site.
Read it the other way
By market, or by what you sell to.
The same engagements, indexed twice. If you arrived by geography, the vertical pages read them by sector.
Markets · United States
Corridors, not a country
California, Florida, Texas and New York have each been researched on a published engagement. A US brief locks the corridor before it locks the titles.
Industries · Healthcare and pharma
Hospital and pharma buyers in the Gulf
Organisation structures vary more between Gulf markets than an export suggests. One published engagement across the UAE and the wider GCC.
Industries · Fintech and payments
Payments buyers in a small market
The tightest scope of the seven published engagements. A padded list would have been obvious on the first send, so nothing was padded.
FAQ
What buyers ask about Gulf research.
Which Gulf states have you delivered into, and how do they differ?
Two published engagements: one across the UAE and the wider GCC, one across Dubai and Saudi Arabia. They were separate briefs because the organisations are structured differently — a Director of IT at a Dubai hospital group and one at a Riyadh network do not hold the same remit. The file reflects that rather than flattening it.
Is cold outreach into the Gulf lawful?
Processing business contact data for B2B prospecting runs on legitimate interest, with the UAE PDPL equivalent. Records come from public business directories, company websites and licensed platforms used under their terms, and the source of any delivered record is auditable on request. The sending obligations stay with you as the sender.
Do you price GCC projects in dirhams?
No. Invoices are raised in USD or INR, and GCC buyers are quoted in USD — a Pilot is $420 for 750 verified leads. There is no AED column because there is no AED invoice. International invoices are raised under export-of-services rules.
Book a project brief