Prompt

Brief yourself on what changed since a new executive arrived

Tools: ClaudeLusha

Example output on this page is a live run via the Lusha connector, September 12, 2026. The company and the individual are masked. Run the prompt with your own account to see live results.

A new senior executive at a target account is the cleanest buying trigger there is, and the one reps act on with the least information. This prompt turns a new executive hire into a before and after brief: Lusha in Claude pulls six months of company signals, finds the arrival, and shows what the company has done since, against what it was doing before. You walk in knowing whether anything actually changed.

The prompt

Brief me on what has changed at a company since its most recent senior executive arrived. Use the Lusha connector.

Company: [company domain]

Steps:

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

2. Call signals_companies_search for the domain with signalTypes: peopleNews, surgeInHiring, headcountIncrease3m, itSpendIncrease, financialEventsNews, productActivityNews, commercialActivityNews. Set startDate to six months ago and maxResultsPerSignal to 100. The default is 10, which cuts off older events and makes the before window look empty.

3. 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 and chairs. The anchor is the most recent qualifying hire. Use eventEffectiveDate, or articlePublishedDate if there is no effective date. If there is no qualifying hire in the last six months, say so and stop.

4. Split every buying signal 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; say how many days have passed. Count these as buying signals, with these thresholds:
- surgeInHiring where changeRatePercent is 25 or more
- 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.

5. Write the brief in this shape:
- Who arrived: title, date, source article title. Days since arrival.
- Before the hire, 60 days: number of buying signals, listed by type with dates.
- Since the hire: number of buying signals, listed by type with dates. Days from arrival to the first one.
- Read: one paragraph. Is the company doing more since the arrival, less, or the same? Name the strongest signal. If the window is not over yet, say what to watch for.
- Outreach angle: two sentences that reference the arrival and the strongest signal since. No flattery, no "congrats".
- Credits used on this brief.

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

What you get

The situation: a developer tools software company, about 480 employees, US headquartered, named a new CEO on June 1, 2026. The rep found out from a LinkedIn post two weeks later and wanted to know whether the arrival had changed anything before reaching out.

The output, run September 12, 2026:

New executive brief · C.B. · pulled September 12, 2026

Who arrived: M.P., Chief Executive Officer. Effective June 1, 2026, announced June 16. Source: company newsroom. 103 days since arrival, so both 60 day windows are complete.

Before the hire, April 2 to May 31: 4 buying signals.
Product launch, April 2 (test intelligence product generally available)
Hiring surge, May 4 (+33% above historical average)
Hiring surge, May 11 (+93%)
Product launch, May 18 (readiness index announced at the company’s user event)

Since the hire, June 1 to July 31: 3 buying signals.
Hiring surge, June 22 (+233%), day 21
Hiring surge, July 20 (+137%), day 49
Hiring surge, July 27 (+48%), day 56
No product launch, funding, partnership or IT spend signal inside the window.

Read: inside the first 60 days, the company is doing about the same as before. Four signals became three, and the two product launches before the arrival were the previous leadership’s roadmap landing. The hiring surges since are stronger than the ones before, which fits a new CEO adding headcount rather than shipping. The window has closed, but the six month history shows what came next: an IT spend increase of +65% on August 8 (day 68) and two hiring surges of +360% and +300% on August 17 and 24. Whatever this CEO is building started showing up in month three, not month one.

Outreach angle: reference the August hiring pattern, not the appointment. Three months in, the team is growing at three times its normal rate and IT budget moved with it; the conversation is about what that growth needs, not about the new role.

Credits used: 16. One for the company search, one per signal returned.

Live example via Lusha connector, September 12, 2026. Company masked to initials, individual masked to initials. Signal values are as returned.

 

Why use Lusha in Claude

Every other version of this play stops at the appointment: someone new arrived, send a note. This one measures what the arrival did, because Lusha in Claude holds both halves of the answer in one place. The company signal history carries the executive hire as a dated news event and carries the buying signals the same way, so Claude can put the arrival date on a timeline and count what fell either side of it. The thresholds in the prompt keep the weekly hiring and headcount series from counting every small move, and the 100 event cap stops the default of 10 from hiding the before window. Everything runs on aggregate company data through Lusha’s compliance framework; no contact is enriched and no personal data is revealed until you decide to reach out.

FAQ

How much does this cost to run?

One credit for the company search, then one credit per signal event returned. A mid sized company with six months of history returns 10 to 25 events, so budget 15 to 30 credits per account. account_usage is called first and is free.

Can I run it on a list of accounts?

Yes, up to 25 domains in one signals call. Ask Claude to repeat steps 3 to 5 per company and rank the output by signals since arrival. Budget about 500 credits for 25 accounts. A list version of this play is coming.

Why 60 days and not 90?

Because the history is six months. To have a full before window and a full after window inside six months, the hire has to sit in the middle, and 60 days each side is what fits. If the hire is recent enough, the prompt also tells you how far into the after window you are.

What if the company has several new executives?

The prompt anchors on the most recent qualifying hire. If you want a specific one, name the title in the prompt: “anchor on the Chief Revenue Officer appointment.”

Does this reveal anyone’s contact details?

No. The prompt runs on company signals only and says so. When you are ready to reach out, the find the decision maker and draft the email play takes it from there.

Ready to run this?

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