An ideal customer profile (ICP) describes the type of customer, often at the account level for B2B businesses, most likely to buy, succeed with, and stay loyal to your product or service. A persona adds a more narrative, individual layer on top: the goals, frustrations, and constraints of a specific type of decision-maker or user. Both tools exist to answer one practical question: who exactly are we trying to reach, and why would they choose us?
ICP vs persona: what's the difference?
For B2B businesses, the ICP usually describes the company: industry, size, revenue range, tech stack, growth stage, or specific operational triggers (for example, 'just hired their first sales rep' or 'recently expanded to a second location'). The persona then describes the individual human inside that company who buys or uses the product, for example a 'Head of Operations' persona with specific daily frustrations. For consumer (B2C) businesses, the ICP and persona often merge into one individual-level profile, since there's no separate 'account.'
| Aspect | ICP (account-level, B2B) | Persona (individual) |
|---|---|---|
| Describes | The type of company or household that fits best | The individual person's goals and constraints |
| Built from | Firmographics, usage data, win/loss patterns | Interviews, support notes, sales calls |
| Used for | Targeting and list-building, account prioritization | Messaging tone and content topics |
Buying triggers, pain points, constraints, and decision roles
A useful ICP or persona answers more than 'who are they'; it answers why they'd buy now. Four elements matter most:
- Buying trigger: the event or realization that starts the search for a solution (e.g. a compliance deadline, a bad customer experience, a new hire).
- Pain point: the specific problem costing them time, money, or stress right now.
- Constraint: budget limits, existing contracts, internal politics, or technical limitations that affect what they can choose.
- Decision role: who actually approves the purchase, who influences it, and who will use the product day to day; these are sometimes different people.
Avoid demographic stereotypes that don't predict behavior
Age, gender, or generic job title alone rarely predict whether someone will buy; behavior and context predict it far better. 'Women aged 25 to 34' tells you very little about why someone buys a specific product. 'Recently promoted to their first management role and anxious about running their first performance reviews' tells you a great deal, and it can apply across ages and genders. Favor trigger-and-context detail over broad demographic buckets unless you have actual evidence those demographics correlate with a real buying difference.
Collecting evidence from existing customers
Build your ICP and persona from real sources, not assumptions: interview five to ten existing customers (see the related article on customer research), review support tickets and sales call notes for recurring phrases, look at which customer segments have the best retention or lowest support burden, and check reviews for the exact language people use to describe their problem. If you have no customers yet, build a labelled hypothesis from the best available evidence, direct competitor reviews, industry forums, and informal conversations, and mark it clearly as unverified until real customer data arrives.
How an ICP informs channel and offer choices
- 1Confirm the ICP's buying trigger and constraint
- 2Identify where this person already looks for solutions (search, peer recommendation, social, marketplace)
- 3Match the channel to that behavior, not to what's trendy
- 4Shape the offer and pricing around the stated constraint (e.g. a low-commitment trial if budget is the main blocker)
ICP and persona template (deliverable)
| Field | Your answer |
|---|---|
| Who (account or individual) | |
| Buying trigger | |
| Top pain point | |
| Constraint (budget, time, politics) | |
| Decision role(s) involved | |
| Where they currently look for solutions | |
| Evidence source (interview, review, sales note) |
Common mistakes
- Writing a persona based on imagined demographics with no evidence behind it.
- Building one generic persona when there are actually two or three meaningfully different buyer types.
- Never revisiting the ICP after launch, even as real customer data accumulates.
- Confusing the economic buyer (who approves the purchase) with the end user (who actually uses the product).
- Making the persona so broad ('busy professionals who want to save time') that it doesn't rule anyone out.
When a detailed ICP isn't necessary yet
If you have fewer than five customers and are still validating whether the product solves a real problem, a lightweight working hypothesis is more useful than a polished, multi-field ICP document; spend that time instead on direct customer conversations (see the next article on customer research). Similarly, for a single-person consulting practice serving a very narrow niche by referral, a formal persona exercise may add less value than simply writing down the two or three questions prospects always ask before hiring you.
