Separate activity from its participants
A tender, construction project or investment plan shows that activity was published or disclosed in a context. It does not automatically identify every buyer or supplier involved. A relationship claim needs evidence connecting specific subjects, a defined relationship and a period—not just industry proximity.
Understand what a capability match contributes
A suitable capability may help explore whether a need has a possible fit. Budget, eligibility, location, timing, competition or evidence of access may still be missing. The opportunity remains potential while those dimensions are unresolved; it should not become a prospect through keyword overlap alone.
Keep distinct states distinct in a decision
A team can separately record observed activity, a declared capability, an inferred relationship and a confirmed relationship. Each answers a different question and requires different support. Activity sources should not be counted again as proof that a supplier participated, and uncertainty should survive an executive summary.
Seek relationship evidence when it matters
If a customer or contract relationship affects a decision, it needs evidence suitable for that predicate, such as an attributable disclosure, record or authorized confirmation. If it cannot be obtained publicly, the state remains unknown. AXIGNAL’s value is context and limits, not filling a sales pipeline. Procurement notices can identify an issuer, project owner or selected bidder, but those roles are not interchangeable. Attribution should follow the source’s exact description. If a company appears only as a possible supplier because of a stated capability, retain that inference and avoid language suggesting that a transaction took place.
Conceptual example
Hypothetical: a city publishes an energy-efficiency project and a manufacturer says it makes compatible controls. The activity and capability may be linked as context for a potential opportunity, but do not prove the city is a customer or that the manufacturer bid.
Scope and limits
AXIGNAL is not a CRM, lead database or contract-matching engine. Public activity does not confirm participants, demand for a supplier or a commercial relationship. Derived opportunities remain POTENTIAL by default; coverage depends on sources, geography and date.
Editorial basis
This page explains product doctrine and boundaries. It does not demonstrate source coverage or observed outcomes.
Read the product modelExplore AXIGNAL
Explore AXIGNAL