Build my ICP from my closed-won deals

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own closed-won customers and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

Your ICP should come from your data, not a workshop. The companies that converted fastest, renewed at the highest rate, and expanded the most reliably — they have something in common. Usually several things. This Claude prompt takes your closed-won customers, runs them through Lusha to pull verified firmographics, funding history, tech stack, and the signals that were firing before each deal closed, and identifies the patterns that appear consistently across your best wins. What comes back is a precise ICP definition you can use immediately — to score new prospects, filter your pipeline, and brief your team on who to go after next quarter.

The prompt

<context>
I want to build a precise ICP definition from my actual
closed-won customers — not from assumptions or filters,
but from the patterns that appear consistently in the
deals I've already won.

My closed-won customers:
1. [Company name or domain]
2. [Company name or domain]
3. [Company name or domain]
4. [Company name or domain]
5. [Company name or domain]
[Add as many as you have — minimum 5 for reliable patterns]

What I sell: [one sentence describing your product and
the problem it solves]
My target buyer: [e.g. VP of Sales, Head of RevOps, CFO]
</context>

<task>
1. FIRMOGRAPHIC ANALYSIS — Use Lusha to pull the verified
   profile for each closed-won customer:
   - Industry and sub-vertical
   - Employee count at time of close
   - Revenue range
   - Funding stage and total raised
   - HQ geography
   - Company type: public / private / PE-backed

2. SIGNAL ANALYSIS — For each customer, check what signals
   were firing at the account in the 90 days before the
   deal closed:
   - Hiring surges in the target function
   - Executive moves in the buying role
   - Funding events
   - Intent signals on relevant topics
   - Tech stack changes

3. PATTERN IDENTIFICATION — Across all customers, find
   the attributes that appear most consistently:
   - Which firmographic combinations appear in 70%+
     of wins?
   - Which signals appeared before most deals closed?
   - Which tech stack signals correlate with conversion?
   - What does the typical deal look like at the moment
     it entered the pipeline?

4. ICP DEFINITION — Return a structured ICP built from
   the patterns found:
   - Firmographic profile: the specific ranges and
     categories that appear most in your wins
   - Signal triggers: the events that most commonly
     preceded a close
   - Tech stack indicators: technologies that correlate
     with fit
   - Exclusion criteria: attributes that appear in
     low-fit or lost deals if identifiable
   - Confidence level for each criterion based on how
     consistently it appears across your wins

5. SCORING FRAMEWORK — Return a simple scoring model
   based on the ICP found:
   - Which criteria are must-haves vs nice-to-haves?
   - How to score a new prospect against this ICP
     in under 2 minutes
</task>

What you'll get back

A precise ICP definition built from your actual closed-won data — firmographic patterns, signal triggers, tech stack indicators, and a scoring model you can use immediately.

Your ICP definition

Customers analyzed: 8  ·  Patterns identified: 6 high-confidence, 3 directional  ·  Confidence threshold: 70%+

Firmographic profile

CriterionPattern foundConfidence
IndustryB2B SaaS, Revenue Intelligence, Sales TechHigh — 7 of 8 customers
Employee count150–500High — 6 of 8 customers
Funding stageSeries A or Series BHigh — 7 of 8 customers
GeographyNorth America, UKHigh — 8 of 8 customers
Revenue range$5M–$30M ARR (estimated)Medium — 5 of 8 customers
Company typeVC-backed privateHigh — 7 of 8 customers

Signal triggers

Signals that appeared in the 90 days before most deals closed:

SignalFrequencyAvg days before close
Hiring surge in sales function (5+ roles)6 of 8 customers45 days
New VP of Sales or CRO hired5 of 8 customers62 days
Funding event in last 90 days5 of 8 customers71 days
Intent on sales prospecting tools4 of 8 customers30 days

Tech stack indicators

TechnologyFrequencySignal type
Salesforce7 of 8 customersMust-have indicator
Outreach or Salesloft6 of 8 customersStrong indicator
HubSpot (without Salesforce)1 of 8 customersWeak indicator

Exclusion criteria

