Builds a defensible ICP (ideal customer profile) that constrains the outbound list to accounts whose situation actually maps to the claim. Output is an exclusion-first checklist, not a vanity list of titles.
Installs into .claude/skills of the current project.
Are you the author of Icp Builder?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/veneris-io-icp-builder)
---
name: icp-builder
description: Builds a defensible ICP (ideal customer profile) that constrains the outbound list to accounts whose situation actually maps to the claim. Output is an exclusion-first checklist, not a vanity list of titles.
---
# ICP Builder
Produces an ICP definition you can actually enforce as a list constraint — the one that's enforced against 500CandidateList → ~150TargetList before any copy gets written.
## Inputs
- Product/claim
- Agreed exclusion criteria
- Timing signals required before first-touch
- Persona-ownership mapping
## Rules
- **Exclusion-first.** Write down who is never worth contacting — recent competitor sign-in, leadership-change hiatus, hiring-freeze, etc. If you can't name exclusions, you don't have an ICP; you have a hope.
- **Timing signals as gates.** Only accounts where a live signal (hiring, expansion, tooling change, compliance event) currently maps to your claim are eligible.
- **Persona mapping.** For each role, the change-measured outcome that person owns. The "decision-maker" you email must be able to answer "why now?"
- **Constraint, not description.** Output is written as testable filters (e.g., exclude: employee count <N; require: recent leadership event <90d; require: not in a hiring freeze).
## Approval
Show the constraint-checklist (of include + exclude + gate) and explicit failure-modes — what you not claiming to solve. Wait for approval before using the list.
