icp-builder

name	icp-builder
aliases	["icp-builder"]
description	Build, validate, or expand a client's ICP (Ideal Customer Profile) using the GAP method, SPICED framework, and customer interview pipeline. Triggers on 'build their ICP,' 'check their ICP,' 'ICP validation,' 'ICP quality,' 'they don't have an ICP,' 'ICP is too broad,' 'who should they sell to,' 'segment their market,' 'ICP workshop,' 'customer interviews for ICP,' 'GAP method,' 'ICP expansion,' 'Goldilocks zone,' 'tier their customers,' 'A/B/C segmentation,' 'are they targeting the right customers,' 'segmentation check,' 'ICP review,' 'who are they actually selling to,' or any client engagement where the ICP is missing, broken, or needs validation. This skill covers the full ICP lifecycle: validate what exists, build from scratch, refine with interviews, and plan expansion. BOUNDARY: For positioning/messaging (step AFTER ICP), see positioning-messaging-designer.
status	stable

ICP Builder: Validate, Build & Expand

You are helping work with a client's ICP. This is one of the highest-leverage activities in a revenue engagement : when the ICP is wrong, everything downstream (positioning, messaging, territory design, pipeline quality, CS segmentation) breaks.

Your role is to guide the process, not lecture the client. You structure the work, prepare the materials, and synthesize the outputs.

---

Mode Selection

Every ICP engagement starts with the same question: does the client already have an ICP?

• If YES → Start with Mode 1: Validate to assess what they have. The validation tells you whether they need refinements or a full rebuild.
• If NO → Go straight to Mode 2: Build : there's nothing to validate.
• If MATURE + SATURATING → Use Mode 3: Expand : the ICP works but the market is tapped out.

If an ICP definition, call notes, or transcript where a client describes their customers is shared, default to Mode 1 first.

---

Mode 1: Validate an Existing ICP

This is a quality check : take the client's existing ICP as input and produce a gap assessment with specific recommendations.

Input

Accept any combination of: client's ICP document, verbal description from call notes, transcript, CRM deal distribution data, win/loss data, or notes from a diagnostic.

If the client has no ICP at all, flag this immediately : that's the finding. Recommend Mode 2.

The Seven-Dimension Validation Framework

Score the client's ICP across seven dimensions. Each gets a rating: Strong / Adequate / Weak / Missing.

Dimension 1: Specificity - Named firmographic criteria: industry, size by revenue and headcount, geography, tech stack, growth stage. Not "mid-market SaaS companies" but "B2B SaaS, EUR10-50M ARR, 100-500 employees, post-Series B, EU-based, using HubSpot or Salesforce." Red flags: "We sell to everyone," only one firmographic dimension, criteria describing 50,000+ companies.

Dimension 2: Pain Clarity - Specific problems in customer language, not vendor language. External problems (business issues), internal problems (how it feels), philosophical problems (why it feels wrong). Mapped by persona. Red flag: pain described as "they need better visibility" instead of "I can't answer simple revenue questions without pulling three spreadsheets." Reference: references/persona-dmu.md for benchmark pain language.

Dimension 3: Buying Signals & Timing : Clear triggers that indicate a company is in-market NOW (new CRO hired, missed target, board pressure, CRM migration planned). Red flag: no distinction between in-market and total addressable.

Dimension 4: Customer Count & Evidence Base : ICP built on evidence, not theory. You need at least 8 comparable great customers before claiming a real ICP. Thresholds:

• Below 8 customers: Early Customer Profile (ECP), hypothesis only
• 8-30: Real ICP emerging, motion-specific confidence varies
• 30-50: Patterns validatable across segments
• 50+: High-confidence, scalable ICP Red flag: ICP defined in a strategy offsite without customer input, never validated against win/loss data.

Dimension 5: Segmentation & Motions : ICP broken into segments with different GTM motions, buying processes, DMUs, value props, and success metrics. Red flag: one definition for radically different customer types, same sales motion for EUR5K and EUR50K deals.

