EvoLusha 2026 | Driving Growth with Data in the Agentic Age

Watch now »

Find new VP of Sales hires at your ICP accounts

Example outputs in this play 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 ICP and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

A VP of Sales who just joined a new company is one of the highest-converting signals in outbound. They’re in their first 30 days, evaluating their inherited tool stack, and making vendor decisions before their first QBR. This Claude prompt uses Lusha in Claude to find VP of Sales, Head of Sales, and CRO contacts who changed companies in the last 30 days and match your ICP — verifies each one live, checks for stacked signals at the account, and drafts a first-touch email that uses the hire as the reason to reach out now.

The prompt

Open in Claude Open in ChatGPT 
Find VP of Sales contacts who joined a new company in the last
30 days and match my ICP.

ICP: [describe your ideal customer — industry, company size,
geography, funding stage]
Target titles: VP of Sales, Head of Sales, Chief Revenue
Officer, or equivalent
Signal: company change in the last 30 days

For each contact found:
1. Verify their current title, company, and start date via Lusha
2. Confirm the company matches my ICP criteria
3. Check for additional signals at the account — hiring surges,
   funding, intent
4. Draft a first-touch email that opens with their new role and
   connects it to a specific reason to reach out now

Return a ranked list with verified contact details and a
ready-to-send email for each.

What you'll get back

What you’ll get back

You give it your ICP. It gives you a ranked list of VP of Sales, Head of Sales, and CRO contacts who just joined a new company — each one verified live via Lusha, each one with a ready-to-send first email.

For each contact:

R.M. — VP of Sales, [Company] Contact confirmed live via Lusha connector, [date]

FieldValue
Current titleVP of Sales
Previous company[Previous company]
Tenure in seat3 weeks
Verified emailr.m@[company].com
Direct dial+1 512 555 ••••
Company — employees280–320
Company — fundingSeries B, $24M raised
ICP match✓ Confirmed

Stacked signals at this account:

  • Hiring surge: 8 SDR roles posted in the last 14 days
  • Intent signal: “sales prospecting tools” — score 74
  • News: new EMEA office announced 3 weeks ago

First-touch email — ready to send:

Subject: Scaling the SDR team at [Company]

R.M. — congrats on the new role. Saw you’re already building out the SDR team — 8 open roles in the last two weeks.

We work with a lot of sales leaders in your position who are standing up a new stack from scratch. One of the first things they fix is making sure every new SDR has verified contact data from day one, not a list that was last touched six months ago.

Worth a 20-minute call this week?

[Your name]

Example outputs in this play 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 ICP and connectors to see live results.

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude, Lusha
Type: Prompt

Why use Lusha in Claude

A new VP of Sales is one of the few moments in B2B where timing and relevance are both guaranteed. They have a mandate to improve results, they’re evaluating everything their predecessor left behind, and they’re making vendor decisions before their first QBR — usually within 60 to 90 days of joining. After that window, the stack is set and the conversation becomes a displacement play.

What makes this play work is the quality of the signal underneath it. Lusha tracks executive hire events as named, verified, time-stamped data points — confirmed across multiple independent sources, not inferred from a LinkedIn profile update or a news mention. The signal is specific: this person, at this company, started this week. That’s what separates a reason to reach out from a guess. Anonymous intent data tells you a company is researching a category. This tells you a specific person just walked into a new role with an open vendor evaluation on their desk.

The stacked signal check adds another layer. A new VP of Sales at a company that just raised a Series B and posted 8 SDR roles in the last two weeks isn’t just changing jobs. They’re building something, and they’re doing it fast. Lusha’s buying signals — 1.2B+ data points processed daily, 7M new signals every week — surface that pattern in one pass so your outreach arrives with context, not just a congratulations line.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use.

FAQ

  • How recent is "last 30 days" — how does Lusha know when someone joined?

    Lusha tracks executive hire signals as named, time-stamped events — when a contact’s company changes in Lusha’s database, the signal is logged with a date. This isn’t inferred from a LinkedIn scrape. It’s a verified data point confirmed across multiple independent sources. The 30-day window is a starting point — you can adjust it in the prompt to 7, 14, or 60 days depending on how fresh you want the signal.

  • Can I target a different function, not just VP of Sales?

    Yes. Replace “VP of Sales, Head of Sales, Chief Revenue Officer” in the prompt with any target function — VP of Marketing, Head of RevOps, CFO, CTO, or any seniority and department combination. The signal is the same: someone new in seat, evaluating their inherited stack, making decisions. The outreach angle changes based on the function.

  • How is this different from the Find People Who Just Changed Jobs play?

    The Find people who just changed roles play is a broad signal sweep — it finds any contacts in your target persona who changed roles recently. This play is narrower and more actionable: it targets a specific high-value signal (new VP of Sales), filters against your ICP, checks for stacked signals at the account, and writes the outreach in one pass. It’s built for the moment you want to move fast on a specific trigger, not build a general list.

  • What if the contact joined more than 30 days ago but I'm just finding them now?

    Widen the window in the prompt — change “last 30 days” to “last 60 days” or “last 90 days.” The email angle shifts slightly: instead of “congrats on the new role,” you open with a reference to something that’s happened since they joined — a hiring surge, a funding announcement, a product launch. The timing window gets narrower as tenure increases but it doesn’t close entirely until they’ve been in seat long enough to have locked in their vendor decisions, usually 6 months or more.

  • Can I run this weekly as an automated signal trigger?

    Yes. Save the prompt in a Claude Project with your ICP criteria as a custom instruction and run it every Monday morning. It will surface any new VP of Sales hires that appeared in Lusha’s database since your last run. For a fully automated version that fires a notification without manual prompting, connect Lusha’s API to n8n or Make and trigger the workflow on the executive hire signal directly. The Lusha Campus plays library has workflow plays for both approaches.

Related Prompts

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs