Keep these three things.
- Trace the event to a dated, first-party source where possible.
- Explain the possible connection in one careful sentence.
- Use uncertainty to choose whether to research, write or stop.
Define a signal that matters to your offer
Start from the work you do. Ask which observable company changes could make that work more relevant now: a new product line, a leadership appointment, a new location or a hiring plan. Avoid generic triggers that merely indicate activity.
Write down why the event might matter before collecting a list. If the connection depends on several unsupported assumptions, the signal is too weak to justify outreach. A useful trigger reduces timing uncertainty; it does not manufacture fit.
Check the original event
Prefer the company’s own announcement, careers page or product update. Record the source URL, the event date if shown and the date you checked it. Search snippets and third-party summaries can help discovery, but verify the underlying claim before using it in a message.
Confirm that the event refers to the correct organization and is still current. Similar company names, old announcements and undated pages can all create false relevance. If you cannot verify the event, say so internally and do not present it as fact.
Separate observation from interpretation
“The company is hiring a client-services lead” is an observation if the current listing supports it. “The team is overwhelmed with handovers” is an interpretation that needs separate evidence. Keep both statements distinct in your notes.
The connection to your offer should be framed as a possibility, not a diagnosis. You may have a timely reason to ask a question; you do not yet know the company’s priority, budget, process or satisfaction with its current approach.
Choose a proportionate next step
A strong signal may justify a short, specific note to a verified person. A weak or stale one may justify more research or no action. If you do write, state the observable event accurately and ask a question that lets the recipient correct your interpretation.
Stop when the person declines, the contact is wrong or the evidence no longer supports the reason for writing. Do not keep sequencing messages simply because a system can. Respect suppression requests and the laws and platform rules that apply to your audience.
From event to decision · fictional business
Event: a studio advertises a client-services lead role.
Possible relevance: the role may take ownership of client handovers.
Unknown: whether handovers are difficult or a current priority.
Next step: verify the role and ask one open question, or skip if the evidence is stale.
Continue the method
Link each statement in the draft to evidence that supports it.
A first signal does not justify repeating the same message indefinitely.
This is practical editorial guidance, not a report of customer performance. Product previews show example work; available actions depend on the live Scout service and the permissions you configure.