Lead List Qualifier — Domain Hotness Scorer

Score a list of company domains for outbound-readiness. This Actor calls four of our own live lead-gen Actors in parallel for every domain — tech stack, active hiring, funding mentions and contact reachability — and combines what they find into one transparent hotness score, so you know which leads on your list to call first.

What you get

• One hotness score (0-96) per domain, with a full text breakdown of exactly which signals contributed and how many points each one added — never a black-box number.
• Signals combined: contact info found on the site, hiring momentum + role keyword matches, ecommerce/sales-tool detection, and SEC funding-filing mentions.
• Honest about uncertainty: a guessed hiring-board token is checked against the board's public owner signal when one is available. A confirmed mismatch is shown for diagnosis but contributes no score; unavailable evidence stays explicitly unverified rather than being silently promoted to a match.
• Domains with zero signal from all four sources come back free (not charged) — you only pay when we actually found something to report.
• Runs on Apify: call it from the API, export to JSON/CSV/Excel or push straight into your CRM/outreach pipeline.

How to run it

1. Click Try for free — no card needed on the free plan.
2. Paste up to 25 domains into Domains to qualify.
3. Optionally set Role keywords (e.g. sales, marketing) to flag domains currently hiring for those roles.
4. Hit Start and pull the scored list from the dataset.

Pricing

Pay-per-event: $0.005 per run start + $0.01 per domain scored. A domain with zero signal from all four sources, or one we couldn't check at all (all four sources unreachable), is returned but never charged. 10 domains scored cost about $0.11 (the one-time start fee plus 10 billed rows).

Input

Field	Required	What it does
domains	yes	Up to 25 company domains to score, e.g. "stripe.com".
role_keywords	no	Words to match against open job titles (default: ["sales","marketing"]).
company_name_overrides	no	{"domain":"correct-slug"} — override our guessed ATS token/company name for specific domains (see limitation below).

{
    "domains": ["stripe.com", "shopify.com"],
    "role_keywords": ["sales", "marketing"]
}

⚠️ Important limitation: guessed company identity for 2 of the 4 signals

Two of the four signals (contact info, tech stack) work directly off the domain you give us — no ambiguity there. The other two (hiring activity, funding mentions) need a company NAME or ATS token, not a domain, so by default we guess one from the domain itself (stripe.com → stripe). This guess can attach an unrelated company's data to your domain. Verified live: qualifying example.com (which has no real hiring-board presence at all) returned "strong hiring, 21 open roles" — because some UNRELATED company happens to sit under the token example on one of the three job-board providers we check. Similarly, querying "stripe" against public funding filings surfaces real SEC filings that merely contain the word "stripe" in an unrelated fund's name (e.g. "Rockefeller Stripe LP"), not Stripe Inc. itself.

Every row tells you the input path via matchBasis ("guessed-domain" or "buyer-override") and the hiring ownership result via attributionConfirmed (true, false, or null) plus attributionEvidence. A false hiring match is excluded from scoring. null means the public board did not expose enough evidence, not that ownership was confirmed. If you know the real ATS token or legal name for a domain, pass it via company_name_overrides to remove the guesswork for that domain — though even then, a name match on public filings is never proof of identity (see matchedFundingFilings — always check it yourself before treating funding mentions as fact).

Output

Full signal found (real output, live run 30.07.2026):