CriterionReason
Under 100 employeesAppears in 0 closed-won deals
Enterprise (2,000+ employees)Appears in 0 closed-won deals — different motion
Non-SaaS business modelAppears in 0 closed-won deals
Bootstrapped / no fundingAppears in 1 closed-won deal — low confidence

Scoring model

Use this to score any new prospect in under 2 minutes:

CriterionWeightScore if met
B2B SaaS, 150–500 employees, Series A/BMust-havePass / Fail
Salesforce in tech stackHigh+2
Hiring surge in sales functionHigh+2
New sales leader in last 90 daysHigh+2
Funding event in last 90 daysMedium+1
Intent signal on relevant topicMedium+1
North America or UK HQMedium+1

Score interpretation:

  • 7–9 — Strong ICP match. Prioritize immediately.
  • 4–6 — Partial match. Qualify further before investing time.
  • 0–3 — Weak match. Deprioritize unless a compensating signal exists.
  • Fail on must-have — Exclude regardless of score.

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own closed-won customers and connectors to see live results.

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude, Lusha
Type: Prompt

Why use Lusha in Claude

Most ICP definitions are built from opinion. A sales leader describes the kind of company they think they sell best to, a marketing team turns that into filter criteria, and the result is a profile that reflects intuition rather than evidence. It feels right because it’s based on experience — but it misses the specific combinations of attributes that actually predict conversion, and it almost never captures the signals that were firing at accounts in the weeks before they closed.

Lusha’s data layer changes what’s possible here. Every closed-won customer in your list gets pulled from Lusha’s verified database — current and historical firmographics, funding history, tech stack, and the 24 live signal types that Lusha tracks across 1.2B+ data points daily. That means the analysis isn’t based on what you remember about those accounts. It’s based on what was verifiably true about them at the time they converted.

The pattern identification step is where the ICP stops being a description and becomes a prediction. When 7 of your 8 best customers were running Salesforce, Series A or B, and had a new VP of Sales in seat within 90 days of signing — that’s not a coincidence. It’s a pattern. And a pattern you can score new prospects against before your reps spend time on accounts that don’t fit it.

The scoring model at the end closes the loop. Instead of a written ICP that lives in a slide deck and gets ignored, you get a weighted scoring framework your team can apply in under two minutes — must-have criteria that immediately disqualify, signal-based criteria that rank the rest. Every downstream play in the Campus library becomes more precise when it runs against an ICP built this way rather than one assembled in a conference room.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use.

FAQ

  • How many closed-won customers do I need?

    Five is the minimum for reliable patterns — enough to distinguish signal from noise. Ten or more gives the analysis meaningful statistical weight. If you have fewer than five, the output will still surface patterns but the confidence levels will be lower and you should treat the results as directional rather than definitive. The more customers you include, the more precise the ICP becomes.

  • Should I include all my customers or just my best ones?

    Your best customers — the ones that converted fastest, expanded most, and renewed at the highest rate. Including customers who churned, required heavy discounting, or turned out to be a poor fit will dilute the patterns and produce an ICP that describes who you sell to rather than who you win with. If you want to understand why certain accounts don’t work, run the prompt separately with your churned accounts to identify the exclusion criteria.

  • How often should I rebuild my ICP?

    Once a quarter is a good baseline, or any time your win rate changes significantly. Markets shift, your product evolves, and the companies that fit your ICP today might look different from the ones that fit it 18 months ago. Running this play quarterly keeps your scoring model current and catches drift before it shows up in pipeline quality problems.

  • How is this different from the ICP Score and Route Skill?

    The ICP Score and Route Skill takes an ICP you’ve already defined and scores new leads against it. This play builds the ICP in the first place — from your actual closed-won data rather than from criteria you set manually. Run this play first to build the ICP definition, then use the ICP Score and Route Skill to apply it at scale to every new lead and account that comes in.

  • Can I use this for a specific segment, not my full customer base?

    Yes — and it’s often more useful that way. If you sell into multiple verticals or segments, run the prompt separately for each one. An ICP built from your FinTech wins will look different from one built from your Healthcare wins, and mixing them produces a blended profile that fits neither segment precisely. Segment-specific ICPs give your reps a sharper filter for the territory they’re actually working.

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.