The Operational ICP
How to build an ICP your outbound team actually uses.
An ICP that lives in a slide is a marketing artifact. An ICP that routes a record to a sequence is an operating system. This playbook builds the second kind.
The problem nobody names
Almost every B2B company has an ICP. Almost none have one their outbound team can execute.
The document exists. It says things like “mid-market SaaS, 50–500 employees, in growth mode.” It was written once, approved in a meeting, pasted into a Notion page, and never opened again. The reps prospect off instinct. The data vendor builds off whatever filters were easy. The automation sends to whoever cleared a verification check. Three “ICPs” run at once, and none of them match. The ICP is a definition when it needs to be an instruction set.
Spray and decay
Loose targeting means more sends to weak-fit accounts. They complain. A bad ICP wastes sends — worse, it burns the domain that delivers the good ones.
AI hallucinates a market
Autonomous outbound trained on a vague ICP scrapes bios and guesses. Fluent, personalised, aimed at the wrong people. The engine inherits the ICP's precision and amplifies its error.
Reps stop trusting the list
When a list is off-target, reps abandon it and fall back on their gut. Now you pay for data and tooling that route around themselves.
You cannot automate, delegate, or scale your way out of a vague ICP. Volume multiplies whatever you point it at. Point it at the wrong market and you build a bigger machine for losing.
Lock the vocabulary, stop the arguing
Half of ICP debates are vocabulary problems. The Operational ICP combines four of these — account fit, exclusions, committee, and signals — into one scored instruction the whole funnel reads from.
Want the rest of this one?
You have read the opening of “The Operational ICP”. Tell me where to send it and I will email you the full play, plus every new one I publish. Operator notes, no spam.
I send it by hand · No spam · Unsubscribe anytime