
Ideal Customer Profiles
Part of Ideal customer profiles for outbound prospecting
Choosing account criteria from existing customer evidence
Compare successful and difficult customer cases, test why a trait matters, and turn supported patterns into checkable account criteria.
Choose account criteria by looking for observable traits that relate to successful use of your current offer. Compare customers served well with difficult cases, ask why a pattern matters, then write a rule a researcher can check.
A trait shared by a few customers is a hypothesis, not proof of a market boundary.
Define the outcome before looking for patterns
Agree on what shows that the offer worked for the customer and was feasible to deliver. Depending on the offer, evidence might include continued use, implementation effort, a solved workflow problem or the customer’s account of its value. Keep revenue visible, but do not use it alone as a measure of fit.
Include contrasting cases. A customer may have bought despite an expensive workaround; another may have declined because of a requirement the business still cannot meet. Ask delivery and customer-facing colleagues what differed, and distinguish recorded facts from recollection.
Successful vs. Difficult Customer Cases: Key Differences
- Outcome Evidence
- Continued use, solved workflow problem, positive value feedback
- Delivery Effort
- Low implementation effort, minimal workarounds
- Customer Feedback
- Clear articulation of value and ease of integration
- Contrast Case
- High effort despite purchase; declined due to unmet requirement
Turn a pattern into a criterion
For each proposed trait, make a brief evidence note:
Record / Question
- Observed trait
- What is known about the accounts?
- Link to fit
- Why might this trait affect delivery or customer value?
- Counterexample
- Which cases challenge the pattern?
- Check method
- Can a researcher verify it before contact?
- Decision
- Is it required, useful context or still unproven?
Suppose a hypothetical service connects stock records to a planning system. Several successful customers use the same planning platform. That does not show the platform is required.
Ask whether delivery technically depends on it or whether those customers arrived through one referral channel. The answer determines whether it is an eligibility rule or a research note.
Turning a Pattern into a Checkable Account Criterion
- Record Observed TraitE.g., Use of same planning platform (e.g., SAP ERP)
- Link to FitMay reduce integration complexity or improve data flow
- Counterexample CheckSome customers succeeded without it; others failed despite using it
- Check MethodVerify via CRM or public company data (e.g., industry, software usage)
- DecisionEligibility rule only if technical dependency is proven
Watch for weak proxies
Use an employee-count or revenue band only if scale changes the problem or the ability to deliver. Do not invent a threshold because a prospect database offers the filter. An industry label can conceal differences in workflow; describe the operational condition first, then decide whether industry helps identify it.
A small or narrow customer base cannot settle the wider market boundary. Record the cases behind a proposed rule and mark uncertain rules as provisional. A blank CRM field is missing information, not evidence that an account lacks the trait.
Check whether the rule is usable
Give each criterion a plain definition and specify acceptable evidence. Ask colleagues to apply it to candidate accounts. Disagreements may reveal unclear wording or information that needs a further check.
Revisit a rule when it repeatedly excludes accounts the business could serve, admits accounts with the same avoidable mismatch or becomes outdated after the offer changes. Keep the reason for each revision.
Usability Check for Account Criteria
- Plain definition provided?Yes – e.g., 'Uses SAP ERP for production planning'
- Acceptable evidence specified?Yes – e.g., public software listings, CRM field entry
- Colleagues tested the rule?Yes – identified ambiguity in 'large enterprise' threshold
- Rule reviewed after changes?Yes – updated after new API integration reduced dependency on specific platforms



