Website Tech Stack & Contact Enricher

The BuiltWith / Wappalyzer alternative without the subscription fees.

Stop paying $295+/month for tech lookups you'll run a few thousand times a year. This Actor scans any list of company domains and returns their technology stack, key contact signals, and social profiles — in a clean, ready-to-export dataset. Pay per run, not per month.

Why sales, RevOps, and growth teams use this

• Kill your BuiltWith / Wappalyzer subscription. Get the same signal — CMS, analytics, CRM, payments, CDN — without a recurring license.
• Qualify leads at a glance. Instantly see if a prospect runs Shopify vs. Magento, HubSpot vs. Marketo, or Stripe vs. Adyen — and pitch accordingly.
• Skip-trace contact info for free. Pulls the public contact email and social profiles (LinkedIn, Twitter/X, GitHub, Facebook) straight off the site — no separate enrichment tool required.
• Built for scale. Fully async with configurable concurrency — profile hundreds of domains in the time a browser-based tool takes to load one.
• Zero maintenance. No browser, no proxies, no flaky headless Chrome — just fast HTTP requests and battle-tested signature matching.

What it detects

Category	Technologies
CMS & E-commerce	Shopify, WordPress, Webflow, Magento, BigCommerce, Squarespace
Analytics & Tracking	Google Analytics 4, Mixpanel, Segment, Hotjar
Marketing & CRM	HubSpot, Marketo, Klaviyo, Intercom, Zendesk
Frameworks & CDNs	Next.js, Nuxt, React, Cloudflare, AWS CloudFront
Payments	Stripe, PayPal, Adyen

Plus for every site: page title, meta description, contact email, and social links (Twitter/X, LinkedIn, GitHub, Facebook).

Input

Field	Type	Default	Description
domains	array of strings	["https://cal.com", "https://linear.app"]	Domains or full URLs to profile
maxConcurrency	integer	10	Max sites processed in parallel
timeoutSecs	integer	15	Per-request timeout in seconds

Example input

{
    "domains": ["shopify.com", "https://stripe.com", "hubspot.com"],
    "maxConcurrency": 10,
    "timeoutSecs": 15
}

Output

One row per domain, pushed straight to the Apify dataset. Example record:

{
    "domain": "cal.com",
    "url": "https://cal.com/",
    "status_code": 200,
    "technologies": ["Cloudflare", "Google Analytics 4", "Next.js", "React", "Stripe"],
    "technologies_by_category": {
        "Analytics & Tracking": ["Google Analytics 4"],
        "Frameworks & CDNs": ["Cloudflare", "Next.js", "React"],
        "Payments": ["Stripe"]
    },
    "social_links": {
        "twitter": "https://twitter.com/calcom",
        "linkedin": "https://linkedin.com/company/cal-com",
        "github": "https://github.com/calcom",
        "facebook": null
    },
    "email": "hello@cal.com",
    "title": "Cal.com - Scheduling infrastructure for absolutely everyone",
    "meta_description": "Cal.com is an open source scheduling tool..."
}

Export results directly to CSV, Excel, JSON, or connect via the Apify API to your CRM, spreadsheet, or lead-scoring pipeline.

How it works

For each domain, the Actor:

1. Requests the page over HTTP with redirect-following enabled.
2. Matches response headers, HTML, inline scripts, and CDN footprints against a curated signature library.
3. Parses the DOM for <title>, meta description, mailto: links, footer text, and social profile links.
4. Streams a structured, typed record straight to the dataset — no post-processing needed.

Requests run concurrently (bounded by maxConcurrency), so a list of hundreds of domains typically finishes in minutes, not hours.

Use cases

• Sales prospecting — segment target accounts by CMS, CRM, or payment provider before outreach.
• Competitive intelligence — track which technologies competitors' customers are adopting.
• Lead enrichment pipelines — bolt this onto existing scraped domain lists to add firmographic-style tech signals.
• M&A / vendor due diligence — quickly audit the tech footprint of an acquisition target's public site.

Notes & limitations

• Detection is based on publicly observable HTTP responses (headers, HTML, inline scripts) — it does not execute JavaScript, so client-side-only integrations loaded after page render may not be detected.
• Contact email extraction relies on mailto: links and visible page text; sites that obfuscate emails via JavaScript or forms only will return null.
• Be a good web citizen: keep maxConcurrency reasonable for very large lists to avoid overloading target sites.