AgentSkillsCN

icp-development

全面构建深度契合用户心理的理想客户画像(ICP)的方法论。包含痛点挖掘、需求画像绘制、用户认知层次评估,以及推动用户转变的叙事框架。 适用场景: - 构建或优化客户画像 - 分析客户调研数据 - 绘制客户认知层次图谱 - 编写用户旅程文档 - 为以转化为核心的优质内容创作做好准备 - 当用户提及“ICP”“人物角色”“目标受众”“客户心理”时 提供内容:ICP 构建的框架、模板与质量标准

SKILL.md
--- frontmatter
name: icp-development
description: |
  Comprehensive methodology for building psychologically deep Ideal Customer Profiles. Includes frameworks for pain point excavation, desire mapping, awareness level assessment, and transformation narratives.
  
  USE THIS SKILL WHEN:
  - Building or refining customer profiles
  - Analyzing customer research data
  - Mapping customer awareness levels
  - Creating user journey documentation
  - Preparing for conversion-focused content creation
  - User mentions "ICP", "persona", "target audience", "customer psychology"
  
  PROVIDES: Frameworks, templates, and quality standards for ICP creation
allowed-tools: Read, Grep, Glob

ICP Development Skill

Overview

An Ideal Customer Profile is not a demographic description—it's a psychological portrait. This skill provides the frameworks and methodologies for building ICPs that drive conversion, not just categorization.

The ICP Development Framework

Why Most ICPs Fail

Generic ICP (Useless):

code
"Sarah, 34, Marketing Manager, $85k income, urban, interested in productivity tools"

Psychological ICP (Actionable):

code
"The Overwhelmed Operator"
- Manages a team of 5 but does the work of 10
- Has tried 4 productivity tools in the past year, all abandoned
- Feels guilty about missed deadlines but also resentful of workload
- Core fear: Being exposed as someone who "can't handle it"
- Core desire: To feel in control for the first time in years
- Buying trigger: A particularly bad week that makes them say "something has to change"

The second ICP gives you copy angles. The first gives you nothing.


Core Frameworks

Framework 1: The Awareness Spectrum (Schwartz)

Eugene Schwartz's 5 Levels of Awareness determines HOW you talk to someone, not just what you say.

code
┌─────────────────────────────────────────────────────────────────┐
│                    THE AWARENESS SPECTRUM                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  UNAWARE ──► PROBLEM ──► SOLUTION ──► PRODUCT ──► MOST         │
│              AWARE       AWARE        AWARE       AWARE         │
│                                                                  │
│  "What       "I have     "Solutions   "Your       "Give me     │
│   problem?"   a problem"  exist"       product"    the deal"    │
│                                                                  │
├─────────────────────────────────────────────────────────────────┤
│  CONTENT STRATEGY BY LEVEL:                                      │
│                                                                  │
│  Unaware:     Educate about the problem (articles, stories)     │
│  Problem:     Agitate & introduce solutions (guides, videos)     │
│  Solution:    Differentiate your approach (comparison, proof)    │
│  Product:     Overcome objections (testimonials, guarantees)     │
│  Most Aware:  Make the offer (deals, urgency, friction removal)  │
└─────────────────────────────────────────────────────────────────┘

Assessment Questions:

  • Do they know they have a problem?
  • Have they actively sought solutions?
  • Do they know your product category exists?
  • Have they heard of you specifically?
  • Have they already decided to buy from you?

Critical Insight: Most marketing talks to the MOST AWARE audience (deals, features) while most prospects are PROBLEM or SOLUTION AWARE. This mismatch kills conversion.

Framework 2: Pain Point Archaeology

Surface pains are symptoms. Root pains are causes. Emotional pains are conversion triggers.

code
THE PAIN EXCAVATION MODEL

                 ┌─────────────────┐
                 │  SURFACE PAIN   │  ← What they SAY
                 │  "I need better │
                 │   software"     │
                 └────────┬────────┘
                          │
                          ▼
                 ┌─────────────────┐
                 │   ROOT PAIN     │  ← The actual PROBLEM
                 │  "I waste 2hrs/ │
                 │   day on manual │
                 │   processes"    │
                 └────────┬────────┘
                          │
                          ▼
                 ┌─────────────────┐
                 │ EMOTIONAL PAIN  │  ← The FEELING (this sells)
                 │  "I feel like   │
                 │   I'm falling   │
                 │   behind"       │
                 └────────┬────────┘
                          │
                          ▼
                 ┌─────────────────┐
                 │  IDENTITY PAIN  │  ← The THREAT (deepest)
                 │  "I'm not the   │
                 │   professional  │
                 │   I should be"  │
                 └─────────────────┘

Excavation Questions:

  • What's the symptom? (Surface)
  • What causes that? (Root)
  • How does that make them feel? (Emotional)
  • What does that say about them? (Identity)

