Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
This Claude prompt closes the loop on the most basic Lusha workflow: 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.
Tools: Claude, Lusha, Gmail
<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 to this company: [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 most senior verified decision-maker in that function
- Pull their verified work email and direct phone
- Note their tenure in the current role
2. Use Lusha's signals layer 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 — not "I hope this finds you well"
- One specific question or ask at the end
- No "just checking in", no "I wanted to introduce myself", no "circling back"
4. Return:
- Verified contact: name, title, email, phone, 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>
- Only return contacts Lusha verifies. Don't guess titles or emails.
- The email must reference the signal or a specific reason tied to this company.
- If no verified contact is found in the target function, return the closest available and flag the gap.
- Under 80 words. Count them.
</constraints>The situation: An SDR wants to reach out to Waverly Digital — 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 and wants to sell into the Sales leadership function.
Output: Verified contact found, live signal surfaced, email drafted and ready.
New VP of Sales hired 22 days ago — first VP Sales at a company that previously had the founder running sales. This is the highest-intent moment for a sales tooling conversation: the new VP is building the stack from scratch with no existing vendor loyalty.
To: s.r@[waverly].com Subject: Building the sales stack at Waverly
Hi Sofia,
Saw you recently joined Waverly 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?
[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 Waverly — D.K., 14 months in role. If the VP Sales doesn’t respond within the sequence, D.K. is a strong second contact who may have more influence over tooling decisions day-to-day.
Contact and signal validated via Lusha connector, May 21. Details masked for privacy.
“I know the company, who do I call?” is the question every rep starts with. The answer used to be 10 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 that references the specific signal — in 90 seconds. The senior contact flag at the end is the part that changes the follow-up strategy: knowing there’s a RevOps contact who’s been there 14 months gives the rep a second path before the sequence runs out.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
The prompt flags it as “ICP fit only” and the email shifts to lead with the company’s context — their size, what they do, and why that makes the conversation relevant — rather than a specific trigger event. Still specific, just differently framed.
If you already know the person, use the prospect research before outbound prompt instead — it’s built for when you have a name and want a brief and an email for that specific person. This prompt is for when you have a company but no contact yet.
Run it per company — the signal check and email draft are specific to one account at a time. For building a prioritized list of companies to target first, use the prospect list from signal prompt to build the list, then run this prompt for each one you decide to work.
Lusha returns a verified work email — not a guessed format. Verified emails have significantly lower bounce and spam rates than pattern-guessed ones. The email itself is under 80 words with no attachments and no trigger phrases — that also helps deliverability.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
