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.
Markets · UK and Europe
Outbound into Europe turns on one clause.
Article 6(1)(f) is what makes B2B prospecting lawful in the UK and EU, and it is a balancing test rather than a box. This page sets out how we meet it, who the processor is, and — plainly — that we have not yet published an engagement in either market.
No published engagement yet · lawful basis stated · 5–7 day turnaround
- 92%+
- Deliverability target
- Stated guarantee · 2026
- 750
- Verified leads, Pilot
- 250 companies · 3 contacts each · 2026
- 5–7d
- Turnaround
- From a confirmed brief · 2026
What we can show you
What we can evidence here, and what we cannot.
This is a market we research into, on a client’s behalf — and the one market page here with no published engagement behind it. Stated at the top rather than left to be found.
We research the United Kingdom and Europe and price work there on the same terms as everywhere else. We have not published a case study from either, and we are not going to imply one. So this page states what is checkable instead — which is most of what a UK or EU buyer is actually assessing before a first project.
- The lawful basis
- Legitimate interest under GDPR Article 6(1)(f), balanced against the individual’s rights, with a first contact relevant to their professional role.
- A named processor
- One office in Kaloor, Kochi, operating as Gallivant Ventures LLP. That is the answer a DPA needs, and most firms selling contact data will not give it.
- A signed DPA
- Published in full and signed for any engagement where we handle records you already hold. Ask on the Project Brief and we send it.
- Removal that works
- Deletion requests honoured against a suppression list. Source data is deleted within ninety days of delivery unless you ask us to hold it.
- EMEA sourcing
- Cognism, which describes itself as EMEA-centric, is one of the twenty-plus sources we triangulate across. No record rests on a single source.
- The same method and price
- Four stages with a person at every one, and a Pilot at $420 for 750 verified leads in 5–7 days. Geography changes neither the standard nor the rate card.
What we cannot show you
- A published UK or EU case study. There is not one yet, and this page will carry it when there is.
- A delivered volume in these markets, because we have not published one and will not quote a figure we cannot point at.
- Your own sending setup. SPF, DKIM and DMARC stay yours, and the bounce replacement assumes they are in place.
Seven engagements are published in the other markets — see the case studies, or 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 countries, regions or cities — the UK and a single EU market are different briefs
- Company band
- Revenue, headcount or funding stage, set per project and checked per account
- Buying centre
- CIO · VP Engineering · Head of Data · the titles you name on the brief
- Lawful basis
- Legitimate interest under GDPR Article 6(1)(f). Sources auditable on request
- On the call
- A senior analyst will tell you if this is not a market we should take on for you
The compliance basis
Article 6(1)(f) is a balancing test, not a checkbox.
Processing business contact data for B2B prospecting is lawful in the UK and EU under legitimate interest, provided the interest is balanced against the individual’s rights and the first contact is relevant to their professional role. What it is not is consent — and a purchased list cannot manufacture consent it never had.
- Not consent
- It is not lawful to treat a purchased list as consent. Any vendor implying otherwise is selling you a problem, not a shortcut.
- Provenance
- What matters in practice is whether the seller can show where each record came from. Ours come from public business directories, company websites and licensed platforms under their terms, and the source of any delivered record is auditable.
- Deletion
- A deletion request has to actually work. Ours is honoured against a suppression list, and the DPA states it rather than leaving it to goodwill.
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.
Is a bought list legal in the EU?
A list is not consent
Legitimate interest is the basis, and it holds only where the seller can evidence provenance and honour deletion. Both of those are things you should ask any vendor to demonstrate rather than assert — including us. We publish the DPA and the sourcing position so the question is answerable before the call.
You have no European case study.
Correct, and we say so
Seven engagements are published, five in the United States and two in the Gulf. None in the UK or EU. We could have written this page as though there were, and you would have found out later. The method, the lawful basis and the price are the same; the delivered proof in this market is what is missing, and it is the first thing this page tells you.
Your researchers are in India.
That is the DPA answer
A UK or EU buyer has to name the processor and the jurisdiction in a DPA, and most vendors will not say where the work happens. We answer with an address in Kaloor, a legal entity, and five named analysts. Being able to answer that is worth more here than a nearer postcode.
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 · 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.
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.
Industries · IT services
Delivery capacity sold to a CIO
Your buyer is a technology function inside an industry you do not work in. Three published engagements mapped that buying centre in three sectors.
FAQ
What UK and EU buyers ask before briefing us.
You have not published a UK or EU engagement. Why brief you at all?
Because the parts that transfer are the parts you are buying: a person checking every record against a live profile and the company website, a stated lawful basis, an auditable source trail and a 7-day bounce replacement. What does not transfer is delivered proof in your market, and a Pilot at $420 exists precisely so you can test that for the price of finding out.
Who is the processor, and where does the processing happen?
Gallivant Ventures LLP, from one office in Kaloor, Kochi. There is no offshore delivery arm behind the Indian one and no subcontracted data supplier — the analyst who joins your Project Brief is the analyst who runs the delivery. That is the answer that goes in your DPA.
Do you treat the UK differently from the EU?
The lawful basis is the same test under UK GDPR and EU GDPR, so the research standard does not change. What changes is the brief: the UK and a single EU market are separate territories with separate company sets, and pricing one territory does not cover the other.
Book a project brief