Build a signal-based ICP report for the demand gen team
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha connector output, but were not pulled from a live session. Run the prompt with your own ICP parameters to see live results. Personal details in any live examples are masked or abbreviated for privacy.
A signal-based ICP report for demand gen shows which segments of the target market are showing the most buying activity right now — funding rounds, exec hires, headcount surges — ranked by signal density so budget follows intent rather than assumption. This Claude prompt scans ICP segments via Lusha‘s signals layer, ranks every segment by signals per 100 companies, surfaces example accounts currently signaling in the top segments, and posts a heat map with budget shift recommendations to Slack before the monthly demand gen planning meeting.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I want to understand which segments of my ICP are showing the most buying activity right now — not based on last quarter's data, but based on what's actually happening in the market this month. I want to know which industries, company sizes, and geographies have the most funding rounds, exec hires, and headcount surges so I can concentrate demand gen spend where intent is highest.
My ICP:
- Industries to analyze: [e.g. "B2B SaaS, Fintech, Healthcare Tech" — or "all"]
- Company size ranges: [e.g. "50–200 / 200–500 / 500–1,000 / 1,000+"]
- Geographies: [e.g. "US / EMEA / APAC" — or "global"]
- Target function: [e.g. "Sales, RevOps, Finance" — the function we sell into]
- Signals to track: [e.g. "funding rounds, exec hires, headcount surge" — or "all signals"]
- Timeframe: [e.g. "last 30 days" / "last 60 days"]
- Slack channel for output: [CHANNEL NAME OR "return as report only"]
</context>
<task>
1. Use Lusha's signals layer to scan the ICP segments specified:
- For each segment combination (industry + size range + geography): count signal activity
- Signal types: funding events, exec hires in the target function, headcount surges 15%+, M&A as acquirer
- Return signal counts and signal density (signals per 100 companies in the segment)
2. Rank segments by signal density:
- A small segment with high density is more actionable than a large segment with low density
- Top 5 segments by signal density
- Bottom 3 segments — lowest signal activity
3. For the top 3 segments, find representative example accounts currently signaling:
- Company name, size, industry, specific signal, verified contact in the target function
- These illustrate what the signal looks like — they are not campaign targets
4. Build the ICP signal report:
## Signal heat map: segment matrix showing signal density per ICP segment
## Top 5 segments: segment name · density · count · recommended channel
## Bottom 3 segments: segment name · density · why signal is low
## Example accounts currently signaling: 3 per top segment
## Recommended budget shift: specific — which segment, which channel, directional shift
5. Post to Slack if channel specified.
</task>
<constraints>
- Signal density (signals per 100 companies) is the primary metric — not total count.
- Example accounts illustrate the segment pattern — not a campaign target list.
- Budget shift must be specific: not "increase spend on SaaS" but which segment,
which channel, and directional shift.
- Zero-signal segments reported, not skipped.
</constraints>What you'll get back
The situation: A demand gen manager runs this at the start of the month before allocating Q3 budget across segments. ICP: B2B SaaS and Fintech, 200–1,000 employees, US and EMEA, RevOps and Sales function.
Signal heat map — last 30 days
| Segment | Companies in segment | Signals detected | Signal density |
|---|---|---|---|
| B2B SaaS · 200–500 · US | 1,240 | 187 | 15.1 per 100 |
| B2B SaaS · 500–1,000 · US | 680 | 89 | 13.1 per 100 |
| Fintech · 200–500 · US | 820 | 94 | 11.5 per 100 |
| B2B SaaS · 200–500 · EMEA | 960 | 92 | 9.6 per 100 |
| Fintech · 500–1,000 · EMEA | 430 | 38 | 8.8 per 100 |
| B2B SaaS · 500–1,000 · EMEA | 510 | 31 | 6.1 per 100 |
| Fintech · 200–500 · EMEA | 390 | 18 | 4.6 per 100 |
| Fintech · 500–1,000 · US | 280 | 9 | 3.2 per 100 |
Top 5 segments — concentrate spend here
1. B2B SaaS · 200–500 employees · US · density 15.1 Highest signal density in the ICP. Funding rounds and SDR/AE headcount surges are driving most signals. Series A and B companies in active growth phase. Recommended channel: LinkedIn paid + targeted cold email. Window is 4–6 weeks from signal.
2. B2B SaaS · 500–1,000 employees · US · density 13.1 Strong density driven by exec hires in Sales and RevOps functions — new leaders evaluating tools in the first 60 days. Recommended channel: LinkedIn paid targeted at new hires + ABM direct outreach to new exec contacts.
3. Fintech · 200–500 employees · US · density 11.5 Funding-led signals dominating — Series B and C rounds in US Fintech. Budget available, headcount targets being set. Recommended channel: Post-funding congratulations campaign + event invite to upcoming Fintech-focused event.
4. B2B SaaS · 200–500 employees · EMEA · density 9.6 Good density but lower than US equivalent — EMEA SaaS funding activity running at roughly 60% of US pace this month. Recommended channel: Maintain current EMEA spend, don’t increase until density matches US levels.
5. Fintech · 500–1,000 employees · EMEA · density 8.8 Steady signal activity. Not a priority increase — maintain current allocation.
Bottom 3 segments — consider pausing or reducing
Fintech · 500–1,000 · US · density 3.2 Very low signal activity despite being a large segment. Funding and hiring activity in US enterprise Fintech has slowed significantly this month. Recommend pausing paid spend here and redirecting budget to Segment 1 and 2.
Fintech · 200–500 · EMEA · density 4.6 Low density — EMEA Fintech mid-market is quiet this month. Maintain nurture email only.
B2B SaaS · 500–1,000 · EMEA · density 6.1 Below average. No immediate action — monitor next month before reducing spend.
Example accounts currently signaling — Segment 1
B2B SaaS · 200–500 · US — illustrative of current signal pattern
| Company | Size | Signal | Contact |
|---|---|---|---|
| Dunmore Analytics | 580 | Series B · 18 days ago | T.K., VP Sales ✓ |
| Crestline Software | 340 | Hiring surge +22% · RevOps | R.V., VP RevOps ✓ |
| Falcrest Tech | 380 | Series A · 9 days ago | P.N., VP RevOps ✓ |
Example accounts illustrate what signals look like in this segment. Not a campaign target list — use the ABM target list play to build the full campaign list.
Recommended budget shift
Increase: B2B SaaS 200–500 US (Segment 1) — highest density, most actionable window. If currently 25% of budget, consider 35%. Increase: B2B SaaS 500–1,000 US (Segment 2) — exec hire signals mean new buyers actively evaluating. Good candidate for ABM direct outreach budget. Pause: Fintech 500–1,000 US — density too low to justify paid spend this month. Redirect to Segments 1 and 2. Maintain: All EMEA segments — density is below US but stable. No increase or decrease.
Illustrative example — fictional company names used. Run with your own ICP parameters to see live results.
Why use Lusha in Claude
Lusha in Claude converts raw signal data into a budget allocation decision in one pass — without a data analyst, without a BI tool, and without waiting for last quarter’s results. Signal density — signals per 100 companies — is the metric that matters here, not total signal count. The Fintech 500–1,000 US segment has 280 companies but only 9 signals — a density of 3.2 per 100. The B2B SaaS 200–500 US segment has over 1,200 companies and 187 signals — density of 15.1. A demand gen team allocating budget based on segment size alone would over-invest in large, quiet segments and under-invest in smaller, active ones. The density metric corrects that bias. Lusha’s 7M new signals per week is what makes this report actionable on a monthly cadence — the picture changes meaningfully from month to month.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What is signal density and why use it instead of total signal count?
Signal density is the number of signals detected per 100 companies in a segment — it normalizes for segment size. A segment with 1,000 companies and 50 signals has a density of 5.0. A segment with 200 companies and 30 signals has a density of 15.0. The second segment has fewer signals in absolute terms but is far more active proportionally — meaning a higher percentage of companies in that segment are in a buying window right now. Total count alone would lead to over-investing in large quiet segments.
How often should I run this report?
Monthly. Lusha adds 7M new signals per week, so the signal picture shifts meaningfully between months. A segment that was quiet in April may be active in May after a wave of funding rounds. Running the report monthly before budget allocation meetings ensures spend follows current intent, not assumptions from the previous quarter.
Can I use this report to decide which events to sponsor?
Yes — segment signal density is a strong proxy for event ROI. If B2B SaaS 200–500 US has the highest density this month, events that attract that segment are the highest-value sponsorship targets. If Fintech 500–1,000 US is at 3.2 density, a Fintech enterprise event this month is unlikely to generate returns.
Are the example accounts in the report actual campaign targets?
No — the example accounts illustrate what the signal pattern looks like in each segment. To build a verified campaign list for the top segments, use the ABM target list play which runs Lusha’s full prospecting engine against the segment criteria.
What signals does Lusha track for this report?
Funding rounds (Series A and above), executive hires in the target function, headcount surges of 15% or more in the target function, and M&A activity as acquirer. Each signal is time-stamped so the density calculation only includes signals within the specified timeframe.
Ready to build this?
Get started with Lusha and set up this play in minutes.