Prompt

Find which target accounts hired a senior executive

Tools: ClaudeLusha

Example output on this page is a live run via the Lusha connector, September 12, 2026, on 25 companies of 200 to 500 employees with people news in the last six months. Companies are masked to initials, individuals are not named. Run the prompt with your own account list to see live results.

Somewhere in your territory a senior executive started this quarter and nobody told you. This prompt scans a list of target accounts for new executive hires and ranks them by what each company has done since: Lusha in Claude pulls six months of signals for up to 25 accounts in one call, finds the arrivals, and shows which ones turned into activity. You work the list from the top.

The prompt

Find which of my target accounts hired a senior executive in the last six months, and rank them by what the company has done since the arrival. Use the Lusha connector.

Accounts (up to 25 domains):
[domain 1]
[domain 2]
[domain 3]

Steps:

1. Call account_usage first. It is free. Tell me the credit balance before you spend anything.

2. Call signals_companies_search once for all the domains, with signalTypes: peopleNews, surgeInHiring, headcountIncrease3m, itSpendIncrease, financialEventsNews, productActivityNews, commercialActivityNews. Set startDate to six months ago and maxResultsPerSignal to 100. The default is 10 and it hides older events. If I gave you more than 25 domains, split them into calls of 25.

3. For each account, find the executive hire. From peopleNews, take events with eventType "Executive Hire". Read the eventSummary and keep only senior titles: chief officer titles, CEO, CFO, COO, CTO, CIO, CISO, CMO, CRO, CHRO, president, managing director, vice president, SVP, EVP, head of. Drop board seats, advisors, partners, chairs and director level roles. The anchor is the most recent qualifying hire. Use eventEffectiveDate, or articlePublishedDate if there is no effective date. Accounts with no qualifying hire go in a short list at the end and are not ranked.

4. For each account with a hire, split the buying signals into before and after the anchor date. Before is the 60 days before the hire. After is the 60 days after, or up to today if fewer than 60 days have passed. Count these as buying signals:
- surgeInHiring where changeRatePercent is 25 or more. Ignore any surge row where historicalAvg is 0; that is the first week of tracking, not a surge.
- headcountIncrease3m where changeRatePercent is 3 or more
- itSpendIncrease where changeRatePercent is 10 or more
- financialEventsNews with eventType Funding Round, IPO or Strategic Investment
- productActivityNews with eventType Product Launch
- commercialActivityNews with eventType New Customer, Partnership, Facilities Expansion or New Location
Where several news events share one article, count them once. If the hire date is within 60 days of the start of the history, mark the before window as incomplete.

5. Rank the accounts by number of buying signals since the arrival. Break ties by days since arrival, fewer first. Show a table with these columns: Account, Who arrived (title and date), Days since, Signals before (60 days), Signals since, First signal on day, Strongest signal since, Window (complete, or days elapsed out of 60).

6. Under the table, write a five line brief for each of the top three: who arrived, what has changed, and the outreach angle in two sentences that reference the strongest signal since the arrival. No flattery, no "congrats".

7. End with the accounts that had no qualifying hire, the accounts where the window is too early to judge, and the credits used.

Do not enrich any contacts. Do not reveal emails or phone numbers.

Paste up to 25 domains where the placeholders are. For a territory you have not listed, ask Claude to build the list first with the build a target account list play, then run this on the result.

 

What you get

The situation: a rep covering mid market accounts wanted to know which of 25 companies had brought in a new senior leader since spring, and which of those had started doing something about it.

The output, run September 12, 2026:

New executive hires across 25 accounts · 10 qualifying · pulled September 12, 2026

AccountProfileWho arrivedDays sinceBefore (60d)SinceFirst signal, dayStrongest sinceWindow
U.T.B.Specialist bank, UK, ~480Head of Clubs and Networks, Jun 16897813Hiring surge +193%, Aug 10Complete
N.C.B.Cooperative bank, US, ~500Vice President, May 26110376Hiring surge +289%, Jun 22Complete
Z.G.Data analytics platform, US, ~400COO, CFO and SVP GTM, May 4132247Hiring surge +109%, May 18Complete
C.A.Space and defense comms, US, ~480VP Business Development, Jun 2580536IT spend +138%, Aug 8Complete
C.B.Developer tools software, US, ~480CEO, Jun 11044321Hiring surge +233%, Jun 22Complete
S.B.Regional bank, US, ~500SVP Private Banker, Jul 29461310Hiring surge +633%, Aug 1046 of 60
C.L.Network security, US, ~480Chief Customer Officer, Jul 2748420Hiring surge +49%, Jul 2748 of 60
R.L.Fuel and lubricants distributor, US, ~400CHRO, Jul 136230nonenoneComplete
M.B.Church management software, US, ~470SVP Information Technology, Sep 4970nonenone9 of 60
M.A.Advertising agency, US, ~480CEO, Mar 1196incomplete0nonenoneBefore window incomplete

