Skip to main content

Ideal customer profile template for ABM

David & Goliath | Last updated

An ideal customer profile template records which enterprise accounts fit your offer, what evidence supports that view and what would rule an account out. This worksheet turns those decisions into fields that sales and marketing can both challenge, with fictional examples. It covers the problem, buying entity, required fit evidence, hard exclusion, preference, timing hypothesis, access and permissions, and a pass, hold or exclude decision.

The full template

Fictional illustration: a cybersecurity vendor entering ANZ. These entries show how to fill in the worksheet. They describe no real organisation, customer or result.

ICP worksheet: fictional selection criteria, with no client results or scoring benchmark
FieldYour promptFictional filled-in illustration
ProblemWhich business problem can the offer credibly address, and who owns its operational consequences?A cybersecurity vendor proposes helping an enterprise evaluate its security workflow; the buyer's exact problem remains to be confirmed.
Buying entity and territoryWhich entity would evaluate, contract and receive delivery? What is confirmed locally?An ANZ operating business is relevant, but the contracting entity and regional approval path need research.
Required fit evidenceWhat must be true for the offer to work, and which source can establish it?The technical owner requires a compatible deployment environment; published material alone has not confirmed compatibility.
Hard exclusionWhat service, technical or commercial condition prevents responsible delivery?An unsupported deployment requirement excludes the account unless delivery explicitly approves a feasible alternative.
PreferenceWhat makes an otherwise eligible account more suitable without becoming a mandatory condition?Relevant public evaluation documentation may make research more useful; its absence does not itself prove a poor fit.
Timing hypothesisWhat suggests a decision may be relevant now? What still needs buyer confirmation?A published security programme suggests a discussion topic, while budget and purchase timing remain unknown.
Access and permissionsWhich relationships are confirmed and what separate channel checks remain?The team has no confirmed invitation route. A public role description is a research lead, not contact permission.
Decision and unknownsPass, hold or exclude? Who resolves each material gap, using which permitted source?Hold. The technical owner checks deployment fit; the account owner researches the buying entity before selection.
Version and reviewWho approves the criteria, when do they apply and what evidence triggers a change?Sales, marketing and delivery approve the brief together; a changed support model triggers a new version.

How to use it

  1. Define the problem and delivery boundary

    Write the operational problem, the buying entity that could own it and the change your offer can support. Ask delivery to confirm prerequisites, implementation responsibility and situations the offer cannot serve. Separate confirmed capability from planned capability; an aspiration must not become an eligibility promise.

  2. Write observable fit criteria and hard exclusions

    For each criterion, record why it matters, an acceptable source and what would disprove it. Distinguish a necessary condition from a useful preference. Put unsupported deployment requirements, territory limitations or conflicts into explicit exclusions instead of hiding them inside a weighted score.

  3. Separate fit, timing, access and permission

    Keep long-term problem fit apart from evidence of an active decision. A published initiative may justify research; it does not prove budget or intent to purchase. Record relationship access and contact permissions separately, so a reachable executive or an intent signal cannot make an unsuitable account pass.

  4. Test the criteria against contrasting account cases

    Have sales and delivery independently apply the brief to a plausible fit, a clear exclusion and an uncertain case. Use permitted internal evidence or clearly fictional cases. Compare disagreements and tighten ambiguous criteria. Do not claim the profile is validated by a fictional illustration or a handful of favourable examples.

  5. Agree pass, hold and exclude decisions

    An account can pass when the required evidence exists, stay on hold while a material question is unresolved, or be excluded for a documented reason. Assign an owner and permitted research route to each unknown. A hard exclusion is not outweighed by a large potential deal; any exception needs the responsible owner's explicit approval.

  6. Approve a version and hand it to account selection

    Record the profile owner, effective date, sources and review triggers. Hand the approved criteria to the existing account-selection process, then use the tiering worksheet to allocate effort. Preserve the earlier version when criteria change so later reporting can explain which cohort was selected under which assumptions.

Who fills it in

The commercial owner defining the offer, marketing and sales owners selecting the segment, and a delivery or technical owner who can verify serviceability. For ANZ market entry, include whoever can confirm local delivery, support and contracting arrangements. A person's job title is not an account-fit criterion.

What to bring

  • Offer and delivery prerequisites confirmed by the responsible owner
  • Source register with dates, evidence and labelled assumptions
  • Necessary criteria, preferences and hard exclusions
  • Contrasting calibration cases and recorded disagreements
  • Profile version, decision owner and change history

When to do it

Complete the fit brief and calibration review before committing research or media effort to a segment. Set a review date with the accountable owner. Reopen the profile when delivery capability, territory, buying-entity evidence or recurring exclusion reasons change; do not rewrite it merely to improve a reporting period's conversion rate.

What to review

  • Required criteria supported by evidence, with unknowns reported separately
  • Sales and delivery disagreements about inclusion and their resolved reasons
  • Accounts held or excluded by reason, without treating rejection as lost pipeline
  • Changes to fit criteria with an owner, evidence and effective date
  • Selection consistency checked against the same approved version; no universal score or threshold is supplied

Use the ABM measurement guide for stage definitions. Activity alone does not establish sales acceptance, pipeline or revenue.

When to use it, and when not to

Use this worksheet before selecting named accounts, entering an ANZ segment or revising a cohort whose fit assumptions have changed. Sales, marketing and delivery should be able to use the same criteria and explain why an account belongs. The output is a versioned selection brief, ready for account research and subsequent tiering.

Pause selection when the offer, delivery constraints or buying entity are unclear. Do not turn a list of desirable logos into fit criteria after the accounts have already been chosen. This worksheet does not discover accounts or validate contact details.

Common mistakes

  • Using industry and company size as proof of a business problem
  • Calling a published initiative a confirmed buying project
  • Weighting away a delivery constraint because the logo is attractive
  • Turning missing evidence into a low score rather than a visible unknown
  • Changing the profile retrospectively without preserving the original cohort

Compliance notes

Apply the checks relevant to your channel and buyer. These sources do not establish clearance for New Zealand activity, which needs a separate local review.

Questions

How is an ideal customer profile different from an account list?

The profile defines the business-fit criteria, exclusions and evidence needed for selection. The account list records the named organisations checked against that version. Use the existing account-selection process to build the list.

Does an intent signal make an account a fit?

Treat the signal as a reason to investigate a relevant question. Check problem fit, delivery prerequisites and the buying entity independently. A signal neither confirms a purchase nor creates permission to contact someone.

Should we assign a numerical ICP score?

A score is useful only when its criteria, evidence and decisions are understood. Start with explicit required conditions, exclusions and unknowns. This worksheet supplies no universal weights, pass mark or predictive claim.

What should happen when evidence is missing?

Keep the material question visible and put the account on hold if it prevents a responsible selection decision. Assign a research owner and review point. Do not silently treat an unknown as a pass or an exclusion.

Sources

Cite this template

This template is a working aid from David & Goliath: its examples are fictional and it reports no client results or benchmarks.

David & Goliath, "Ideal customer profile template for ABM", last updated 5 November 2026, https://davidandgoliath.ai/templates/ideal-customer-profile-template

Related

Getting help with this

Use the approved profile to agree which accounts can enter the programme and which questions must be resolved before activity begins.