Outputs on this page come from a live run on September 10, 2026. Company and executive names are masked to initials. No contacts were previewed or revealed.
The Lusha plugin for Claude carries seven news signal types, and People News is the one that names the person. Filtered to Executive Hire, it is the trigger your signals playbook calls “the best window”: a new leader building a stack, with budget and no loyalty to the vendors they inherited.
Find which of my target accounts have a newly hired executive and tell me who is in the outreach window.
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 list (domain, one per line):
[PASTE UP TO 25 DOMAINS]
Customer domains (or write "none"):
[PASTE]
Steps:
1. Run signals_companies_search on the list with signalTypes ["peopleNews"], filters.include.newsEventTypes ["Executive Hire"], startDate 90 days ago, maxResultsPerSignal 3. Batch in groups of 25 if the list is longer.
2. For every event, pull the person's title, the effective date of the hire, the article date, and the source type (company press release, trade press, other). Use the effective date, not the article date, to compute days in role as of today. If no effective date is present, use the article date and mark it as approximate.
3. Deduplicate: the same person at the same company reported twice is one hire.
4. Tier each hire by title: EXEC for C level, President, SVP, EVP and VP; MID for Director, Head of and Senior Director; BOARD for board of directors and advisory appointments. Drop BOARD from the ranking; board members do not buy software.
5. Classify the timing: EARLY if under 30 days in role, WINDOW if 30 to 90 days, LATE if over 90. Rank EXEC before MID, WINDOW before EARLY before LATE.
6. Tag customers as CHAMPION CHECK (a new leader at a customer is a relationship to rebuild, route to the account owner) and everyone else as NEW LOGO.
7. For the top 5 NEW LOGO hires in WINDOW or EARLY, write one opening line addressed to the new executive. For EARLY, congratulate and say nothing about your product. For WINDOW, reference the new role and one priority the title implies, without quoting the article.
Output: one table with columns Account | New executive (title only) | Days in role | Tier | Timing | Source type | Segment | Opening line. Then two lines: what the ranking is based on, and credits used. Do not preview or reveal any contacts in this run.The situation. A list of 25 enterprise software companies, 2,000 to 70,000 employees. No customer domains supplied.
The run. account_usage first, at zero credits. Then one batch call on 25 domains for peopleNews filtered to Executive Hire, 90 day window, up to three events per account. 9 of 25 fired, 16 events, 16 credits. After dedupe and removing board seats: 11 hires at 8 companies. After tiering and timing: 7 in EXEC or MID and inside the window.
What came back.
| Account | New executive (title only) | Days in role | Tier | Timing | Source type | Segment | Opening line |
|---|---|---|---|---|---|---|---|
| B.L. (financial operations, ~2,500 emp) | Chief Revenue Officer | 66 | EXEC | WINDOW | Company press release | NEW LOGO | Two months into a CRO seat, the pipeline you inherited is the one you are being measured on. Happy to show how revenue leaders at your stage find out what is real in it. |
| F.T. (cybersecurity, ~14,000 emp) | SVP, Asia Pacific | 66 | EXEC | WINDOW | Paid press release | NEW LOGO | Taking on a region that size usually starts with a question about which accounts the team is actually working. That is a data question before it is a sales one. |
| B.L. (financial operations) | Chief Technology Officer | 85 | EXEC | WINDOW | Trade press | NEW LOGO | Internal promotion to the seat; skip unless the conversation is about the AI platform the role now owns. |
| D.S. (agreement software, ~7,000 emp) | Vice President, Business (regional) | 90 | EXEC | WINDOW, last day | Trade press (non English) | NEW LOGO | Ninety days in is when the first plan becomes the second plan. If verified data for the region is on the list, this week is the moment. |
| A.V. (tax compliance, ~4,000 emp) | Director, DACH | 43 | MID | WINDOW | Company press release (reported twice, deduped) | NEW LOGO | Building a regional book from a standing start. We help new regional leads know who to call before the first quarter closes. |
| S.P. (customer experience software, ~3,500 emp) | Senior Director, Customer Success EMEA | ~36 (approximate) | MID | WINDOW | Trade press | NEW LOGO | |
| C.P. (spend management, ~3,500 emp) | Interim Chief Executive Officer | 17 | EXEC | EARLY | Trade press | NEW LOGO | Congratulations on stepping in. No pitch; the CEO departure the same day is the more useful signal, see below. |
| A.D. (creative software, ~30,000 emp) | AI Strategy and Evangelism lead, APAC | 15 | MID | EARLY | Trade press | NEW LOGO | Congratulations only. |
| B.X. (content management, ~2,500 emp) | Managing Director, Legal | 132 | MID | LATE | Trade press, conference report | NEW LOGO | Hired May 1, written up August 31. Window closed. |
| S.P., P.C. (two companies) | Board of Directors (three appointments) | BOARD | dropped | Press release | |||
| F.T. | Regional Director, Systems Engineering | 64 | MID | WINDOW | School alumni newsletter | Source too weak to act on without a second confirmation. | |
| 16 accounts | no signal |
Ranking based on tier, then timing window, then days in role. Credits used: 16. Confirmed live via Lusha connector, September 10, 2026. Names masked to initials.
What happens next. The new executive is named in the news, so the contact step is short: hand the top five to the verify a contact’s title play to confirm they are in seat and get a verified email before the opening line goes out. For customers, a new leader is a champion check, not a pitch: the champion left play is the right next step.
A new leader is the one buyer who has budget, a mandate to change things, and no relationship with the incumbent vendor. The difficulty has never been knowing that; it has been finding them in time, across a whole list, without reading trade press all day. Inside Claude, the plugin turns the news feed into a table you can act on: the person’s title, how long they have been in the seat, how good the source is, and whether the window is still open. The filtering steps above are what separate a usable trigger from a pile of headlines, and they run in the same call. The run costs signal credits only; the executive’s contact details are not touched until you decide to reach out. Every signal is sourced under Lusha’s data methodology and compliance framework.
A People News event tagged Executive Hire: a published appointment to a leadership role, with the person, the title, an effective date where available, and the source article. In practice the tag covers everything from CEO to director to board seat, which is why the prompt tiers by title.
Under 30 days the leader is listening, not buying; a congratulation lands, a pitch does not. Between 30 and 90 they are deciding what to keep and what to replace. After 90 the first plan is set. The prompt sends a different opening line for each phase.
Because news lags. In the live run one hire was reported four months after it happened. Ranking by article date would have put a closed window at the top.
Signal reads cost 1 credit per event returned, including the events the prompt later drops as board seats or duplicates. In the live run, 25 domains cost 16 credits. account_usage runs first at zero credits and the prompt stops under 50. No contact preview or reveal runs in this play.
Yes, with the Executive Departure event type in the same signal. For customers it is a churn warning; for closed lost accounts it is the moment the person who said no has left. That is its own play.
A published appointment is public information about a business role. Reaching out still runs through Lusha’s verified contact data and the same consent and opt out handling as any other contact. The plugin does not reveal a phone or email in this play; that happens in the next step, under the standard rules.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