Dimension 6: CRM Operationalisation : ICP criteria exist as filterable, reportable CRM fields. Lead scoring reflects ICP fit. Pipeline reports filterable by segment. Red flag: ICP lives in a slide deck but not in the CRM.

Dimension 7: Feedback Loop : ICP treated as living document with quarterly review cadence. Win/loss analysis by segment feeds back. CS health data informs definition. Red flag: defined once, never revisited.

Validation Output

Produce:

1. Summary Score Table : All seven dimensions with rating and one-sentence finding.

2. The One Constraint : The single dimension that, if fixed first, unlocks the most downstream value. Connect to the revenue system: a broken ICP sits at the centre of the customer value loops.

3. Three Recommendations : Maximum three, in priority order. Each: what to do, why it matters, how long it takes, who owns it.

4. Probing Questions : 3-5 questions that can be used in the next conversation to dig deeper on the weakest dimensions. Truth-revealing, not leading.

5. Mode Recommendation : Based on the validation: "Refinements sufficient" (tweak what exists) or "Full rebuild recommended" (proceed to Mode 2).

---

Mode 2: Build an ICP from Scratch

Step 0: Assess ICP Maturity

Before building, determine where the client stands using customer count thresholds:

Motion Type	Customers Needed for Real ICP	Confidence
No Touch / Product-Led	~160	95%
Low Touch / 1-Stage	~80	90%
Medium Touch / 2-Stage	~40	85%
High Touch / Field Sales	~27	80%
Dedicated / Named Accounts	~20	75%

Below threshold = Early Customer Profile (ECP), not ICP. Be honest: "You have directional signals, not a production-grade ICP. We can build toward one, but the output will need quarterly iteration."

At or above threshold = real ICP territory. Enough data to identify repeatable patterns.

For the full maturity framework, read references/icp-building-reference.md Sections 1-2. For AI-native techniques, see Section 4.5.

Step 1: Gather Data (GAP Phase G)

Collect from four sources:

CRM Data : Deal history (won + lost), ACV, LTV, cycle length, churn, expansion. Pull the numbers, don't trust narratives. Messy CRM data = flag for data governance (cross-reference: revops-data-governance).

Market Data : Industry benchmarks, competitive landscape, TAM/SAM sizing. Use current GTM benchmarks for your context when sizing TAM or benchmarking.

Enrichment Data : Firmographic, technographic, intent signals. Help identify what they have vs. need.

Conversation Data : Customer interviews (the gold), sales recordings, support tickets, win/loss reviews. If none exist, move to Step 3 (Interview Pipeline).

For detailed collection guidance, read references/icp-building-reference.md Section 3 (Phase G).

Step 2: Analyse Patterns (GAP Phase A)

Analyse across 8 dimensions: Industry/Vertical, Company Size, Tech Stack, Revenue Model, SPICED Patterns, Product Usage, Enrichment Signals, Pipeline Behaviour.

Key outputs: pattern map (what predicts success), segment clusters (micro-ICPs forming), confidence scores, data gaps.

For the full framework, read references/icp-building-reference.md Section 3 (Phase A).

Step 3: Customer Interview Pipeline (If Needed)

When conversation data is missing or shallow, run the 7-step pipeline:

1. Select : 10-20 best customers (high-value + high-retention, not just biggest)
2. Prepare : CRM data, account overviews, SPICED interview playbook
3. Interview : 30-45 min structured using 8 SPICED steps
4. Extract Testimonials : "Describe working with us in one sentence"
5. Extract Quotes : Run transcript through LLM for 5-10 most quotable lines
6. Build Case Studies : Problem-focused 1-2 pagers (with consent)
7. Feed Back : Add language to SPICED library, update personas, sharpen positioning

For the complete interview guide, read references/icp-building-reference.md Section 5.

Pain language enrichment: Reference your own collection of raw customer pain quotes.

Step 4: Profile (GAP Phase P)

Synthesize into 4 deliverables:

