Build an enriched ICP scoring table
A Claude prompt that takes a list of accounts, enriches each one with verified firmographics and signal data, then scores every row against your ICP criteria. The output is a tiered, ranked table — Tier A, B, or C — built for territory planning, ABM prioritization, and sequence assignment. Built for ABM leads, RevOps territory planners, and marketing ops who need a decision, not just a refresh.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the account list and your ICP, then 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 an account list. I want each account enriched with verified firmographics and signals, then scored against my ICP and tiered A/B/C for prioritization.
My ICP:
- Headcount: [RANGE, e.g. 500-5,000]
- Revenue: [RANGE, e.g. $50M-1B]
- Industry: [TARGET, e.g. B2B SaaS]
- Geography: [REGION, e.g. United States]
- Signal preference: [e.g. recent funding round, hiring surge, leadership change]
Scoring weight (rebalance as needed):
- Size fit: [weight]
- Industry match: [weight]
- Geography match: [weight]
- Active signal: [weight]
- Stage indicator (public / growth / early): [weight]
</context>
<task>
1. Take this account list (one row per line, with company name or domain):
[PASTE LIST]
2. For each account, use Lusha to enrich:
- Company name, HQ, headcount band, revenue range, industry
- Funding history (total raised, last round, last round date, IPO status)
- LinkedIn follower count (as a soft market-presence indicator)
- Office footprint (HQ + count of regional offices)
3. Apply the ICP framework to each account:
- Size fit: does the headcount and revenue land inside the target range?
- Industry match: does Lusha's sub-industry match the ICP industry?
- Geography match: does the HQ or office footprint match the target region?
- Active signal: is there a funding round in the last 12 months, or a public-company event?
- Stage indicator: public (mature stack, replacement sale), growth (rebuilding stack, expansion sale), early-stage (foundational stack, greenfield sale)
4. Assign a tier per account:
- Tier A — Strong fit on 4+ ICP dimensions plus active signal in last 12 months
- Tier B — Strong fit on 3 ICP dimensions, or 4 dimensions without an active signal
- Tier C — Strong fit on 2 or fewer ICP dimensions
5. Output a scoring table:
Company | Tier | Size fit | Industry | Geography | Active signal | Stage | Notes
6. Summarize at the top: total accounts, count per tier, recommended first-touch count for Tier A.
</task>
<constraints>
- Use Lusha's canonical company name and verified data. Do not invent fields.
- Surface the scoring reasoning per row so the user can adjust weights and re-tier.
- An account that fails industry or geography match cannot be Tier A regardless of size.
- An account without any verifiable signal can still be Tier B if size and industry are strong fits.
- Flag any account Lusha cannot resolve as no-match — do not auto-tier missing data.
</constraints>What you'll get back
Input: 5-account list (Snowflake, Datadog, Notion, Together AI, Verkada) and an ICP defined as B2B SaaS, US-based, headcount 500-10,000, revenue $50M-10B, with preference for accounts that closed funding in the last 12 months.
Output: 3 Tier A, 1 Tier B, 1 Tier C. Below is the real result from running the prompt against the live Lusha connector.
| Company | Tier | Size fit | Industry | Geo | Active signal | Stage |
|---|---|---|---|---|---|---|
| Snowflake | A | ✓ (5,001-10,000) | ✓ Software Development | ✓ US (San Mateo) | Post-IPO Equity $621M, in window | Public — replacement sale |
| Datadog | A | ✓ (1,001-5,000) | ✓ Software Development | ✓ US (New York) | Post-IPO Debt $870M, Dec 2024 | Public — replacement sale |
| Verkada | A | ✓ (1,001-5,000) | ✓ Software Development | ✓ US (San Mateo) | Series E $200M, Feb 2025 | Growth — rebuilding stack |
| Together AI | B | ✗ (201-500, below floor) | ✓ Software Development | ✓ US (San Francisco) | Series B $305M, Feb 2025 (strong) | Growth — rebuilding stack |
| Notion | C | ✓ (501-1,000) | ✓ Software Development | ✓ US (San Francisco) | Last round Oct 2021 (no active signal) | Quiet — no signal window |
The Together AI row is the most useful demonstration of how the scoring works. Industry, geography, and active signal are all strong. Size fit fails because the headcount is below the ICP floor. The framework holds — a single failed dimension drops it from Tier A to Tier B even with a strong recent round.
Five rows enriched, zero new credits consumed — this demo reuses the firmographic data already verified in the company-enrichment prompt.
Why use Lusha
CP scoring on raw account data is guesswork. The same account can score Tier A in one framework and Tier C in another depending on which signals were even checked. Three patterns matter for any team running a real scoring pass.
The framework is transparent and tunable. Every tier assignment shows the reasoning per dimension — size fit, industry, geography, active signal, stage. When the AE or marketer disagrees with a tier, they adjust the weight and re-run. The framework is not a black box. The verified data underneath it is the fixed input; the scoring weights are the variable.
Active signal separates Tier A from Tier B. Two accounts with identical firmographics can sit in very different buying windows. A company that closed a Series E last quarter has budget, mandate, and stack-rebuild appetite. A company that has been quiet on funding for three years has none of those things. The prompt surfaces the last round date and IPO history so the signal layer is visible, not assumed.
Stage indicator changes the sales motion. A public company runs a replacement sale — they have a stack, they are evaluating vendors against incumbents, the conversation is about TCO and switching cost. A growth-stage company runs a rebuild sale — they are scaling beyond their original tooling, the conversation is about future-fit and integration depth. The same product gets pitched differently. The prompt flags stage so the rep picks the right script.
Data drawn from 300M+ verified contacts and millions of company records under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How do I set the right ICP criteria?
Start with the firmographic shape of your closed-won customers from the last 6 months. Headcount range, revenue band, industry concentration, geographic mix. The ICP for scoring is the average of what already converts, not the aspirational target. Adjust upward only after the framework matches reality.
Can I run different ICPs against the same account list?
Yes. Run the prompt twice with different ICP definitions and compare which accounts tier into A on each. Accounts that score Tier A on both ICPs are core fit. Accounts that score Tier A on only one are conditional. Useful for AEs working multiple products or segments.
What if my ICP doesn't fit a single firmographic shape?
Run the prompt per ICP segment. A 5-account list scored against enterprise ICP and another 5-account list scored against mid-market ICP gives a cleaner result than one mixed list trying to satisfy both. The framework rewards specificity.
How is "active signal" defined?
The default in the prompt is a funding round in the last 12 months. You can replace or augment with hiring surge, leadership change, or news event signals — Lusha’s signals layer covers all of those. Pair this prompt with the funded-companies or hiring-surge prompt for richer signal input.
Does the tiering account for technographics or intent?
Not by default. Technographic and intent layers are powerful but require separate enrichment passes. For technographic-aware tiering, run the tech-stack prospect list prompt first to identify accounts using a target platform, then bring that list into this prompt for ICP fit scoring on top.
Can I push the tiered list to my CRM or ABM platform?
The Claude output is a structured table that copies cleanly into a CRM, ABM platform, or campaign tool. Direct push to Salesforce, HubSpot, 6sense, Demandbase, and other systems runs through Lusha’s standard integrations.
Ready to build this?
Get started with Lusha and set up this play in minutes.