Technographic data API: what a company runs, as rows

Those are different products that happen to share a label. A website scan sees the script tags, the payment widget and the analytics library on a public page, including on a small shop that never hires. A job posting reveals the systems a company is about to spend money on, because it is hiring somebody to run them. A field on an enrichment record is whatever the provider's own index holds, refreshed on its schedule rather than yours.

The directory carries the posting-led source as a full review, TheirStack, and the website scanner as a comparison-only record, BuiltWith.

Most of the rest are enrichment providers that return technographics beside firmographics, Apollo, Crustdata and ZoomInfo among them. They are the cheapest route when you already enrich people with one of them.

So the first decision is not which vendor. It is which of the three questions you are asking: what is on the site, what are they hiring for, or what does a broad company record say. The rest of this page sorts the providers by that question, then by what a lookup costs and how fast you can ask.

The source is the part a vendor page rarely leads with, and it is the part that decides whether a row is useful for outbound. A stack read off a website is evidence that a technology is installed. A stack read off job postings is evidence that a team is working in it this quarter. Neither says the other.

The three sources line up with the providers like this, and each line is read off that provider's own record:

• The website itself. BuiltWith detects the technologies on a site and sells them two ways: one domain at a time by the credit, or the list of every site using a technology on a monthly plan. It is carried here as a comparison-only record, which is why it is not in the grid below. DataForSEO's Domain Analytics API also detects the technologies on a site, from $0.012 a task, pay as you go.
• Job postings. TheirStack sells job postings and technographics as rows: every posting a company has published, the technologies those postings and its stack reveal, and the firmographics around them. Hiring for a system is a budget signal as well as a stack signal.
• A field on the company record. Apollo returns a technology stack with its organization enrichment, Crustdata adds technographics as a paid add-on to a company record, and Clearbit's successor, HubSpot data enrichment, which HubSpot launched as Breeze Intelligence, covers more than 40 attributes that include technologies. ZoomInfo, Lusha and RocketReach carry technographics on their company data too.
• A filter rather than a field. Cognism lists technographic filters among its prospecting features, and Crustdata's docs say its search filters on technographics without returning them. A filter builds a list; it does not hand you the stack to store.

Pick the source first, then the vendor. A team selling an integration wants the posting signal; a team selling to ecommerce sites that rarely hire wants the website scan.

Two different calls hide behind "technographic data". One takes a domain you already have and returns its stack. The other takes a technology and returns every company that runs it. The first is enrichment; the second is list building, and it is usually the one a sales team actually wants.

The list is where the prices diverge. BuiltWith gates it behind a monthly plan from $295. TheirStack filters companies by technology through its API at 3 API credits a company with no separate list plan, out of the same monthly API credits, and can push new matching companies to a webhook as they appear. Crustdata filters a company search on technographics and bills 1 extra credit a result on top of the 0.03 base, so size the result set before you run it at scale.

Enrichment by domain is cheaper and more common. Apollo, Crustdata, ZoomInfo, Clearbit through HubSpot and BuiltWith all do it, and Findymail lists technologies by domain among its endpoints, each with its own credit rule. If you already enrich people with one of these, the stack may be one more field on a call you already make.

The honest answer for most teams is both: build the list from the source that fits the motion, then enrich the survivors with whatever provider already sits in your waterfall.

A stack on its own is a filter, not a message. The teams that get value out of a technographic data API use it in one of three ways, and each one wants a different source.

The first is fit: only sell to companies running a system you integrate with. That is a list-building job, and the cheapest honest route is a technology filter that returns companies rather than one lookup per domain, which is what TheirStack's company search and BuiltWith's Lists plans are for.

The second is timing. A company posting for an administrator of a platform you replace, or for an engineer in the language your product targets, is telling you about budget this quarter. Job postings are the source that carries that, which is why the posting-led provider is the usual answer for a sales team rather than a marketing one.

The third is personalization at the moment of research: an agent or a rep looking at one account and wanting the stack beside the contacts. That is enrichment by domain, and it is cheapest from a provider you already call for people, as one more field on the same request.

Write down which of the three you are doing before you buy, because a team that wants timing and buys a website scan will get an accurate list of companies that are not in market.