Find people who just changed roles in your target persona
A Claude prompt that returns verified contacts in your target persona who recently changed roles — promotions inside their company or moves to a new one — with the new title, the move date, and a validated email plus direct dial. Built for outreach timed to the first 90 days of a new mandate.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the prompt and run.
Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.
The prompt
<context>
I sell [PRODUCT] to [PERSONA].
I want to find verified contacts in my target persona who recently changed roles — promotions or new companies — in the last [WINDOW, e.g. 6 months].
</context>
<task>
1. Use Lusha's contact search with the signal premium filter:
- Signal: promotion OR companyChange
- Title family: [TITLE FAMILY, e.g. VP Sales, CRO]
- Seniority: [LEVELS, e.g. VP and C-suite]
- Industry: [INDUSTRY]
- Headcount: [RANGE]
- Geography: [REGION]
- Window: last [WINDOW]
2. For each contact, return:
- Full name
- New title and company
- Signal type (promotion / new company / both)
- Validated email
- Direct dial / mobile
3. For the top 10 by recency, draft a one-line outreach hook tied to the change. The hook references first-90-days scope, not "congrats."
4. Order contacts by signal type (promotion + companyChange combined first), then by recency.
</task>
<constraints>
- Only include contacts where Lusha has verified the role change.
- Skip lateral moves under 30 days unless ICP-perfect.
- No "congrats on the new role" as the hook — reference the mandate, not the move itself.
</constraints>What you'll get back
Input: Title family — VP Sales / CRO / Head of Sales · Seniority — VP and C-suite · Industry — B2B SaaS (Software Development) · Geography — United States · Headcount — 201–5,000 · Window — last 6 months.
Output: 143 verified Sales leaders who recently changed roles. Below is a real slice of the live result — eight named contacts with verified promotion or company-change signals, all with validated work emails and phones.
| Contact | New title | Company | Signal type | Phone |
|---|---|---|---|---|
| Ariel Z. | Assistant VP of Commercial Sales | ClickHouse | Promotion + Company change | ✓ |
| Christopher I. | VP of Sales Enablement | Smart Communications | Promotion + Company change | ✓ |
| Maria S. | VP of Global Sales | Vasion | Promotion + Company change | ✓ |
| Ankit S. | VP of Sales Strategy and Operations | Scale AI | Promotion + Company change | ✓ |
| Jared F. | Regional VP of Enterprise Sales | Harness | Promotion | ✓ |
| Danielle S. | SVP of Sales Enablement and Chief of Staff | AlphaSense | Promotion | ✓ |
| Jim C. | Global VP of Strategic Sales | SailPoint | Company change | ✓ |
| Mike M. | VP of Sales | Showpad | Company change | ✓ |
Names abbreviated for privacy. Full records — including emails and direct dials — are returned inside your Claude session.
Why Lusha
Job-change outreach converts at multiples of generic outbound because the buyer is actively rebuilding. The first 90 days of a new mandate is when the budget gets scoped, the vendor stack gets reviewed, and the playbook gets rewritten. Three things change when the signal is paired with verified contact data.
The signal is segmented by type. Promotions and company changes look the same on LinkedIn but they’re different buying contexts. A promoted VP knows the existing stack and the existing politics — outreach lands as “what would you fix if you had a clean slate?” A new-company VP is rebuilding from scratch — outreach lands as “what’s the first lever you’re testing?” The prompt surfaces the signal type so the rep picks the right opening.
The contact is verified at the moment of the signal. Lusha returns the new title, the new company, validated email, and direct dial — drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe. The contact who got promoted last week is in the result with a callable phone, not a stale row from a CRM import.
The hook references mandate, not movement. Most job-change outreach opens with “congrats.” That phrase is signal to every buyer that the message is templated. The prompt is built to skip the congrats and reference the actual first-90-days scope — what gets reviewed, what gets cut, what gets bought.
FAQ
What's the difference between a promotion and a company change?
A promotion means the contact moved up at the same company — title expanded, scope grew, team got bigger. A company change means the contact moved to a new employer. Both unlock buying windows, but the buying psychology differs. The prompt surfaces both, separated by signal type.
How recent is a "recent" role change?
Default is 6 months. Tighten to 60 or 90 days for hot signals, widen to 12 months for thinner persona pools. The signal date is returned with each row so the rep can read recency in context.
Does the prompt cover lateral moves and internal transfers?
Lateral moves are captured under the
companyChangesignal when the contact moved between divisions or subsidiaries. The constraint block defaults to skipping laterals under 30 days unless they’re ICP-perfect — easy to relax in your version.Can I combine job-change with company-level signals?
Yes. The strongest signal stack is “company surging hiring in this function PLUS a new leader in the function in the last 60 days” — the company is scaling, the new leader is rebuilding, and the budget is unlocking simultaneously. Run this prompt first, then cross-reference with the hiring-surge prompt.
How is this different from finding contacts in my target persona?
A regular contact search returns the full persona pool — everyone in role today. Adding the job-change signal narrows to people who are actively in a rebuilding moment. The conversion delta between those two pools is significant in real-world outbound data.
Ready to build this?
Get started with Lusha and set up this play in minutes.
