See reports

How to Get Verified Decision-Maker Leads and Pay Only for Qualified Ones

Most lead tools charge you whether or not the contact is real, relevant, or reachable. Qualified Leads flips that: you bring target company domains and your ICP, and you pay only for leads that clear your bar. Every contact is a real named person scraped from the company's own site and mapped to a real on-page email, never invented. Off-ICP, unverified, or contactless rows come back free with a reason.

Steps
  1. Open the actor and paste your domains. In the Apify Console, open qualified-leads and fill domains with your target companies (as domains, URLs, or emails). This is your account list; the actor works each one in turn.
  2. Describe your ICP and target roles. Set icp to describe who you sell to (this drives the fit score). Optionally set rolesWanted to the titles you want (e.g. VP Sales, Head of Ops). Leave it empty to accept any senior contact.
  3. Set your qualification bar. Adjust minFitScore (default 70), requireVerifiedEmail (default true, so only real on-page verified emails count), requireIntentSignal (default false), and maxQualifiedLeads as a budget cap (default 25). These define exactly what you pay for.
  4. Run it and review the records. Click Start. You get one record per person with company firmographics, contact name/title/email, emailStatus, fitScore and fitReasons, intentSignals, roleMatch, an opener, and a qualified flag. Disqualified rows carry a disqualifiedReason and are free.
  5. Export the qualified leads. Filter for qualified: true, then export to JSON/CSV/Excel or pull via the API into your CRM or sequencer. The emails are real on-page addresses, ready to work.
Frequently asked questions

What exactly do I pay for?

$1.50 per qualified lead, and nothing else. A lead qualifies only when it meets your minFitScore, matches a rolesWanted title if you set any, has a deliverable email, and shows an intent signal if you required one. Everything else is returned free.

Are the emails verified against the mailbox?

Not via a live SMTP handshake, because port 25 is blocked on this infrastructure. 'verified' means a personal address found on the site with a valid domain MX record. For hard mailbox verification, run the output through a dedicated verifier afterward.

Where do the contacts come from?

Real named people scraped from the company's own homepage plus about/team/leadership/contact pages, mapped to real on-page emails. The actor never invents a person or an email.

What does emailStatus 'inferred' mean?

The person is named on the site but no email was published, so the actor built the standard first.last@domain pattern and confirmed the domain accepts mail. It is a high-probability guess like Hunter or Apollo pattern matches, not confirmed. Set requireVerifiedEmail false to accept these.

Is this compliant to use for outreach?

It returns business, role-based contact data from public company pages. You are the data controller for how you use it, so GDPR and CAN-SPAM apply to your outreach.

Try it now

Run it on Apify — no install, results in minutes.

Open on Apify