{
    "domain": "stripe.com",
    "found": true,
    "hotnessScore": 78,
    "scoreBreakdown": [
        "contact info found on the site (+15)",
        "aggressive hiring (+38)",
        "113 open role(s) matching your keywords (+15)",
        "11 SEC filing(s) mention \"stripe\" — UNVERIFIED (+10)"
    ],
    "reachable": true,
    "emailsFound": 1,
    "phonesFound": 3,
    "hiringMomentum": "aggressive hiring",
    "openRolesCount": 540,
    "matchedRolesCount": 113,
    "techStackCount": 2,
    "ecommerce": null,
    "cms": null,
    "fundingMentionsCount": 11,
    "fundingConfidence": "low — name-substring match on public SEC filings against a guessed slug, NOT a verified link to this domain; see matchedFundingFilings",
    "matchedFundingFilings": [
        { "company": "Pantera Opportunities Fund LP Stripe", "filedAt": "2026-07-24", "url": "https://www.sec.gov/Archives/edgar/data/2147228/000090266426003236/0000902664-26-003236-index.htm" }
    ],
    "companySlugUsed": "stripe",
    "identityConfidence": "guessed",
    "matchBasis": "guessed-domain",
    "attributionConfirmed": true,
    "attributionEvidence": { "method": "greenhouse-board-name", "requestedDomain": "stripe.com", "signal": "Stripe", "detail": "greenhouse's board name matches stripe.com." },
    "techStackChecked": true,
    "contactsChecked": true,
    "hiringChecked": true,
    "fundingChecked": true,
    "partial": false,
    "partialReason": null,
    "error": "",
    "summary": "stripe.com — hotness 78: contact info found on the site (+15); aggressive hiring (+38); 113 open role(s) matching your keywords (+15); 11 SEC filing(s) mention \"stripe\" — UNVERIFIED (+10).",
    "checkedAt": "2026-07-30T10:36:08.928Z"
}

No signal found (real output, live run 30.07.2026 — free, not charged):

{
    "domain": "zzqfakenonexistentdomain999999.example",
    "found": false,
    "hotnessScore": 0,
    "scoreBreakdown": [],
    "error": "",
    "summary": "zzqfakenonexistentdomain999999.example — no signal detected from any of the four sources (checked: techStack, contacts, hiring, funding).",
    "checkedAt": "2026-07-30T10:39:46.032Z"
}

Field	Meaning
found	true only when hotnessScore > 0 — the billable outcome.
hotnessScore	0-96 heuristic index, sum of the components in scoreBreakdown. Not a percentage or a guarantee.
reachable, emailsFound, phonesFound	From website-contact-extractor.
hiringMomentum, openRolesCount, matchedRolesCount	From company-hiring-radar, keyed on companySlugUsed.
techStackCount, ecommerce, cms	From tech-stack-detector.
fundingMentionsCount, fundingConfidence, matchedFundingFilings	From funding-round-tracker — always check matchedFundingFilings yourself, see the limitation above.
identityConfidence	"guessed" or "override" — see the limitation above.
matchBasis, attributionConfirmed, attributionEvidence	How the ATS token was chosen and whether the board's public owner signal matched the requested domain. null is unknown, not confirmed.
techStackChecked/contactsChecked/hiringChecked/fundingChecked	Whether that source's own call succeeded this run (independent of whether it found anything).
partial / partialReason	true when some (not all) of the four sources failed to respond — the score is still computed from whatever did answer.
error	Empty string when the check completed (including "nothing found"); non-empty only when ALL FOUR sources failed to respond.

Other tools we built

Related tools

Related tools for adjacent workflows in B2B lead generation and data enrichment.

Actor	What it does
B2B Lead Enricher	Pair it in the B2B lead generation and data enrichment workflow: Turn a list of company websites into sales-qualified lead cards: detected tech stack, a rough revenue...
Company Profile Lookup	Pair it in the B2B lead generation and data enrichment workflow: Turn a domain or company name into one unified company card: website tech stack (CMS, ecommerce, key tech)...
Intent Signal Aggregator	Pair it in the B2B lead generation and data enrichment workflow: Is this company in-market right now? Combines public hiring activity (Greenhouse, Lever, Ashby) and recent...
Counterparty Risk Rollup — Sanctions, Courts, Registry, Hiring	Pair it in the B2B lead generation and data enrichment workflow: One call, one row per counterparty: sanctions screening (OFAC + EU), legal-entity registry (GLEIF),...
Company Hiring Radar	Pair it in the B2B lead generation and data enrichment workflow: Pull every open role a company is hiring for from its public job board (Greenhouse, Lever, Ashby) and turn...

FAQ / Limitations

Why is my score lower than I expected? Check partial first — if some sources didn't respond this run, the score only reflects what did. Then check identityConfidence — a "guessed" slug for a distinctive company name usually still works; a common word as a domain label (like "example") is where guesses go wrong.

What this is NOT. This is not a verified company database and does not confirm that a domain and a matched hiring board or funding filing are the same legal entity — see the limitation section above. It is a prioritization heuristic, not proof.

Found a bug or need a custom scoring weight? Issues on the Actor's page.