The problem this solves
Target account lists go stale in the way that matters most: the accounts change and the list does not say so. A leadership role is posted, a round closes, the marketing platform is swapped, and the rep working the account learns about it from the prospect, months late, if at all. The information was public the day it happened.
A standing watch turns the list into a live object. The Signals Agent checks each company for the three changes that most often open a conversation and posts only when something moved, with the evidence attached and a one-line suggestion of what to do. The channel stays quiet on quiet weeks, which is what keeps people reading it.
How the mission runs
- Register the watch on list <name>. The Signals Agent records the current state of each company on the list - open leadership roles, latest round, detected core technologies - as the baseline for change detection.
- Check for the three changes on a cadence. On the cadence you set, hiring data is checked for new VP or C-level postings, funding data for new rounds, and technographics for changes in CRM, marketing automation, analytics or infrastructure. Only differences against the baseline count as events.
- Attach evidence and a suggested action. Each event carries its source - the posting, the announcement, the detection - and a one-line suggested action, such as reaching the new leader once they start or referencing the round in the next touch.
- Post alerts to #account-alerts. Events are posted to #account-alerts as they are detected, one message per account per run, and the baseline is updated so the same change is never posted twice.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A standing mission that posts to #account-alerts whenever a company on list <name> posts a leadership role, announces funding or changes a core technology, each alert carrying the evidence link and a suggested action. A weekly summary counts the events by type so you can see how active the list is, and the list itself accumulates a change history per account.
Make it yours
- Add expansion news and office openings as a fourth event type.
- Route alerts per account owner by reading the owner from HubSpot and posting to their DM.
- Create a CRM task instead of a Slack post, using the signal-triggered tasks playbook.
- Send a weekly digest instead of real-time alerts for teams that prefer one post.
Frequently asked questions
How often does it check?
Daily by default; weekly for large lists where a day's latency does not matter. You set the cadence in the prompt.
Will it flood the channel?
No. Only real changes against the baseline are posted, and a quiet week produces only the short summary.
Can I add companies to the watch later?
Yes. Anything added to list <name> is baselined on the next run and watched from then on.
What counts as a core technology change?
A tool added or removed in the categories you name - CRM, marketing automation, analytics and infrastructure by default - detected on the company's public properties, with the property and date recorded.
Can alerts include the person to contact?
Yes. Ask for the relevant leader with a verified email and each alert carries a contact and a suggested opener.
What does it cost to run?
Daily checks are metered per company; enrichment and verification are spent only when an event fires, so a quiet list costs little to watch.
Can I pause the watch for an account in an active deal?
Yes. Mark the account in the thread or in the CRM and its alerts are held until you resume them, so a rep mid-negotiation is not surprised by a channel post.