Define your ICP by problem space, not just industry or company size.

Learning Goal

Create a problem-first ICP v1.
List 3–5 “bad fit” signals.
Write a short, testable ICP definition.

Why It Matters

Wrong ICP = more activity, worse conversations.
Problem-first ICP connects to pain and decision-making.
Speeds qualification: you know when to say no.

Explanation

Problem-first ICP elements

Pain: the concrete operational or revenue problem.
Trigger: what sparked the search (growth goal, churn, new market).
Maturity: tools/processes already in place.
Stakes: risk of not fixing it.

Bad-fit signals

No pain owner.
No budget or decision maker.
“Curious” motivation with no clear trigger.

Examples

Bad ICP (industry-first): “Mid-market SaaS companies.”

Good ICP (problem-first): “15–80 person B2B SaaS team, 15–30% churn, GTM team 3–6 people, sales cycle >90 days, seeking qualified pipeline growth.”

Guided Exercise (10–15 minutes)

Draft ICP v1 using the 4 elements (pain, trigger, maturity, stakes).
Write 5 ICP test questions for qualification (e.g., “What triggered this project?”, “Who owns the pain?”).
List 3–5 bad-fit signals.

Independent Exercise (5–10 minutes)

Take one active lead and score it with your test questions: do you fit? If not, write how you will say “no” fast.

Self-check

ICP v1 (problem-first) done.
Qualification test questions ready.
Bad-fit signals listed.
Applied the filter to one lead.

Optional Deep Dive

Gartner ICP guide: https://www.gartner.com/en/insights/sales
OpenView ICP example: https://openviewpartners.com/blog/ideal-customer-profile

ICP 2026: Problem-First, Not Industry-First