Systems Lab

Agent skill

icp-builder

dormantSelf-containedInstructions only2,477 words

Filed under Prospecting and list building.

From VijayMatt/go-to-market-agent-skills · 12 skills · 1 · pushed 2026-03-29

What it does when it runs

Read from the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about icp-builder

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/VijayMatt/go-to-market-agent-skills.git /tmp/go-to-market-agent-skills
git -C /tmp/go-to-market-agent-skills sparse-checkout set "icp-builder"
mkdir -p ~/.claude/skills/icp-builder
cp -R "/tmp/go-to-market-agent-skills/icp-builder/." ~/.claude/skills/icp-builder/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from VijayMatt/go-to-market-agent-skills/blob/c948db28e7a0147976cc91ad91479900a75f7904/icp-builder/SKILL.md, which is licensed MIT (repository). 2,477 words, 32 headings.

ICP Builder: Complete Methodology

The Core Principle

Your Ideal Customer Profile is not a persona slide deck that collects dust. It's an operational filter that every team uses daily — marketing uses it to target ads, SDRs use it to prioritize accounts, AEs use it to qualify deals, and CS uses it to predict churn. If your ICP is vague ("mid-market SaaS companies"), it's useless. A good ICP is specific enough that two people could independently look at the same company and agree on whether it qualifies.


The 4-Layer ICP Framework

Most ICPs stop at firmographics (industry + company size). That's layer 1 of 4. To build an ICP that actually predicts closed-won deals, you need all four layers.

Layer 1: Firmographic (Who they are)

These are the observable, static characteristics of the company.

DimensionExample CriteriaWhy It Matters
Industry / verticalSaaS, FinTech, Healthcare ITYour product may solve different problems by vertical
Company size (employees)50-500 employeesDetermines buying process complexity
Revenue range$5M-$100M ARRIndicates budget and sophistication
GeographyUS, UK, India, DACH regionAffects compliance, language, sales motion
Growth stageSeries A-C, post-PMFDetermines urgency and budget availability
Organizational structureCentralized vs. distributedAffects buying committee composition
Business modelB2B, B2C, marketplace, SaaSDetermines which pain points resonate

How to extract from closed-won data: Export your last 12 months of closed-won deals from your CRM. For each deal, capture these dimensions. Look for clusters — if 70% of your wins are Series B SaaS companies with 100-300 employees, that's your firmographic sweet spot.

Layer 2: Technographic (What they use)

The tools a company uses tell you more about their sophistication, budget, and pain points than their industry does.

DimensionExample CriteriaWhy It Matters
Core platformSalesforce vs. HubSpot vs. no CRMIndicates maturity and integration needs
Complementary toolsUses Snowflake + dbt + LookerSignals data sophistication
Competitor presenceCurrently uses [competitor X]Indicates awareness of the category
Tool gapsHas Salesforce but no enrichment toolSignals a problem you can solve
Integration ecosystemHeavy API usage, Zapier, custom integrationsIndicates technical sophistication
Build vs. buy tendencyIn-house engineering team builds custom toolsAffects competitive positioning

How to extract from closed-won data: Use BuiltWith or your CRM's tech stack fields to profile your closed-won accounts. Look for common tools. If 80% of your customers use Salesforce, that's a technographic filter. If none of your customers have an in-house data team, "has in-house data team" might be a disqualifier.

Layer 3: Behavioral (What they do)

These are observable actions that indicate engagement, interest, or operational maturity.

DimensionExample CriteriaWhy It Matters
Content engagementDownloaded whitepaper, attended webinarShows awareness of the problem
Website behaviorVisited pricing page 3+ timesIndicates active evaluation
Community participationActive in Slack communities, Reddit, forumsSignals they're seeking solutions
Event attendanceAttended industry conferencesIndicates budget and engagement
Inbound inquiry historyPreviously requested a demoPrior interest, even if they didn't buy
Referral sourceCame through partner or customer referralHighest-quality behavioral signal

How to extract from closed-won data: Pull marketing attribution data for closed-won deals. What content did they engage with? How many touches before they booked a demo? What was the referral source? Look for patterns in the buyer journey, not just the company profile.

