BuiltWith

@BuiltWith what technologies is stripe.com currently using for analytics and tracking?

Based on the Domain API lookup for stripe.com, the site currently uses Google Analytics 4 for web analytics, Segment for customer data infrastructure, and Cloudflare for CDN and security. Historical data shows they migrated from Universal Analytics to GA4 in March 2023. The site also implements Optimizely for A/B testing and uses custom tracking pixels for conversion attribution. This represents a snapshot as of the last crawl date.

This example demonstrates the Domain API's ability to surface both current and historical technology stacks. Requires an API key with domain lookup credits. Note that BuiltWith's crawl frequency varies by site popularity—enterprise domains like Stripe are typically refreshed weekly, while smaller sites may show data that's 30-90 days old.

@BuiltWith find me 50 e-commerce sites in the US that use Shopify and have between 100-500 employees

The Lists API returned 50 matching domains. Sample results include: allbirds.com (San Francisco, ~200 employees, Series E funded), bombas.com (New York, ~150 employees), and gymshark.com (UK-based but US operations, ~400 employees). Each entry includes the company's headquarters location, employee count range, estimated revenue band, and last technology verification date. The full list has been formatted as a CSV with columns for domain, company name, location, employee count, and Shopify plan tier detected.

This showcases the Lists API with metadata filtering—powerful for lead generation and competitive research. Requires a Lists API subscription tier. Employee counts and revenue estimates are sourced from third-party data providers and should be verified for high-stakes decisions. Results are limited to domains BuiltWith has recently crawled and matched against business registries.

@BuiltWith analyze the technology adoption trends for React versus Vue.js over the past 3 years across the top 10k websites

Querying the Datasets API for 2021-2024: React adoption among the top 10,000 sites grew from 18.2% (Q1 2021) to 31.7% (Q4 2024), while Vue.js held steady at 4.1% to 5.8% over the same period. React's growth accelerated in 2023, coinciding with Next.js 13's release. Vue.js saw a brief spike in Q2 2022 (7.2%) but declined as Nuxt 3 adoption remained slower than anticipated. The data shows React's dominance in enterprise contexts, while Vue maintains a niche in Asia-Pacific markets and among smaller development teams.

This example pairs BuiltWith's Datasets API with the AI's analytical capabilities to extract meaningful trends from raw historical data. Requires a Datasets API subscription—this is BuiltWith's premium tier. The analysis reflects technology detection accuracy limitations: client-side frameworks can be obfuscated by build tools, so treat percentages as directional rather than absolute. Best used for macro-level market intelligence, not precise competitive tracking.

When BuiltWith beats manual research for sales prospecting

A 6-person B2B SaaS sales team needs to qualify inbound leads by checking if prospects use competing tools. The Domain API Lookup tool pulls current and historical tech stacks in seconds—no more manually inspecting page source or guessing from job postings. This MCP wins when you're qualifying 20+ leads per week and need to route them based on incumbent tools (e.g., "uses Stripe but not our analytics platform"). The trade-off: BuiltWith's data is sampled, not exhaustive, so you'll miss technologies that don't leave client-side fingerprints. If your ICP uses server-side-only tools or custom builds, you'll get false negatives. Best fit for teams selling dev tools, martech, or infrastructure where the tech stack is visible and the API key cost ($295/month minimum) pencils against manual research hours.

How product teams use Lists API for TAM validation

A 3-person product team at a developer tool startup needs to size the addressable market for a new Kubernetes monitoring feature. The Lists API Get List With Meta tool returns a filtered list of domains running Kubernetes plus company metadata (employee count, revenue band, location). This beats scraping job boards or guessing from GitHub stars because it's tied to live production usage. The scenario works when your feature targets a detectable technology and you need a rough TAM number for a pitch deck or roadmap prioritization. The boundary: BuiltWith's coverage skews toward mid-market and enterprise sites with public footprints. If your ICP is early-stage startups or stealth-mode companies, the list will undercount. Use this MCP when you need directional TAM data in hours, not a $50k analyst report in weeks.

When Datasets Lookup flags at-risk accounts before they cancel

A 10-person customer success team at a CMS vendor monitors whether enterprise customers are testing competitor platforms. The Datasets Lookup tool surfaces historical technology changes—if a customer added WordPress or Contentful in the last 90 days, that's a churn signal worth a check-in call. This MCP works when your product leaves a detectable footprint (analytics tags, CDN patterns, CMS headers) and you're managing 50+ accounts where manual monitoring doesn't scale. The catch: BuiltWith's refresh cycle is weekly to monthly depending on the site, so you're not getting real-time alerts. If a customer migrates over a weekend, you'll learn about it days later. Best for teams where early churn signals justify the API cost and where the technology change is visible in the HTML or network layer.