TL;DR
- BuiltWith is the stronger first trial when the sales motion starts with a technology-defined market: “Find sites using this platform, including historical adoption or removal, then qualify the accounts.” Its report subscriptions start at $295/month; free individual site lookups and its separate API family solve different jobs.
- Wappalyzer is a good first trial when the team needs repeatable website lookups and list construction in a controlled workflow. Pro is $250/month, but its current v2 technology lookup and lead-list APIs require Business at $450/month. The two technology targets on Pro are a lead-list limit, not a cap of two websites.
- Neither product can prove that an account has an active replacement project. A detected tag is evidence about a website at a time, not a company-wide purchase decision. Historical additions and removals deserve investigation before outreach.
- Compare the same domains, technologies and acceptance rule. A cheap lookup that returns duplicate subsidiaries or a technology the team cannot act on can cost more per qualified account than a pricier report.
The buyer question: list, lookup or change?
Technographic data is most valuable when it answers one of three explicit questions. List building: which websites appear to run a technology relevant to our offer? Lookup: what appears on the site of a company we already know? Change: has visible use of a technology appeared, disappeared or shifted since a previous observation? A single vendor can offer all three, but each operation can have different plans, credits and output detail.
An integration agency, for example, may want every mid-market ecommerce site running a named platform in two countries. That is list building. A rep preparing for a meeting with a known retailer may want its current storefront and analytics stack. That is lookup. A migration partner might care whether an old platform tag disappeared and a new one appeared on the same domain. That is change research, but only if the team can inspect the evidence and understand whether the observation reflects a genuine switch.
Specify the unit of account before buying. Is one domain one prospect? A global company can have a corporate site, regional commerce stores, documentation subdomains and acquired brands. A technology found on one storefront may not belong to the entire legal company. Conversely, several domains can be one buying account. A usable export needs enough domain, subdomain, parent-company and observation detail to join to the CRM without creating five “new” accounts for one organization.
The commercial purpose follows from that mapping. A web technology matters when it changes what the seller can responsibly propose: an integration path, likely implementation constraint, compatibility check or migration risk. “We saw you use X” with no relevant next step is decoration. A detected vendor's presence is not evidence of budget, dissatisfaction or purchase timing. For broader signals, see our buying signal platforms guide; technographics are one input, not a standalone intent score.
BuiltWith and Wappalyzer side by side
These public figures were checked on 27 September 2026. Monthly prices exclude possible annual discounts or separately priced API credits.
| Decision point | BuiltWith | Wappalyzer |
|---|---|---|
| Free research | Individual website lookup without a paid report plan | Free account with 50 technology lookups monthly and sample lists |
| First relevant paid UI plan | Basic $295/month: two technology reports, two keyword reports, two retail reports, one login | Pro $250/month: one user, two lead-list technology targets, 5,000 technology lookups |
| Broader team/list plan | Pro $495/month: unlimited technology/keyword/retail reports, one login; Team $995 adds unlimited Pro logins | Business $450/month: five users, unlimited lead-list technology targets, 20,000 lookups and 20,000 included API credits |
| Existing-domain API | Separate Domain API with current and historical website technology data | v2 Lookup API on Business or higher: one credit per URL normally; five for live recursive crawl |
| Market-list API | Lists API for websites using selected technologies; confirm the route's credit and license terms | Lead-list API on Business or higher, with filtering and list-credit economics |
| Change evidence | Historical technology records, Change API and usage alerts | Website alerts and lookup observations; verify alert event and refresh cadence for the plan |
The headline price comparison can therefore mislead. If your team needs an automated Wappalyzer lookup API, comparing its $250 Pro UI plan with BuiltWith's $295 Basic report plan is comparing two products that do not perform the same operation. If you only need occasional human lookups, buying either vendor's full API path may be unnecessary. Ask for the exact plan plus operation before turning a table into a budget.
BuiltWith for technology-defined markets
BuiltWith's strength is starting from a technology and generating a researchable website market. The plan page lists Basic at $295 monthly with two technology reports, two keyword reports and two retail reports under one login. Pro at $495 makes those report categories unlimited under one login; Team at $995 expands access to unlimited Pro logins. Individual website lookup is free. These plans also describe CSV and Excel report export, technology history and usage alerts.
For a seller of a Shopify integration, the first useful action is not merely downloading every domain that appears to use Shopify. Filter the resulting report to the relevant country, scale and commerce context; merge related domains; remove agencies, test stores and existing customers; then check the actual storefront. The technology report is a candidate-account generator. The buyer's accepted list is smaller. BuiltWith's report filtering and re-download rights can make repeated market work worthwhile when several technology segments are central to a team's pipeline.
The vendor also has a Domain API returning current and historical technologies with confidence and metadata where available, a Change API for additions and removals, and a Lists API for technology-based website sets. Those are distinct from opening a report in the web product. The public plan page does not make every API's unit cost and allowance directly comparable with the report subscription, so request the API route, credit schedule and permitted redistribution for the intended job. A team that just needs a monthly CSV can avoid assuming it must build an integration; a team that needs daily domain refresh should not assume the $295 report price covers all API calls.
BuiltWith's historical emphasis helps a migration motion, but history must be interpreted. A first observed tag may be a late detection rather than the first day the company installed it. A disappeared tag may be due to a redesign, consent banner, region-specific rendering or a move to a different subdomain. “Started using” and “stopped using” are observation labels. Save the domain, observed date, technology and evidence link; have an analyst check high-value changes before a rep refers to them in a message.
BuiltWith is a strong first purchase when the team runs multiple technology-led segments, needs repeated exportable reports or values historical context for account planning. It is weaker for a small queue of known accounts needing only occasional current lookups, or for a product team that has not priced its exact API and storage rights. Its marketing scale claims do not answer whether a specific tag is right for a specific domain in your market.
Wappalyzer for lookups and workflow automation
Wappalyzer makes several jobs explicit in its pricing page: a free account for limited lookup and sample lists, Pro $250/month for one user and two lead-list technology targets, and Business $450/month for five users, unlimited lead-list technology targets, 20,000 lookups and included API credits. Enterprise starts at $850/month with higher limits and custom terms. The two-target figure on Pro restricts list technology selection; it does not say the buyer may inspect only two websites.
Its v2 Lookup API documentation says the operation requires Business. A normal lookup is one credit per URL. A live recursive crawl is five credits per URL, uses a callback and can return asynchronously after a crawl that may take up to 15 minutes. The endpoint allows up to ten requests per second and has rules for batching up to ten URLs. If a production job needs fresh recursive evidence, price the five-credit route; a one-credit cached lookup is not an identical substitute. Keep a timestamp and response mode with the result so a cached value does not masquerade as a live observation.
The v2 lead-list API also requires Business. It can combine selected technologies with country, industry, company size, root-path, subdomain and recency filters. The API's list creation can be free while the eventual list has its own credit price; inspect the calculated total and sample before finalizing. This is particularly useful when the team knows a narrow ICP and wants to reject irrelevant domains before buying a larger export. It is not evidence that a matched website includes a current decision-maker or verified contact channel.
Wappalyzer's included API credits expire after 60 days under its current pricing FAQ, while purchased bundles have different expiration. A team doing a large one-off backfill followed by tiny monthly refreshes should model that timing. It may have enough nominal credits on Business but lose value if they expire before the next job. Conversely, a recurring lookup process can use the pool efficiently if it only rechecks domains where freshness matters.
Wappalyzer best fits a repeatable lookup or list workflow whose Business-tier API requirement is acceptable, and a team that can act on the technology fields it receives. It is weaker when someone picks the $250 Pro price for a production API without checking the plan gate, or when a team wants deep historical adoption evidence but has not tested its alert and recency behavior for the exact technologies involved.
What a technology observation actually proves
Both vendors infer technologies from the publicly observable web. The best-detected categories tend to leave recognizable artifacts: scripts, headers, assets, markup, domain patterns or visible implementation. Other tools live entirely in private systems and may leave little or no public trace. A detected website tag should therefore be described as evidence of use on that site or page, not proof that every business unit uses the product. A missing tag is even less definitive: absence of public evidence is not evidence that the company has no contract.
For account qualification, separate five fields: technology, domain or path, source, observation time, and confidence or verification state. Add the company mapping only after resolving subsidiaries and regional properties. If the source reports a first-seen or last-seen date, store the date's meaning. “First seen by this vendor” differs from “installed on this date.” This field-level context prevents a CRM checkbox from becoming an unsupported claim months later.
The seller should make a narrow inference. “The current public checkout appears to use Platform A; an integration we offer may fit that setup” is defensible after checking the page. “You are replacing Platform A next quarter” is not. If an alert suggests a change, look for a second observation and a plausible business event: a relaunch, acquisition, new digital-commerce role or public implementation project. Even then, it is a reason to ask a relevant question, not a prediction about budget.
One practical trap is technology taxonomy. The vendors may label the same script under slightly different names or group related products differently. Normalize category and vendor names before declaring one source wrong. Test named products that matter to your sale, not a generic “percentage of technologies detected” across unrelated categories. A false positive in the one platform that drives your offer is more damaging than missing a background analytics tag.
Historical change and alerts
BuiltWith explicitly offers historical usage, usage alerts and a Change API. Wappalyzer offers website alerts, and its lookup/list products expose recency and live-versus-cached options. Neither should be described as categorically “historical” or “only current.” The useful question is what event each product emits and when that event can be verified.
Run a small alert test. Choose 50 domains whose public technology footprint your team can inspect. Record the current tags, enable alerts or schedule lookups, and save every notification with its timestamp. For each apparent addition or removal, inspect the relevant page and a comparable prior snapshot if available. Classify the result as confirmed change, site redesign, consent or regional variation, taxonomy rename, detection uncertainty or unknown. A sales task should be created only for categories whose confirmed changes genuinely affect the account strategy.
The workflow needs a human-friendly sentence backed by evidence, not just an event stream. “The checkout page we reviewed on 12 September exposed a different payment script from the prior observation” is more useful than an unexplained “technology removed” badge. It also avoids sending a prospect an embarrassing claim when a tracker was blocked by a browser setting. Link any alert to the exact domain and business unit in the CRM; do not let a subsidiary alert trigger outreach to an unrelated global owner.
Price a usable account list, not a subscription
Assume a team wants to build a list of 500 target companies using a technology its product integrates with. It starts from a vendor report or API list, then checks country, company size, parent-account duplicates, live technology evidence and a real person to contact. Imagine BuiltWith's $295 Basic report returns 1,200 candidate domains and 240 become qualified accounts; Wappalyzer's $450 Business workflow returns 900 candidates and 300 become qualified. The subscription-only costs would be $1.23 and $1.50 per accepted account respectively. Those candidate and acceptance counts are invented for the calculation, not measured vendor results. API credits, contact enrichment and analyst work would be added to both.
Now change the workflow. If only one named technology is required and the analyst runs a one-off report, BuiltWith Basic's two-technology scope may be ample. If an engineer must look up 500 known URLs via Wappalyzer's API, the cached route could use 500 credits; the live recursive route could use 2,500. Both require Business according to current v2 documentation. The price difference is not a question of which subscription starts lower; it is a question of whether the necessary operation exists in the tier and whether the returned evidence passes acceptance.
Contact data adds another line. Neither technology detector automatically supplies the current role owner, an accepted work email or consent to use it. If the list yields 300 qualified companies but only 120 with the right person after separate enrichment, the cost per contactable target account is much higher. The team should not judge technographic sourcing by raw website count while judging its sales outcome by meetings. Keep domain-to-account and account-to-person conversion visible.
A 500-domain comparison test
Take 500 domains from the team's current CRM: 300 ordinary ICP companies, 100 known users of one target technology and 100 difficult cases such as subsidiaries, multi-country sites or recent redesigns. Use a second set of technology-first list queries so the test covers both lookup and discovery. Hold the technology names and filters constant as far as the products allow.
For known domains, record whether each vendor detects the target tool, where it appears, observation date, historical evidence and how the result maps to the correct account. Manually inspect a stratified sample of disagreements; a “no detection” on a technology with no public footprint is not a proven false negative. For generated lists, measure duplicates, out-of-ICP domains, false positives and accounts that can be matched to an owner. Do not discard misses from the denominator.
Run the operation you would actually buy. If the plan is a monthly CSV report, test report creation, filtering, export fields and download rights. If the plan is an API, test the exact endpoint, plan gate, credit deduction, rate behavior, cached versus live response and permitted data storage. For Wappalyzer, include a live-recursive sample so the asynchronous result and five-credit cost do not appear as a surprise in production. For BuiltWith, ask for the Domain, Change or Lists API credit allowance rather than assuming the report subscription covers it.
Finally, follow 20 accepted accounts through to an actual outbound research task. Can a rep explain the technology observation and why it matters, find the appropriate contact and avoid implying a purchase intention the data never established? The winning tool is the one that produces more qualified, explainable account tasks at an acceptable total cost in your market.
Which should your team choose?
Choose BuiltWith when technology-led market mapping, repeated reports and history are the core work. Basic is sensible for a fixed one- or two-technology project; Pro or Team makes more sense when the team creates many segments or needs more logins. Price APIs separately when automation, rather than report export, drives the purchase.
Choose Wappalyzer when known-domain lookup and a controlled list/API workflow fit your process. Pro can suit a small human-led list workflow. Choose Business for the documented v2 technology lookup or lead-list APIs, and budget cached versus live-recursive credits and expiration. If all you need is a few one-off checks, use the free options before buying either subscription.
Use both only after showing that the second source yields enough additional accepted accounts or verifies a critical disagreement. Overlapping subscriptions with no CRM join, no contact handoff and no sales action simply create more unreviewed tags. The adjacent B2B data enrichment tools comparison can help once the account list needs people and contact fields.
Use the Signal-Based Outbound Playbook to decide how an observed technology change affects account priority and the reason for contacting it.
FAQ
Is BuiltWith more accurate than Wappalyzer?
No universal answer follows from their product pages. Compare the exact technologies, domains, dates and evidence that matter to your market. Score false positives that would cause bad outreach and missed accounts separately; a broad cross-category average can hide the one technology that drives your campaign.
Does Wappalyzer Pro allow only two website lookups?
No. The two-technology figure is its lead-list technology target allowance. Its monthly pricing page shows 5,000 technology lookups on Pro. The current v2 lookup API, however, requires Business; UI lookups and API access are distinct entitlements.
Can I use Wappalyzer's API on the $250 Pro plan?
Its current v2 lookup and lead-list API documents state Business is required, which is listed at $450 monthly. Confirm the exact endpoint and current account rights if you have an older or custom agreement. API credits included in a plan expire after 60 days under the present pricing FAQ.
Does BuiltWith's $295 Basic plan include unlimited API calls?
The public plan page describes two technology reports and other report access, while BuiltWith has separate Domain, Change and Lists API surfaces. Do not infer unlimited API usage from the report subscription. Request the credit allowance and contract terms for the route you intend to run.
Does a newly detected technology mean the company is buying?
No. A public website observation can indicate a deployed tag or implementation change; it does not establish budget, dissatisfaction, ownership or a replacement timeline. Check the specific page and account context, then use the finding as a relevant question or research clue.
Which is cheaper for a 500-domain enrichment job?
It depends on whether the job is report export, cached lookup, live recursive crawl or list purchase. Wappalyzer's documented API charges one credit per normal URL lookup and five for live recursive lookup, with a Business plan gate. BuiltWith's report and API pricing must be scoped separately. Divide the full spend by accepted account records, including de-duplication and contact handoff, rather than by domains requested.