Output 1: ICP Definition : Firmographic + technographic + behavioural criteria. Include exclusions (who is NOT ICP). Specific enough for a rep to say "yes" or "no" in 30 seconds.

Output 2: SPICED Tiers : A/B/C segmentation:

• T1 (Perfect Fit): All ICP criteria, high SPICED match. Win rate target: 60-80%.
• T2 (Good Fit): 70% of criteria. Win rate target: 30-50%.
• T3 (Opportunistic): 40-70%. Win rate target: 10-30%. Don't chase.

Output 3: Buyer Personas : Role-level profiles with goals, pains, decision criteria, buying committee, proof needed. Tied to SPICED.

Output 4: Informational Needs per Buying Phase : Content/proof needed at Awareness, Consideration, Decision, Onboarding.

For detailed templates, read references/icp-building-reference.md Section 3 (Phase P). For existing SPICED language patterns, read references/spiced-icp-library-v1.md.

Step 5: Goldilocks Zone Check

Before finalizing, validate ICP size matches client's stage:

• ACV sustainable with sales model? (>=20K for Medium Touch; >=50K for High Touch)
• Deals closing in 2-4 months? (6+ months = ICP too big for stage)
• 5+ reference customers? (Fewer = ICP too new for scale)
• Cost-to-serve proportional to ACV? (>30% = ICP too small)
• 100+ addressable targets? (Fewer = TAM too small)

For the full Goldilocks framework, read references/icp-building-reference.md Section 7.

---

Mode 3: Expand an Existing ICP

Only relevant when the current ICP is mature and showing saturation signals. Four phases:

1. Seed : 1 ICP, 1 geo, 1 motion. Validate with 8-20 comparable customers.
2. Geo Expansion : Same ICP, new markets. Test if SPICED transfers.
3. New Verticals : Different industries. May need SPICED variants.
4. Tier-Up : Larger accounts. Shift from ICP to Ideal Account Profile (IAP).

Expansion triggers: Win rate plateaus, pipeline saturates, NRR signals expansion, competitive pressure, TAM exhaustion, product expansion.

For the full framework, read references/icp-building-reference.md Section 6.

---

Delivery Formats

Within a short diagnostic engagement (1-2 days): Quick validation (Mode 1) + gap identification. Flag whether full build needed.

Within a 90-Day Programme (full build): Complete GAP method over 2-3 weeks. Customer interviews weeks 2-4. Profile deliverables by week 6. Expansion if relevant.

Standalone ICP Workshop (half-day): Compressed : gather data in advance, analyse together, build initial profiles. Follow up with interview pipeline recommendation.

---

What Happens After ICP

ICP → Positioning → Messaging → Copy

Hand off to positioning-messaging-designer to translate ICP insights into positioning framework and messaging architecture. The SPICED language becomes the raw material for messaging.

---

Voice Rules

• System first, blame never : "your ICP isn't broken because someone failed; it's broken because nobody installed a feedback loop"
• Concrete over abstract : use specific examples of what good looks like
• British spelling
• Short, direct assessments : CROs don't have time for padding

---

Reference Files

File	When to read	What's inside
references/icp-building-reference.md	Always for Mode 2 : full methodology	GAP method, 8-dimension analysis, interview pipeline, expansion, Goldilocks zone, thresholds
references/spiced-icp-library-v1.md	When building SPICED tiers or need language examples	Canonical SPICED language for ICP clusters
references/persona-dmu.md	Mode 1 validation (pain clarity benchmark)	Full persona & DMU with Dreams/Problems/Headaches
references/brand-canvas.md	When connecting ICP to brand narrative	Brand Canvas (StoryBrand framework)

Related Skills

• revops-data-governance : CRM data quality often surfaces as a blocker during GAP Phase G
• gtm-planning : ICP tiers feed directly into territory design and capacity planning
• cs-operations : CS health data informs ICP feedback loops

Cross-References

• positioning-messaging-designer : The NEXT skill: ICP → Positioning → Messaging
• sales-methodology : Discovery calls produce SPICED data that feeds ICP work

Built by Neon Triforce