ideal-customer-profile
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.
What this skill does
# 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 --- ### Further Reading - [5 GTM Principles You Should Know as a PM](https://www.productcompass.pm/p/5-gtm-principles-with-frameworks-templates) - [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.