Build a verified contact list for a named account list
A Claude prompt that takes an ABM target account list and returns the right verified contacts inside each account — by role family, by tier, with email and direct dial. Ready to load into a sequence, an outbound batch, or a campaign.
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 have a named ABM account list. I want verified contacts inside each account, organized by buying role.
</context>
<task>
1. Take this account list (paste with company domain or name, and tier):
[PASTE LIST]
2. For each account, use Lusha to find contacts in these role families:
- [ROLE FAMILY 1, e.g. CRO and VP Sales]
- [ROLE FAMILY 2, e.g. RevOps and Sales Ops]
- [ROLE FAMILY 3, e.g. Marketing leadership]
3. For each contact, return:
- Full name, title, company, tier
- Validated email
- Direct dial / mobile
- LinkedIn
- Role family
4. Output grouped by account, then by role family.
5. Flag any account where a target role returns zero contacts — that gap is useful intelligence.
</task>
<constraints>
- Only include contacts with a validated email.
- Cap output at 5-7 contacts per account.
- Skip contacts who left the company.
</constraints>What you'll get back
Input: 10-account ABM list (Snowflake, Databricks, MongoDB, Okta, Cloudflare, Twilio, Datadog, HashiCorp, Elastic, Fastly). Role families — CRO and VP Sales, Head of Revenue Operations.
Output: 160 verified contacts identified across the 10 accounts. Below is a real slice of the live result — eight verified Sales and RevOps leaders across six named ABM accounts, all with validated work emails and phones.
| Contact | Title | Company | Validated email | Phone |
|---|---|---|---|---|
| Keegan R. | SVP of Sales, Americas Acquisition | Snowflake | ✓ | ✓ |
| Marcie W. | SVP of Revenue Strategy and Operations | Snowflake | ✓ | ✓ |
| Bill H. | Vice President of Sales | Databricks | ✓ | ✓ |
| Salvatore D. | Area Vice President of Sales | MongoDB | ✓ | ✓ |
| Slim R. | VP of Commercial Sales EMEA | Datadog | ✓ | ✓ |
| Darryl P. | Vice President of Partner Sales | Elastic | ✓ | ✓ |
| Tony C. | Vice President of EMEA Sales | Twilio | ✓ | ✓ |
| Adam G. | Director of Revenue Operations | Snowflake | ✓ | ✓ |
Names abbreviated for privacy. Full records — including emails and direct dials — are returned inside your Claude session.
Why it works
ABM execution dies in the contact-discovery step. A list of 50 named accounts with no verified contacts is just a list of names. Three things shift when you pair the account list with verified contact data inside Claude.
The contact list is callable today. Every row carries a validated email plus a verified phone, drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
The output is grouped by account. Each account becomes a mini buying group on the page — the AE running the play sees the full surface inside one company, not a flat list of 160 names.
The gaps surface as data. An account that returns zero CRO contacts isn’t a failure — it’s a flag that the buying group has a hole. That gap is the discovery question for the next meeting.
FAQ
How big a named account list can the prompt handle?
Up to a few hundred accounts per run. For 500+ accounts, batch by tier — run Tier 1 first, then Tier 2 — so the output stays readable inside the Claude session.
Can I tier the output?
Yes. Pass tier as a column in the input list, and the prompt groups output by tier first, then by role family inside each tier.
What if some accounts return no contacts?
The prompt flags them. Usually it means one of two things — the company name needs disambiguation (a US fintech versus a UK fintech with the same name), or the role family needs widening for that account. Both are easy fixes in a follow-up prompt.
Can I push results to my campaign platform from Claude?
The Claude output is a structured table you can copy into a CRM, sequence builder, or ABM platform. Direct push runs through Lusha’s standard integrations.
Does the prompt work for EMEA or APAC ABM lists?
Yes. Lusha publishes email accuracy bands at 98% NA, 97% EMEA, 96% APAC, 95% LATAM. The prompt returns rows in any region under the corresponding compliance framework.
Ready to build this?
Get started with Lusha and set up this play in minutes.
