ideal-customer-profile skill

by phuryn·phuryn/pm-skills·27k stars·MIT

Identify the Ideal Customer Profile (ICP) from research data with demographics, behaviors, JTBD, and needs. Use when defining your ICP, analyzing PMF survey data, or understanding who your best customers are.

A100/100content scan

Is the ideal-customer-profile skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the ideal-customer-profile skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-go-to-market/skills/ideal-customer-profile ~/.claude/skills/ideal-customer-profile

available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Ideal Customer Profile

Overview

Identify your Ideal Customer Profile (ICP) from research and survey data. This skill synthesizes customer research to define the customer most likely to find value, retain, and expand with your product.

When to Use

Defining ICP from product-market fit survey data
Targeting high-value customer segments
Analyzing customer success and expansion patterns
Prioritizing sales and marketing efforts
Evaluating new customer opportunities for fit
Refining target market definition

ICP Framework Components

Demographics

Who are they from a firmographic and personal perspective?

Company size (employees, revenue)
Industry or vertical
Geographic location
Job title and department
Years of experience in role
Education and background
Organizational structure and reporting

Behaviors

How do they work and make decisions?

How they discover and evaluate solutions
Buying process and decision-making timeline
Technical literacy and product adoption speed
Collaboration style (solo decision vs committee)
Change management and adoption style
Tool switching frequency
Community involvement and peer influence

Jobs to Be Done (JTBD)

What are they trying to accomplish?

Primary job/goal they're trying to achieve
Secondary jobs that support the primary job
Emotional jobs (how they want to feel)
Social jobs (status and perception)
Jobs they avoid or want to eliminate
Frequency and importance of each job
Success metrics for completing job

Needs and Pain Points

What problems does your product solve?

Specific pain points they experience
Current workarounds and limitations
Impact on productivity or outcomes
Cost or time burden of the problem
Emotional frustration levels
Barriers to solving the problem
Available budget to solve
Competing priorities

How It Works

Step 1: Gather Customer Data

Collect research about actual and potential customers:

Product-market fit survey responses
Customer interview transcripts
Trial or freemium user behavior data
Customer feedback and support tickets
Churn analysis and customer lifecycle data
Win/loss analysis from sales
Competitor customer analysis

Step 2: Segment by Value

Identify customer cohorts and their value:

Highest LTV (lifetime value) customers
Fastest time-to-value customers
Lowest churn rate customers
Highest expansion/upsell customers
Most enthusiastic/engaged customers
Best reference/case study potential
Most aligned with product vision

Step 3: Profile Demographics

Extract firmographic patterns:

Common company sizes (employee count, revenue)
Industry verticals and sub-verticals
Geographic concentrations
Typical department and reporting structure
Budget holders and budget available
Company stage (startup, growth, enterprise)
Company culture indicators

Step 4: Identify Behaviors

Map decision-making and adoption patterns:

How they discovered your product (channel)
Evaluation process and timeline
Key stakeholders in decision
Obstacles during sales process
Product adoption speed and breadth
Team involvement in onboarding
Frequency of feature usage
Support and service needs

Step 5: Define JTBD

Articulate what they're trying to accomplish:

Primary job/goal (functional job)
Emotional dimensions (how they want to feel)
Social dimensions (team and stakeholder impact)
Success metrics (how they measure success)
Context and constraints (when, where, with whom)
Competing jobs and priorities
Importance ranking of various jobs

Step 6: Document Pain Points and Needs

Synthesize specific problem areas:

Before state (current situation and frustrations)
Desired after state (ideal future state)
Gap size and impact quantification
Emotional dimensions of the problem
Resource constraints preventing solutions
Skepticism or hesitations
Success criteria for solution

Input Format

Use $ARGUMENTS to pass:

Research data (surveys, interviews, transcripts)
Customer success/metrics data
Product usage analytics
Sales activity and win/loss data
Existing customer database
Competitive intelligence

Output

A comprehensive ICP definition including:

Firmographic profile (company size, industry, location)
Behavioral profile (buying patterns, adoption style)
Complete JTBD mapping (functional, emotional, social jobs)
Top 5-7 pain points and specific needs
Quantified impact metrics (cost of problem, value of solution)
Decision-making process and key stakeholders
Typical customer journey and timeline
Go-to-market implications and messaging
Disqualification criteria (who is NOT a good fit)
High-value segment within ICP (ideal-of-the-ideal)

Framework

Based on Jobs to Be Done theory by Clayton Christensen and customer profiling methodology. Combines behavioral data with motivational insights to define actionable customer profiles.

Tips

Use quantitative and qualitative data together
Interview 10+ high-value customers for pattern identification
Look for non-obvious demographic patterns (outliers can be high-value)
Define both ideal ICP and acceptable secondary segments
Revisit ICP quarterly as you gather more customer data
Use ICP to evaluate all new sales opportunities
Share ICP across entire organization (marketing, sales, product)
Remember: ICP should drive focus, not exclude all others

More skills from phuryn/pm-skills

Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

All agent skills → · MCP servers