ICPSignalKnowing who you can't help is part of knowing who you can. I would put that directly into a customer profile. Otherwise, a broad description can make a lot of unrelated posts sound like opportunities.
Exclusions give the profile boundaries. They also force you to make decisions about your offer: the work you take, the requirements you support, and the requests you should leave to somebody else.
Describe the mismatch clearly
Start with situations you've actually had to reject. Perhaps the person is offering the same service, needs an unsupported platform, or wants work outside your service area. Explain why the request is out of scope.
For a fictional migration agency, ‘exclude posts from agencies advertising migration services’ is more useful than ‘exclude bad leads.’ The first gives you a recognizable situation. The second repeats the conclusion you are trying to reach.
Keep missing information separate from a mismatch
A post that doesn't mention budget hasn't told you there is no budget. A person learning about the problem may still become a customer later. I'd be careful about excluding every situation that isn't ready for a sales conversation today.
Use hard exclusions for conditions that make your offer unsuitable. For incomplete or early questions, decide whether you can offer education or ask a useful question. You can choose not to reply without declaring that the entire audience is wrong.
| Situation | How I would treat it |
|---|---|
| Explicitly requires an unsupported feature | A concrete fit problem. |
| No budget information given | Unknown; do not invent the answer. |
| Another vendor promoting the same service | An exclusion candidate for a buyer-focused profile. |
| Relevant question before tool selection | Potential learning or educational conversation. |
Check what the exclusion would remove
Test the wording against a good match and a poor one. Could a real customer use the same phrase as the person you mean to exclude? If so, add context rather than banning the phrase broadly.
For example, someone can mention a tutorial while asking for paid implementation help. Read the request as a whole. I want an exclusion to clarify the situation, not punish a word that happens to appear in it.
Review the next results with the boundary in mind
Add the relevant exclusions when describing your ideal customer profile in ICPSignal. Review the resulting profile before activating discovery, then check the original posts behind the matches.
Keep a small list of useful posts the boundary might accidentally rule out and poor matches it should remove. Revisit the wording when real evidence changes your understanding. A good boundary makes decisions easier while leaving room for the people you can actually help.