Build a prospect list from a signal, not a job title

✦ Open in Claude

<context>
I want to build a prospect list based on a specific trigger signal — not just a job title or company size filter. I'm looking for accounts where something is happening right now that makes them more likely to need what we sell.

My outbound:
- What I sell: [PRODUCT / SOLUTION]
- My ICP (ideal customer profile): [COMPANY SIZE / INDUSTRY / REGION]
- The signal I'm targeting: [FUNDING ROUND / EXEC HIRE / HEADCOUNT GROWTH / M&A / OTHER]
- Why this signal matters for us: [ONE SENTENCE — e.g. "a new CRO typically audits the sales stack in the first 90 days"]
- How many accounts I want: [NUMBER — e.g. 10, 20, 25]
</context>

<task>
1. Use Lusha to find accounts that match both the ICP criteria and the signal:
   - Filter by company size, industry, and region as specified
   - Within those, surface accounts where the trigger signal is active in the last 90 days
   - For each account, confirm the signal is real — not inferred. Return only accounts where Lusha's data confirms the trigger.

2. For each account returned, identify the right first contact:
   - The person most likely to own the problem we solve, given the signal
   - Validate their current title and confirm they're still at the company
   - Pull verified work email and direct phone where available
   - Note how recently the signal occurred — fresher signals are higher priority

3. Rank the list by signal strength and recency:
   - Tier 1: signal occurred in the last 30 days, contact validated, direct contact details available
   - Tier 2: signal occurred in the last 31–90 days, contact validated
   - Tier 3: signal detected but contact details incomplete or signal is older than 90 days

4. For each Tier 1 and Tier 2 account, return:
   - Company name, size, industry
   - The specific signal and when it occurred
   - Primary contact: name, verified title, email, phone
   - One-line outreach angle tied directly to the signal — not a generic pitch

5. Flag any account where the signal is strong but the right contact is unclear or unverified — these need manual research before outreach.
</task>

<constraints>
- Only include accounts where Lusha confirms the signal. Don't infer from company size or industry alone.
- The outreach angle must be specific to the signal. "Congratulations on the funding" is not an angle — "You just raised a Series B and are likely building out the sales team — here's why that timing matters for us" is.
- If fewer than the requested number of accounts have a confirmed signal, return what's there. Don't pad the list.
- Tier the output clearly. A list of 20 accounts with no prioritization is not useful.
</constraints>

The situation: An SDR at a sales intelligence platform runs the prompt on a Monday morning. ICP: B2B SaaS companies, 100–500 employees, North America. Signal: new CRO or VP of Sales hired in the last 30 days. Reason: a new sales leader typically audits and resets the sales stack within 60–90 days of joining. She asks for 15 accounts.

Output: 9 Tier 1 accounts, 4 Tier 2, 2 flagged for manual research. 13 accounts ready to work before lunch.

Summary

15 accounts scanned. 9 Tier 1 · 4 Tier 2 · 2 flagged.

Signal: new CRO or VP of Sales hired in last 90 days. Run: May 21, 2025.

Tier 1 — act this week (signal within 30 days)

4 additional Tier 1 accounts available in full output — truncated here for display.

Tier 2 — work this week (signal 31–90 days ago)

Flagged — manual research needed

Aster Platforms · New CRO signal confirmed · Contact unclear — two people with CRO-adjacent titles, neither confirmed as the hire. Recommend checking LinkedIn before outreach.

Novela Group · New VP of Sales signal confirmed · Email unverified — direct phone available but cold-call only until email is confirmed.

Signals and contacts pulled via Lusha connector, May 21. Company details and contact information abbreviated for privacy.