Negative ICP criteria | Outbound Wiki

Negative ICP criteria tell you where to stop spending outbound effort. Write each one as an observable condition, tie it to the failure it predicts, and give it an action. Separate an account outside the customer size your offer can serve from one that may fit but is not ready to move. A size mismatch can remove an account from active pursuit. A readiness gap can pause the account until a stated trigger appears.

Define the failure you want to avoid

Start with the reason an account would fail to buy, adopt, or succeed with the offering. Then describe the signal you could see before spending more outbound time.

A useful criterion answers four questions:

What condition makes the account a poor fit?
What would you hear or observe that confirms the condition?
Does the condition concern account fit or buying timing?
Should the account be excluded, held, or reviewed manually?

Keep the criterion close to the failure. "Bad fit" cannot guide a list decision. "The account cannot use the offering at its current size" gives you a condition to test. "The account has no current readiness signal" gives you a reason to pause outreach.

Use a sentence pattern that makes the decision clear: "Exclude companies when [observable condition] shows [fit problem]. Hold companies when [readiness signal] shows [timing problem]." Fill the brackets with language you can check from account information or a conversation.

Run discovery in order

Move the conversation from the mismatch to its meaning and then to the action you will take. Use these questions to keep a vague objection from becoming an untested exclusion.

Stage	What you are trying to learn	Example question
Surface	what makes the account seem unsuitable	What makes this feel like a poor fit for your company?
Classify	whether the issue concerns account fit or timing	Is this about the kind of company you are, or about when you can act?
Verify	what observable condition sits behind the objection	What would need to change for the offering to become workable?
Route	what should happen to the account record	Should we close this out, or revisit after that condition changes?

Ask the surface question before proposing a workaround. If the answer names the account's size, operating context, or ability to use the offering, classify it as a fit condition. If it names timing or preparedness, classify it as a readiness condition.

Set the size boundary

This stage decides whether the company belongs in active pursuit. Turn the fit objection into an account rule you can check before the next call.

A product fit objection can sound like a smaller customer saying the solution is made for bigger customers.¹ When you hear that signal, ask what makes the account feel too small for the offering. Look for the attribute behind the statement, such as the scale of the operation or the amount of complexity the account can support.

Write the boundary in terms of that attribute. Avoid recording the objection as a loose label such as "small company." The usable version explains what the account cannot support and why that blocks a successful engagement.

Move to exclusion when the answer describes a lasting mismatch with the way the offering is delivered. Keep the account in review when the concern is unclear or depends on information you have not checked. The rule should tell the next rep what to do without requiring a fresh interpretation of the original conversation.

Handle readiness as a separate exit

Readiness needs its own route because a company can fit the offering and still have no reason to act now. Treat the signal as a timing condition until the conversation shows that the problem reaches deeper than timing.

A readiness objection can sound like "We're not ready yet".¹ Ask what readiness means in that account. It may refer to an internal decision, an unresolved operating condition, or a lack of capacity to take on a change. The answer gives you the trigger for future outreach.

Record the trigger in plain language. Examples include a stated change in priorities, a completed internal decision, or a condition the account says must exist before action is possible. Leave the account on hold when the trigger is missing. Resume pursuit when the account can point to the change that removed the timing barrier.

A readiness statement calls for a hold until you identify what readiness requires. Exclude an account when it cannot use the offering; hold it when movement is postponed.

Turn language into a rule

A negative criterion becomes useful when another person can apply it consistently. Write the rule after the call while the account's wording and the reason for the decision are still clear.

Use this structure:

Condition: describe the account characteristic that creates the mismatch.
Signal: capture the words or observable detail that confirms it.
Action: state whether to exclude, hold, or review.
Trigger: state what would make the account eligible for another look.

The signal should distinguish a real boundary from a polite objection. The action should affect the next outbound decision. The trigger should describe a change in the account, not a vague hope that interest will appear later.

Keep fit and readiness in separate fields if your workflow allows it. That preserves the reason for the decision and prevents a held account from disappearing with permanently excluded accounts. If your workflow has a single notes field, write the route at the start of the note so the next person can act on it quickly.

Validate the criterion before expanding it

A phrase becomes a negative ICP criterion only after you can connect it to a repeated failure pattern. Review the account conversations that produced the signal and ask what happened after the objection.

Check whether the condition stopped a purchase, blocked adoption, or made success unlikely. Check whether the same observable condition appeared across accounts with the same outcome. If the signal appears without a consistent consequence, keep it as a question for discovery instead of turning it into an exclusion rule.

Test the rule against accounts that look similar on the surface. If it sends some accounts to exclusion and others to a hold, put the distinction in the rule. If the rule requires information you cannot obtain before outreach, rewrite it around an earlier signal or make manual review the route.

Review the wording whenever the offering, target customer, or delivery model changes. A criterion describes a boundary in the current motion, so its action must stay connected to how the offering creates customer success.

Put the rule into outbound

Apply the criterion before writing the sequence or making the call. An excluded account should leave active pursuit. A held account should retain its reason and its return trigger. A manual review should have a clear owner and a clear question to resolve.

Use the criterion to shape the opening question when the account is close to the boundary. Ask about the condition that could prevent success, then let the answer determine the route. This keeps the call focused on whether the account can use the offering and whether the timing supports movement.

Keep the account's own wording in the record when it explains the decision. Exact language makes later review easier and gives you a better basis for refining the rule.

What not to do

Do not turn "We're not ready yet" into a permanent exclusion without identifying what readiness would require.¹
Do not treat a statement that the solution is made for bigger customers as a generic objection. Find the account condition behind it and decide whether that condition blocks use of the offering.¹