Technographic Data Providers by Method, Coverage and Price

A technographic data provider sells company-level records that show which software and infrastructure a business runs. That covers the CMS and analytics on its website, and sometimes the CRM, ERP or cloud tools behind it. Most providers bundle this with firmographics such as size, industry and location. Many also add named contacts.

These are the names buyers usually compare:

• BuiltWith and Wappalyzer, which read websites.
• TheirStack, which sells job postings and technology data together.
• ZoomInfo, which puts tech insights inside its higher credit tiers.
• G2, which reports company-level research activity on its own review sites.
• Demandbase, whose main signal is intent.

On their own pricing pages, they range from one-time credit packs to no published price at all.

Choose by collection method before you choose by brand. The method decides what a provider can see, and every method has a blind spot.

In outbound, the database is the fuel, and a technographic filter is an optional sieve on top of it. When a campaign goes quiet, I ask for the list first. I read the emails after.

What does a technographic data provider actually sell?

Three kinds of data travel under one label:

• Technographic data: which tools a company runs.
• Firmographic data: what kind of company it is, such as headcount, industry, revenue band and location.
• Contact data: the named people, with titles, emails and phone numbers.

The first two describe the company. Contact data describes people, and that is where data protection law attaches. Many packages include mobile numbers. We do not cold call from them. Phone enters only as an optional warm follow-up to people who have already replied or opted in.

Vendors package this data as three products:

1. Install lists. Every company detected running a given tool, filtered by country, size or industry.
2. Enrichment or appending. You upload the CRM records you already hold, and the vendor fills empty fields such as tech stack, industry or headcount.
3. Raw datasets and APIs. Bulk files or live endpoints, for teams that want to plug the data into their own systems.

A provider collects its own data directly. BuiltWith, for example, says it does not get data from any third parties (BuiltWith FAQ). An aggregator routes several providers' data through one account. You get wider coverage, but you lose sight of where a given record came from. Appending is a service that providers and aggregators both offer.

For a founder, the useful question is where this sits in a list build. Build lists in established databases such as Sales Navigator, UpLead or ZoomInfo, because a built list beats a scraped one (the prospecting databases comparison covers those). A stack field is one more filter you run on that list once it exists.

How is technographic data collected, and what does each method miss?

Vendor documentation describes four ways of getting the data. Two of them detect installed tools. The other two pick up research activity, which buyers often mix up with stack data.

If a vendor does not state its method, treat that field as unproven until your own test says otherwise.

A job ad naming a tool is a hint. The company may be hiring to replace that tool, or to run it for the first time next year.

Which providers sell which data?

What each vendor's own pages say you get, and who that suits:

BuiltWith vs Wappalyzer. Both work from websites, but they suit different jobs.

• BuiltWith says it tracks 128,051 technologies across 491.9 million domains, with history going back 41 years (BuiltWith plans). That depth suits market sizing and spotting when a company added or dropped a tool.
• Wappalyzer prices its plans in technology lookups and bundles email verifications into every paid plan (Wappalyzer pricing). That suits a small team checking domains it already has and cleaning the contacts in the same tool.

The decision rule: if your question is "how many companies run tool X," start with BuiltWith. If your question is "what does my current list run," start with Wappalyzer.

Expect to combine sources. A Forrester survey from early 2023 found that more than 70% of intent data users source it from several providers. Almost half receive data from three or more sources (Forrester). It covers intent rather than installs and is more than three years old, but the point holds: teams that lean on company signals rarely get everything from one feed.

What do technographic data providers cost?

Prices below are copied from each vendor's own pricing page, with the billing unit stated, at the time of writing.

Sources: BuiltWith, Wappalyzer, TheirStack, ZoomInfo.

Compare per unit. Domains, companies, lookups and credits are different units, so plan prices cannot be compared directly.

• TheirStack: $109 for 1,000 companies -> about 11 cents a company. $999 for 200,000 -> about half a cent.
• Wappalyzer: Pro's 5,000 lookups work out at about 5 cents each, but only if you use every one before they expire.
• BuiltWith: charges per account plan, so your cost per record depends on how many lists you pull in the month you pay for.

The other names that come up in the same searches price in very different ways. Each row comes from that vendor's own pricing page:

Sources: the pricing pages of G2, Demandbase, HG Insights, 6sense, Cognism, Coresignal and Clay, all read at the time of writing. Clay and Coresignal sell enrichment and raw company data rather than a stack index, so their credits buy a different unit again. G2's Starter plan does not include Buyer Intent, so its price tells you nothing about what the intent data costs.

For every vendor you shortlist without a published number, ask for a written quote that names four things:

