Build a verified buying group for a target account
A Claude prompt that turns a single target account into a complete map of decision-makers, influencers, users, and economic buyers — each with validated email and direct dial. Lusha runs the contact and org search. Claude structures the output by role in the buying process.
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'm working a target account: [COMPANY NAME / DOMAIN].
I sell [PRODUCT] to [PRIMARY BUYER].
The full buying group includes economic buyer, technical evaluator, end user, and influencer.
</context>
<task>
1. Use Lusha to find verified contacts at [COMPANY NAME] across these role families:
- Economic buyer: [TITLES, e.g. CFO, VP Finance]
- Technical evaluator: [TITLES, e.g. CTO, VP Engineering]
- End user: [TITLES, e.g. VP Sales, Head of Sales]
- Influencer: [TITLES, e.g. RevOps, Procurement]
2. For each contact, return:
- Full name
- Title
- Validated email
- Direct dial / mobile
- Buying role (one of the four above)
3. Group the output by buying role and order by seniority inside each group.
4. Flag any role family where the result returns zero contacts — that gap is a discovery question, not a failure.
</task>
<constraints>
- Only include contacts with a validated email.
- Skip contacts who left the company.
- Cap at 5 contacts per role family for readability.
</constraints>What you'll get back
Input: Target account — Snowflake. Buying group spec — CFO and VP Finance (economic), CTO and VP Engineering (technical evaluator), VP Sales and Head of Sales (end user), VP RevOps and Director RevOps (influencer).
Output: 63 verified contacts identified across the four role families — 7 in Finance, 40 in Engineering, 14 in Sales leadership, 2 in RevOps. Below is a real slice of the live result — eight named decision-makers across all four buying roles, all with validated work emails and phones.
| Contact | Title | Buying role | Validated email | Phone |
|---|---|---|---|---|
| Brian R. | Chief Financial Officer | Economic buyer | ✓ | ✓ |
| Brad F. | SVP of Finance | Economic buyer | ✓ | ✓ |
| Dwarak R. | VP and Head of AI Engineering and Research | Technical evaluator | ✓ | ✓ |
| Alex D. | SVP of Solutions Engineering | Technical evaluator | ✓ | ✓ |
| Keegan R. | SVP of Sales, Americas Acquisition | End user | ✓ | ✓ |
| Mark F. | SVP of Sales | End user | ✓ | ✓ |
| Patrick H. | VP of Revenue Operations | Influencer | ✓ | ✓ |
| Adam G. | Director of Revenue Operations | Influencer | ✓ | ✓ |
Names abbreviated for privacy. Full records — including emails and direct dials — are returned inside your Claude session.
Why it works
ingle-threaded outbound is the most common reason enterprise deals stall. The fix is multi-thread from the first touch — but the work of finding the right contact at every level inside one account is exactly the work that gets skipped. Pairing the four-role buying group spec with verified contact data turns that work into a one-prompt step.
Three things shift when the buying group lands inside Claude this way.
The output is grouped by buying role. The economic buyer thread sits next to the influencer thread, with seniority preserved inside each. The AE running discovery sees the full surface of the buying committee, not a flat list of names.
The data is callable today. Every contact carries a validated email plus a verified phone, drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
Gaps surface as intelligence. An account that returns zero contacts in a role family isn’t a failure — it’s a flag. Either the role lives under a different title at this account, or the buying group has a real hole. Both turn into questions for the next discovery call.
FAQ
How many contacts should a full buying group have?
For enterprise opportunities, 7-15 verified contacts across the four role families. Mid-market and SMB deals can run with 3-5. The prompt caps at five per role for readability — for deeper coverage, pass higher caps in the constraint block.
Can the prompt handle accounts in EMEA or APAC?
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.
What if a role family returns zero contacts?
The prompt flags the gap. Two common causes — the role lives under a non-standard title at that company (Snowflake has “VP of Solutions Engineering” rather than “CTO,” for example), or the buying group has a real hole. Both are useful information for discovery.
Can I run this for a list of accounts instead of one?
Yes, but the output gets long. For a multi-account run, use the named account list prompt instead — it returns a flatter table designed for batch outbound. This prompt is built for the single-account drill-down before a strategic meeting.
How is this different from a regular contact search at the company?
A flat contact search returns everyone in seniority at the account. This prompt structures the output by buying role, which is the lens an AE actually needs — economic buyer thread, technical thread, end-user thread, influencer thread — and surfaces gaps the flat search hides.
Ready to build this?
Get started with Lusha and set up this play in minutes.
