Matches

Matches is part of the Revenue objective.

A match identifies a company whose current state is relevant to a revenue objective and explains why, in terms of the evidence and assumptions behind the conclusion.

A match is therefore not a lead score attached to a name. It is an application of a company's maintained understanding to a specific objective.

A match only means something in relation to an objective.

The same company can be a strong match for one objective and a weak match for another, because different objectives care about different aspects of the company.

Matches apply the shared company understanding to a revenue objective rather than constructing a separate company for the purpose of matching.

This is why a match can be explained rather than merely ranked.

A match is produced by applying objective-conditioned reasoning to maintained understanding.

At a simplified level:

Evidence → Beliefs about the company → Revenue objective → Match

Because the beliefs behind a match are drawn from the company's maintained understanding, a match reflects what the evidence currently supports rather than a one-time read.

This also means a match can rest on beliefs established earlier, without rediscovering the company for the purpose of matching.

A match is expressed so that its reasoning can be inspected. It can show:

• why the company appears relevant to the objective;
• the evidence supporting each part of that relevance;
• the assumptions the conclusion depends on;
• where support is strong and where it is thin;
• and the uncertainty that remains.

This lets a team act on why a company matched rather than trusting a score without a basis.

A match preserves the reasoning path from the result back to its basis, which is the property of traceability.

From a match you can move toward its support:

Match → Belief → Proposition → Assumption → Evidence

A reviewer can therefore ask why the company matched and inspect the beliefs responsible, then continue to the evidence and assumptions beneath them.

A match does not need to claim certainty to be useful.

Where the evidence supports a conclusion only partially, or where a match depends on an assumption, that should remain visible rather than hidden behind a single number.

Where competing explanations remain unresolved, a match can preserve that tension instead of forcing one interpretation.

This keeps a match aligned with what the underlying understanding actually supports.

A match is not fixed at the moment it is produced.

Because it is built on maintained understanding, a match reflects revision.

New evidence can strengthen a match, weaken it, qualify it, or make it obsolete, and a match can change when an assumption it depends on is rejected.

A match therefore represents the current relevance of a company to the objective, not a one-time verdict.

A match can be inspected and challenged through verification.

Verification can occur at different levels. A reviewer might find that the underlying company belief is sound but should not have influenced the objective as strongly, or that a supporting assumption should be challenged, or that the evidence was extracted incorrectly.

When a verified correction changes the basis of the company understanding, the match is re-evaluated accordingly.

Matches are often kept and organized in lists for follow-up.

Because a list references maintained understanding rather than snapshotting it, matches kept in a list stay current as the companies behind them change.