Prompt

Find a warm path into a target account

Tools: ClaudeLusha

The short version: before you go cold on an account, check whether anyone there came from a company you already have relationships with — your own alumni, a customer, a partner. Claude searches by shared employment history and returns the people who bridge the two. Costs 1 credit per batch of 25, before any contact details are revealed.

Target account research usually starts with the org chart and ends with a cold email. This starts one step earlier: who inside that account already has a connection to your world, and can either introduce you or tell you how the place actually works.

Runs in Claude with the Lusha connector.

The example output below was pulled live via the Lusha connector on August 15, 2026. Contacts are real, masked to initials, with companies replaced by category descriptors. No emails or phone numbers are published.

The prompt

 

<context>
I'm working a set of target accounts. Before I go cold, I want to know
who inside them has a connection to my world already — someone who can
introduce me, or at minimum tell me how the place actually buys.

My inputs:
- Target account domains: [PASTE, one per line]
- Companies where I have relationships: [PASTE]
  Include: my own company, current customers, partners, and former
  employers of people on my team.
- Function I sell into: [SALES / REVOPS / IT / FINANCE / OTHER]
</context>

<task>
1. Use Lusha to find people currently employed at my target accounts
   whose previous employer appears on my relationship list.

2. For each match, return a preview row:
   Name | Current title | Target account | Shared company | Seniority

3. Classify each person:
   - IN the buying centre — they sit in the function I sell into
   - NEAR it — adjacent function, could route me internally
   - ELSEWHERE — no functional overlap, but still a possible introduction

4. Group by target account. For each account, say whether a warm path
   exists at all, and how strong it is.

5. Flag any account where several people share history with my
   relationship list. That is a stronger entry than a single contact.

6. Wait for my shortlist, then reveal verified email for those only.
</task>

<constraints>
- Preview only until I confirm the shortlist. Reveal email only, not phone.
- Seniority is not the ranking criterion here. A mid-level person who
  can make an introduction beats a VP who has never heard of me.
- Do not assume a shared employer means a relationship. Flag these as
  paths to check, not contacts to name-drop.
- If an account returns nothing, say so plainly rather than returning
  loosely related people.
</constraints>

 

What you'll get back

The situation: five target accounts in a collaboration-software territory, all cold. The rep listed two large companies where the team has existing relationships and ran the check before building sequences.

Output: 54 people across the five accounts share employment history with the relationship list. A slice:

ContactCurrent titleTarget accountPath
M.K.Head of Global Channel Sales[Collaboration platform]IN buying centre
T.S.Strategic Account Director[Workflow SaaS]IN buying centre
C.M.Strategic Account Manager[Collaboration platform]IN buying centre
J.D.Renewal Manager[Workflow SaaS]NEAR — ops adjacent
D.H.Senior Performance Marketing Manager[Workflow SaaS]ELSEWHERE — possible intro

Five of 54 returned, individually masked. Live result via Lusha connector, August 15, 2026.

What it cost: 1 credit. Contact search bills at 1 credit per batch of up to 25 records. Revealing email costs 1 credit per contact and only for the shortlist. Phone reveals cost 5 each and are the wrong instrument for this play — you are asking for an introduction, not cold calling.

Seniority is the wrong sort order here

Notice what came back: account executives, a renewal manager, a marketing manager. Not a VP among the first five. That is the play working correctly rather than failing.

A warm path does not need to be the decision-maker. It needs to be someone who will reply, and who can point you at the right person internally with a sentence of context attached. A senior account executive two levels below your buyer is often a better first message than the buyer, because they have a reason to answer and nothing to lose by helping.

Sort by whether they will respond, not by title. The prompt classifies by proximity to your buying centre for exactly this reason.

If an account returns nothing

Widen the relationship list before assuming there is no path. Teams routinely list only current customers, when the useful set is broader: your own company’s alumni, partners, and the previous employers of people on your team. That last group is usually the largest and the least used.

Also confirm you have passed domains rather than company names — a misspelled or abbreviated name can match a different organisation entirely and return a confident-looking result for the wrong company.

Why use Lusha in Claude

Everyone accepts that a warm introduction outperforms a cold email. Almost nobody checks for one, because checking has meant asking around internally, scrolling connections one profile at a time, and giving up before the answer arrives. The cost of looking has been higher than the expected value of finding.

Searching by previous employer collapses that. One query against your target list and your relationship list returns every person who bridges the two, across every account at once, before you have written a single email.

The grouping step is where it earns its place in a territory plan. A few accounts will have several people who share history with your world, and some will have none. That is a real input to sequencing — work the accounts where a path exists first, and let the truly cold ones wait until you have a better reason to call.

Data drawn from 290M+ verified contacts, sourced and processed under GDPR, CCPA, SOC 2 Type II, ISO 27001, ISO 27701, and TRUSTe Responsible AI. Full detail in the Trust Center and privacy notice.

FAQ

How do I find a warm introduction to a company?

Search by shared employment history rather than by title. Give Lusha your target account domains plus a list of companies where you already have relationships — your own employer, current customers, partners, and the previous employers of your team — and it returns people at the target who came from one of them. The result is a list of possible introducers rather than a list of buyers.

How many credits does this cost?

1 credit per batch of up to 25 records. Checking five target accounts against two relationship companies returned 54 people for 1 credit at preview. Revealing email costs 1 credit per contact, and only for the people you decide to contact.

Does a shared former employer actually mean a warm path?

Not on its own, and the prompt is written not to overstate it. Two people can work at the same large company for years without meeting. What a shared employer gives you is a reason to write and something true to open with, which is more than a cold email has. Treat the output as paths to check rather than relationships to claim.

Should I contact the senior match first?

Usually not first. The person who will reply counts for more than the person who will sign, and a mid-level contact with a real connection is a better first touch than a VP receiving another cold email. Use the junior contact to understand the account and get pointed at the right person, then approach the buyer with context.

What should I put on the relationship list?

Broader than teams usually do. Current customers are the obvious entry, but the larger set is your own company’s alumni, your partners, and the former employers of everyone on your team. A team of ten people has typically worked at thirty companies between them, and every one of those is a potential bridge.

What if there is no path into an account?

That is useful information rather than a dead end. It tells you the account is properly cold, which is reason to sequence it behind the ones where a path exists rather than treating every target the same way. Re-run the check periodically, since people move constantly and a path can appear without you doing anything.

 

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.