Layer 4: Intent / Trigger (When they're ready)

These are time-sensitive signals that indicate a company is actively looking to buy — not just a fit, but a fit right now.

DimensionExample CriteriaWhy It Matters
Hiring specific rolesPosting for RevOps, Data EngineerIndicates investment in the area
Funding eventRaised Series B in last 90 daysBudget unlocked
Leadership changeNew CRO in last 60 daysStrategic re-evaluation
Contract expirationCompetitor contract renews in Q4Window to displace
Regulatory changeNew compliance requirementCreates urgency
Pain eventPublic outage, data breach, audit failureImmediate need

How to extract from closed-won data: For your last 20 closed-won deals, interview the AE or review the CRM notes. Ask: "What happened at this account that made them start looking?" You'll find 3-5 common triggers. These become your intent layer.


Reverse-Engineering ICP from Closed-Won Deals

Step 1: Export and Clean

Export your last 12-18 months of closed-won deals. Minimum 20 deals for statistical relevance, ideally 50+.

For each deal, capture:

  • Company name
  • Industry
  • Employee count
  • Revenue (estimated if not known)
  • Geography
  • Deal size (ACV)
  • Sales cycle length
  • Lead source
  • Champion title
  • Economic buyer title
  • Key technologies used
  • Trigger event (what made them start looking)
  • Competitive situation (who else they evaluated)

Step 2: Segment by Deal Quality

Not all closed-won deals are equal. Segment into:

  • A-deals (top 20%): Highest ACV, fastest sales cycle, lowest churn, best expansion revenue
  • B-deals (middle 60%): Solid deals, average metrics
  • C-deals (bottom 20%): Low ACV, long sales cycle, high churn risk, heavy support burden

Your ICP should be built from A-deals only. B-deals are acceptable targets. C-deals are accounts you should stop pursuing — they cost more to acquire and serve than they're worth.

Step 3: Find Patterns

For your A-deals, answer these questions:

Firmographic patterns:

  • What industries appear most often?
  • What's the employee count range? (Look for the cluster, not the outliers)
  • What's the revenue range?
  • What growth stage?
  • What geography?

Technographic patterns:

  • What CRM do they use?
  • What other tools do they have?
  • Do they use any competitor products?
  • What's their technical sophistication?

Behavioral patterns:

  • How did they find you? (Referral, inbound, outbound, event?)
  • What content did they engage with before buying?
  • How many stakeholders were involved?
  • What was the average sales cycle?

Intent/trigger patterns:

  • What event triggered the purchase?
  • Was there a new hire, funding round, or competitive displacement?
  • Was there a regulatory or compliance driver?

Step 4: Define Your ICP Statement

Write a one-paragraph ICP statement that combines all four layers:

Template:

Our ideal customer is a [growth stage] [industry] company with [employee range] employees and [revenue range] in annual revenue, headquartered in [geography]. They use [core technologies] and [do/don't] have [specific capability]. They are typically triggered to buy by [trigger events] and the buying process involves [champion title] and [economic buyer title] over a [timeline] sales cycle. Our average ACV with these accounts is [amount].

Worked example:

Our ideal customer is a Series A-C B2B SaaS company with 100-500 employees and $10M-$80M in ARR, headquartered in the US. They use Salesforce as their CRM and have at least one dedicated RevOps person but haven't yet built a data engineering team. They are typically triggered to buy when they hire a new VP of Sales or CRO and realize they don't have pipeline visibility. The buying process involves the RevOps Manager (champion) and VP of Sales (economic buyer) over a 30-45 day sales cycle. Our average ACV is $36K.


Building the Lead Scoring Model

Point-Based Scoring System

Assign points for each ICP dimension. Total points determine the lead tier.

Scoring principles:

  1. Intent signals score highest (they indicate timing)
  2. Firmographic fit scores second (right company type)
  3. Technographic fit scores third (right tech environment)
  4. Behavioral signals add bonus points
  5. Negative signals subtract points (disqualification)

Score Architecture

Maximum possible score: 100 points

CategoryMax PointsWeight
Firmographic fit3030%
Technographic fit2020%
Behavioral signals2020%
Intent signals3030%

Firmographic Scoring (30 points max)

DimensionCriteriaPoints
IndustryExact ICP industry match10
IndustryAdjacent industry5
IndustryNon-ICP industry0
Company sizeSweet spot (e.g., 100-500)10
Company sizeAcceptable range (e.g., 50-100 or 500-1000)5
Company sizeOutside range0
RevenueSweet spot range5
RevenueAdjacent range2
GeographyTarget geography5
GeographySecondary geography2

Technographic Scoring (20 points max)

DimensionCriteriaPoints
Core platform matchUses target platform (e.g., Salesforce)8
Complementary toolsUses tools that integrate with you5
Competitor presenceUses a direct competitor4
Tech sophisticationRight level (not too basic, not too advanced)3

Behavioral Scoring (20 points max)

DimensionCriteriaPoints
Website visit (pricing page)In last 30 days8
Content downloadIn last 30 days4
Webinar/event attendanceIn last 60 days4
Referred by customerAny time10
Replied to outreachIn last 90 days6
Opened 3+ emailsIn last 30 days2

Intent Scoring (30 points max)

DimensionCriteriaPoints
Requested demoIn last 14 days15
Relevant job postingIn last 30 days8
Funding roundIn last 60 days8
Leadership changeIn last 60 days7
Competitor contract expiringIn next 90 days10
Third-party intent dataBombora/6sense surge6

Lead Tiers

TierScoreActionOwner
A-lead70-100Immediate outreach, multi-channelAE or senior SDR
B-lead50-69Priority outreach sequenceSDR
C-lead30-49Nurture sequence + monitor for signalsMarketing automation
D-lead0-29Do not pursueNone — recycle or disqualify

Negative Scoring (Disqualification Signals)

These signals subtract points or automatically disqualify a lead, regardless of positive score.

Hard Disqualifiers (auto-DQ, score = 0)

  • Too small: Below minimum viable company size (e.g., <10 employees for enterprise product)
  • Wrong business model: B2C company for a B2B-only product
  • Non-target geography: Country where you can't legally sell or support
  • Already a customer: They're in your CRM as active
  • Competitor employee: They work for a direct competitor
  • Student/consultant: Individual using a business email for personal research
  • Bankrupt/shutting down: Company is winding down operations

Soft Disqualifiers (point deductions)

SignalDeductionRationale
Previous closed-lost (last 6 months)-15Recently evaluated and rejected
No budget authority in org-10Will stall at procurement
Heavy "build" culture-10Will try to build instead of buy
Extreme regulatory environment-5Long sales cycles, heavy compliance
Multiple incumbents already-5Hard to displace entrenched tools
Previous no-show on demo-8Low intent signal

ICP Validation

Your ICP is a hypothesis until you test it. Here's how to validate.

Test 1: Blind Sort (Internal)

Give 5 salespeople a list of 50 accounts (mix of ICP and non-ICP) without labels. Ask them to rank by "likelihood to close." Compare their rankings to your ICP scoring. If they align >70%, your ICP reflects reality. If they diverge, interview the reps to understand what they're seeing that your model isn't capturing.

Test 2: Win/Loss Correlation

Score your last 50 closed-won deals and your last 50 closed-lost deals using your new model. If the model works, closed-won deals should score significantly higher on average. If there's no meaningful difference, your scoring dimensions are wrong.

Expected results:

  • Closed-won average score: 65-80
  • Closed-lost average score: 30-45
  • If the gap is <15 points, revisit your scoring weights

Test 3: Outbound Campaign Split

Run two outbound campaigns simultaneously:

  • Campaign A: ICP-scored accounts (top tier only)
  • Campaign B: Random accounts from your TAM

Compare reply rates, meeting rates, and pipeline generated. ICP-scored accounts should outperform by at least 2x on meeting rates.

Test 4: Quarterly Review

Every quarter, re-run the closed-won analysis. Your ICP should evolve as:

  • You enter new markets or segments
  • Your product adds capabilities
  • Market conditions change
  • You accumulate more closed-won data

Anti-Patterns

1. ICP by committee. Building your ICP in a workshop where everyone adds their pet criteria until it describes every company on earth. Build it from data first, then validate with the team.

2. Aspirational ICP. Defining your ICP as the accounts you wish you could sell to (Fortune 500) instead of the accounts you actually close (mid-market). Your ICP should reflect reality, not ambition.

3. Single-dimension ICP. "Our ICP is SaaS companies with 100-500 employees." That's one layer. Without technographic, behavioral, and intent layers, you're still spraying and praying — just at a slightly smaller list.

4. Static ICP. Building the ICP once and never updating it. Your ICP should be a living document reviewed quarterly.

5. Scoring without calibration. Assigning point values based on gut feel and never validating against outcomes. If your A-leads close at the same rate as C-leads, your scoring is broken.

6. Ignoring negative signals. Only scoring positive attributes and wondering why some high-scoring accounts never close. The disqualification layer is just as important.


Output Format

When building an ICP, produce two deliverables:

Deliverable 1: ICP Document

A structured document covering all four layers with specific criteria, the ICP statement paragraph, and the rationale behind each dimension. Use the template in references/icp-template.md.

Deliverable 2: Scoring Rubric

A point-based scoring model with specific criteria for each dimension, tier definitions, and disqualification rules. Use the template in references/scoring-model.md.

Both documents should be reviewed and validated quarterly using the validation tests above.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what icp-builder does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.