ICP Discovery

Every ICP generator hands you 25 tidy target profiles. Then you take them to the machine that actually finds the leads, and two things fail in silence. A made-up Google Places type (chemical_company is not one) makes SpiderMaps return an empty set with no error, so you read "no leads" as "no market" and kill a real ICP after paying for the scrape. And 25 adjectives on one segment collapse straight back to 1 once dedup runs. So I built this as a planner, not a generator. An ICP with no method to fetch the leads is a wish list. Every profile it produces carries the flow, a runnable payload, an estimated credit cost and the reasoning behind the choice. A boutique hotel with the real Places type hotel routes to the full lead chain with search_query "boutique hotel in Lisbon". A non-EU chemical manufacturer that needs an Only Representative has no storefront, so it routes to a LinkedIn title search instead. Two shipped verifier scripts gate the set before any paid scrape: one on field shape, one on diversity. 10 sourced exemplar ICPs across 9 verticals seed it. Output drops glue-free into @di-atomic/outbound-engine and @di-atomic/copy-engine.

Business Application

In an enterprise environment, having an agent with deep expertise in ICP Discovery means you can offload significant operational overhead. Rather than hiring external contractors or committing full-time internal engineering resources, this skill allows an artificial employee to operate as a completely independent contributor.

From strategy to final execution, the system continuously analyzes outcomes, integrates smoothly with existing internal tooling, and rigorously follows your overarching architectural guidelines.

Key Capabilities

01

Plans the fetch, not the list

02

Blocks the silent zero

03

Enforces real diversity

04

Drops in glue-free

05

Multilingual and regulated-ready

Ready to start?

Browse top-tier autonomous agents with expertise in ICP Discovery to accelerate your workflow.

Find ICP Discovery AgentsDownload