Startup Icp Definer

Startup ICP Definer - Ideal Customer Profile Builder

Overview

Help indie founders precisely define who they're building for using Hexa's Opportunity Memo methodology. Execute rigorous customer definition by guiding users through buying center mapping, pain point hierarchies, and validation frameworks.

Hexa's Core Principle: "Define the company type + the buying center people involved in the decision-making process."

When This Activates

• "Who is my customer"
• "Define my ICP"
• Target audience questions
• Customer personas
• "Everyone could use this"
• "Who should I target first"

The Framework: ICP Stack

┌─────────────────────────────────────────┐
│         BUYING CENTER                    │
│    (All people in the decision)          │
├─────────────────────────────────────────┤
│         USER PERSONA                     │
│    (Who uses it daily)                   │
├─────────────────────────────────────────┤
│         BUYER PERSONA                    │
│    (Who signs the check)                 │
├─────────────────────────────────────────┤
│         COMPANY PROFILE                  │
│    (The organization)                    │
└─────────────────────────────────────────┘

Build from bottom up: Company → Buyer → User → Buying Center.

Quick Workflow

Step 1: Company Profile

• Industry/vertical
• Company size (employees/revenue)
• Stage (startup, growth, enterprise)
• Geography
• Tech stack

Step 2: Buyer Persona

• Title/role, seniority
• Goals and KPIs
• Decision authority
• What they care about (cost, time, risk)

Step 3: User Persona

• Daily workflow
• Pain points
• Tech savviness

Step 4: Buying Center Map

• Champion, Economic Buyer, Technical Evaluator
• End User, Influencer, Blocker

Step 5: Pain Hierarchy

Score: Urgency + Cost + Frequency + Actively Solving Focus on pains scoring 8+

The 50-Company Test

Before finalizing ICP:

1. List 50 specific companies that fit 2. Find buyer's name at 20 of them 3. Reach out to 10

If you can't do this, your ICP isn't specific enough.

Too Broad Warning Signs

• Can't name 50 specific companies
• Can't find 10 people to interview
• Messaging must be vague to apply
• Sales conversations feel scattered

Integration

• idea-validator - Validate the problem
• market-sizer - Size the segment
• leads-researcher - Find matching companies
• offer-architect - Design offer for ICP
• outbound-optimizer - Write outreach

---

For complete persona canvases, buying center maps, interview questions, pain hierarchy scoring, fit scoring framework, and output templates, see: references/full-guide.md

Startup ICP Definer - Full Guide

The Framework: ICP Stack

┌─────────────────────────────────────────┐
│         BUYING CENTER                    │
│    (All people in the decision)          │
├─────────────────────────────────────────┤
│         USER PERSONA                     │
│    (Who uses it daily)                   │
├─────────────────────────────────────────┤
│         BUYER PERSONA                    │
│    (Who signs the check)                 │
├─────────────────────────────────────────┤
│         COMPANY PROFILE                  │
│    (The organization)                    │
└─────────────────────────────────────────┘

Build from bottom up. Define the company first, then the buyer, then the user, then the full buying center.

Detailed Execution Workflow

Step 1: Company Profile Definition

Ask the user:

What type of company is your ideal customer?

>

1. What industry or vertical?

2. What company size? (Employees or revenue)

3. What company stage? (Startup, growth, enterprise)

4. What geography?

5. What technology stack or tools do they use?

6. What business model? (B2B, B2C, marketplace)

Company Profile Template:

Example:

Industry: B2B SaaS companies
Size: 50-500 employees
Stage: Series A to Series C
Geography: US, UK, Western Europe
Tech Stack: Salesforce, HubSpot, Slack
Business Model: Recurring revenue software

Step 2: Problem Segmentation

Not all companies in your profile have the same pain intensity.

Ask the user:

What triggers a company to seek your solution?

>

1. What event creates urgency? (Growth, pain, mandate)

2. What symptoms indicate they need you?

3. What makes some companies better fits than others?

4. What situations make them NOT a fit?

Trigger Events:

Common B2B Triggers:

• Rapid headcount growth
• New executive hire
• Failed with competitor product
• Compliance/regulatory requirement
• Major customer demand
• Funding event (just raised)
• Manual process breaking down
• Integration with new tool

Step 3: Buyer Persona Definition

The buyer = the person who signs the check.

Ask the user:

Who is the buyer in your ICP?

>

1. What's their title/role?

2. What's their seniority level?

3. What are their goals and KPIs?

4. What are their frustrations?

5. What's their decision-making authority?

6. What do they care about most? (Cost, time, risk, outcomes)

Buyer Persona Canvas:

