Half of B2B positioning is conditional on a stack. If your product replaces a tool, integrates with one, or only makes sense alongside one, then knowing which companies run it turns a guess into a filter.
A filter, not a personalisation line
The strongest use of a technographic is deciding who to contact, not what to say to them. Opening an email with a detected tool name reads as surveillance to a lot of buyers, and the detection is not reliable enough to be worth the risk when it is wrong.
Used as a filter it is excellent. If your product only works alongside a particular platform, a list filtered on that platform is a fundamentally better list, and nobody receiving the email ever needs to know how it was built.
Inconclusive is a real answer
Plenty of software leaves no public trace on a company's website. The output distinguishes between detected, not detected and inconclusive rather than collapsing the last two, because treating an inconclusive as a no quietly removes real accounts from your market.
What you feed it
It starts from domains you already have, so it sits downstream of discovery rather than replacing it. A list build, another signal skill, or a plain CSV all work as the input.
Runs well with
Skills compound. These are the ones we usually install alongside it.