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
A small market is where padding shows first.
BNPL providers and e-commerce payments enablers mapped across Dubai and Saudi Arabia. It is the tightest scope of the seven published engagements: the addressable set was small enough that precision mattered far more than volume.
1 delivered engagement · 150 verified leads · 40 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
One engagement, published in full.
You sell payments or banking technology. This is a page about the market you sell into, not about your own company.
Each row below is a project that shipped, and each opens the case study it came from. A vertical with nothing behind it would be a claim rather than a capability, so this table is generated from the engagements — not written.
| Engagement | Market | Package | Companies | Verified leads |
|---|---|---|---|---|
| Fintech and payments | Dubai and Saudi Arabia | Growth lead generation | 40 | 150 |
What we research into — see how the two lists are told apart.
The buying centre
The titles an analyst actually researched.
Not the titles this vertical probably has. Every row below appears in the persona research on an engagement above, and each says which one.
- CIO
- Named on the GCC fintech engagement.
- Head of Digital
- Named on the GCC fintech engagement.
- VP of Product
- Named on the GCC fintech engagement.
Why this vertical is hard
When the market is small, volume is the tell.
A narrow vertical in two markets has a countable number of real accounts. Any list longer than that number is padded, and the buyer finds out on the first send. We size the file to what can be verified and state the number before you buy.
- Scope agreed as a count, not as a target to fill.
- Every contact triangulated across at least two of twenty-plus sources before a person checks it.
- Generic inboxes — info@, sales@, hello@ — are excluded rather than counted.
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.
Our addressable market is 40 companies.
Then 40 is the file
The published engagement delivered exactly that shape: a narrow vertical, two markets, high precision and no padding. A list that arrives longer than your market is not generosity. It is the first evidence that nobody checked it.
We need compliance and risk contacts.
Name them on the brief
The published engagement mapped CIOs, Heads of Digital and VPs of Product — the roles shaping the regional payments stack. Compliance and risk titles can be added, and like every other title they ship only where a person confirmed the role against a live profile.
Regional banking data is unreliable.
Unread data is
Payments firms restructure and rename faster than a database re-crawls them. That is an argument for reading the company site rather than for accepting the export. Anything we cannot confirm is removed before delivery, and the count you get is the count that survived.
What the brief locks
Agreed in 30 minutes, before any sourcing starts.
A senior analyst runs the Project Brief — not an SDR. These are the fields that decide the file in this vertical. If the brief shows we are not a fit, we say so before any work begins.
- Geography
- Dubai and Saudi Arabia on the published engagement; US, UK and EU on request
- Account type
- BNPL providers and e-commerce payments enablers
- Buying centre
- CIO · Head of Digital · VP Product
- Volume
- Sized to the addressable set, and stated before you buy
- Lawful basis
- Legitimate interest under GDPR Article 6(1)(f), with CCPA and UAE PDPL equivalents
Nearby verticals
Adjacent work, published the same way.
Industries · B2B SaaS
Software sold to a committee
Engineering, data and product leaders evaluate the same purchase. Two published California engagements mapped all three at every account.
FAQ
What payments vendors ask about a narrow market.
Is 150 leads enough to run a campaign on?
In a vertical with 40 real accounts, yes — that is roughly four decision makers at every company in the market. Volume targets are set by the addressable set, not by a package. If your market supports 2,500 leads, Growth delivers that instead.
Do you cover UK and EU fintech as well as the Gulf?
Yes. The published fintech engagement ran across Dubai and Saudi Arabia, and the firm researches the US, UK, Europe and the Middle East. UK and EU outreach runs on the same lawful basis — legitimate interest under GDPR Article 6(1)(f) — which is stated on the compliance page.
Can you tell us which payments firms are actively buying?
We qualify on what is evidenced: funding, hiring signals, tech-stack indicators and public initiatives. We will not label an account as in-market on the strength of an inference. Where the signal exists it is on the row; where it does not, the row says nothing.
Book a project brief