Any one of these three signals is worth a call. All three on the same account, at the same time, is a different conversation — three independent reasons a deal opens, not one. Connect Lusha to Claude and this prompt checks a list of accounts you provide against all three signal types in a single pass, then sorts them by how many fired.
The prompt
Here are my target accounts: [paste company names or domains, up to 25].
Using the Lusha connector, check each one for three signals in the last
90 days: a funding event, a hiring surge, and an executive hire. Return
a table with company name, which of the three signals fired, and the
date of each.
Then sort into three groups:
(1) all three signals fired - call this week
(2) two of three fired - strong, worth prioritizing
(3) one signal fired - standard priority
Finish with the top five accounts by signal count and a one-line
reason for each.
What you’ll get back
The situation: an AE pastes 20 target accounts from an active territory and asks for a three-signal check.
The output:
Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own account list to see live results.
Why it works
Lusha’s signal API can check multiple named signal types on the same company in a single call — funding, hiring surge, and executive hire come back together, each with its own date, rather than as one blended “something happened” flag. Claude does the part that actually takes judgment: counting how many signals fired per account, checking whether they cluster in the same window, and ranking the list by conviction instead of just presence. Nothing here is a pre-built number — every result is generated against your own account list, in your own session, so there’s no static count to go stale. Contact and company data is verified across multiple sources and handled under GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance.
FAQ
How is this different from “Find accounts with stacked buying signals”?
That play checks any combination of signals loosely. This one checks three specific, named signals — funding, hiring surge, and executive hire — and tells you exactly which of the three fired per account, not just that “multiple signals” fired. Use this one when those three specific triggers matter to your motion; use the other for a broader sweep.
How many accounts can I check at once?
Up to 25 per run through the connector. For a larger territory, run it in batches and ask Claude to keep a combined ranked list across runs.
Can I swap in different signals?
Yes — the prompt names funding, hiring surge, and executive hire specifically, but any combination of Lusha’s signal types can be substituted. Risk signals, product launches, and website traffic changes all work the same way.
Why 90 days as the window?
Long enough to catch signals that don’t move in lockstep — a funding round and the hiring surge it funds often land a few weeks apart, not the same day. Narrow it to 30 days for a tighter, more urgent list.
What if an account shows zero signals?
It’s simply excluded from the output rather than padding the list with a “no signal” row — the table only shows accounts with at least one hit, so the list stays short and usable.
