LaunChad Data · early access

Know who is adopting AI.
In numbers.

Every company gets an AI adoption score, an overall score, its rank against everyone else, its hiring velocity and the trend behind it, with the evidence for every number. Stop guessing which accounts are ready: sort them.

From our database

Companies tracked
42,404
Active signals
83,265
Values with a source
287,090
Sources
20

48 % of the hiring companies we track have open AI roles. 37,379 new values in the last 24 hours.

Questions it answers in one request

  • Which companies building on OpenAI are hiring AI engineers right now?

    GET /v1/data/ai-adoption?tool=OpenAI&hiring=ai
  • Who runs on Vercel and Supabase and ships AI in the product?

    GET /v1/data/ai-adoption?stack=Vercel,Supabase
  • Where does this company rank against everyone else?

    GET /v1/data/companies/stripe.com → percentiles
  • Is their hiring speeding up or slowing down?

    GET /v1/data/companies/{id}/metrics → slope per week, R²
  • Which companies look like my best customer?

    GET /v1/data/companies/{id}/similar → shared stack
  • What changed this week: new AI tools, new AI roles, a new price?

    GET /v1/data/signals?event=new

The AI adoption score

Seven signals, one number, every reason shown

Each signal counts by how sure we are: confirmed (DNS, code, official APIs), strong (the company's own website or job board), likely (named in a job post or on a page), weak. Old signals count half. The score never hides its working: the API returns the points, the evidence and the source link.

Verified AI vendor domain
DNS record that a company set up at OpenAI, Anthropic, Cursor…
25
AI tool detected
Model providers, AI coding, AI infrastructure, from code, DNS, pages, job posts
20
AI hiring
Open AI and ML roles on the company's own job board
20
AI in the product
AI features on the pricing page or in the changelog
15
AI in code or open models
AI libraries in their repositories, models on Hugging Face
10
AI on the website
AI assistants and MCP keys
10
Recent funding
A recent Y Combinator batch
10

Company intelligence

The boring numbers that decide deals

Signals tell you something happened. Numbers tell you how much, how fast and compared with whom. Everything is measured the same way for every company, so it can be sorted, compared and benchmarked.

Scores
AI adoption 0–100, overall 0–100 with coverage, buying intent, AI usage tier with trend
Percentiles
Rank among every tracked company for scores, open roles, AI roles, team size, stars, downloads, stack size
Ratios
AI share of open roles, engineering and remote share, roles per week, open roles per 100 staff, AI share of the stack
Trends
Least-squares slope per week, R² and coefficient of variation over 90 days, change over 30 and 90 days
History
Daily series of every number for up to 400 days
Pools and network
Ready-made company pools with their own statistics, and similar companies by shared stack

Tool use across the 42,404 companies we track

  • Cloudflare15.2 %
  • Next.js9.3 %
  • Vercel7.3 %
  • AWS3.8 %
  • Anthropic2.8 %
  • OpenAI1.6 %
  • Stripe1.6 %
  • PostHog1.3 %
  • Cursor0.9 %
  • Google Cloud0.8 %
  • Netlify0.8 %
  • Sentry0.6 %

Statistics of the companies LaunChad Data tracks, not of the whole market. The base is every tracked company; a tool counts only where we saw it in use (loaded on the website, in DNS records or in code). A company that only mentions a tool is not counted.

How it works

We read public sources, merge them into one company, turn them into signals with a confidence, score them and keep a daily history of every number. You get a ranked list, a profile per company, market statistics and a feed of what changed.

  1. 01

    Ask

    Enter a domain

  2. 02

    Scan

    Sources are checked

  3. 03

    Profile

    One profile

  4. 04

    API

    Same answer by API

Illustration · fictional company

An illustration of how LaunChad Data will work: you enter a company domain, the sources are checked, a company profile with tech stack and signals is built, and the same result is available from the API. The company shown is fictional.

One API

Into your CRM, your agents, your spreadsheets

The same key as the rest of LaunChad. Ranked lists with filters and cursor paging, company profiles by domain, a change feed for alerts, NDJSON exports and CSV for the spreadsheet people. Your AI agents can call it as a tool.

  • GET /v1/data/ai-adoption
  • GET /v1/data/intelligence
  • GET /v1/data/pools
  • GET /v1/data/companies/{domain}
  • GET /v1/data/companies/{id}/similar
  • GET /v1/data/companies/{id}/metrics
  • GET /v1/data/signals
  • GET /v1/data/stats
  • GET /v1/data/export
{
"name": "Example SaaS",
"domain": "example.com",
"ai_adoption": {
"score": 81,
"tier": "Very high AI adoption intent",
"buying_intent": "High",
"breakdown": [
{ "part": "Verified AI vendor account (DNS)", "points": 25 },
{ "part": "AI hiring", "points": 17, "because": "4 AI/ML roles open, 2 in 30 days" }
],
"recommended_outreach": "Builds on OpenAI and is hiring for AI, with no vector database seen: offer retrieval or evaluation."
},
"intelligence": {
"overall_score": 68,
"coverage": 89,
"ai_usage": { "tier": "High", "trend": "rising", "confidence": "medium" },
"ratios": { "ai_hiring_share": 0.18, "hiring_velocity_per_week": 3.5 },
"trends": { "open_roles": { "slope_per_week": 1.2, "r2": 0.91 } },
"percentiles": { "ai_score": 94.2, "open_roles": 71.5 }
},
"stack": {
"model_provider": [{ "name": "OpenAI", "confidence": "confirmed", "first_seen": "2026-10-02" }]
}
}
● 200 OK · application/jsonExample · fictional company

Built for the people who sell to, build for and invest in AI companies

AI vendors

A ranked list of companies that already pay for AI and are hiring for it, with the reason and an opening line.

DevTools

Who runs on the tools next to yours, how big their engineering team is, and who just added a competitor.

Investors

Comparable numbers for every company: hiring velocity, AI intensity, engineering activity, percentiles.

Agencies and sales teams

Fresh accounts every week from the signal feed, exported to CSV or pulled into your CRM by API.

What we build, in this order

  • 01Being built

    AI adoption

    Which companies adopt AI: model providers, AI coding tools, AI infrastructure, verified AI vendor domains, AI in the product. One 0–100 score with the reasons.

    For AI vendors, DevTools, VC

  • 02Being built

    Developer tool adoption

    Which developer tools companies use (Vercel, Supabase, Sentry, PostHog…), confirmed from code, DNS and their websites, with first and last seen.

    For DevTools companies, VC

  • 03Being built

    Hiring signals

    Which teams companies hire for (AI, data, security, platform, growth, RevOps, sales) and which tools their job posts name.

    For AI vendors, sales, investors

  • 04Being built

    Technographics as enrichment

    The wider stack behind every profile, each tool with a confidence: confirmed, strong, likely or weak.

    For Sales, marketing

  • 05Being built

    GitHub and open source

    AI and developer libraries in a company's own repositories, open models on Hugging Face, repository activity.

    For DevTools, security, VC

  • 06Being built

    Market changes

    Alerts when a company's pricing page changes or its changelog starts talking about AI.

    For Product, sales, investors

  • 07Later

    SaaS spend estimates

    Later, and only as estimated spend tiers once we have sources that support them.

    For SaaS, investors, procurement

  • 08Later

    Web intent

    Later, and only with first-party traffic or partners; we do not guess intent.

    For Marketing, sales

Where the data comes from

Public sources, read politely, shown openly

  • Greenhouse job boardsPublic job board API
  • Lever job postingsPublic postings API
  • Ashby job boardsPublic job posting API
  • Recruitee careers sitesPublic careers API
  • Company home pagesPublic pages, robots.txt respected
  • Company pricing and changelog pagesPublic pages, robots.txt respected
  • Public DNS (Cloudflare DNS over HTTPS)Public DNS records
  • GitHub organisationsGitHub API terms
  • Hugging Face HubHugging Face Hub API
  • npm registrynpm public registry
  • pypistats.orgPublic API
  • crates.iocrates.io data access policy
  • RubyGems.orgPublic API
  • PackagistPublic API
  • NuGetPublic API
  • Docker HubPublic API
  • Stack Overflow tagsCC BY-SA 4.0
  • Y Combinator directory (yc-oss)Public directory copy (yc-oss, MIT)
  • Common Crawl (Go worker)Common Crawl terms of use
  • Company sites (Go worker)Public pages, robots.txt respected
  • Hacker News: Who is hiring?Public API; AI reading checked against the text

robots.txt is respected for every host; no logins, no proxies, no disguises. No personal data: no names or contacts of people. Every value keeps its source link and the date it was seen. Numbers we cannot see in public (revenue, spend, tokens, users) are not guessed; where only a proxy exists we call it an estimate and show its basis and confidence. Statistics describe the companies we track, not the whole market.

launchad · getting started

# 1. point your OpenAI client at LaunChad
export OPENAI_BASE_URL=https://api.launchad.si/v1
export OPENAI_API_KEY=$LAUNCHAD_KEY

# 2. call any model, or start an agent run
curl $OPENAI_BASE_URL/agents/researcher/runs \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -d '{"message":"What changed on our competitors' pricing pages?"}'

Get started

Two lines of config.
The rest is built.

Keep your OpenAI client, change the base URL and the key. Limits, logs and guardrails are on from the first request.

Free during the beta. No credit card. Launch updates only, no spam.