Framework 3: Desire Mapping

Desires have layers too. Map all three for complete messaging ammunition.

code
THE DESIRE HIERARCHY

┌─────────────────────────────────────────────────────────────────┐
│                                                                  │
│    FUNCTIONAL DESIRE                                             │
│    ─────────────────                                             │
│    "I want to automate my invoicing"                             │
│    → Feature-level, easy to articulate                          │
│    → Addresses the ROOT pain                                     │
│                                                                  │
│                         ▼                                        │
│                                                                  │
│    EMOTIONAL DESIRE                                              │
│    ────────────────                                              │
│    "I want to feel in control of my business"                    │
│    → Feeling-level, sometimes unspoken                          │
│    → Addresses the EMOTIONAL pain                                │
│                                                                  │
│                         ▼                                        │
│                                                                  │
│    IDENTITY DESIRE                                               │
│    ───────────────                                               │
│    "I want to be a real business owner, not just self-employed" │
│    → Self-concept, often unconscious                            │
│    → Addresses the IDENTITY pain                                │
│    → THIS IS THE TRANSFORMATION THEY'RE BUYING                   │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Mapping Questions:

  • What specific outcome do they want? (Functional)
  • How do they want to feel when they have it? (Emotional)
  • Who do they want to become? (Identity)

Framework 4: Objection Taxonomy

Every objection has a root. Counter the root, not the surface.

code
OBJECTION CATEGORIES AND ROOTS

┌──────────────┬────────────────────────────┬──────────────────────┐
│ CATEGORY     │ SURFACE OBJECTION          │ ROOT FEAR            │
├──────────────┼────────────────────────────┼──────────────────────┤
│ PRICE        │ "It's too expensive"       │ "I'll waste money"   │
│              │ "I can't afford it"        │ "This won't work"    │
├──────────────┼────────────────────────────┼──────────────────────┤
│ TIME         │ "I don't have time"        │ "I'll fail to        │
│              │ "Too complicated"          │  implement properly" │
├──────────────┼────────────────────────────┼──────────────────────┤
│ TRUST        │ "How do I know it works?"  │ "I've been burned    │
│              │ "Sounds too good"          │  before"             │
├──────────────┼────────────────────────────┼──────────────────────┤
│ TIMING       │ "Not right now"            │ "I'm not ready to    │
│              │ "Maybe next quarter"       │  commit to change"   │
├──────────────┼────────────────────────────┼──────────────────────┤
│ AUTHORITY    │ "Need to check with..."    │ "I can't decide      │
│              │ "Have to get approval"     │  alone"              │
├──────────────┼────────────────────────────┼──────────────────────┤
│ FIT          │ "Is this for me?"          │ "I'll look foolish   │
│              │ "I'm not sure I'm ready"   │  if I don't belong"  │
└──────────────┴────────────────────────────┴──────────────────────┘

For each objection, document:

  1. The stated objection (what they say)
  2. The root fear (what they mean)
  3. The counter-argument (how to address)
  4. The proof needed (what would convince them)

Framework 5: The Transformation Narrative

People don't buy products. They buy the transformation from BEFORE to AFTER.

code
THE TRANSFORMATION ARC

    BEFORE                                    AFTER
    ──────                                    ─────
    
    ┌──────────────┐                    ┌──────────────┐
    │ EXTERNAL     │                    │ EXTERNAL     │
    │ What's       │                    │ What's       │
    │ happening    │                    │ happening    │
    │ around them  │                    │ around them  │
    └──────────────┘                    └──────────────┘
           │                                   ▲
           │        ┌──────────────────┐       │
           │        │                  │       │
           └───────►│   YOUR PRODUCT   │───────┘
                    │   IS THE BRIDGE  │
           ┌───────►│                  │───────┐
           │        └──────────────────┘       │
           │                                   ▼
    ┌──────────────┐                    ┌──────────────┐
    │ INTERNAL     │                    │ INTERNAL     │
    │ What they    │                    │ What they    │
    │ feel         │                    │ feel         │
    │              │                    │              │
    └──────────────┘                    └──────────────┘

Document both dimensions:

DimensionBEFORE StateAFTER State
External SituationWhat's happeningWhat changes
Internal FeelingHow they feelHow they feel
Daily ExperienceWhat's hardWhat's easy
Self-PerceptionWho they think they areWho they become

Research Methods

Method 1: Review Mining

