Public B2B Prospect Finder — Apollo.io Alternative

Find public B2B prospects from role, company, industry, and location queries. Export LinkedIn profile URLs, headlines, source queries, ranks, and timestamps to build a source-linked prospect-review list. For sales researchers, each dataset record is a public prospect reference with a profile URL, headline, and source query.

Workflow: put the results to work

Translate your ideal-customer profile into roles, companies, industry terms, and the appropriate search market. Review the resulting public profile links before adding approved prospects to a contact-research workflow. Discovery here does not include a verified email database or message sending.

What this workflow replaces—and what it does not

Use this as an on-demand alternative for the public prospect-discovery step: turn a role/company/industry query, with a selected Google country market, into reviewable public profile links with the exact search query, source URL, rank, and collection time.

It does not replace Apollo's proprietary contact database, verified emails or phone numbers, buying-intent signals, CRM sync, sequences, mailbox sending, call tools, or team sales workspace. Apollo is the better choice when those broader suite features are the job. This independent Actor is not affiliated with, associated with, or endorsed by Apollo.io.

Comparing this workflow with Apollo.io

This Actor covers source-linked public discovery and its reviewable output contract. Apollo.io covers a broader sales-intelligence and engagement suite. The pricing models differ as well: this Actor declares per-run events plus platform usage, while Apollo's public pricing presents seat and credit plans. Public discovery records keep the exact search query and collection time beside the profile URL, which helps a reviewer decide whether a candidate is current enough for the next approved workflow.

Decision area	This Actor	Apollo.io	Practical routing
Scope	Public prospect discovery with source links and timestamps.	A broader sales-intelligence and engagement suite.	Select the tool matching the requested workflow boundary.
Billing	Pay per event plus platform usage; see the Pricing tab for current rates.	Public pricing presents seat and credit plans.	Budget a bounded run with maxResults; check the live pricing surfaces before purchase.
Same-job cost	A private cloud run is pending before total buyer cost is measured.	A comparable plan allocation needs the same workload assumptions.	Keep cost comparison private until both sides use the same usable-output definition.
Effective efficiency	Each persisted row carries a reviewable source query and collection time.	Broader-suite operator efficiency depends on selected product workflows.	Measure usable rows and active review time for the same query before choosing at scale.
Integrations and automation	The dataset is prepared for a separate approved API, CRM, or outreach workflow.	Apollo provides broader integration and outbound workflow features.	Use the next approved system for enrichment, CRM updates, and engagement.
Freshness and provenance	Each row includes sourceSearchUrl and collectedAt.	Apollo documents data enrichment and refresh capabilities.	Review provenance and collection context before acting on a discovered profile.

This independent Actor is not affiliated, associated, or endorsed by Apollo.io.

Best fit

Use it when you need a small, current, source-linked list to review before outreach or to pass into a separate approved enrichment workflow. Avoid it when you need verified work location, email or phone data, sales engagement, CRM operations, or a comprehensive proprietary contact database; use an approved provider that explicitly supplies those capabilities instead.

Input

{
  "jobTitles": ["Head of Growth"],
  "keywords": ["B2B SaaS"],
  "companyNames": ["ExampleCo"],
  "industry": "software",
  "location": "United States",
  "country": "US",
  "maxResults": 25
}

At least one of jobTitles, keywords, or companyNames is required. The Actor combines the supplied role, company, keyword, and industry terms into each source-visible Google query constrained to public linkedin.com/in/ results; country controls the Google market, while location is retained as request context and is not a verified profile-location filter. DataForSEO Google Organic is the primary request route; a direct Google route through Apify Residential Proxy is retained only as a disclosed fallback. It caps role/company combinations at ten and persists no more than maxResults unique profile records.

Output

One dataset item means one validated public-profile discovery, not a verified person, employment assertion, email address, or outreach permission.

Field	Meaning
profileUrl	Canonical public LinkedIn profile URL found through public web search.
displayName, headline, snippet	Public search-result text; fields are null when not safely available.
sourceQuery, sourceSearchUrl, sourceRank	Replayable discovery context for review.
selectedJobTitle, selectedCompany	The input plan that produced the record.
country, collectedAt, source	Market context, collection time, and collection route (DataForSEO Google Organic or a disclosed direct fallback).

{
  "profileUrl": "https://www.linkedin.com/in/jordan-lee",
  "displayName": "Jordan Lee",
  "headline": "Head of Growth at ExampleCo",
  "snippet": "Growth leader in B2B SaaS.",
  "sourceQuery": "site:linkedin.com/in/ \"Head of Growth\" \"B2B SaaS\"",
  "sourceSearchUrl": "https://www.google.com/search?q=site%3Alinkedin.com%2Fin%2F",
  "sourceRank": 1,
  "selectedJobTitle": "Head of Growth",
  "selectedCompany": null,
  "country": "US",
  "collectedAt": "2026-09-07T10:00:00.000Z",
  "source": "DataForSEO Google Organic"
}

From ICP to reviewed list

An SDR targeting growth leaders at B2B software companies starts with a title, industry, location, and a low maxResults cap. The Actor returns public profile links, preserves the search provenance, and gives the SDR a compact review queue. The team can remove mismatches, check data authority and contact preferences, then use its approved enrichment or CRM process. This keeps data collection, contact verification, and outreach as distinct, auditable steps.

Terminal outcomes

Read OUTPUT or RUN_SUMMARY before downstream use. COMPLETE means every selected public-search route and validated record path completed; PARTIAL preserves useful records while disclosing route or write interruptions; VALID_EMPTY means a functioning search found no matching public profiles; INVALID_INPUT explains how to refine the request; and UPSTREAM_FAILED signals that the required public-search route needs a later retry.

Public search snippets can be stale, incomplete, personalized, or unavailable by geography. Always review sourceSearchUrl and collectedAt before treating a record as current. If OUTPUT.outcome is UPSTREAM_FAILED, retry later and inspect the route errors in RUN_SUMMARY; do not treat an empty dataset from a failed route as no prospects. DataForSEO is a pay-as-you-go upstream data provider that needs the Actor owner's configured API credentials; it is not an Apollo account or a source of private contact data.

API and AI-agent use

curl "https://api.apify.com/v2/acts/khadinakbar~apollo-alternative/runs?token=$APIFY_TOKEN" \
  -X POST -H "Content-Type: application/json" \
  -d '{"jobTitles":["Head of Growth"],"keywords":["B2B SaaS"],"country":"US","maxResults":10}'

AI agent prompt:

Find up to ten public LinkedIn profiles for Heads of Growth in US B2B SaaS. Return the profile URL, headline, source query, source link, collection time, and terminal outcome. Label this dataset as public prospect discovery for human review before a separate contact-data or outreach step.

Responsible use

Use public or authorized data for lawful research, respect applicable terms and data-protection obligations, and obtain the appropriate basis before personal outreach. This Actor intentionally does not collect private profile fields, credentials, email addresses, phone numbers, or messages.

Builder's note

I designed the record shape to keep sourceSearchUrl and collectedAt beside every profile link. Public prospect discovery is most useful when a downstream reviewer can see exactly how a candidate was found and distinguish an observed result from a verified contact record.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
public-prospect-found	Public prospect found	One validated, persisted source-linked public LinkedIn profile discovery. No email, phone, or private contact data is included.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.