The problem this solves
Two technology changes matter more than any other to a replacement product. A company that dropped <competitor tool> has just lived through the pain of leaving it and is choosing what comes next; a company that adopted <technology> has committed to a platform your product is built for. Both changes are visible from outside, and both are invisible in any list that describes the present without describing the past.
The quarter is the right window because technology changes are slow to show and slow to act on. Seeing the direction - dropped or added - and the date the change was detected lets a rep sort by urgency and choose the right message: a replacement pitch for the drop, an extension pitch for the adoption. Delivered to #sales with a CSV, the list is a quarter's worth of the best-timed conversations.
How the mission runs
- Query technographic changes for the quarter. The Signals Agent reads technographic change data for two events: <competitor tool> no longer detected where it previously was, and <technology> newly detected. Both are limited to the current quarter, with the date each change was observed.
- Record direction and confidence. Each row is labelled dropped or adopted, with the date and the property where the change was seen. Drops are checked against the company's other properties so a redesign of one site is not mistaken for leaving the tool.
- Enrich with firmographics. Headcount, industry and HQ are filled through the waterfall so the list can be filtered to your ICP and sorted by size.
- Post to #sales with the CSV. The list is posted to #sales grouped by direction, with one line per company and a CSV attached carrying every column. Rows are ordered by change date so the most recent moves sit at the top.
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 post in #sales listing every company that dropped <competitor tool> or adopted <technology> this quarter, grouped by direction, with the change date, the property where it was observed, headcount, industry and HQ per company, plus a CSV of the same rows. The report states the total drops and adoptions detected and how many fall inside your ICP.
Make it yours
- Add the tool owner at each company with a verified email for immediate outreach.
- Watch several competitors at once and get a column naming which tool was dropped.
- Run it monthly as a standing mission so each post covers only that month's changes.
- Create HubSpot tasks for account owners at companies on your target list that appear in the post.
Frequently asked questions
How does the agent avoid false drops?
It checks whether the tool disappeared from all of the company's monitored properties or only one, and marks partial drops separately with lower confidence.
Can I see what replaced the dropped tool?
Often, yes. Where a new tool in the same category was detected around the same time, the row names it, which is useful for understanding the switch.
Is this the same as intent data?
It is a behavioral signal from the company's own properties rather than research activity; the two combine well, and the intent playbooks can be layered on this list.
Can I limit the list to a size band?
Yes. Name the headcount range and industries and the firmographic filter is applied before the post, with the counts removed reported.
How far back can changes be traced?
Technographic history reaches back well beyond a quarter; ask for a longer window on the first run and then keep to quarterly for the standing version.