B2B Lead Enrichment Suite

Multi-API B2B lead orchestration: Google Maps + LinkedIn + enrichment + scoring in one run.

Why This Actor Is Better

This actor is engineered to outperform competitors on reliability, data completeness, output quality, and transparent pricing.

Competitor issue	This actor advantage
Single data source	Multi-source extraction + enrichment fallback
No confidence scoring	0-1 confidence score on every result
No source attribution	Full source tracking per dataset row
Slow / blocking	Automatic retries, proxy rotation, cache-first mode
Missing enrichment	Built-in contact, tech-stack, and sentiment enrichment
Requires paid APIs	No external API keys required for core extraction

Key Features

• Fuses Google Maps business data with LinkedIn decision-makers
• Email/phone enrichment and DNS validation
• Lead scoring and deduplication
• One input returns a complete enriched lead record
• Pay less than buying separate actors

Architecture

flowchart LR
    A[Input Query/URL] --> B[Playwright/HTTP Scraper]
    B --> C{Success?}
    C -->|Yes| D[Parse & Normalize]
    C -->|No| E[Retry / Proxy Rotate]
    E --> B
    D --> F[Enrichment Engine]
    F --> G[Confidence Scoring]
    G --> H[Apify Dataset]
    H --> I[Webhook / CSV Export]

1. Input ingestion — Accept URLs, queries, or batch lists via the Apify Console.
2. Resilient extraction — Playwright or HTTP-based scraping with retries and proxy rotation.
3. Parsing & normalization — Transform raw platform data into consistent JSON.
4. Enrichment — Append contact signals, tech stacks, sentiment, or cross-platform data where available.
5. Confidence scoring — Each record receives a 0-1 reliability score.
6. Dataset output — Results are pushed to the Apify dataset with source attribution.

Input

Parameter	Type	Required	Default	Description
queries	array	✅	...	Business search queries
maxResults	integer	✅	25	Max businesses per query
webhookUrl	string	—		Optional webhook URL for result delivery

Output

Results are stored in the Apify dataset as structured JSON objects. See .actor/output_schema.json for the full schema.

Field	Type	Description
query	string	Input query, URL, or search term used to drive the scrape
businessName	string	businessName value
businessUrl	string	businessUrl value
location	string	Location, city, or address
category	string	Category, industry, or vertical
emails	array	Extracted email addresses
phones	array	Extracted phone numbers
website	string	Business website URL
techStack	array	Detected technologies or platforms
decisionMakerName	string	decisionMakerName value
decisionMakerUrl	string	decisionMakerUrl value
jobTitle	string	Job title or role
company	string	Company or organization name
leadScore	number	Computed lead quality score
confidenceScore	number	0-1 confidence score for the result
enrichment	object	Extra enrichment data
scrapedAt	string	ISO timestamp when the row was scraped

Pricing

This actor uses transparent pay-per-event (PPE) pricing. You only pay for successful results.

Plan	Price per 1K results	Savings
Leading competitors	~$3.60/1K	—
This actor	$2.67/1K	26% cheaper

A small one-time Actor Start fee applies per run. No monthly subscription required.

Use Cases

• ABM list building — generate enriched target accounts + contacts
• Local B2B sales — find businesses and their decision-makers
• Agency prospecting — generate ready-to-contact lead lists
• CRM enrichment — append missing contacts and firmographics
• Outbound sales — score and prioritize leads before outreach

Legal & Compliance

This actor scrapes publicly available data from Multi-API. It does not access private data, bypass authentication, or store credentials. Users are responsible for complying with applicable data protection laws (GDPR, CCPA, etc.) and the platform's Terms of Service.

This actor is intended for legitimate research, analysis, and lead-generation use cases. It must not be used for spam, harassment, or unlawful activity.

AI-DLC / Data Lifecycle

This actor follows AI-DLC principles for ethical data handling:

• Collection — Public data only; respects robots.txt and rate limits.
• Processing — In-memory normalization; no PII logging.
• Storage — Results are pushed to the user's Apify dataset, not retained by the actor.
• Usage — Designed for analysis, enrichment, and legitimate outreach.
• Disposal — No long-term caching of user data between runs.

Enhancement Roadmap (API / MCP Integrations)

• Add Apollo.io/ZoomInfo contact-enrichment MCP for higher email coverage
• Integrate 6sense/LeadIQ intent-score MCP for priority routing
• Add sales-enablement MCP (Outreach/Salesloft) to push leads directly

Changelog

• v1.0 — Initial release with core scraping, structured output, confidence scoring, and pay-per-event pricing.
• v1.1 — Premium README, full output schema, and AI-DLC documentation added.