A departure from a competitor is two signals in one: a candidate who needs no market education, and a team that may be about to lose more people.
Connect Lusha to Claude and this prompt checks your competitor set for recent job changes, maps where the leavers went, and flags the clusters that suggest a team is coming apart.
The prompt
Here are our competitor companies: [paste company names or domains].
Using the Lusha connector, find people in [target function, e.g. sales or
engineering] who left these companies in the last 90 days, and where they went.
Return a table with name, previous role, new company, new role, and when they moved.
Then flag three groups:
(1) anyone whose new role looks like a lateral move or a step down
- possibly still open to the right offer
(2) three or more departures from the same team - a cluster, more may follow
(3) anyone who moved into a role close to [target role]
Finish with the top five to contact this week and a one-line reason for each.
What you’ll get back
The situation: a recruiter hiring account executives pastes six competitor domains and asks for sales departures in the last 90 days.
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
Lusha’s contact records carry employment history and dated job-change signals, so a departure isn’t something you notice — it’s something you query. Claude runs the sweep across the whole competitor set in one pass, compares previous role to new role, and applies the judgment layer: which moves look final, which look like soft landings, and which teams are shedding people fast enough to signal more departures coming. 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 do competitor leavers ramp faster?
They already carry the market knowledge a new hire spends months building — the buyer personas, the objections, the competitive landscape. In sales roles especially, a competitor hire often arrives with a working mental map of your exact territory.
What does a departure cluster actually tell me?
Three or more exits from one team in a quarter usually means a shared cause — a manager change, a comp restructure, a missed target. The people still on that team are the warmest possible outreach: they’ve watched colleagues leave and are often already deciding.
What if someone shows as still at the competitor?
Company-side records can lag individual moves — someone may appear on the old team roster while their personal record already shows the new employer. When results conflict, the individual contact record is the fresher source. Claude can cross-check both in the same run.
How far back should the window go?
90 days is the sweet spot. Recent enough that lateral movers may still be open, long enough to catch clusters forming. Past six months, treat a move as settled and check again next cycle.
Is tracking competitor employees like this compliant?
The prompt reads business-profile changes — employer, title, and role history — the same data a recruiter checks profile by profile today. 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.
