How to Define an ICP Your Team Will Actually Use
Most ICP documents are a slide. They get written for a fundraise or a website, then ignored the first time someone has a list to upload. The version I care about is operational: it decides who deserves a message today, and who the team is never allowed to contact.
Pramod Kumar, co-founder of Kingdom of Kumar. On X
·
Adugbo Victory put the first half of that plainly when talking about motions that are just a prompt on a list: deciding who deserves a message today, and why, is the actual work. The second half — who it is allowed to contact, and who it never contacts — is what keeps a sequencer from embarrassing you. This gets sharper when a tool is expensive to experiment with. In a thread about Clay for a small company, a recurring complaint is that the platform punishes you for experimentation. A messy ICP plus a metered tool is how you burn a month of credits learning you should not have emailed those people.
This is the one-pager I would write, and the way I would keep it alive. Adjacent pieces: Signal-based prospecting, Lead scoring for early-stage SaaS, A founder-led outbound system. The work is also described on GTM engineer and GTM engineering. If the offer itself is still soft, take the App Launch Score before you refine a typography of buyers.
"Deciding who deserves a message today, and why"
An ICP your team will use has to answer that in a way a tired founder can apply on a Tuesday.
I would separate *fit* from *timing*. Fit is "this kind of company, this kind of person, this kind of problem." Timing is "why today," which might be a signal, an inbound, or simply "they are on the hand-built list we committed to this week." If you mix them into one vague paragraph, people will email anyone who looks vaguely right when they feel behind.
Write fit as rules, not adjectives. "Mid-market innovative companies" is not a rule. "B2B team of [range], in [regions], where a person with [role] owns [problem], and they already do [behaviour or tool] we can see or ask about" is a rule you can argue with. You will get the ranges wrong at first. That is fine, as long as the rule is written down so you can change it on Friday.
"Who it's allowed to contact, and who it never contacts"
This is the half teams skip, and it is the half that prevents damage.
The never-contact list should be boring and specific: current customers, open opportunities, people who asked to be left alone, competitors if that is your policy, companies you cannot serve well (wrong size, wrong geography, wrong use case), personal addresses if you have no policy for them, and anyone who is only on the list because a model or a vendor said they were "similar."
The allowed-to-contact list is not "everyone else." It is people who meet the fit rule, have a verified way to reach them, and have not been worked last week by someone else on the team. If your CRM cannot tell you that last part, fix that before you scale sending. Hygiene is not a side quest.
Put both lists on one page. If a new sequencer, intern, or "AI SDR" cannot obey the never-contact rules, it does not get access.
A one-page ICP template
Copy this into a doc your team actually opens.
Offer, in one sentence. What we sell, to whom, for what job.
In: company. Industry or use case, size range, region, and any must-have condition (for example, they run a function we sell to).
In: person. Roles we may contact, and the problem they have to live with.
Out: company. The "almost, but no" cases that waste weeks.
Out: person. Roles we do not contact even at a fitting company.
Never, regardless of fit. Customers, active deals, opt-outs, and any legal or reputational line you will not cross.
Evidence we need before a first line can mention a fact. If the evidence is missing, the first line stays plain or the row waits.
Timing (optional). The one or two signals that move someone up the queue, with a window.
Owner. Who may change this page, and when it is reviewed.
If the page is longer than two screens, you are writing a strategy memo. Cut it until a new contractor could follow it without a call, then have a call anyway to watch them try.
How to build it in a week, from real conversations
Do not start with a TAM model.
Days 1–2: list the last ten to twenty conversations that felt like a real fit, and the ones that felt like a trap. Write what they had in common, in boring words.
Day 3: draft the in and out rules. Argue with them. If two cofounders disagree, write both versions and pick one for two weeks.
Day 4: take twenty new accounts and mark them in, out, or unsure. If more than a handful are unsure, the rules are still adjectives.
Day 5: load the never-contact rules into whatever you send from, even if that is a sheet and a filter.
Friday: review who got a message, who should not have, and one change to the page.
Why teams abandon the document
- It was written to sound large, not to be used
- It lives in a slide deck no one opens before they hit send
- It is updated only at offsites
- The tool stack cannot enforce the never-contact list
- Founders override it every time a slightly famous company appears
The repair is social as much as it is documentary. Review the overrides on Friday. If the founder keeps making an exception for the same kind of company, change the rule, or admit the rule was theatre.
A metered enrichment tool will make this pain expensive, which is the Clay thread's useful warning. Get the rules usable before you pay to experiment at volume.
A short conversation you can use when two people disagree
Sit down with the last ten "yes, that felt right" accounts and the last ten "we should not have done that" accounts. For each, say out loud: company size, role, the problem, and what you wish you had known before the first message. Do not argue from a market map. Argue from those twenty rows.
If you still disagree, pick the tighter rule for two weeks, not the wider one. A tight rule you will actually honour teaches you something. A wide rule that exists to end the meeting will fill the sequencer with maybes, and the Friday review will become a negotiation all over again.
Write the decision, the date, and the date you will look at it again on the same page. An ICP without a review date is how the slide version comes back.
FAQ
Is ICP the same as a persona?
A persona is a story about a person. An ICP your team will use is a rule about which companies and roles may enter a motion. You can have both. You cannot send from a story alone.
How often should we change it?
When the Friday review keeps showing the same miss, or when the offer changes. Not every time a single email gets a polite reply.
What if we have two products?
Write two pages, or two clearly marked sections. A blended ICP is how the wrong offer is sent to the right company. If you want help turning this page into a motion with approvals and a list that respects it, Kingdom of Kumar builds and runs that system on Grok and Claude for $500 a month, three-month minimum. You own the rules, and you approve what goes out. We will not replace a missing ICP with a bigger tool.