How to enrich HubSpot companies with technographic data from BuiltWith

Why add technographic data?

Firmographic data tells you how big a company is. Technographic data tells you how they operate. A company running Salesforce and Marketo has different needs, budget, and buying process than one running HubSpot Free and Mailchimp. That signal is one of the strongest predictors of sales fit — but fewer than 10% of B2B sales teams use it consistently because the data is hard to get.

BuiltWith detects technologies across 50,000+ categories by analyzing what's publicly deployed on a company's website. Automating this lookup for your HubSpot companies lets you:

• Score leads on tech fit — companies using a competitor's CRM are replacement opportunities worth +20 points in your scoring model
• Segment by technology — build lists of companies using specific tools (Marketo users, Shopify merchants, AWS customers)
• Personalize outreach — "I noticed you're running Google Analytics and Mixpanel — most teams consolidate to one after hitting scale"
• Identify displacement opportunities — flag every company running a direct competitor for targeted campaigns

How it works

Every approach follows the same pattern:

1. Find unenriched companies — search HubSpot for companies where the tech_stack_crm custom property has never been set
2. Look up the domain — call BuiltWith's API with each company's domain to retrieve the full list of detected technologies
3. Categorize the stack — sort technologies into buckets (CRM, marketing, analytics, e-commerce) based on BuiltWith's tag taxonomy
4. Write to HubSpot — update custom company properties with the categorized tech stack and an enrichment date for tracking

Tech stacks change slowly, so quarterly re-enrichment is usually sufficient. Most teams run a weekly batch of new or recently targeted companies.

What you'll need

Which approach should I use?

• n8n — best for teams that want visual workflow management with full control over the categorization logic. The Code node handles BuiltWith's deeply nested response well. Self-hosted n8n means zero platform cost beyond BuiltWith credits.
• Make — good if you prefer a visual builder and your batch sizes are small (under 50 companies). The Iterator handles per-company processing naturally, and the Code module (Core plan) simplifies the categorization. Credit costs add up with larger batches.
• Code + Cron — most cost-effective for larger batches. Full control over the categorization map, error handling, and rate limiting. GitHub Actions provides free scheduling. Best if you want to customize the category taxonomy or add competitor detection logic.
• Claude Code — a guided skill that lets you enrich companies conversationally ("look up the tech stack for Acme Inc") or in batches on a schedule. No code to write — the agent reads API reference files and handles the lookup, categorization, and HubSpot update. Best for ad-hoc lookups or testing BuiltWith on a few target accounts before committing to automation.

Choose your approach

Select an approach below to see the full step-by-step guide.