The problem this solves
Adoption is a decision made recently by someone who is still paying attention. A company that added <technology> in the last month has a project under way, a budget that was just approved, and a team looking at what else the new platform needs. Everything that complements or extends the technology sells best in exactly this window.
Detecting adoption requires history rather than a snapshot: the technology must be present now and absent before. Technographic change data provides that, and the rest of the mission is the familiar work of enrichment and ICP filtering. Saved as a list, the result keeps producing new adopters every time it is refreshed, which is the difference between a one-off list and a signal.
How the mission runs
- Find first-seen detections in the window. The Signals Agent queries technographic change data for companies where <technology> was first detected in the last 30 days, capturing the detection date and the property where it appeared.
- Enrich the adopters. Each company is enriched with headcount, industry and HQ through the firmographic waterfall so the ICP filter can be applied on current data.
- Keep the ICP fits. Companies outside your headcount band, industries or regions are dropped and counted; the rest are ranked by how closely they fit and by how many properties show the new technology.
- Save and export. The adopters are saved as list <name> with the detection evidence and exported as a CSV to Google Drive. Because the list stores its criteria, a refresh adds next month's adopters without rebuilding.
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
List <name> holding every ICP-fit company that adopted <technology> in the last 30 days, each with the detection date, the property where it was seen, headcount, industry and HQ, plus a CSV in Google Drive. The report shows how many adopters were detected in total and how many fell inside your ICP.
Make it yours
- Add the person most likely to own the new technology with a verified email, and the list becomes an outreach list.
- Track adoption of any of several technologies and get a column for which one triggered each row.
- Schedule a monthly refresh and post the new adopters to #sales.
- Combine with hiring data to keep only adopters also hiring for the technology, the strongest sign of a serious rollout.
Frequently asked questions
How reliable is a first-seen date?
It is the date detection began on the company's public properties, which follows adoption by days to weeks. The row shows the date and the property so you can judge it.
Can I see adoption over a longer period?
Yes. Ask for 90 days and the list is larger; the 30-day window is the default because the timing advantage fades after that.
Does it distinguish trials from deployments?
Detection across several properties suggests a deployment; a single property suggests a pilot. The row records the property count so you can weight it.
Which categories of technology can be tracked?
Any technology the technographic sources detect on public properties - CRMs, marketing platforms, analytics, e-commerce, payments, infrastructure and many more. Ask for a category and the agent lists the tools it can watch.
Can I be alerted rather than running it monthly?
Yes. Turn it into a standing watch and each new adopter inside the ICP is posted as it is detected.
Does it show what the company used before?
Where a previous tool in the same category was detected and removed, the row names it, which is useful context for the first message.