Outputs on this page come from a live run on September 11, 2026. Contact and company names are masked to initials. No emails or phones were revealed.
Company change is one of the two contact signals in the Lusha plugin for Claude. It fires on people you already know, which is what makes closed lost the right list to run it on: every hit is an account with a history in your CRM and a reason the deal died that may have just walked out of the building.
Check my closed lost contacts for people who have left, find who took their seat, and tell me which accounts to reopen.
Before anything else, run account_usage and tell me my remaining credits. Do not run any signal call if fewer than 50 credits remain; stop and tell me.
Here is my closed lost contact list (one per line: LinkedIn URL or full name plus company domain, then the month we lost the deal and the contact's title at the time):
[PASTE UP TO 25 CONTACTS]
Steps:
1. Run signals_contacts_search on the list with signalTypes ["companyChange"], startDate 180 days ago, maxResultsPerSignal 1. Batch in groups of 25 if the list is longer. Report any contact that comes back NOT_FOUND; a stale company field in my CRM is the usual cause, and it often means the person already left.
2. For every contact who changed company, record the signal date, the previous title, the previous company (this is the closed lost account) and the contact's city and country from the profile.
3. Find the seat at the previous company. Run prospecting_contact_search with companyDomains set to the previous company, jobTitlesExactMatch set to the previous title, a location filter matching the departed contact's city or country (validate the value with prospecting_contact_filters first), and enrich set to false.
If it returns 1 to 3 people, list them as BACKFILL candidates.
If it returns more than 3, the seat is a team, not a person. Rerun for the manager one level up (the departed contact's likely manager title in the same location) and list that person as the ENTRY POINT instead.
If it returns 0, retry with the similar title option. If still 0, mark NOT YET BACKFILLED and flag the account for a rerun next month.
4. Classify timing from the signal date: FRESH under 30 days, WINDOW 30 to 90 days, OLDER past 90.
5. Rank accounts for reopening: WINDOW first (the replacement is settled enough to talk and new enough to have no vendor loyalty), then FRESH, then OLDER. Within a tier, accounts where the departed contact was the person who said no rank above accounts where they were a champion.
6. For the top 5, write one opening line to the backfill or entry point that mentions the team had looked at this area before, without naming the departed contact, quoting the old objection, or saying "your predecessor."
7. For each reopened account, tell me to create a new opportunity rather than reviving the old record, and to loop in the original AE for context before sending.
Output: one table with columns Account | Departed contact (title only) | Left on | Now at | Seat status | Backfill or entry point (title, location) | Timing | Opening line. Then two lines: what the ranking is based on, and credits used. Do not reveal any emails or phones in this run.The situation.
A stand in for a closed lost contact list: 25 sales leaders across 20 B2B software companies, with one known departure among them. No loss dates supplied, so the champion versus blocker ranking in step 5 could not be applied.
The run.
account_usage first, at zero credits. One batch call on 25 contacts for companyChange, 180 day window: 2 of 25 fired, 3 credits. Then the backfill search on the clearest departure: exact title at the previous company, preview only, 1 credit.
What came back.
| Account | Departed contact (title only) | Left on | Now at | Seat status | Backfill or entry point | Timing | Opening line |
|---|---|---|---|---|---|---|---|
| S.F. (CRM platform, ~70,000 emp) | Regional Sales Manager, Sydney | Jul 1 | B.Z. (customer engagement platform), as Senior Sales Director | TEAM: 90 people hold the exact title company wide; first page of results all in Dublin | Rerun with a Sydney location filter; if still more than 3, target the regional sales director for Australia as the ENTRY POINT | WINDOW (72 days) | Your team in the region had looked at verified contact data earlier this year. A few things have changed on our side since; happy to show you what, with no assumption about where the conversation left off. |
| C.T. (mobile marketing, ~1,000 emp) | Title not returned | May 1 | B.Z., as Area Vice President of Sales | Cannot search: previous title missing | Check the contact’s profile for the prior title, then rerun step 3 | OLDER (133 days) | |
| 23 contacts | still in seat |
Ranking based on timing tier; the champion versus blocker rule needs loss context that was not supplied. Credits used: 3 for signals, 1 for the backfill preview. Confirmed live via Lusha connector, September 11, 2026. Names masked.
What happens next. The entry point goes to the verify a contact’s title play before anything is sent, then into a new opportunity, not the old record. The original AE gets the context first. And the departed contact is a second play, not a footnote: they now sit at a new company as a Senior Sales Director who knows your product, which is the job change outreach case.
Most closed lost lists get a check in on a calendar, sent to the same person who said no, and the answer does not change. This play waits for the one event that changes it: the person leaves. Inside Claude, the plugin finds the departure across your whole lost list in one call, works out where the empty seat is, and previews who sits in it now without spending a credit on their details. What used to be an accident, a rep noticing on LinkedIn that a contact moved, becomes a monthly run against the list where it matters most. Every signal is sourced under Lusha’s data methodology and compliance framework.
A known contact’s employer differs between two readings. The plugin returns the previous company and domain, the current company and title, and the signal date. Where it can, it returns the previous title too.
Because on a closed lost list every departure has a known consequence: the objection left. On a general list a company change is interesting; here it is a reason to act. The general version is the monitor role changes play.
Narrow by location first. If that still returns a group, the person you want is the manager of that group, not a guess at which member replaced your contact. The prompt escalates one level and calls it the entry point.
Monthly, on the full closed lost list, in batches of 25. Readings are monthly, so weekly runs return the same result for the same credits.
One credit per signal event, so a 25 contact batch with two departures costs 2 or 3 credits. Each backfill preview costs 1 credit per 25 results and reveals nothing. account_usage runs first and the prompt stops under 50.
No. The old record carries the reason for the no. Create a new opportunity linked to the departure, so the pipeline shows a fresh conversation rather than a dead one reopened, and attribution stays honest.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
