Decision-Maker Email Finder — Verified B2B Contacts
Pricing
from $40.00 / 1,000 company checkeds
Decision-Maker Email Finder — Verified B2B Contacts
Find decision-makers (CEO, founder, C-level, VP, director) at any company domain with high-confidence B2B email addresses. Crawls team, about and contact pages, infers the company email pattern, checks DNS/MX and scores each contact. No LLM, no proxies needed.
Pricing
from $40.00 / 1,000 company checkeds
Rating
0.0
(0)
Developer
Hossam Mohamed
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Find decision-makers (CEO, founder, C-level, VP, director) at any company domain with high-confidence B2B email addresses — built for outbound teams, lead-gen agencies and AI agents.
Give it a list of domains. It crawls each company's homepage plus team / leadership / about / contact pages, extracts people and their roles, infers the company's email pattern from any published addresses, checks the domain's mail (MX) records, and returns ranked contacts with an honest confidence score for every email.
No LLM calls, no proxies needed, fully deterministic.
Honest confidence labels on every email —
on-site, pattern-observed, MX-confirmed or guess. No fake "verified" claims; you decide what is safe to send.
AI agent quick start
Actor tool ID: dev-hoss/decision-maker-email-finder
- Send
domains(1–200). Filter dataset items bytype === "contact"for people;type === "domain-summary"gives coverage (people found, pattern, MX, provider). - Rank by
emailConfidence(on-site>high>medium>low) — the Actor already orders contacts by role seniority, then confidence, capped bymaxContactsPerDomain. - JavaScript-rendered team pages may yield no role-matched people: that is a
no-role-matchsummary, not a failure.
How confidence works (no fake "verified" labels)
| Confidence | Meaning |
|---|---|
on-site | The company itself published this exact email next to the person |
high | The email pattern was observed in ≥2 emails published on the site |
medium | The standard first.last@ pattern + the domain has mail (MX) records |
low | A pattern guess without corroboration |
generic | Role inbox (info@, contact@) — only if you enable generic emails |
We deliberately do not claim "verified deliverable" for pattern-based guesses — anyone promising that from a crawler is guessing too. Confidence ranks are honest so you can decide what to send.
Quick start
{"domains": ["basecamp.com", "automattic.com"],"maxContactsPerDomain": 3}
Input
| Field | Type | Default | Description |
|---|---|---|---|
domains | array (required) | — | 1–200 company domains or URLs. A URL path is used as a hint (e.g. https://acme.com/team). |
roles | array | senior list | Role keywords to match (case-insensitive, plurals handled). Edit to target departments or specific titles. |
maxContactsPerDomain | integer | 3 | Contacts returned per company, ranked by seniority + confidence. |
maxPagesPerDomain | integer | 6 | Homepage + team/about/contact pages per company. |
includeGenericEmails | boolean | false | Also return info@-style inboxes when no person matches. |
concurrency | integer | 5 | Domains processed in parallel. |
proxyConfiguration | object | off | Optional. Public pages only — rarely needed. |
Output (default dataset)
contact — one per decision-maker:
{"type": "contact","company": "basecamp.com","name": "Jason Fried","role": "co-founder","email": "jason.fried@basecamp.com","emailConfidence": "medium","pattern": "first.last","linkedinUrl": null,"mxFound": true,"mailProvider": "other","sourceUrl": "https://basecamp.com/about","checkedAt": "2026-09-12T12:00:00.000Z"}
Plus domain-summary (coverage: people found, emails on site, pages fetched, pattern, MX), error (unreachable domains) and info records. Contacts are ranked by role seniority, then email confidence.
Honest limitations
- JavaScript-rendered team pages (e.g. Zapier, GitHub) may yield no role-matched people — the run reports
no-role-matchinstead of pretending. Static HTML sites (most SMB and mid-market companies) work best. - Emails are pattern-inferred unless published on-site — sendability is never guaranteed. MX + provider checks catch dead domains and webmail, not full SMTP validation.
- Only public pages are visited. No logins, no scraping of LinkedIn member data.
How much does it cost?
Pay per event: a small fee per domain checked plus a fee per contact found (the result itself). Compare: dedicated email-finder SaaS charges $30–$100+/month, and verified-contact actors charge ~$0.14 per contact.
Who is this for?
- Outbound / SDR teams — find the right person at target accounts with a defensible email guess
- Lead-gen agencies — bulk domain lists in, ranked contacts out
- Recruiters & journalists — reach founders and executives directly
- AI agents — enrichment tool calls with structured, schema-documented output
Use with AI agents
Documented JSON input schema, one stable record per contact, no auth beyond the caller's own Apify token. Simplest integration:
POST https://api.apify.com/acts/dev-hoss~decision-maker-email-finder/run-sync-get-dataset-items?token=YOUR_API_TOKENContent-Type: application/json{"domains": ["basecamp.com", "automattic.com"], "maxContactsPerDomain": 3}
Also works with Apify's hosted MCP server (mcp.apify.com).