Static lists age the moment they are created
Industry, size and region tell you who might buy. They do not tell you what is happening now. In prospecting, timing can matter as much as profile.
Signals that change context
A hire, tender, expansion, decision-maker change or public complaint can alter whether a conversation makes sense. The signal should retain date and source.
Research before contact
Sibila and similar architectures can combine fit, signals and context to prepare a commercial hypothesis. The goal is not automated spam; it is deciding who deserves research and when.
Fit describes structure; timing describes change
Size, industry, geography and installed technology tend to change slowly. Timing appears when something happens: expansion, a new decision maker, incident, tender, hiring or project. Mixing both dimensions into one number hides why an account is relevant now.
Signals need date and source
An event without time loses operational value. Knowing a company “is hiring” is insufficient if the evidence is nine months old. Each signal should preserve provenance and time so the system can distinguish current context from a historical characteristic.
Absence is informative too
Finding no recent signal does not prove lack of interest, but it changes strategy. It may justify lower priority, more research or a different message. Keeping missing data as missing prevents silence from becoming an invented story about intent.
Two axes enable two actions
An organization with high fit and low timing may enter observation; one with medium fit and high timing may deserve immediate research. Separate axes create more explainable decisions than a ranked list where nobody knows what elevated each account.
Timing is dynamic
A good list today can be poor next week. The system therefore needs to refresh signals and record what changed rather than generate a prospect database once. Useful commercial intelligence looks more like maintaining state than exporting a final CSV.
A useful test
One concrete way to put this idea under pressure is to hold an account profile constant while varying only recent events and observe whether priority changes without redefining what makes a good fit. The test should not ask only whether an answer appears, but which state remains, what evidence is preserved and whether another operator can understand why the system behaved that way. This turns an editorial principle into an observable property and exposes places where architecture still depends on invisible assumptions.
What this note does not claim
Timing signals do not prove purchase intent; they indicate contextual change and should trigger investigation rather than automated mind-reading. This distinction matters because a good practice stops being useful when it becomes a universal promise. The goal is to make one design boundary explicit so it can be discussed, tested and adapted to the domain while facts, inferences, permissions and decisions remain separate.