Which buying signals deserve a response?

“The company posted two maintenance vacancies” is an observation. “The plant is struggling to maintain its equipment” is an inference. “We should call the operations director” is a proposed action. Keeping those statements separate makes the uncertainty visible.

The same event can mean different things. Hiring may reflect expansion, replacement or work moving in-house. An announced site may still be far from opening. The useful question is which part of your offer could matter, given the account’s situation, and what needs checking before anyone acts.

Keep the account and relevant site, the observed change, its original source and the date you checked it. Record the publication date and event date separately when available: an old announcement found today is not a new event. Add the relationship owner, relevant history, the possible commercial connection and the next unanswered question. Preserve a link someone can open.

Check whether the evidence still applies. For a vacancy, return to the employer’s page and inspect its status and dates. Google’s structured-data guidance for job postings requires expired postings to be marked or removed from its job-search experience. A search result alone cannot confirm that a role remains open. Record when the underlying page was checked.

Start with the account’s fit, then add the relationship. An existing customer’s new site may matter to a supplier that already serves its other locations. A former staffing client’s vacancy may be relevant when it matches the roles previously filled. In both situations, the history changes who should review the event and what they should ask.

Reject a generic connection such as “they are growing, so they need help.” Name the service, product or decision the event could affect. If that sentence needs several unsupported assumptions, gather more evidence before adding the account to someone’s call list.

Several news sites repeating one announcement are one underlying event. Group reposts under the original source. Separate “a source repeated this” from “a second independent observation supports this.” Volume can otherwise make a weak hypothesis look established.

Apply the same discipline to an intent-data alert or a company-level website visit. Ask what was observed, how activity was matched to the account and what uncertainty the provider reports. A company label does not identify the person behind the activity or establish a purchase decision. Keep inferred activity distinct from a direct request or a conversation recorded by the team.

For example, HubSpot describes matching website activity to companies using data including IP addresses. Its tracking-code documentation explains the role of account settings and visitor consent preferences. These are properties of the observation method, not evidence of an individual buyer’s requirement. The website-activity guide develops that distinction.

Consider four records beyond a prospecting queue. Repeated buyer questions about installation requirements can prompt the content owner to review an explanation. An existing customer’s new site can prompt an expansion review. Slowing orders with an unresolved delivery query can prompt an order and service review. An event linked to the wrong company should create a data correction, not customer contact.

For each, write the observation, interpretation, review rule and permitted action as separate fields. A service record might say: “Orders below the usual pattern; delivery query open; cause of the change unknown; service owner checks the current issue before the account owner asks about future requirements.” The possible explanation remains visible without becoming a claim of dissatisfaction.

Monitoring and no action are also valid outcomes. State the condition that would justify another review, such as a confirmed site date or an answered technical question. Keep a rejected event’s reason so the next alert does not restart the same investigation. The account prioritisation guide helps put this work alongside existing commitments and available capacity.

If the evidence does support an outbound task, use the connected campaign guide to agree the audience, context, contact checks and handover. The campaign should receive the checked record rather than a raw alert with an assumed sales story attached.

Before sending or calling, name who checks the channel, recipient, market requirements, relationship and recorded exclusions. A public announcement does not supply those answers. Keep the check connected to the tool that creates the next action, so an excluded account cannot simply re-enter through a fresh alert.

Distinguish permission to research an account from permission to contact a person. Record who approved the next step and what remains prohibited. The tools and agents guide explains why this boundary belongs in the working system.

1. Reconstruct the evidence. Find the original source, remove repeats and mark stale or uncertain information. Keep the raw alert alongside the corrected record.

2. Choose one next action. Ask the relevant owner to choose research, service work, a content review, a commercial conversation, monitoring or no action, with a reason. Record whether contact is appropriate and which checks it depends on.

3. Review what happened. Track whether the alert was useful, the next step occurred and the hypothesis held up. An alert may arrive correctly yet have no commercial relevance. Use the review findings to refine what the watchlist collects.

Choose a small set of company pages and record what each check establishes. Keep checks with no relevant change and coverage gaps visible. The account watchlist guide specifies sources, identity, cadence and failure handling; the implementation planning guide helps define a first release. In a Build campaign, relevant observations can guide account selection, the contact route and timing alongside the agreed operation. A standalone signal review or workflow is scoped separately. Use the workflow specification to retain the human decisions and permitted actions.