Build a list of companies in a specific geography
A Claude prompt that returns verified companies and contacts inside a specific country, region, state, or metro — with regional accuracy bands and compliance footprint surfaced upfront so the list is safe to action.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the prompt and run.
Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.
The prompt
<context>
I want to build a verified prospect list inside [GEOGRAPHY, e.g. DACH region, UK, Texas, APAC].
I sell [PRODUCT] to [BUYER DESCRIPTION].
</context>
<task>
1. Use Lusha's company search to find companies matching:
- Geography: [SPECIFIC REGION / COUNTRY / STATE / METRO]
- Industry: [INDUSTRY]
- Headcount: [RANGE]
2. For each company, find contacts in [TITLE FAMILY].
3. Enrich each contact with verified email, direct dial, and country.
4. Return a table:
Company | HQ city | Country | Contact | Title | Email | Direct dial | Compliance footprint (GDPR / CCPA / both)
5. Group output by country.
</task>
<constraints>
- Only include contacts with a validated email.
- Note the regional email accuracy band in a header line (NA 98%, EMEA 97%, APAC 96%, LATAM 95%).
- Surface any contact based in a region with stricter consent rules so the user can confirm outreach approach.
</constraints>What you'll get back
Input: Geography — DACH (Germany, Austria, Switzerland) · Industry — manufacturing · Headcount — 501–5,000 · Titles — Head of Procurement, COO, VP Procurement.
Output: 437 matching contacts identified in the first batch across DACH manufacturing. Below is a real slice of the live result — five verified procurement and operations leaders at named German manufacturers, all with validated work emails and phones. EMEA email accuracy published at 97%, processed under GDPR.
| Contact | Title | Company | Validated email | Phone |
|---|---|---|---|---|
| Jan Henner T. | Chief Procurement Officer | MEYER WERFT | ✓ | ✓ |
| Oliver F. | Vice President of Procurement | RENK Group | ✓ | ✓ |
| Christian S. | VP of Global Procurement | KraussMaffei | ✓ | ✓ |
| Florian H. | Chief Operating Officer | Brainlab | ✓ | ✓ |
| Norbert T. | Chief Operating Officer | SAMSON GROUP | ✓ | ✓ |
Names abbreviated for privacy. Full records — including emails and direct dials — are returned inside your Claude session.
Why it works
Geographic prospecting fails when the data quality drops at the regional level. A list of EMEA contacts with NA-grade decay rates is not safe to send — and a list of APAC contacts pulled from a US-skewed database returns thin coverage with stale titles.
Lusha publishes accuracy bands by region — 98% in North America, 97% in EMEA, 96% in APAC, 95% in LATAM — and processes data under the relevant regional compliance frameworks. The prompt surfaces those bands inline, so the geography filter doesn’t silently degrade the output.
The prompt pulls from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe — safe to action across regions.
FAQ
Can I target a specific metro or state, not just a country?
Yes. The prompt accepts metro-level inputs like “Greater London,” “Bay Area,” or “São Paulo.” Claude resolves the location against Lusha’s catalog before running the search.
Does the prompt handle multi-country territories?
Yes. List each country in the geography variable — for example, DACH as Germany, Austria, Switzerland — and the output groups by country for clean territory work.
Are contacts in regulated regions flagged?
The prompt is built to surface contacts where the compliance footprint requires opt-in or specific consent handling, so you can route to the right channel deliberately.
What's the email accuracy band by region?
98% North America, 97% EMEA, 96% APAC, 95% LATAM. Published in the Lusha data documentation and refreshed continuously.
Does Lusha cover EMEA, APAC, and LATAM as deeply as North America?
Coverage varies by region and industry. The prompt returns only verified rows — if a region or persona is thin in Lusha’s data, the search returns fewer rows rather than padding with low-confidence matches. Use the filter-relax suggestion at the bottom of the prompt if results come back light.
Ready to build this?
Get started with Lusha and set up this play in minutes.