Extract customer voice from reviews (yours or competitors').

Where to mine:

  • G2, Capterra, TrustRadius (B2B)
  • Amazon, Yelp, Google Reviews (B2C)
  • Reddit, Quora, industry forums
  • Facebook Groups, LinkedIn discussions
  • App store reviews

What to extract:

markdown
REVIEW MINING TEMPLATE

Source: [Platform, competitor name if applicable]
Sample size: [# of reviews analyzed]
Date range: [Review dates]

PAIN EXPRESSIONS (verbatim):
- "[Quote]" [Rating, context]
- "[Quote]" [Rating, context]

DESIRE EXPRESSIONS (verbatim):
- "[Quote]" [Rating, context]
- "[Quote]" [Rating, context]

OBJECTION EXPRESSIONS (verbatim):
- "[Quote]" [Rating, context]

TRANSFORMATION LANGUAGE (verbatim):
- "[Quote]" [Rating, context]

PATTERNS OBSERVED:
- [Theme]: Mentioned [X] times
- [Theme]: Mentioned [X] times

Method 2: Interview Synthesis

If customer interviews are available:

markdown
INTERVIEW SYNTHESIS TEMPLATE

Interview: [ID/Name]
Date: [Date]
Duration: [Length]
Customer type: [Segment]

KEY QUOTES:
Pain: "[Quote]" [Timestamp]
Desire: "[Quote]" [Timestamp]
Objection: "[Quote]" [Timestamp]
Trigger: "[Quote]" [Timestamp]

JOURNEY INSIGHTS:
- How they found us: [Quote/Summary]
- Decision process: [Quote/Summary]
- Key moment: [Quote/Summary]

UNMET NEEDS:
- [What they wish existed]

Method 3: Survey Analysis

If survey data is available:

markdown
SURVEY ANALYSIS TEMPLATE

Survey: [Name/Purpose]
Sample size: [n=]
Date range: [Dates]
Response rate: [%]

QUANTITATIVE FINDINGS:
- [Metric]: [Value] ([n=])
- [Metric]: [Value] ([n=])

QUALITATIVE THEMES (from open-ended):
- Theme 1: [X mentions]
  - Representative quote: "[Quote]"
- Theme 2: [X mentions]
  - Representative quote: "[Quote]"

CROSS-TABULATIONS OF NOTE:
- [Segment] + [Response pattern]

Quality Standards

The "Coffee Test"

A good ICP should pass the "coffee test":

"Could I sit across from this person at a coffee shop and recognize them? Could I predict what they'd order? What they'd complain about? What would make them light up?"

If your ICP is too abstract to pass this test, it needs more depth.

The "Messaging Test"

For each ICP, you should be able to write:

  • A headline that would stop them scrolling
  • An opening line that would make them nod
  • An objection that would make them hesitate
  • A proof point that would convince them

If you can't do this, the ICP lacks actionable specificity.

The "Differentiation Test"

Your ICPs should be distinct enough that:

  • Different content would resonate with each
  • Different objections would arise from each
  • Different transformation narratives would apply

If all your ICPs would respond to the same messaging, you probably have one ICP, not three.


Common Pitfalls

Pitfall 1: Demographic Obsession

Wrong: Spending 80% of the ICP on age, income, location Right: Demographics only when behaviorally relevant ("household income matters because our product is $500/month")

Pitfall 2: Persona Theater

Wrong: "Meet Sarah, she loves yoga and drives a Prius" Right: Psychological traits with evidence, not lifestyle guesses

Pitfall 3: Single-Source Syndrome

Wrong: Building entire ICP from one interview or assumption Right: Triangulating from multiple sources, noting confidence levels

Pitfall 4: Confirmation Bias

Wrong: Looking for evidence that supports your assumptions Right: Looking for evidence that challenges your assumptions

Pitfall 5: Static ICPs

Wrong: Building ICP once and never updating Right: Treating ICP as living document, updated with new research


ICP-to-Copy Translation

The ICP should directly inform copy decisions:

ICP ElementCopy Application
Awareness LevelDetermines headline approach
Pain PointsHeadlines, opening lines, agitation
DesiresBenefits, transformation promises
ObjectionsFAQ, guarantee language, social proof
Buying TriggersCTAs, urgency messaging
TransformationCase studies, testimonial selection
Voice of CustomerExact phrases to use in copy

Quick Translation Formula

code
HEADLINE = [Pain/Desire] + [Awareness-appropriate promise]

UNAWARE:     "Why Your Back Hurts After Sitting" (educate)
PROBLEM:     "Finally, a Fix for Chronic Back Pain" (introduce)
SOLUTION:    "The Chair That Eliminated My Back Pain" (differentiate)
PRODUCT:     "Join 10,000+ Happy Backs" (prove)
MOST AWARE:  "Get 20% Off This Week" (offer)

References

For additional frameworks and examples, see:

  • references/awareness-messaging-examples.md - Copy examples by awareness level
  • references/objection-counters.md - Common objection counter-argument templates
  • references/transformation-examples.md - Before/after narrative examples