Top three briefs

U.T.B. A head of intermediary sales channels arrived June 16 at a UK specialist lender. Before the hire the company was already busy: six hiring surges and one product launch in 60 days. Since: four more surges, three product launches in July, and the first IT spend increase in the history on August 8. The launches cluster in the first four weeks after arrival. Angle: three product launches in one month means new distribution and new processes; ask what the sales team is using to work the new channels, and reference the July launches by name.

N.C.B. A vice president joined a US cooperative bank May 26. Before: three signals, mostly IT spend recalculations. Since: seven, including four hiring surges between June 1 and July 13, the largest at nearly three times the normal posting rate. First signal on day 6. Angle: the hiring started the week the new VP arrived and ran for six weeks; the conversation is about the team being built, not the appointment.

Z.G. A data analytics company appointed a COO, a CFO and an SVP of GTM operations on the same day, May 4. Before: two headcount growth readings, nothing else. Since: four hiring surges in six weeks, first on day 7. Angle: a three seat leadership change on one day is a reset, and the GTM operations seat is the one to reach; the hiring pattern since suggests the operating model is being rebuilt.

Too early to judge: S.B. (46 days, 3 signals so far, trending up), C.L. (48 days, 2 so far), M.B. (9 days, nothing yet; the company showed seven signals in the 60 days before the hire, so watch this one).

No change since arrival: R.L. (CHRO, 62 days, zero buying signals since; three before). M.A. (CEO, March 1, before window falls outside the history).

No qualifying hire in six months: 15 of 25 accounts. Six had executive hire news that did not pass the seniority filter: two directors of business development, a chief underwriter, a law firm partner, a design practice leader and a quant trading strategist.

Credits used: 416. Fifty two for the company search with the news filter, 364 for signals across 25 companies.

Live example via Lusha connector, September 12, 2026. Companies masked to initials, no individuals named. Signal values are as returned.

 

Why it works

The single account version of this play tells you whether one arrival changed anything. The list version tells you where to spend the week. Lusha in Claude returns six months of dated signals for 25 companies in a single connector call, and because the executive hire is itself a dated news event in the same history, Claude can anchor each account on its own arrival date and count what fell either side of it. The ranking is then a plain count of buying signals since the arrival, which is the question a rep is actually asking: not who hired, but who hired and then started moving. The seniority filter and the thresholds are published in the prompt, so the ranking can be checked, and the accounts that fell out of the filter are listed rather than dropped silently. Everything runs on aggregate company data through Lusha’s compliance framework. No contact is enriched until you decide who to call.

FAQ

How many accounts can I run at once?

Twenty five per connector call. The prompt splits larger lists into calls of 25 and merges the ranking. A 100 account territory is four calls and roughly 1,500 to 2,000 credits depending on how active the companies are.

What counts as a senior executive?

Chief officer titles, CEO through CHRO, president, managing director, vice president, SVP, EVP and head of. Board seats, advisors, partners, chairs and director level roles are excluded. The list is in the prompt and can be edited.

Why rank by signals since arrival rather than by seniority of the hire?

Because a CEO who has changed nothing in 60 days is a weaker opening than a VP whose team has been hiring at three times the normal rate since week one. Seniority tells you who to contact. Activity tells you whether now is the time. The table shows both.

Can I use this on my existing customers?

Yes, and it is arguably more useful there. A new CRO or CIO at a customer is a renewal risk and an expansion opening at the same time. Run it on the book of business and read the “no change since arrival” list as the accounts where the new leader has not yet decided anything.

What do I do with the accounts that had no qualifying hire?

Nothing, this week. The check buying signals on your target account list play covers the rest of the list without the arrival anchor.

 

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.