┌─────────────────────────────────────────────────┐
│ BUYER PERSONA: [Title]                          │
├─────────────────────────────────────────────────┤
│ Title: [Exact title]                            │
│ Reports to: [Boss's role]                       │
│ Team size: [X people]                           │
├─────────────────────────────────────────────────┤
│ Goals:                                          │
│ • [Goal 1]                                      │
│ • [Goal 2]                                      │
│ • [Goal 3]                                      │
├─────────────────────────────────────────────────┤
│ Frustrations:                                   │
│ • [Frustration 1]                               │
│ • [Frustration 2]                               │
│ • [Frustration 3]                               │
├─────────────────────────────────────────────────┤
│ Success Metrics:                                │
│ • [KPI 1]                                       │
│ • [KPI 2]                                       │
├─────────────────────────────────────────────────┤
│ Decision Authority: [Budget they can approve]   │
│ Decision Process: [How they buy]                │
└─────────────────────────────────────────────────┘

Step 4: User Persona Definition

The user = the person who uses it daily (may differ from buyer).

Ask the user:

Who actually uses your product day-to-day?

>

1. What's their title/role?

2. What's their daily workflow?

3. What tasks do they do that involve your product?

4. What frustrates them about current process?

5. What would make their day easier?

6. How tech-savvy are they?

User Persona Canvas:

┌─────────────────────────────────────────────────┐
│ USER PERSONA: [Title]                           │
├─────────────────────────────────────────────────┤
│ Title: [Exact title]                            │
│ Reports to: [Usually the buyer]                 │
│ Daily tasks: [What they do]                     │
├─────────────────────────────────────────────────┤
│ Current Process:                                │
│ • [Step 1 of how they do it today]              │
│ • [Step 2]                                      │
│ • [Step 3]                                      │
├─────────────────────────────────────────────────┤
│ Pain Points:                                    │
│ • [Pain 1 - What's broken]                      │
│ • [Pain 2 - What's slow]                        │
│ • [Pain 3 - What's frustrating]                 │
├─────────────────────────────────────────────────┤
│ Desired Outcome:                                │
│ [What would make their life better]             │
├─────────────────────────────────────────────────┤
│ Tech Comfort: [Low/Medium/High]                 │
│ Adoption Pattern: [Early adopter/Mainstream]    │
└─────────────────────────────────────────────────┘

Step 5: Buying Center Mapping

In B2B, multiple people influence the decision.

Ask the user:

Who else is involved in the buying decision?

>

1. Who initiates the search for a solution?

2. Who evaluates options?

3. Who influences the decision?

4. Who can block or veto?

5. Who approves the budget?

6. Who implements/onboards?

Buying Center Roles:

Buying Center Map:

                    ┌──────────────┐
                    │   CEO/CFO    │ ← Final approval
                    │ (Eco. Buyer) │   for large deals
                    └──────┬───────┘
                           │
              ┌────────────┼────────────┐
              │            │            │
       ┌──────┴──────┐  ┌──┴───┐  ┌────┴─────┐
       │  VP Sales   │  │  IT  │  │  Legal   │
       │ (Champion)  │  │(Tech │  │(Blocker) │
       └──────┬──────┘  │Eval) │  └──────────┘
              │         └──────┘
       ┌──────┴──────┐
       │  Sales Rep  │
       │ (End User)  │
       └─────────────┘

Step 6: Pain Point Hierarchy

Not all pains are created equal.

Ask the user:

Rank your customer's pain points:

>

1. What pain is most urgent?

2. What pain costs them the most money?

3. What pain is most frequent?

4. What pain are they actively trying to solve?

Pain Hierarchy Framework:

Scoring: H=3, M=2, L=1, Y=+2, N=0 Focus on pains scoring 8+ first.

Step 7: ICP Validation Interview Guide

Validate your ICP with real conversations.

Ask the user:

How will you validate this ICP?

>

1. Do you have access to people matching this profile?

2. Have you talked to 10+ people in this segment?

3. What questions will you ask to validate?

Interview Question Bank:

Step 8: ICP Narrowing Criteria

Start narrow, expand later.

Ask the user:

Which constraints help you focus?

>

1. What makes a company a PERFECT fit?

2. What makes them a GOOD fit?

3. What makes them a BAD fit?

4. What's a disqualifier?

Fit Scoring Framework:

Output Format Template

# ICP Definition: [Product Name]

## Executive Summary

**Target Company:** [One-line description]
**Primary Buyer:** [Title]
**Primary User:** [Title]
**Key Pain:** [Core problem]
**Urgency Level:** [High/Medium/Low]

## Company Profile

### Ideal Company

| Attribute | Definition | Rationale |
|-----------|------------|-----------|
| Industry | [Vertical] | [Why] |
| Size | [Range] | [Why] |
| Stage | [Stage] | [Why] |
| Geography | [Regions] | [Why] |
| Tech Stack | [Tools] | [Why] |
| Business Model | [Type] | [Why] |

### Trigger Events

| Trigger | Description | Urgency |
|---------|-------------|---------|
| [Trigger 1] | [What happens] | [High/Med/Low] |
| [Trigger 2] | [What happens] | [High/Med/Low] |
| [Trigger 3] | [What happens] | [High/Med/Low] |

### Fit Criteria

| Criterion | Perfect Fit | Good Fit | Disqualifier |
|-----------|-------------|----------|--------------|
| [Criterion 1] | [Definition] | [Definition] | [Definition] |
| [Criterion 2] | [Definition] | [Definition] | [Definition] |
| [Criterion 3] | [Definition] | [Definition] | [Definition] |

## Buyer Persona

### [Title] - The Economic Buyer

**Profile:**
- Title: [Exact title]
- Reports to: [Boss role]
- Team size: [X people]
- Decision authority: $[X] - $[Y]

**Goals:**
1. [Goal 1]
2. [Goal 2]
3. [Goal 3]

**Frustrations:**
1. [Frustration 1]
2. [Frustration 2]
3. [Frustration 3]

**Success Metrics:**
- [KPI 1]
- [KPI 2]

**How They Buy:**
- [Step 1 in their process]
- [Step 2]
- [Step 3]

**What Matters Most:**
- [ ] Cost savings
- [ ] Time savings
- [ ] Risk reduction
- [ ] Revenue growth
- [ ] Team efficiency

## User Persona

### [Title] - The Daily User

**Profile:**
- Title: [Exact title]
- Reports to: [Buyer usually]
- Tech comfort: [Low/Medium/High]

**Daily Workflow:**
1. [Task 1]
2. [Task 2]
3. [Task 3]

**Current Process (Without Your Product):**
1. [How they do it now - Step 1]
2. [Step 2]
3. [Step 3]
4. [Where it breaks down]

**Pain Points:**
1. [Pain 1] — [Impact]
2. [Pain 2] — [Impact]
3. [Pain 3] — [Impact]

**Desired Outcome:**
[What success looks like for them]

## Buying Center

### Stakeholder Map

| Role | Typical Title | Power Level | How to Win Them |
|------|---------------|-------------|-----------------|
| Champion | [Title] | [High/Med/Low] | [Strategy] |
| Economic Buyer | [Title] | [High] | [Strategy] |
| Technical Evaluator | [Title] | [Medium] | [Strategy] |
| End User | [Title] | [Low-Med] | [Strategy] |
| Potential Blocker | [Title] | [Medium] | [Strategy] |

### Decision Process

**Typical buying journey:**
1. [Step 1 - How they discover]
2. [Step 2 - How they evaluate]
3. [Step 3 - How they decide]
4. [Step 4 - How they implement]

**Average sales cycle:** [X weeks/months]

## Pain Hierarchy

| Rank | Pain | Urgency | Cost | Frequency | Score |
|------|------|---------|------|-----------|-------|
| 1 | [Pain] | [H/M/L] | [H/M/L] | [H/M/L] | [X] |
| 2 | [Pain] | [H/M/L] | [H/M/L] | [H/M/L] | [X] |
| 3 | [Pain] | [H/M/L] | [H/M/L] | [H/M/L] | [X] |

**Primary pain to lead with:** [#1 Pain]

## Validation Status

| Validation | Status | Notes |
|------------|--------|-------|
| 10+ interviews completed | [✓/✗] | [Count] |
| Pain confirmed | [✓/✗] | [Evidence] |
| Budget confirmed | [✓/✗] | [Evidence] |
| Buying process understood | [✓/✗] | [Evidence] |
| Design partners identified | [✓/✗] | [Names] |

## How to Find Them

### Where They Hang Out
- [Platform/community 1]
- [Platform/community 2]
- [Events/conferences]

### How to Identify Them
- [Signal 1 - Job posting, tech stack, etc.]
- [Signal 2]
- [Signal 3]

### Outreach Angles
- [Message angle 1]
- [Message angle 2]

## Anti-Personas (Who NOT to Target)

| Type | Why They're Bad Fits |
|------|---------------------|
| [Type 1] | [Reason - no budget, wrong problem, etc.] |
| [Type 2] | [Reason] |
| [Type 3] | [Reason] |

## ICP Evolution Plan

**Current Focus (Now):**
- [Narrow segment to win first]

**Phase 2 (After PMF):**
- [Adjacent segment to expand into]

**Phase 3 (Scale):**
- [Broader market]

## Next Steps

- [ ] Validate with 10 more interviews
- [ ] Identify 5 design partners from this ICP
- [ ] Build outreach list of 100 matching companies
- [ ] Create messaging for each persona

Common Mistakes to Avoid

1. Too broad: "All companies" is not an ICP 2. Too narrow: "Left-handed CEOs in Iowa" is too small 3. Buyer/User confusion: They're often different people 4. Ignoring buying center: Multiple people matter 5. Assuming, not validating: Talk to real customers 6. Static ICP: It should evolve with learnings 7. Feature-led personas: Define by problems, not features 8. Skipping anti-personas: Know who NOT to target