Money in the bank means headcount plans get approved, and the first hires often come from people already inside the company pulling in their own network — which makes the existing team worth mapping before a single role is posted. Connect Lusha to Claude and this prompt checks your target space for recent funding events, then finds the people at those companies in your target function who are worth reaching first.
The prompt
I am sourcing for [target role, e.g. senior product managers] in
[target industry]. Using the Lusha connector, find companies in this
space that raised a funding round in the last 60 days. For each one,
find people currently in a [target function] role there. Return a
table with company, round size, round date, contact name, their title,
and their tenure at the company.
Then flag two groups:
(1) tenure under a year - recent hire, likely not moving, but a useful
source of referrals into the team
(2) tenure over two years - may be due for a change, or positioned to
refer people they managed elsewhere
Finish with the five strongest contacts to reach out to this week and
a one-line reason for each.
What you’ll get back
The situation: a recruiter placing senior product managers pastes a target industry and asks for recently funded companies with existing PM contacts.
The output:
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 data and connectors to see live results.
Why it works
A funding event is a company-level signal Lusha can confirm directly, and it predicts hiring before any role is posted — the budget exists before the req does. Claude cross-references the funding data with the people already at the company in the target function, then applies the tenure judgment call: a brand-new hire is a referral source into the team being built, a long-tenured person is either due for a change themselves or a source of names from roles they held before this one. Contact data is verified across multiple sources and handled under GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance, with opt-outs honored automatically.
FAQ
Why contact people who probably aren’t looking to leave?
This play isn’t primarily about poaching the people you find — it’s about using them as a way in. A recent hire at a newly funded company usually knows exactly who else is being considered for the team, and a referral conversation with someone happy in their role often opens doors a cold approach never would.
Why does tenure matter here?
It changes what the conversation is for. Under a year, ask about the team they’re building and who they’re bringing in. Over two years, the conversation can go either way — genuine interest in a change, or a long professional network worth tapping regardless.
How recent does the funding round need to be?
60 days is a reasonable window — recent enough that headcount plans are still forming, not so recent that hiring hasn’t started. For very early-stage rounds, extend the window; hiring plans at a small team can take longer to firm up.
Is this different from the layoff sourcing play?
Opposite signal, same mechanic. Layoffs release people who are actively looking right now. Funding rounds identify people who probably aren’t looking, but are positioned to open doors into a team that’s about to grow. Use layoffs for immediate candidates, funding rounds for warm introductions and future pipeline.
Is reaching out this way appropriate?
The prompt reads business and funding data that’s already public — round size, round date, and current role are the kind of information covered in funding announcements and public profiles. Lusha’s data is professionally sourced and opt-outs are honored automatically; no personal contact details are revealed until you choose to enrich a specific person.
