Outputs on this page come from a live run on September 12, 2026. Company names are masked to initials. No contacts were previewed or revealed.
New job post, headcount increase and financial news are three of 26 company signals in the Lusha plugin for Claude. Any one alone is a weak signal. The same account firing on two or three together is a different story, and most teams never see the combination because each shows up as its own separate alert.
Check my target accounts for new job posts, headcount increase and financial news, and score each account by how many fired together.
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]
Steps:
1. Run signals_companies_search on the list with signalTypes ["newJobPost", "headcountIncrease3m", "financialEventsNews"], startDate 90 days ago, maxResultsPerSignal 3. Batch in groups of 25 if the list is longer.
2. For each account, count how many of the three signal types fired at least once.
3. Score: 3 types fired = HIGH; 2 types = MEDIUM; 1 type = LOW; 0 = drop from the output.
4. Within a score tier, sort by most recent signal date across the three types.
5. For HIGH and MEDIUM accounts, list which specific signals fired and the most recent date for each.
Output: one table with columns Account | Score | Signals fired | Most recent date. Then two lines: how many accounts scored HIGH, and credits used.The situation. The same three roster accounts, checked for new job posts, headcount increase and financial news together. Names masked to initials with an industry descriptor: S.K. (data cloud platform), D.D. (cloud monitoring platform), M.G. (database platform).
The run. account_usage first, at zero credits. Two batch calls on 3 domains, 90 day window: one for newJobPost (reused from an earlier pull where the window overlapped), one for headcountIncrease3m and financialEventsNews. 21 signal events combined, 22 credits.
What came back.
| Account | Score | Signals fired | Most recent date |
|---|---|---|---|
| D.D. (cloud monitoring platform, ~9,900 to ~10,700 emp over the quarter) | HIGH | New job post; Headcount +7% (3 month); Financial news ($80B valuation, $223M earnings) | Sep 7 |
| S.K. (data cloud platform) | MEDIUM | New job post; Financial news (37% product revenue increase cited) | Sep 5 |
| M.G. (database platform) | MEDIUM | New job post; Financial news ($772M revenue, guidance raised) | Sep 4 |
Classification based on how many of the three signal types fired inside the 90 day window. Credits used: 22. Confirmed live via Lusha connector, September 12, 2026. Company names masked.
What happens next. D.D. is the account to work first: all three signals fired in the same window, which is a genuinely stronger position than a single unconfirmed posting. S.K. and M.G. sit at MEDIUM, real signal but not yet compounding; re-run monthly, since a third signal appearing moves either one up a tier. Route HIGH accounts to the new job post outreach play for a role-specific opening line.
A rep watching one signal at a time sees three separate alerts and has to decide, on instinct, which account to work first. This prompt scores the combination instead: an account with a fresh job post, a headcount increase and a piece of financial news in the same window ranks above an account with a single unconfirmed posting, without anyone doing that math by hand. Every signal is sourced under Lusha’s data methodology and compliance framework.
New job post, headcount increase and financial news are three independent indicators that a budget conversation may be forming: a role opening, a team growing, and money becoming available, in some order. Swap in other signals, such as leadership change or IT spend increase, if they fit your ICP better.
All three signal types fired for that account inside the 90 day window. In the live run, one of three roster accounts scored HIGH, firing on a new job post, a 7% three month headcount increase and two pieces of financial news in the same period.
Because firing on all three signals inside one 90 day window is a real, comparatively rare alignment. MEDIUM, two of three, is still a meaningfully stronger position than an account with none.
Monthly. A weekly rerun against the same 90 day window mostly returns the same accounts for the same credits.
One credit per event returned across the three signal types. In the live run, three roster accounts returned 21 events combined across two calls for 22 credits. No contact preview or reveal runs in this play.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
