What should an ideal customer profile include?

A B2B ideal customer profile should include a market thesis, positive fit conditions, exclusions, relevant operating context, buying-group roles, observable signals, evidence standards, and a process for learning from outcomes.

Is an ICP the same as a buyer persona?

No. An ICP defines the type of company likely to become a valuable customer. A buyer persona describes a person or role involved in the decision. A useful B2B model connects both.

How many criteria should an ICP have?

Start with the few conditions that meaningfully change customer success or commercial efficiency. Five well-supported criteria and clear exclusions are more useful than a long list of weak attributes.

An Ideal Customer Profile Template That Can Actually Learn

An effective ideal customer profile template captures more than industry and company size. It records the market thesis, positive and negative fit evidence, buying-group roles, timing signals, and the outcomes that will confirm or challenge the model.

Use the template below as a working decision system. Do not complete it once and archive it. Assign evidence, map it to accounts, and revisit it as opportunities are won, lost, expanded, or disqualified.

Ideal customer profile template

Copy these sections into your planning system, CRM documentation, or ICP platform.

1. Market thesis

We believe [type of company] experiences [important problem] because [structural condition or change]. Our offer creates value by [mechanism], and the customer realizes that value when [success condition].

Add:

geographic scope;
category or business-model boundaries;
relevant market changes;
why this market is attractive now;
assumptions that still need evidence.

This paragraph forces the team to explain causality. “Manufacturing companies with 500 employees” is a filter. “Multi-site manufacturers centralizing revenue operations after acquisition” is a thesis.

2. Positive fit conditions

List the conditions that make value and successful delivery more likely.

Condition	Why it matters	Evidence source	Weight
Example: small centralized revenue team	creates a coordination problem we solve	company site, roles, CRM	high
Example: compatible sales motion	aligns with our implementation and economics	interviews, CRM, research	high
Example: recent market expansion	increases urgency and complexity	news, hiring, site	medium

Every condition should have a reason. If the team cannot explain why an attribute changes the probability of success, it may not belong in the ICP.

3. Exclusions

Write explicit reasons not to pursue an account.

Examples include:

incompatible business model;
insufficient data or process maturity;
economics that cannot support the service;
regulatory or geographic constraints;
a buying process that conflicts with the offer;
a use case the product does not reliably support.

Exclusions protect focus and make scoring honest. They also help sales explain why an attractive logo may still be a poor customer.

4. Operational context

Firmographics describe what a company is. Operational context describes how it works.

Capture relevant facts such as:

team structure and ownership;
sales motion and deal complexity;
installed technology;
data maturity;
growth stage;
hiring patterns;
recent strategic change;
partner or channel model.

Choose only the context that affects the problem, buying process, or ability to realize value.

5. Buying group

Define responsibilities before titles.

Role	Responsibility	Likely concern	Evidence needed
Outcome owner	accountable for the business result	economic impact and risk	confirmed ownership
Practitioner	lives with the current process	workflow and usability	role and current state
Evaluator	validates technical or operational fit	integration and governance	involvement in evaluation
Approver	controls budget or final authority	priority and downside	decision authority
Advocate	moves the work internally	credibility and support	relationship strength

Then map actual titles for each market segment. Do not assume the same title performs the same role everywhere.

6. Problems and value conditions

For each important problem, record:

the observable current state;
the consequence of leaving it unresolved;
the event that makes it urgent;
the existing alternatives;
the mechanism by which your offer helps;
what must be true for the customer to succeed.

This prevents the ICP from becoming a list detached from the reason anyone buys.

7. Signals and timing

List evidence that may change an account’s priority, without confusing that evidence with fit.

Examples:

repeat visits to relevant solution or implementation pages;
hiring for a role connected to the problem;
leadership change;
new funding, acquisition, or market expansion;
engagement from multiple buying-group roles;
a technology or process change;
an opportunity stage change or period of inactivity.

For each signal, define source, confidence, recency window, and proportionate action. See the buyer intent data guide for the full framework.

8. Fit scoring

Keep fit scoring explainable.

Use three bands to start:

Strong fit: meets the critical success conditions with no material exclusion.
Possible fit: meets some conditions but requires validation.
Poor fit: violates an exclusion or lacks conditions necessary for value.

If you use a numeric score, preserve the contributing evidence. A user should be able to see why an account received the result and which uncertainty remains.

9. Proof and counter-evidence

Create two lists:

Evidence supporting the ICP might include strong customers, expansions, faster sales cycles, high product adoption, or consistent buying-group patterns.

Evidence against the ICP might include repeated late-stage losses, poor retention, delivery difficulty, unexpected success outside the segment, or strong fit scores that produce no pipeline.

Counter-evidence keeps the document from becoming a story the team only tries to confirm.

10. Review cadence and owner

Name one owner for the model and define:

a quarterly calibration date;
the outcomes included in review;
who may propose a change;
who approves material changes;
how versions are preserved;
where updated logic flows into targeting and workflows.

The ICP should change when evidence changes—not whenever a stakeholder wants a larger list.

How do you turn the template into a living system?

The document becomes intelligence when it connects to actual work.

Map the criteria to a defined universe of accounts.
Attach evidence to each match and exclusion.
Map likely buying-group roles to people.
Add relevant first-party and external signals.
Use fit and timing to prioritize review.
Record why the team chose each action.
Return opportunity and customer outcomes to the model.

That is the larger model described in ICP Intelligence: Build a Living Ideal Customer Profile.

A one-page review checklist

Before the team uses the ICP, ask:

Can we explain why each criterion matters?
Are exclusions explicit?
Do we distinguish company fit from buyer timing?
Have we defined responsibilities as well as titles?
Can a user inspect the evidence behind an account’s fit?
Do the criteria connect to a problem and value mechanism?
Will wins and losses update the model?
Is there a named owner and next review date?

If the answer to several of these is no, keep the model small and fix the reasoning before adding more data.