Qualified B2B Leads on Demand — Pay Per Verified Lead avatar

Qualified B2B Leads on Demand — Pay Per Verified Lead

Pricing

from $660.00 / 1,000 qualified lead delivereds

Go to Apify Store
Qualified B2B Leads on Demand — Pay Per Verified Lead

Qualified B2B Leads on Demand — Pay Per Verified Lead

Pay only for leads that actually qualify against your ICP. Give it domains and your ICP; get back verified decision-maker contacts — charged only per lead that passes your bar.

Pricing

from $660.00 / 1,000 qualified lead delivereds

Rating

0.0

(0)

Developer

Fredrik Hansson

Fredrik Hansson

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 hours ago

Last modified

Features

Limited permissions

Share

Bring your target company domains. Get back verified, ICP-matched, intent-scored decision-maker leads — and pay only for the leads that qualify. Unverified, off-ICP or contactless rows are returned free.

No people-database guesswork: every contact is a real named person scraped from the company's own site (homepage + about/team/contact pages), mapped to a real on-page email. The Actor never invents a person or an email.

How it works

For each domain:

  1. Fetch the homepage plus its about / team / leadership / contact pages.
  2. Extract real on-page emails and the LinkedIn company link (deterministic, no AI).
  3. One AI pass: firmographics, ICP fit score, explicit intent signals, and the named decision-makers matched to your wanted roles — emails only from the real on-page candidates.
  4. Verify each email (syntax + MX records + role/catch-all classification).
  5. Qualify against your bar. Charge one qualified-lead event per lead that passes.

Qualification bar (what you pay for)

A lead is qualified (and the only thing charged) when:

  • fitScore >= minFitScore, and
  • it matches a rolesWanted title (if you set any), and
  • it has a deliverable email (requireVerifiedEmail → a verified personal address), and
  • it shows a buying-intent signal (only if requireIntentSignal is on).

Everything else is delivered with qualified: false and a disqualifiedReason, free.

Input

FieldTypeNotes
domainsstring[]Target companies (domain, URL or email). Required.
icpstringWho you sell to. Drives the fit score. Required.
rolesWantedstring[]Titles to target. Empty = any senior contact.
minFitScoreintegerDefault 70.
requireVerifiedEmailbooleanDefault true.
requireIntentSignalbooleanDefault false.
maxQualifiedLeadsintegerBudget cap. Default 25.

Output (one record per person)

{
"company": { "name": "Acme", "domain": "acme.com", "industry": "SaaS", "sizeSignal": "50-200", "location": "US", "techStack": ["HubSpot"] },
"contact": { "fullName": "Jane Doe", "title": "VP Sales", "email": "jane@acme.com", "emailStatus": "verified", "linkedinUrl": "https://linkedin.com/company/acme" },
"fitScore": 86,
"fitReasons": ["Sells to SMBs", "Hiring SDRs"],
"intentSignals": ["Hiring SDRs"],
"roleMatch": true,
"opener": "Saw you're scaling the SDR team...",
"qualified": true
}

About email verification (be clear)

SMTP port 25 is blocked on this infrastructure, so there is no live SMTP handshake. emailStatus is:

  • verified — a personal address found on the site, domain MX-valid (highest confidence).
  • inferred — the person is named on the site but no email was published, so we built the standard pattern (first.last@domain) and confirmed the domain accepts mail. A high-probability guess, not confirmed — like Hunter/Apollo pattern matches.
  • risky — a personal address on a free provider (gmail etc.).
  • role — a generic inbox (info@); never attributed to a named person.
  • invalid / none — bad syntax, no MX, or nothing found.

requireVerifiedEmail: true qualifies only verified leads. Set it false to also accept inferred and risky. No SMTP handshake is performed (port 25 blocked); for hard mailbox verification, run the output through a dedicated verifier.

Pricing

$1.50 per qualified lead. Nothing else is charged. A single closed deal pays for hundreds of leads.

Compliance

Returns business, role-based contact data from public company pages. You are the data controller for how you use it (GDPR/CAN-SPAM apply to your outreach).

Use it from an AI agent (Apify MCP server)

This Actor is available through the Apify MCP server, so any AI agent that speaks MCP — Claude, ChatGPT, Cursor and others — can call it as a tool directly. Hand it target company domains and an ICP description, get back verified, ICP-matched decision-maker contacts — charged only per lead that qualifies. No custom integration needed.

  • B2B Lead List Builder — Describe your ICP in plain English; get a ranked list of matching companies with domains to feed into this actor.
  • B2B Outbound Engine — Full-funnel: discovery → intent scoring → account brief → personalised cold email sequence in one run.
  • B2B CRM Enricher — Enrich existing CRM domains with firmographics, tech stack, hiring signals and social links.
  • B2B Email Verifier — Run a leads list through syntax, MX and pattern-match verification before sending.
  • AI Prospecting Pipeline — End-to-end: target companies → ICP-scored leads → verified emails → personalised cold-email drafts.

Sample output

{
"domain": "stripe.com",
"qualified": true,
"company": "Stripe",
"decisionMakers": [
{
"name": "David Singleton",
"email": "david@stripe.com",
"title": "CTO"
}
],
"icpScore": 92,
"chargeEvent": "qualified-lead"
}