The problem this solves
The best-fit account for a complementary product is one that has already adopted the platform it plugs into and has not yet filled the gap the product covers. Both facts are readable from the outside through technographics, but most lists stop at the first: 'companies using <technology A>' is a large, undifferentiated set that includes everyone who already solved the problem with <technology B> or an equivalent.
The absence signal is what sharpens the list. A company running <technology A> without <technology B> is either unaware of the gap, has decided to live with it, or is about to fix it, and all three are conversations worth having. Because absence is inferred rather than observed, the evidence has to be shown per row: what was detected, what was looked for and when, so a rep can trust the row before opening with it.
How the mission runs
- Find companies running the first technology. The Prospecting Agent uses technographics to find companies with <technology A> detected, then firmographics to keep those with 100-2000 employees. Detection date and the property where it was seen are kept per company.
- Check for the second technology. Each company is checked for <technology B> and for the closest substitutes you name. Companies where any of them is detected are removed. The row records that the check ran, the date and which substitutes were looked for, so the absence claim is explicit.
- Rank by how settled the first technology is. Companies where <technology A> has been in place for a while and is detected across several properties rank above fresh or partial deployments, because the gap has had time to hurt. Recent adopters are kept but marked, since they may be mid-rollout.
- Save the list and export to Drive. The result is saved as list <name> with the evidence columns and exported as a CSV to Google Drive. The list keeps both technology criteria so a refresh later adds new adopters of the first technology who still lack the second.
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> and a CSV in Google Drive of companies with 100-2000 employees running <technology A> and showing no detection of <technology B> or its named substitutes, each row carrying the detection evidence for the first, the date and scope of the check for the second, headcount, industry and HQ. The report states how many companies run the first technology in the size band and how many of those lack the second.
Make it yours
- Name three substitutes for <technology B> so the absence check is stricter and the list is cleaner.
- Add the person who owns <technology A> at each company with a verified email, and the list becomes outreach-ready.
- Turn the top 300 into a LinkedIn company-matched audience for a campaign aimed at the gap.
Frequently asked questions
How confident is an absence claim?
Detection can miss tools that run only behind a login, so the row shows exactly what was checked and where. Treat absence as a strong hint rather than a certainty, and let the first conversation confirm it.
Can I use a category instead of a specific second technology?
Yes. Say 'no marketing automation platform' and the agent checks the common tools in that category and lists which ones it looked for.
What does the ranking use?
How long <technology A> has been detected and across how many properties, which approximates how embedded it is; you can ask for headcount or funding recency to be weighted instead.
How often should the list be refreshed?
Monthly suits most categories. Each refresh adds new adopters of <technology A> that still lack <technology B> and removes companies that have since filled the gap, and the change log records both movements with dates.