The problem this solves
The best intent signals often come from companies already in the CRM: past prospects, closed-lost deals, dormant accounts that a rep gave up on a year ago. When one of them starts researching <topic>, it is the warmest lead in the database, and nobody sees it because intent lives in a separate tool and the CRM records only what a rep last typed.
Cross-checking the whole HubSpot database against intent data closes that gap. The score and topics land on the company record where views and workflows can use them, the surging accounts are flagged, and the ten strongest are posted to #sales with their history attached, so the rep who owns each account can pick up where the last conversation ended.
How the mission runs
- Read the HubSpot companies. The Signals Agent loads every company in HubSpot with a domain, resolving domains for those that have only a name, and notes each company's lifecycle stage and last activity.
- Check intent on the topic. Intent data is queried for each company's activity on <topic> this month, returning the score and the related topics. Surges are identified where the score rose sharply against the previous period.
- Write scores and topics to the records. The intent score, the surge flag and the top topics are written to company properties as a reviewed batch, created if they do not exist, so lists and workflows can filter on them.
- Post the ten strongest surges. The ten companies with the largest surges are posted to #sales with the score, the topics, the account owner and the last CRM activity, so the owner knows the history before reaching out.
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
HubSpot companies carrying an intent score, a surge flag and top topics for <topic> as properties, and a #sales post naming the ten strongest surges with their owners and last activity. The report gives the number of companies showing any intent and the number surging, and highlights closed-lost and dormant accounts among the surges.
Make it yours
- Run it weekly and post only companies that newly surged since the last run.
- Create a HubSpot workflow trigger on the surge property to assign a task to the owner automatically.
- Feed the surging closed-lost accounts to the winback sequence playbook.
- Limit the check to closed-lost and dormant accounts, where a surge is most actionable.
Frequently asked questions
Does this cost credits for every company in HubSpot?
Intent lookups are metered per company checked, so large databases can be limited to a lifecycle stage or an owner to control spend.
What if a company has no intent data?
The property is left empty with the check date recorded, which distinguishes 'no activity observed' from 'never checked'.
Can I track several topics?
Yes. Each topic gets its own score property, and the post groups surges by topic.
How are surges compared across companies of different sizes?
Each surge is measured against the company's own baseline, so a small company with a sharp rise ranks alongside a large one, and the absolute score is shown beside the change.
Can the owner be notified directly?
Yes. Ask for a task or a Slack DM per surging account and the owner receives it with the score and the last CRM activity.
What about companies with no domain in HubSpot?
They are resolved from the company name first; those that cannot be resolved are listed so the records can be fixed.
Can the surge property feed lead scoring?
Yes. Once the intent score exists as a property, HubSpot's scoring can weight it, and the fit score playbook can blend it with firmographic fit.