Build an Ideal Customer Profile You Can Apply Consistently
A practical way to define an ideal customer profile with evidence, required filters, buyer responsibilities, exclusions, and a repeatable review process.
An ideal customer profile (ICP) describes the kind of organization that is most likely to benefit from an offer. It is not simply a list of industries to search. A useful ICP helps a researcher make consistent choices when deciding whether an account belongs in a prospect list.
Begin with evidence from customers and delivery
Look at customers who receive value from your product or service, not only those who signed a contract. Which business problem did they have? What made delivery successful? Which company characteristics were genuinely important? Compare strong-fit customers with accounts that churned, stalled, or needed support your team could not reasonably provide. Use these observations as hypotheses, then test them rather than treating a small sample as universal truth.
Describe the organization in observable terms
Translate “good customer” into attributes a researcher can assess: industry or business model, operating region, employee range, service area, technology environment, or a particular business trigger. Start with a few meaningful characteristics. Add revenue, growth stage, or other filters only when you can explain why they help distinguish fit and how the information will be assessed.
Rank criteria instead of making every filter mandatory
Separate required conditions from positive signals. A required condition might be that the company operates in a supported market. Positive signals might include a relevant technology, a new location, or a team expansion. This distinction helps avoid excluding promising accounts simply because one optional field is unavailable.
Connect account fit to the buying group
After defining the company, identify who experiences the problem, who evaluates solutions, and who approves spending. Those responsibilities may sit with one person in a small organization or several people in a larger one. Write down likely departments, title variations, and seniority ranges. Use the role description—not a title keyword alone—to judge relevance.
Write an exclusion list
A good ICP also names poor-fit accounts: unsupported countries, business models your service cannot support, direct competitors, current customers, or organizations that already have an active sales owner. Keep exclusions separate from positive criteria so researchers can apply them without guessing.
Test the ICP with real examples
Choose a small set of known good-fit accounts and a set of borderline or poor-fit examples. Apply the written criteria without relying on what the team knows informally about each company. Where reviewers disagree, refine the definition until two people can usually reach the same decision from the same evidence.
Track whether the profile predicts useful outcomes
When possible, compare segments by meaningful outcomes such as qualified conversations, sales acceptance, or customer fit—not just email opens or list size. Record enough context to understand why a segment worked. Review the ICP when your offer, market, or delivery capabilities change.
One-page ICP worksheet
- Core problem your offer solves
- Required industries, markets, and company characteristics
- Optional fit signals and how to verify them
- Buyer responsibilities and likely title variations
- Explicit exclusions and existing-account rules
- Examples of strong-fit, borderline, and poor-fit companies
- Outcome used to review and update the profile
The aim is not to make targeting complicated. It is to make the reasoning visible so that research, sales, and delivery teams can work from the same definition of relevance.
Turn the profile into a research brief
Use the OngoingLead lead-list brief to share your target markets, company criteria, buyer roles, requested fields, and exclusions. A clear brief helps assess the work before a list is researched.
Separate ICP evidence from assumptions
For each proposed targeting rule, note its basis: observed customer pattern, sales-team hypothesis, or a required operational constraint. Then decide how it will be checked during research. This simple evidence label makes it easier to revisit a rule when the market changes and helps prevent assumptions from silently becoming hard filters.
- Observed pattern: Supported by actual customer or delivery experience.
- Hypothesis: Plausible, but should be tested against outcomes.
- Constraint: Required because of geography, capacity, product fit, or another clear limitation.
Do not describe a pattern as proven when it is only a hypothesis, and do not claim performance improvements without measured evidence.