A title-and-size filter gives you a list of people who might need your product someday. A trigger signal gives you a list of people who likely need it right now — a new CRO in their first 60 days, a Series B that just closed, a sales team that grew 40% in a quarter. The window is real and it closes.
These four Claude prompts are built for outbound from first principles: find the right accounts from a signal, write the sequence from the trigger, prep the cold call brief before you dial, and know when a dead thread is worth one more try versus when to archive it and move on.
All four run on Lusha’s verified contact and company data. Connect the Lusha connector once and it runs in the background. The sequence and re-engagement prompts also use Gmail to check for prior threads before writing anything.
PROMPT 1 — Build a prospect list from a signal, not a job title
Instead of filtering by “VP of Sales at a 200-person SaaS company,” this prompt starts from a trigger — a funding round, a new exec hire, a headcount spike — and finds accounts where that signal is confirmed active right now. Lusha returns the accounts, the right first contact at each one, and a tiered list ranked by how fresh the signal is. Tier 1 accounts have a signal from the last 30 days and a verified contact with direct details. Those are the calls worth making today.
Tools: Lusha
→ Full play page and example output
<context>
I want to build a prospect list based on a specific trigger signal — not just a job title or company size filter. I'm looking for accounts where something is happening right now that makes them more likely to need what we sell.
My outbound:
- What I sell: [PRODUCT / SOLUTION]
- My ICP (ideal customer profile): [COMPANY SIZE / INDUSTRY / REGION]
- The signal I'm targeting: [FUNDING ROUND / EXEC HIRE / HEADCOUNT GROWTH / M&A / OTHER]
- Why this signal matters for us: [ONE SENTENCE]
- How many accounts I want: [NUMBER]
</context>
<task>
1. Use Lusha to find accounts matching both the ICP criteria and the signal — confirmed active in the last 90 days.
2. For each account, identify the right first contact: the person most likely to own the problem we solve, given the signal. Validate their title, email, and direct phone.
3. Rank by signal recency:
- Tier 1: signal in last 30 days, contact validated, details available
- Tier 2: signal in last 31–90 days, contact validated
- Tier 3: signal detected but incomplete or older than 90 days
4. For each Tier 1 and Tier 2 account: company, signal, contact, one-line outreach angle tied to the signal.
5. Flag accounts where the signal is strong but the right contact is unclear.
</task>
<constraints>
- Only include accounts where Lusha confirms the signal. Don't infer from size or industry alone.
- The outreach angle must be specific to the signal — not a generic pitch.
- If fewer accounts qualify than requested, return what's there. Don't pad the list.
- Tier the output clearly.
</constraints>PROMPT 2 — Write a cold sequence from a trigger event
A generic cold sequence gets ignored because it could have been sent to anyone. This prompt writes a 4-touch sequence — 3 emails and a LinkedIn message — built from the specific trigger at this prospect’s company. Lusha validates the contact before anything gets written. Gmail checks for prior threads so the sequence doesn’t land on top of an existing conversation. Word limits are enforced in the prompt: Touch 1 under 80 words, Touch 4 under 40. Every touch references the trigger from a different angle.
Tools: Lusha + Gmail
→ Full play page and example output
<context>
I have a prospect I want to reach out to cold. A specific trigger event happened at their company that makes this the right moment. I want a multi-touch sequence — email and LinkedIn — written from the trigger, not from a generic template.
My prospect:
- Company: [COMPANY NAME]
- Contact name and title: [NAME, TITLE]
- Trigger event: [WHAT HAPPENED — e.g. "new CRO hired 3 weeks ago", "Series B closed last month"]
- What I sell: [PRODUCT / SOLUTION]
- Why this trigger matters for us: [ONE SENTENCE]
- Any prior contact or context: [YES / NO]
</context>
<task>
1. Use Lusha to validate the contact — title, tenure, verified email and phone.
2. Check Gmail for any prior thread with this contact or company. If found, flag and adjust.
3. Write a 4-touch sequence:
Touch 1 — Email (Day 1): under 80 words. Name the trigger in the first line. One question at the end.
Touch 2 — LinkedIn (Day 4): under 50 words. Different angle from Touch 1.
Touch 3 — Email (Day 8): under 60 words. Add one new angle or data point. Don't repeat Touch 1.
Touch 4 — Email (Day 14): under 40 words. The break-up email. One final question.
4. For each touch: channel, day, primary angle.
5. Flag if the trigger is older than 60 days — the sequence tone shifts.
</task>
<constraints>
- Every touch must reference the trigger. A sequence that could go to any prospect is not acceptable output.
- Word limits are hard: Touch 1 under 80, Touch 2 under 50, Touch 3 under 60, Touch 4 under 40.
- No "just checking in", no "hope you've been well", no "circling back."
- Stop and flag if Gmail shows a prior thread.
</constraints>PROMPT 3 — Prep a cold call from a LinkedIn profile and account signals
Cold call prep usually means 10 minutes on LinkedIn hoping to find something to mention. This prompt does the same job in 90 seconds and adds what LinkedIn can’t give you: a verified direct mobile, a signal from the account worth leading with, and an opening line under 20 words built from both. The objection handling is written for this specific role at this specific company — a new VP of Sales three weeks into the job gets a different brief than a CFO who’s been there four years.
Tools: Lusha
→ Full play page and example output
<context>
I'm about to make a cold call. I have a name, a company, and a LinkedIn profile. I want to validate the contact, get their direct number, and build a one-screen call brief.
My prospect:
- Name and title: [NAME, TITLE]
- Company: [COMPANY NAME]
- LinkedIn URL (optional): [URL OR "SEARCH BY NAME AND COMPANY"]
- What I sell: [PRODUCT / SOLUTION]
- Why I'm calling today specifically: [SIGNAL OR "FIND ONE FROM LUSHA"]
</context>
<task>
1. Validate the contact via Lusha: title, direct mobile (preferred), email fallback, tenure in role.
2. Use Lusha's signals layer to find the strongest reason to call this company today. If no signals found, flag it.
3. Build a one-screen call brief:
CONTACT: verified name, title, direct number, email fallback, tenure note
SIGNAL: the one thing happening at this company that makes this call timely
OPENING LINE: under 20 words, specific to this person or signal — not "How are you?"
EXPECTED FIRST OBJECTION: most likely pushback and one sentence on how to handle it
GOAL FOR THIS CALL: one specific thing to walk away with
4. If direct number isn't available, flag it and suggest next best action.
</task>
<constraints>
- Opening line must be under 20 words and specific to this person or signal. A line that could be used on any call is not acceptable output.
- Don't invent signals. If Lusha returns nothing, say so.
- One screen only.
- If direct number isn't available, say so clearly — don't return a switchboard number without flagging it.
</constraints>PROMPT 4 — Re-engage a dead outbound thread that went cold
Before archiving a dead thread, this prompt checks whether anything changed at the account since you last reached out. If a new signal exists — a funding round, a new exec, a headcount spike — that’s a legitimate reason to reach out again, and the re-entry message treats it as fresh outreach rather than a fifth follow-up. If there’s no new signal and the contact is still there, it returns HOLD with a suggested timing. If the contact has left, it finds the replacement. If it’s genuinely dead — 4+ touches, no reply, no signal — it returns ARCHIVE. That’s the correct output and it’s as useful as RE-ENGAGE.
Tools: Lusha + Gmail
→ Full play page and example output
<context>
I have a cold outbound thread that went silent. I want to check whether anything has changed at their company that makes it worth re-engaging — and if so, write one message that restarts the conversation without referencing the fact that I already emailed them multiple times.
My dead thread:
- Contact name and title: [NAME, TITLE]
- Company: [COMPANY NAME]
- When we last had contact: [DATE OR "CHECK GMAIL"]
- What I was selling: [PRODUCT / SOLUTION]
- How many touches I sent: [NUMBER]
- Why I originally reached out: [ORIGINAL SIGNAL OR REASON]
</context>
<task>
1. Use Lusha to check what's changed at this account since the last touch:
- Is the contact still at the company in the same role?
- Any new signal — exec hire, funding, headcount change, M&A?
- If the contact has left: find their replacement and return verified details.
2. Check Gmail for the original thread:
- How many times did I reach out?
- Did they ever reply?
- What was my original angle?
- Any signal of interest or soft objection in any reply?
3. Make a re-engagement decision:
- RE-ENGAGE: a new signal exists that's different from the original outreach reason
- HOLD: no new signal, contact still there — flag when to try again
- NEW CONTACT: original contact has left — map replacement, treat as new cold outreach
- ARCHIVE: no signal, contact gone with no successor, or 4+ touches with no reply ever
4. If RE-ENGAGE: write one email under 60 words. Open with the new signal. No reference to prior outreach. One question at the end.
5. If NEW CONTACT: return verified replacement details and a one-line angle.
</task>
<constraints>
- Re-engagement is only justified if there's a new signal. Same angle again is spam.
- The re-entry message must not reference prior outreach.
- ARCHIVE is a valid and useful output.
- Don't manufacture a reason to reach out.
</constraints>Where these prompts live
Each prompt above has a full play page with a detailed example output — worth reading before you run one for the first time.
- Build a prospect list from a signal, not a job title →
- Write a cold sequence from a trigger event →
- Prep a cold call from a LinkedIn profile and account signals →
- Re-engage a dead outbound thread that went cold →
All four are part of the Lusha Pipeline Acceleration Gallery — a library of Claude prompts built for every role in a revenue team.
