Prompt

Find the decision-maker, validate them, and draft the outreach email

Time to build: 1 min
Difficulty: Easy
Tools: ClaudeGmailLusha

The short version: name a company and the function you sell into, and Claude finds the senior decision-maker in Lusha, surfaces a live signal worth leading with, and drafts the email. Costs 3 credits: 1 to find the contact, 1 to reveal their email, 1 to pull the signal. Skip the phone reveal unless someone is going to dial — that adds 5.

This Claude prompt closes the loop on the question every rep starts with: you know the company, you don’t know who to contact or what to say. Lusha finds the right person in your target function, validates their details, and pulls a signal worth leading with. Claude drafts the email. One prompt, ready to send via Gmail.

First, connect Lusha to Claude.

Example outputs on this page are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own data and connectors to see live results.

The prompt

<context>
I want to reach out to a specific company. I know who they are but I don't
know exactly who to contact or what to say. I want to find the right
decision-maker, validate their details, and have a first email ready to
send — all in one pass.

My outreach:
- Company I want to reach: [COMPANY NAME OR DOMAIN]
- What I sell: [PRODUCT / SOLUTION]
- Why I'm reaching out: [SIGNAL / REASON / OR "FIND ONE FROM LUSHA"]
- Function I sell into: [SALES / REVOPS / FINANCE / IT / MARKETING / OTHER]
- Tone: [COLD / WARM — e.g. referral, event met, inbound signal]
</context>

<task>
1. Use Lusha to find the right first contact at this company:
   - Search for current employees in [TARGET FUNCTION]
   - Return the senior verified decision-maker in that function
   - Reveal their verified work email
   - Note their tenure in the current role

2. Use Lusha's signals to find the best reason to reach out now:
   - Recent funding event
   - New exec hire in the relevant function
   - Headcount growth in the team I sell into
   - M&A activity
   - If no signal: flag as "no live signal — reaching out on ICP fit"

3. Draft a first outreach email:
   - Subject line: under 8 words, specific to the signal or their role
   - Body: under 80 words
   - First line names the signal or the reason
   - One specific question or ask at the end
   - No "just checking in", "I wanted to introduce myself", "circling back"

4. Return:
   - Verified contact: name, title, email, tenure
   - Signal used (or "ICP fit only")
   - Draft email, ready to send

5. Flag if a more senior contact exists above the one returned.
</task>

<constraints>
- Reveal email only. Ask before revealing a phone number.
- Only return contacts Lusha verifies. Don't guess titles or emails.
- Confirm the company domain matches before trusting the match.
- If a C-level revenue leader doesn't appear in the target function,
  search without the department filter before concluding there isn't one.
- If no verified contact is found in the function, return the closest
  available and flag the gap.
- Under 80 words. Count them.
</constraints>

What you'll get back

The situation: an SDR wants to reach out to a 190-person SaaS company she’s identified as a good fit. She knows the company but not who to contact. She sells sales intelligence software into the Sales leadership function.

Output: verified contact found, live signal surfaced, email drafted and ready.

Verified contact

  • VP of Sales
  • Verified work email ✓
  • Tenure: 22 days in role — the first VP Sales hire at a previously founder-led sales org
  • Direct mobile: available, not revealed on this run

Signal
New VP of Sales hired 22 days ago, the first at a company where the founder previously ran sales. That’s a high-intent moment for a sales tooling conversation: the new VP is building the stack with no existing vendor loyalty.

Draft email

Subject: Building the sales stack

Hi [First name],

Saw you recently joined as their first VP Sales. When sales goes from founder-led to function-led, the data and tooling layer is usually the first thing that breaks.

Worth 15 minutes to see what the team is currently working with?

[Your name]

52 words. Signal in the first line. One specific ask at the end.

Senior contact flag: Lusha also returns a Head of Revenue Operations at the same company, 14 months in role. If the VP Sales doesn’t respond within the sequence, that’s a strong second contact who may have more day-to-day influence over tooling decisions.

What it cost: 3 credits. One for the contact search, one to reveal the email, one to view the signal. The direct mobile was available but not revealed, which would have added 5 — phone reveal costs 5 credits per contact against 1 for email.

If no contact comes back in your target function: search again without the department filter and read the titles. Senior commercial roles are frequently tagged General Management rather than Sales, so a department-filtered search for sales leadership can miss the person at the top of that function.

Why use Lusha in Claude

“I know the company, who do I call?” is the question every rep starts with. The answer used to be ten minutes on LinkedIn, a guess at the email format, and a generic opening line. Lusha in Claude finds the verified contact in the right function, checks what’s happening at the account right now, and drafts an email referencing the specific signal — in about 90 seconds and 3 credits.

The senior contact flag at the end is the part that changes follow-up strategy. Knowing there’s a RevOps contact who’s been in seat 14 months gives the rep a second path before the sequence runs out, rather than discovering it after four unanswered emails.

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 the decision-maker at a company I’ve never contacted?

Name the company and the function you sell into, and let the search return the senior verified contact in that function rather than guessing from a job-title list. The step people skip is validating tenure — someone 22 days into a role is a different conversation from someone four years in, and it changes both who you write to and what you open with.

How many credits does finding and validating a decision-maker cost?

3 credits: 1 for the contact search, 1 to reveal the email, 1 to view the signal. Adding a direct dial makes it 8, since phone reveal is 5 credits per contact against 1 for email. For a first email you want the address, so the prompt asks for email only.

What if there’s no signal at the company?

The prompt returns “ICP fit only” rather than inventing a reason, and drafts an email that leads with the role instead of a trigger event. That’s a weaker opening but an honest one. If several target accounts return no signal, the more useful move is checking whether they were selected on fit alone.

What if no one comes back in my target function?

Usually the department filter rather than the coverage. Senior commercial roles are frequently tagged General Management rather than Sales, so a department-filtered search for a Chief Revenue Officer can return nothing while the record exists. Search without the filter and read the titles.

Can I run this for multiple companies at once?

Yes, though the economics change. Contact search bills at 1 credit per batch of up to 25, so identifying contacts across 25 companies costs 1. The reveals are what add up: 25 emails is 25 credits. Preview the list first, pick the accounts worth writing to, and reveal only those.

What if I want to target a specific person rather than a function?

Replace the function line with the person’s name and company. The prompt then validates them rather than searching, and confirms whether the title you have on file is still current — which is worth doing before writing, since a stale title in the opening line is more damaging than a generic one.

Ready to run this?

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