Check buying signals on your target account list
A Claude prompt that takes your target account list and scans for recent buying signals — funding rounds, hiring surges, strategic investments, news events — then surfaces which accounts are heating up right now. Built for AEs working active territories, CSMs watching for expansion windows, and ABM teams deciding where to focus the week.
The accounts you already own. The signals you didn’t know fired. One scan.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the account list and run.
Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.
The prompt
<context>
I have a target account list. I want to scan each account for recent buying signals — funding rounds, hiring surges by function, strategic news — so I know which accounts are heating up this week.
</context>
<task>
1. Take this account list (one row per line, domain or name):
[PASTE ACCOUNT LIST]
2. For each account, use Lusha's signals layer to retrieve activity in the last [WINDOW, e.g. 6 months]:
- Funding rounds (amount, date, lead investor, source article)
- Strategic investments (in or by the company)
- Sales, Engineering, or Marketing hiring surges (vs the company's own baseline)
- News events (IPO, M&A, leadership change)
3. Output a signal table:
Account | Hiring surge (function, %, vs baseline) | Funding / news event | Date | Signal intensity
4. Assign a signal intensity per account:
- HOT — multiple signals in the window OR one signal in the last 30 days
- WARM — one signal in the 30-90 day window
- QUIET — no signals in the window (worth a check next month)
5. Order accounts by intensity: HOT first, WARM second, QUIET last.
6. Summarize at the top: HOT count, WARM count, QUIET count. Surface the strongest single signal per HOT account so the rep knows where to lead the outreach.
</task>
<constraints>
- Hiring surges are measured against the account's own historical baseline, not an industry average.
- Funding events include the original news article URL where available — useful for outreach context.
- Do not invent dates, amounts, or investor names. Surface only what Lusha returns.
- QUIET is not failure. It means no signal in the window — useful for territory planning, just not for this week.
</constraints>What you'll get back
Input: 5-account target list (Snowflake, Datadog, Notion, Together AI, Verkada). Window — last 6 months. Signals — funding, hiring surges (Sales and Engineering), strategic news.
Output: 5 HOT accounts, 0 WARM, 0 QUIET. Every account on the list fired at least one signal in the window. Below is the real result from running the prompt against the live Lusha connector.
| Account | Hiring surge | Funding / news event | Date | Intensity |
|---|---|---|---|---|
| Notion | Sales +204% (51 vs 16.7 baseline) | — | Apr 20, 2026 | HOT |
| Together AI | Sales +23% | $1B funding round in negotiation, $7.5B valuation eyed (NVIDIA-powered) | Mar 6, 2026 | HOT |
| Verkada | Sales +37%, Engineering +25% | $5.8B valuation, CapitalG-led investment round | Dec 5, 2025 | HOT |
| Snowflake | Sales +29% | 2 strategic investments — RelationalAI and Ataccama (AI data trust) | Dec 2025 | HOT |
| Datadog | Sales +27% | — | Feb 2, 2026 | HOT |
The hiring surge percentages are measured against each company’s own baseline, not an industry average. Notion’s +204% surge represents 51 sales jobs against a historical pace of 16.7 — over triple the company’s normal hiring rate. Together AI’s $1B round is in negotiation per a NVIDIA-coverage article on Yahoo Finance; valuation target is $7.5B.
The Snowflake row is the most useful demonstration of how strategic investments surface as a signal. The company invested in two AI data trust startups in December 2025. That is intelligence for any seller pitching governance, data quality, or observability into Snowflake — the buying mandate is visibly active.
Why use Lusha
A target account list without a signal layer is a static document. The same five accounts can sit dormant for a quarter, then all light up in a six-week window, and the rep working the list every Monday morning has no way to see which is which. Three patterns change when the signal layer runs across the list.
The output is ranked by heat, not alphabet. AEs working 30-50 active accounts cannot pull discovery on all of them every week. The prompt surfaces which 5 to chase right now. The other 45 stay in the list, scanned again next week, ready when their signals fire.
Hiring surges are normalized against the company’s own baseline. Notion at +204% is genuinely extraordinary because Notion’s historical sales hiring pace is 16.7 jobs in 4 weeks. Snowflake at +29% is meaningful because their baseline is 116. The same percentage from two companies of very different sizes carries very different intelligence. The prompt surfaces the baseline so the rep reads the surge in context.
Strategic investments are buying signals about adjacent categories. When Snowflake invests in two AI data trust companies in the same month, the company is telling the market what they’re building toward. That is direct intelligence for any seller in governance, quality, observability, or data security. The prompt catches strategic-investment news because it is news of intent.
Data drawn from Lusha’s signals layer, applied across 300M+ verified contacts and millions of company records under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How is this different from the funded-companies and hiring-surge prompts in the prospecting gallery?
The prospecting prompts ask “find me companies with this signal” — they surface new accounts the rep does not already know. This prompt starts from accounts the rep already owns and answers “which of these are heating up?” Different starting point, different output. Reps who use both run the prospecting prompts for territory expansion and this prompt for weekly active-account scanning.
What signal types does the prompt cover?
Funding rounds, IPO, M&A, strategic investments, sales hiring surges, engineering hiring surges, marketing hiring surges, leadership change news, risk news, and commercial activity news. Default focus is on funding and hiring surge — both can be widened or narrowed in the prompt’s signals list.
Why does the hiring surge use a percentage instead of absolute jobs?
A 50-job surge means something different at a 5,000-employee company than at a 200-employee company. Normalizing against the company’s own historical baseline produces a percentage that reads as real intensity across very different account sizes. The prompt surfaces both the percentage and the underlying baseline so the rep can verify the math.
How many accounts can the prompt scan in one run?
Up to 100 accounts per call. For larger territories, batch by tier or owner — Tier 1 in the morning, Tier 2 in the afternoon — so the output stays scannable.
Does the prompt charge a credit per account, or per signal?
Lusha credits scale with the signals returned, not the accounts scanned. Accounts with multiple recent signals consume more credits. Accounts with no signals in the window may return without charge. Confirm the exact credit math in your Lusha plan settings.
Can I save the scan as a recurring weekly check?
The prompt itself runs on demand inside the Claude session. For recurring weekly scans against a saved persona or territory, see the buying-signal digest prompt in this gallery.
Ready to build this?
Get started with Lusha and set up this play in minutes.
