Find more contacts like your best buyer
A Claude prompt that takes one known buyer — a champion, a closed-won contact, an active responder — and returns a verified list of more contacts at other companies with the same role, seniority, and company profile.
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 find more contacts who match the profile of a known buyer or champion.
</context>
<task>
1. Take this seed contact:
Name: [BUYER NAME]
Title: [TITLE]
Company: [COMPANY]
Industry: [INDUSTRY]
Company headcount: [RANGE]
Geography: [REGION]
2. Use Lusha's contact search to find more contacts matching the seed's profile:
- Same or adjacent job title
- Same seniority level
- Same industry
- Similar company headcount range
- Same geography
3. For each match, return:
- Full name
- Title
- Company
- Validated email
- Direct dial / mobile
4. Limit to 25 contacts. Exclude contacts at companies already in my customer list.
</task>
<constraints>
- Only include contacts with a validated email.
- Skip the seed contact themselves from the result set.
- If results return fewer than 10 contacts, suggest one filter to relax.
</constraints>What you'll get back
Input: Seed buyer — Global Head of Revenue Operations at Notion. Profile — RevOps leadership, VP/Director level, Software Development, 501–5,000 headcount, US.
Output: 519 contacts matching the seed profile. Below is a real slice of the live result — eight verified RevOps leaders at named US B2B SaaS companies, all with validated work emails and phones.
| Contact | Title | Company | Validated email | Phone |
|---|---|---|---|---|
| Tyler W. | VP of Revenue Operations | Intercom | ✓ | ✓ |
| Saad S. | VP of Revenue Operations | Sigma Computing | ✓ | ✓ |
| Tori M. | Global Head of Revenue Operations | Pigment | ✓ | ✓ |
| Sungwoo C. | VP of Revenue Operations | Airtable | ✓ | ✓ |
| Andrew R. | VP of Revenue Operations | Tealium | ✓ | ✓ |
| Niall M. | Head of Strategy and Revenue Operations | Lambda | ✓ | ✓ |
| Rajesh M. | Head of GTM Strategy and Revenue Operations | Postman | ✓ | ✓ |
| Laura F. | Head of Revenue Operations and Strategy | DevRev | ✓ | ✓ |
Names abbreviated for privacy. Full records — including emails and direct dials — are returned inside your Claude session.
Why it works
Persona prospecting at scale usually means filtering by title and hoping. Pairing the seed buyer’s full profile — role, seniority, industry, company size, geography — with Claude’s reasoning step produces a list calibrated to who actually closed, not who matched a keyword.
The prompt pulls candidates from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe — verified email plus validated phone on every row that passes the filter.
The result reads like a list of named buyers at named companies, not a guess at who might fit.
FAQ
How is this different from a regular contact search?
A title-only search returns everyone who carries the title. This prompt uses the seed buyer’s full profile — title, seniority level, industry, headcount band, geography — so the match is to the person’s full work context, not just the words on their LinkedIn header.
Can I seed with more than one buyer?
The prompt is built around one seed for sharpness. If you want to expand from multiple seeds, run the prompt once per seed and combine. Claude can deduplicate the combined list in one follow-up step.
Why not seed with a LinkedIn URL or contact ID?
Profile attributes — title, seniority, industry, size, geography — produce sharper matches than seed-only modeling for contacts. The seed buyer’s profile is what defines the target persona. LinkedIn URLs and contact IDs are useful for direct enrichment, not for finding more contacts like a person.
What if the seed is in a niche industry or rare role?
Lusha returns only verified matches. If the persona pool is thin, the result will come back with fewer rows rather than padding with low-confidence matches. Use the filter-relax suggestion built into the prompt — usually widening headcount or geography brings the count back up without losing fit.
Can I exclude existing customers?
Yes. Add the customer domains in the constraint block and Claude will route them to the exclude logic.
Ready to build this?
Get started with Lusha and set up this play in minutes.
