Write the outreach when a contact changes jobs
Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
This Claude prompt validates where a contact landed after a job change, checks whether the new company fits your ICP, and writes the outreach message in one pass. Lusha confirms the new role, pulls verified contact details at the new company, and scans for signals. The message is written for the specific relationship — past customer, warm prospect, or cold — not a generic congratulations note.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
Someone I know from a past deal, customer relationship, or outbound sequence just changed jobs. I want to reach out while the move is fresh — but I need to check where they landed first, whether the new company is a fit, and write an outreach message that references the relationship without making it awkward.
The person:
- Name: [NAME]
- Old company and title: [OLD COMPANY, OLD TITLE]
- New company (if known): [NEW COMPANY — or "find it from Lusha"]
- My relationship with them: [PAST CUSTOMER / WARM PROSPECT / NEVER CLOSED / FORMER CHAMPION / MET AT EVENT]
- What I sell: [PRODUCT / SOLUTION]
- Last interaction (if any): [DATE AND CONTEXT — or "none"]
</context>
<task>
1. Use Lusha to find and validate where they landed:
- Confirm their new company and current title
- Pull verified work email and direct phone at the new company
- Note how long they've been in the new role
2. Use Lusha to check whether the new company is a fit:
- Company size, industry, geography
- Headcount in the function relevant to what I sell
- Any signals at the new company: funding, exec hiring, headcount growth
- Quick ICP read: is this worth pursuing, or is the new company outside our target?
3. Check whether the new company is already a customer or an active prospect:
- If joining an existing customer: relationship expansion, not new business
- If joining an active prospect: may accelerate or change the deal dynamic
- If neither: new outbound opportunity with a warm contact
4. Based on the situation, write one outreach message:
PAST CUSTOMER or FORMER CHAMPION joining a new company:
- Reference the past relationship directly — don't pretend it didn't happen
- One specific thing from the previous relationship relevant at the new company
- Under 80 words
- Ask if it makes sense to reconnect, not pitch immediately
WARM PROSPECT who never closed:
- Acknowledge the move
- One sentence on why the new company makes the conversation more relevant (or less)
- Under 80 words
- If the new company is outside ICP: say so and close the loop gracefully
COLD — met once or no meaningful relationship:
- Don't overclaim the relationship
- Lead with the new company signal, not the prior connection
- Under 60 words
5. Return:
- Validated new contact details
- ICP fit read on the new company
- Situation type (existing customer / active prospect / new opportunity)
- The outreach message, ready to send
- One flag: anything about the move worth knowing before you reach out
</task>
<constraints>
- Validate the new role via Lusha before writing anything. Don't assume the LinkedIn notification is current.
- The message must reference something real — the prior relationship, a specific signal, or the new company context. A generic "congrats on the new role" is not acceptable output.
- If the new company is outside ICP, say so — don't write outreach for a company that isn't a fit.
- Under 80 words for warm contacts, under 60 for cold. Count them.
</constraints>What you'll get back
Three examples — one per relationship type. The message changes completely depending on the situation.
Example A: Past customer joined a new company
The situation: M.T. was VP of RevOps at a logistics software company — a paying customer for 18 months. He just moved to a 300-person FinTech as Head of Revenue Operations. Last interaction was 3 months ago, a renewal call.
New contact details (Lusha)
- M.T., Head of Revenue Operations, [FinTech company]
- Verified work email: m.t@[fintech].com ✓
- Direct mobile: available (masked)
- Tenure: 19 days in role
ICP read: ✓ Strong fit — 300 employees, FinTech, North America, RevOps team of 6
Situation type: New outbound opportunity with a warm contact — new company is not a current customer
One flag: M.T. joined as the first standalone RevOps hire at this company — previously handled by the CFO. He’s likely building the function from scratch, which is the highest-intent moment for tooling decisions.
Outreach message
Subject: RevOps at [FinTech] — worth a catch-up?
Hi Marcus,
Congrats on the move. Looks like you’re building the RevOps function from scratch at [FinTech] — we went through that exact build together at [old company] and it went well.
Worth 20 minutes to see if the same setup makes sense here?
[Name]
72 words. References the specific prior experience. Asks for a call, doesn’t pitch.
Example B: Warm prospect who never closed
The situation: S.R. was VP of Sales at a 90-person startup — had two calls, never bought. She just joined a 380-person SaaS company as CRO.
New contact details (Lusha)
- S.R., Chief Revenue Officer, [SaaS company]
- Verified work email: s.r@[saas].com ✓
- Direct mobile: available (masked)
- Tenure: 5 weeks in role
ICP read: ✓ Strong fit — 380 employees, SaaS, North America, sales team of 45
Situation type: New outbound opportunity — new company not a current customer or active prospect
One flag: CRO title at a company this size means S.R. now owns a significantly larger budget than when we last spoke. Previous conversation was at VP level with a 90-person company — different scope entirely.
Outreach message
Subject: CRO at [SaaS] — different conversation than last time
Hi Sofia,
We spoke at [old company] a while back but the fit wasn’t quite there. CRO at a 380-person SaaS company is a different conversation — curious whether the timing works better now.
Worth a quick call?
[Name]
44 words. Acknowledges the prior contact without dwelling on it. Frames the new role as the reason it’s worth trying again.
Example C: Outside ICP — close the loop
The situation: D.K. was a Director at a mid-market SaaS company — had one call, never progressed. He just joined a 15-person early-stage startup as VP of Sales.
ICP read: ✗ Outside ICP — 15 employees, pre-product-market-fit stage, below minimum company size threshold
Situation type: Outside ICP — outreach not recommended
Output:
D.K.’s new company is below our minimum ICP threshold (15 employees, early stage). Writing outreach here isn’t worth the touch. Flag D.K. in your CRM with a note to revisit when the company grows, or monitor via Lusha signals for a headcount milestone that brings them into range.
No message written. Correct output.
Contact details validated via Lusha connector. Names masked to initials for privacy.
Why use Lusha in Claude
A job change notification is a trigger with a real window — roughly the first 30 days before the person is fully settled and less open to new conversations. Acting on it well means knowing where they actually landed, whether it’s worth the outreach, and what to say that’s specific to the relationship. Lusha in Claude handles the first two in one pass. The message comes from the situation — a past customer building a new RevOps function gets a completely different email than a warm prospect who joined a company outside your ICP. That specificity is what makes the message worth opening.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What if I don't know where they went yet?
Put “find it from Lusha” in the new company field. Lusha searches by name and last known company and returns the current verified employer. That’s often faster than waiting for a LinkedIn notification that may be delayed.
How long after the job change is it still worth reaching out?
The first 30 days is the window where the person is actively making decisions about how to set up their new role. 30–60 days is still viable. Beyond 60 days the “congrats on the new role” frame starts to feel dated — shift to a different angle.
What if the new company is already a customer?
The prompt flags it as a relationship expansion, not new business. In that case the right move isn’t outreach — it’s a note to the CS or AE who owns the account to introduce the new contact before they encounter the product cold.
Should I always reach out after a job change?
Only if the new company fits your ICP. The prompt explicitly returns a “do not write outreach” output when it doesn’t — and that’s the correct result. A bad touch at the wrong company wastes the relationship equity you built at the previous one.
What about the old company — do they need coverage now?
If this person was your champion or main contact at the old company, run the find who owns an account after your champion leaves play against the old account at the same time.
Ready to build this?
Get started with Lusha and set up this play in minutes.
