Lead Finder PRO — Public B2B Business Leads

Lead Finder PRO returns CRM-ready public-business lead records for sales teams, agencies, and AI agents. Give it a business category and location, and it delivers a deduplicated company domain, website, public homepage contact routes, source URL, organic-search rank, and explainable lead score.

Best fit and next workflow

Choose Lead Finder PRO for focused B2B prospect discovery from public company websites. It works well for turning a category-plus-location brief into a reviewable company list with clear provenance.

For a map-first local-business workflow, pair this actor with Google Maps Leads Scraper, then pass the highest-scoring company domains into your CRM review queue. This actor is a focused standalone workflow when organic website discovery is the primary source.

Workflow: from search brief to CRM review

A growth agency starts with web design agencies and B2B SaaS consultants in Austin. Lead Finder PRO first searches Google organic results through an owner-managed provider, then filters common directories and duplicate domains. Next, it visits each selected company homepage, collects public contact routes, and writes a scored lead record. The agency then reviews the source URL and score reasons before assigning the company to a campaign or CRM owner.

Quick start

{
    "searchQueries": ["web design agencies", "B2B SaaS consultants"],
    "location": "Austin, TX",
    "maxResults": 20,
    "enrichContacts": true
}

searchQueries accepts up to ten focused business categories. location adds geographic context, and maxResults limits unique company domains across the run. Contact-route collection records public homepage emails and a likely contact link when present.

Output fields

Field	Meaning
companyName	Company name derived from the company website or organic-result title.
websiteUrl and domain	Resolved company website and normalized duplicate-prevention domain.
publicEmails and primaryEmail	Public business email routes observed on the visited homepage.
contactPageUrl	A likely contact, team, about, or company page linked from the homepage.
leadScore and scoreReasons	Explainable score based on reachability, relevance, location signals, and public contact routes.
sourceUrl, sourceRank, and searchQuery	Provenance for reviewing how the company was discovered.

Output example

{
    "companyName": "Example Agency",
    "websiteUrl": "https://example.com/",
    "domain": "example.com",
    "publicEmails": ["hello@example.com"],
    "primaryEmail": "hello@example.com",
    "contactPageUrl": "https://example.com/contact",
    "leadScore": 90,
    "scoreReasons": [
        "Found in a Google organic business search",
        "Public business email found on the website",
        "Contact or company page identified"
    ],
    "searchQuery": "web design agencies in Austin, TX",
    "sourceUrl": "https://example.com",
    "sourceRank": 1,
    "location": "Austin, TX",
    "enrichmentStatus": "completed",
    "scrapedAt": "2026-07-21T12:00:00.000Z"
}

Pricing and platform usage

Lead Finder PRO uses Pay per event pricing. A validated public-business lead is charged at $0.01 per persisted record, plus Apify platform usage. The lead-found event occurs only alongside a completed dataset write. The live Pricing tab is the current source of truth for effective pricing and platform-usage settings.

For example, a 20-record run creates twenty lead-found events at $0.01 each, plus the platform usage shown in the Pricing tab.

API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/lead-finder-pro').call({
    searchQueries: ['cybersecurity consulting firms'],
    location: 'London, UK',
    maxResults: 10,
    enrichContacts: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

AI agent prompt card

Use Lead Finder PRO to collect 25 public business leads for fractional CFO firms in Chicago, IL. Return each company domain, source URL, public homepage email when observed, contact page URL, lead score, and score reasons. Exclude example-competitor.com, keep directory inclusion disabled, and use dataset readback for the CRM handoff.

The compact OUTPUT record provides the run outcome and totals, while RUN_SUMMARY provides provider, charge, and dataset diagnostics. Agents can use the source URL and collection time as provenance for a later review step.

Best results and responsible use

• Provide specific business categories such as cybersecurity consulting firms or fractional CFO services.
• Start with a city, country, or region when geographic relevance matters.
• Keep homepage contact-route collection enabled when public routing information adds value to the review.
• Validate the source URL and score reasons before using a company in a campaign.
• Use this actor for public business information that you are authorized to collect and process under applicable laws and site terms.

Builder's note

I designed Lead Finder PRO around a simple audit trail: every returned company has its organic-search provenance, and each score includes the reasons behind it. My goal is to give a human or agent enough source context to make an informed CRM decision while keeping the data surface focused on public business information.