Separate what you know from what you need to ask
A company can match your size and industry filters without experiencing the problem your product solves. An ICP should describe the operational condition in which your product creates value, the constraints that make adoption possible and the disqualifiers that make a sale unsuitable.
For each target, save the source URL, date, observed fact, pain hypothesis and validation question. A funding announcement is an observation about capital, not a prospect's consent, budget or need. Research quality improves when a seller can see why a hypothesis was made and how a buyer could disprove it.
Prioritization should consider account fit, plausible urgency, contact coverage and commercial feasibility. Avoid one opaque numeric intent score that hides unsupported assumptions. The related worksheet and worked Schematic brief show how to make research inspectable and useful at the next conversation.
How do we build an ideal customer profile for a B2B product?
Build an ICP from the operating conditions behind real wins and losses: problem, workflow, buyer roles, adoption constraints, economics and disqualifiers. Add evidence and a validation question for each condition. Industry and employee count can help filter accounts, but they do not establish whether your product solves a meaningful problem.
What belongs in an ICP worksheet with evidence and disqualifiers?
Include account identifier, operating condition, source URL and date, observed fact, pain hypothesis, relevant roles, adoption constraint, disqualifier, confidence and next validation question. A good worksheet lets a seller inspect the reasoning and reject an account. Leave unknowns explicit instead of filling every field with AI-generated certainty.
What is the difference between an ICP and a buyer persona?
An ICP describes which organizations and operating conditions fit your product. A buyer persona describes a relevant person's role, responsibilities, pressures and influence in the decision. Use the ICP to select accounts and personas to plan conversations. Neither should claim private pain or budget without validation, and enterprise purchases usually involve several roles.
How do we prioritize accounts within our total addressable market?
Prioritize TAM accounts by operational fit, credible reason to investigate, reachable stakeholders, adoption feasibility and commercial value. Keep the supporting evidence visible. A large nominal market or opaque intent score is less useful than a smaller cohort your sellers can explain, reach and serve responsibly.
Which buying signals justify outbound without pretending to know intent?
Use public signals as reasons to investigate, not proof of buying intent. Product launches, hiring, pricing changes, funding and technical documentation can support a relevant hypothesis when connected to your product's problem. Save the source and date, explain the possible consequence and ask a neutral question that could disprove it.
Does funding mean a prospect has a buying need?
No. Funding establishes that a company announced capital under the reported terms; it does not establish a buying problem, available budget, intent or approval authority. It can justify research when your product connects to the company's next operating stage. Confirm the actual problem and buying decision before treating the account as an opportunity.
How should we validate a pain hypothesis from public company information?
Validate a public-research pain hypothesis by preserving the source fact, stating the inference and asking a buyer about the actual workflow and consequence. Seek disconfirming evidence as well as agreement. Public information can make discovery more relevant, but it cannot establish private operational pain on its own.
How do we identify the buying committee for enterprise software?
Map the actual decision roles: problem owner, users, technical evaluator, budget authority, procurement, legal and possible blockers. Begin with hypotheses from public roles, then validate responsibility and influence in discovery. A senior title or enthusiastic champion is not proof that a person controls the purchase.
What makes a researched target account different from a qualified lead?
A researched account has source-backed fit observations and a hypothesis worth testing. A qualified lead or opportunity requires the agreed buyer evidence and an owner who accepts the next commercial step. Public fit, a verified email or a funding event does not establish an active buying decision. Define the terms in your operating system rather than relying on the label lead.
How do we reject poor-fit accounts before wasting sales time?
Reject poor-fit accounts using explicit product, problem, adoption and economic boundaries before investing substantial selling time. Keep the reason and source so the team does not repeatedly rediscover the same mismatch. Distinguish confirmed disqualification from missing information; uncertainty may need research rather than automatic rejection.
Schematic