• The unit (seat, credit, record, domain or API call).
• The minimum term.
• What happens to unused credits.
• Whether technographics are an add-on.

For the people side of the cost, see what B2B contact data costs per contact and per seat.

On outbound projects, data, tools, domains and mailboxes are billed to the client directly and sit outside our monthly fee. So the data invoice is yours to judge.

How do you test a provider before you pay?

Headline coverage describes the vendor's index, not your market. A test against companies you already know does, and it is quick once the domains are in a sheet.

I always start a list with a client's past and current customers, and only then look for companies like them. The test follows the same order:

1. Pull the past and current clients whose stack you know for certain. You can check every answer, so every miss is real.
2. Note the 1 to 3 tools per account that matter for your offer. These might be the system you integrate with, the competitor you replace, or the platform you sell into.
3. Run the domains through the free tier or trial.
4. Mark each tool as a hit, a miss or a false positive. A false positive means the vendor lists a tool the company does not run. Even a vendor admits this happens. PredictLeads, which sells technographic data, says a script found on a website may not prove the company actively uses the tool.
5. Take a batch of lookalike accounts you have never sold to. Check their stack by hand from their website and current job ads, then score the vendor on those too.
6. Run the same accounts through every vendor on your shortlist, so the scores compare like with like.
7. Only then try the filters you plan to pay for.

Score each row on a sheet like this:

Write your pass mark down before the first run: the share of known tools the vendor must find, and the false positives you will accept. A good demo then cannot move it. A provider that misses the tools you know on your own clients will miss them on strangers too, and false positives on accounts you know well mean more of them on accounts you do not.

Any contacts that come with the export get the same treatment as every list my team sends out. Every address is verified with NeverBounce or DeBounce before use, and we keep bounces under 0.5%.

The same goes for cheap data. In my experience, a list bought cheap from a freelancer opens poorly and bounces hard. Then the email gets blamed, and nobody opens the spreadsheet. Before anything is sent, audit the lead list line by line.

When is a technographic filter worth it, and when should you skip it?

Match your situation to a row before you buy.

The small-market row needs the reasoning. Say only about 10 of your 2,000 target companies show any intent signal at all. We skip intent data there and write one offer that fits the whole market. That rule is about intent.

My read, not a tested result, is that the same logic applies to stack filters: in a market that small a filter shrinks an already short list, and the companies it removes may still buy. The trade-off is laid out in how a small team should weigh intent data.

Copy cannot rescue a bad list, and neither can a stack filter. If the base list has wrong titles and unverified addresses, technographics only decide which wrong people you write to.

Volume matters too: in our campaigns, 30-35 booked calls a month has needed at least 10,000 people contacted a month, so a filter that cuts the list hard has a price. Shrink it to 50 to 100 perfect-fit accounts a month and you are playing a coin flip: some of those people will be busy, some not ready, some not interested.

What does the law say about buying third-party B2B data?

Pure company data, such as "this domain runs a given CMS," is usually not personal data. A named contact is. The ICO's B2B marketing guidance says UK GDPR applies when a business contact can be identified, for example from a name and phone number on file, or an email address like initials.lastname@company.com.

When you hold personal data that came from someone other than the person themselves, GDPR Article 14 sets out what you owe them (GDPR on EUR-Lex):

• Art. 14(2)(f): you must tell them which source the data came from, and whether the source was publicly accessible.
• Art. 14(2)(b): if you rely on legitimate interests, you must state which interests.
• Art. 14(3): the information is due within a reasonable period, and no later than one month. If you use the data to contact the person, it is due at the latest with your first communication.

For outbound, the first message is usually your deadline. That means the sequence needs a short line saying where you got the address, plus a link to your privacy notice.

Buying a list does not hand your duties to the seller. The ICO says your use of personal data on a bought list must comply with UK GDPR. Its guidance on using marketing lists adds that you must check the list is accurate and that the details were collected fairly.

When someone opts out, record them on a suppression list instead of deleting them. Otherwise your next data purchase can bring them straight back.

Email rules depend on who you write to:

• Corporate subscribers: PECR needs no prior consent. You still must not hide your identity, and you must give a valid opt-out address.
• Sole traders and some partnerships: the ICO treats them as individual subscribers, so you need consent or the soft opt-in before emailing them. If you are unsure which kind of subscriber you have, the ICO says to treat them as an individual.

Both ICO pages carry a notice that they are under review because of the Data (Use and Access) Act. For what each vendor claims about its own position, see what each data provider says about GDPR. This is not legal advice.

Not sure a tech-stack filter is worth paying for? Book a call and tell me which tool your buyers use. I will say how I would test it on your own customers first.