A company can look relevant and still be a poor contact target. Similar industry labels, impressive growth, or a broad capability match do not establish a timely business reason to start a conversation.
The decision is narrower: does the available evidence justify spending attention on this relationship now? A useful answer must connect fit, timing, evidence, access, and a concrete next step. It should also make clear what is still unknown.
Start with the decision, not the company
Before researching a target, write one sentence that defines the decision:
Should Company A contact Company B within this time window, about this problem, with this proposed angle?
This sentence prevents the research from drifting into a general company profile. It also makes a negative result useful. A company may be strategically interesting but not contactable now; it may have a visible trigger but no credible fit; or it may fit well while the buying role remains inaccessible.
The five gates
1. Capability fit
State the specific capability Company A can bring and the problem it might solve for Company B. Avoid category-level statements such as “both companies work in manufacturing.” Name the process, constraint, user, or outcome that creates the relationship.
Useful evidence includes product scope, deployment conditions, technical boundaries, reference use cases, delivery geography, and explicit exclusions. A capability that cannot operate in the target environment is not a fit, regardless of semantic similarity.
2. Timely trigger
Look for a change that makes the relationship worth examining now: a new facility, product launch, capacity expansion, regulatory deadline, leadership mandate, procurement notice, quality issue, partnership shift, or disclosed investment plan.
A trigger is not proof of demand. It is a reason to test whether demand may exist. Record the event date, expected decision window, and the point at which the signal becomes stale.
3. Evidence strength
Separate direct facts from inference. A first-party filing, procurement notice, official product document, or named executive statement usually supports a narrower and stronger claim than a repost or unsourced summary. Several pages repeating one announcement are still one underlying source.
For every important claim, preserve the source, publication date, relevant excerpt, entity, scope, and any counter-evidence. If the evidence cannot support the outreach angle without adding assumptions, the priority should fall.
4. Access path
An opportunity without an owner is hard to advance. Identify the likely business user, technical evaluator, budget owner, procurement gate, and internal sponsor. Then distinguish a known access path from a guessed job title.
The access question is not merely “Can we find an email?” It is whether Company A has a legitimate route to the person who can validate the problem and whether the proposed message respects that person's role and context.
5. Actionability
Define the smallest next action that can reduce the most important uncertainty. This may be a ten-minute expert check, a targeted question to an existing contact, validation of a project stage, or a short note that offers one relevant proof point.
“Contact the company” is not an action plan. A defensible action names the person or role, the hypothesis to test, the evidence to reference, the question to ask, and the condition for stopping.
Do not let a total score hide a veto
A weighted score is useful for ordering candidates, but it should not average away critical failures. Strong fit cannot compensate for fabricated evidence. A recent trigger cannot compensate for a legal or ethical boundary. Easy access cannot compensate for having no relevant problem to discuss.
Use explicit gates before ranking:
- Eligible: no hard veto; enough evidence exists for a bounded hypothesis.
- Research: plausible relationship, but one decisive unknown must be resolved first.
- Observe: strategically relevant, yet timing or access is currently weak.
- Reject: evidence contradicts the fit, the signal is stale, or outreach would cross a boundary.
Only eligible candidates should receive a contact priority. The other states should receive a research or observation action instead.
A reviewable output
For each candidate, the final note should contain:
- Decision: contact, research, observe, or reject.
- Relationship hypothesis: why Company A and Company B may matter to each other.
- Confirmed facts: dated claims with sources.
- Inference: the reasoning that connects those facts to the hypothesis.
- Unknowns and counter-evidence: what could invalidate the opportunity.
- Access path: the likely roles and the known route, if any.
- Next action: one bounded step, owner, timing, and stop condition.
This format is more useful than a long company profile because another reviewer can challenge the evidence, reproduce the reasoning, and decide whether to proceed.
An anonymized example
Suppose Company A provides in-line inspection software. Company B announces a new production line. The announcement confirms timing and broad process scope, but says nothing about inspection architecture, incumbent suppliers, integration ownership, or budget.
The result should not be “high-probability sales lead.” It may be:
- capability fit: plausible, pending line-level requirements;
- trigger: confirmed and recent;
- evidence: one strong first-party event, no demand confirmation;
- access: engineering role identified, no trusted route yet;
- next action: validate whether inspection design is already frozen before preparing outreach.
The framework turns an exciting signal into a smaller, testable decision. That protects attention and produces a message grounded in what is actually known.
A short pre-contact check
Before sending anything, ask:
- Can every factual sentence be traced to a source?
- Is the relationship type explicit?
- Is the trigger recent enough to matter?
- Have repetition and independent corroboration been distinguished?
- Is the recipient connected to the hypothesis?
- Does the message state one relevant reason for contact?
- Is the key unknown turned into a respectful question?
- Is there a clear reason not to proceed?
Contact priority is not a prediction of success. It is a disciplined allocation of attention under uncertainty. The goal is to make fewer, better-founded approaches and to learn quickly when the relationship is not real.