People Enrichment — Find a Person's Title, Seniority & Business Email From Name + Company

What it does: give it Jane Smith, acme.com (or just an email) and it resolves the person against the company's live website — returning job title, seniority level, department, the best-available business email with a confidence score, and a live MX check on the domain. Who it's for: SDRs, recruiters, and RevOps teams who need to reach a specific named person without paying for an Apollo seat or a ZoomInfo contract. What it costs: $0.02 per resolved person ($20 per 1,000) + $0.01 per run. People we can't resolve to a title, email, or site match are returned but never charged.

How to find someone's business email from their name and company

Add people one per line — all three formats work, mixed freely:

Patrick Collison, stripe.com
Dylan Field @ figma.com
jane.doe@notion.so

• Name + company domain → the Actor crawls the company's team/about/leadership pages, matches the person, extracts their title, and finds or derives their email.
• Email only → it enriches the person behind the address and verifies the domain's mail infrastructure.

One structured row per person, exportable to JSON, CSV, Excel, or your CRM.

What a resolved person looks like

{
  "name": "John Lincoln",
  "firstName": "John",
  "lastName": "Lincoln",
  "title": "Co-Founder",
  "seniority": "Founder/Owner",
  "department": "Executive",
  "companyName": "Ignite Visibility",
  "companyDomain": "ignitevisibility.com",
  "email": "john@ignitevisibility.com",
  "emailInferred": true,
  "emailConfidence": 0.5,
  "emailPattern": "first",
  "domainHasMx": true,
  "mxProvider": "Google Workspace",
  "matchedOnSite": true,
  "matchType": "site-match+pattern-email",
  "confidenceScore": 0.7
}

Field notes:

• seniority is classified from the title into C-Level · VP · Director · Manager · Founder/Owner · Senior · Entry/IC — ready for routing rules.
• department — Executive, Engineering, Sales, Marketing, Finance, HR/People, and more.
• emailInferred is the honesty flag: false means the address was found published; true means it was constructed from the company's email pattern — and a pattern is only trusted when ≥2 real emails confirm it.
• matchType gives full provenance of how the person was resolved (e.g. site-match+real-email), so nothing is a black box.
• domainHasMx / mxProvider — a live DNS lookup confirming the mail server exists and naming it ("Google Workspace", "Microsoft 365", …).

Apollo alternative for contact enrichment (and ZoomInfo, for named people)

Apollo and ZoomInfo are search engines over a static contact database — superb when you don't yet know who to contact. This Actor is the opposite tool: you already know the person; it verifies them against what their employer publishes today.

	This Actor	Apollo (people search)	ZoomInfo
Input	A name you already have (or an email)	Search filters over their DB	Search filters over their DB
Data recency	Read from the employer's live site at run time	Database refresh cycles	Database refresh cycles
Person left the company?	You'll see it — no site match	Stale record risk	Stale record risk
Inferred emails labeled as such	Yes (emailInferred)	No	No
Pricing	$20 per 1,000 resolved, pay-as-you-go	Per-seat plans (from ~$49/user/mo)	Annual contract, typically five figures
Unresolved people cost	$0	Credits/plan either way	Contract either way
Account or API key needed	No	Yes	Yes

(Competitor pricing is list pricing at the time of writing.)

Use them to discover prospects; use this to verify and enrich the ones you've named — including checking whether a database-sourced contact is still real.

Adding job title, seniority and department to a list of names

If what you need is not the email but the shape of a list — who on it is a decision maker, who sits in which function — the two classification columns do that job without any manual tagging. Both are derived from the title text found on the employer's site, so they are consistent across a list assembled from different sources.

seniority returns exactly one of, checked in this order: C-Level (CEO, CTO, CFO, COO, CMO, CIO, CISO, CRO, CPO, or any "Chief … Officer") · Founder/Owner (founder, co-founder, owner, proprietor, principal) · Partner · VP (VP, SVP, EVP, AVP, vice president) · Director (including "Head of …" and managing director) · Manager (manager, lead, supervisor, foreman) · Senior (senior, staff, principal engineer) · Entry/IC (associate, analyst, specialist, coordinator, engineer, developer, designer, consultant, junior, intern). Order matters: a "Founder & VP of Engineering" lands in Founder/Owner, not VP.

department returns one of Executive, Engineering, Product, Design, Sales, Marketing, Finance, HR/People, Operations, Customer Success, Data, Legal, IT/Security.

Together they make a raw list of names filterable in one step — keep seniority in (C-Level, Founder/Owner, VP) and department in (Executive, Sales) and you have the people worth a personal email, without reading a single title by hand. Both fields are null when no title could be found, rather than defaulted to a guess.

Reading matchType: how each person was actually resolved

Every row says how it got there, which is the column to sort by when you want to know how much to trust a list:

matchType	What happened	Trust
site-match+real-email	The person was found on the employer's own team/leadership page and their address is published there	Highest — nothing was constructed
site-match+pattern-email	The person was found on the site, but their address was not published, so it was built from the company's confirmed email pattern	Person confirmed, address inferred
site-match-no-email	The person and title were confirmed on the site; no address and no usable pattern, so none is returned	Title is solid, no email
pattern-email	The person was not found on the site; the address follows the company's confirmed pattern	Weakest — treat as a candidate address
provided-email	You supplied the email; the person and company were enriched around it	Depends on your input
none	Nothing could be resolved — returned, and not charged	—

For "is this person still there?" checks, matchedOnSite: true is the column that answers it: a contact exported from an old database who no longer appears anywhere on the employer's site is the row to retire.

What teams run through it

• Email discovery — a likely, MX-verified address for each name on your outreach list.
• Contact verification — is this person still at this company, with this title? The live site answers.
• CRM contact append — add title, seniority, and department to existing contact records.
• Decision-maker filtering — keep only C-Level/VP/Director rows from a raw list of names.
• Recruiting research — confirm role and reach a candidate via their published company page.

Frequently asked questions

Will it always return an email? No, deliberately. An email is returned when the company publishes it or a confirmed pattern exists. Inferred addresses carry emailInferred: true and a lower confidence — a blind guess is never dressed up as verified.

Which companies resolve best? Ones that publish team/about/leadership pages: agencies, professional services, SMBs, mid-market SaaS. Enterprises that hide their org chart behind logins return company-level context only — and you're not charged for unresolved people.

How is the email confidence calculated? From how the address was obtained (published on-site > pattern-constructed), whether it's on the company domain, and the live MX result. It's a 0–1 number per email, not a flat "verified" badge.

Can I check whether contacts from another database are still valid? Yes — that's a common workflow: export names from your old tool, run them through, and keep the rows with matchedOnSite: true.

What does a 500-person list cost? $0.01 + $0.02 × resolved people. If 320 of 500 resolve: ≈ $6.41. The other 180 cost nothing.

Do I need an API key? No. Runs on Apify; also callable via the Apify API from your own code.

Can it find personal (non-work) emails? No — it reads business information companies publish about their own team. That's a scope choice, not a limitation bug.

Is this compliant to use? It processes only publicly published business information from the employer's own website. Lawful use under your jurisdiction (GDPR, CAN-SPAM, etc.) is your responsibility.

Related Actors

• Company Enrichment API — domain → full company profile with decision-makers.
• Lead Enrichment & Scoring — score any lead 0–100 against your ICP.
• CRM Enrichment — flat firmographic rows for CRM import.
• All my Actors.

---

Built by Renzo Madueño. Found a bug or want a field added? Open an Issue — I read and respond to every one.