Reverse Lookup: Email → Profile
Outcome: a list of bare email addresses turned into named, titled, company-attached profiles, with a measured match rate and a plan for the misses.
- Surface
- App and MCP server
- Level
- Beginner
- Uses
- find_linkedin_from_work_email · find_linkedin_from_personal_email · linkedin_profile_enrich
- Credits
- ~2 per row
- Prerequisite
- A list of email addresses
The problem this solves
You have addresses and nothing else. A newsletter list, a webinar export, form fills with only an email field, a partner list, a support inbox.
Every one of those is a set of people you cannot qualify, route or personalize to — because you know nothing except that they exist. Reverse lookup turns them into records.
Two routes in
| Address type | Tool | Expected match rate |
|---|---|---|
| Work email | find_linkedin_from_work_email | Higher — the domain anchors it |
| Personal email | find_linkedin_from_personal_email | Lower — no company anchor |
Split your list by address type first. Running the wrong route wastes credits and produces misses that look like coverage gaps.
Classifying is a free formula: consumer domains (gmail, outlook, yahoo, and the rest) go to the personal route, everything else to the work route.
The chain
Resolve the profile
Email → LinkedIn profile URL. This is the step that either works or does not.
Enrich the profile
linkedin_profile_enrich on the resolved URL returns name, current title, company, location, and history.
Enrich the company
From the company domain that comes back, run organization enrichment. Now the row has firmographics.
Score
The row is now a normal prospect record and everything from the other courses applies.
Two paid steps, and the second only runs where the first succeeded — so misses cost you once, not twice.
What to expect
| Input | Match rate |
|---|---|
| Work email at a corporate domain | 60–75% |
| Work email at a small business | 35–55% |
| Personal email | 25–45% |
Role address (info@, sales@) | Near zero — no individual behind it |
Filter out role addresses before running the lookup. There is no person to resolve, so every one is a guaranteed miss — and while a miss is not billed at the resolve step, it is a row of noise in your match-rate calculation that makes the number look worse than it is.
What to do with the misses
A miss is not a dead row. Three fallbacks in order of cost:
- Domain-level enrichment. You still have the company from the address. Enrich the organization, and you at least know the account even if not the person.
- Find people at that company. If the account qualifies, look for the right role directly — you may reach a better contact than the one whose address you had.
- Keep and wait. Coverage improves over time; a quarterly re-run on unmatched rows recovers a slice for very little.
Where this is worth doing
| Source | Value |
|---|---|
| Newsletter or content list | High — these are self-identified interested people with no qualification attached |
| Webinar or event export | High — plus the topic is a signal in itself |
| Form fills with email only | High — and it makes routing possible |
| Support or sales inbox contacts | Moderate — often existing customers |
| Purchased list | Low — usually stale, and the misses cluster |
The first three are the strongest case for this lesson: people who raised their hand, sitting unqualified because nobody knew who they were.
Do this now
Split by address type
Free formula on the domain.
Drop role addresses
They cannot resolve to a person.
Run resolution on 20 rows
One batch of each type. Compare match rates.
Enrich the matches
Profile, then company.
Score them
Using your existing model. Many will not qualify — that is a useful finding about the list.
Handle the misses
Domain enrichment at minimum.
Compute cost per qualified contact
Total credits ÷ rows that ended qualified and contactable. Compare it to your normal sourcing cost.
Check your work
- List is split by address type before any lookup
- Role addresses are excluded
- Match rate recorded per address type
- Misses have been routed to domain-level enrichment
- You have a cost per qualified contact to compare against sourcing
Where this breaks
A resolved profile is not necessarily current. Someone whose address you captured eighteen months ago may have changed companies — and reverse lookup returns their profile, which reflects where they are now, not where the address belongs. Always check whether the resolved company matches the email domain. Where it does not, you have found a job change, which is a stronger lead than the one you were looking for. See Job Changes & Champions.
Further automation
Wire it into intake. Any form, webinar or download that captures only an email can trigger the chain immediately, so the contact is qualified and routed before anyone looks at it. That is exactly the build in Automated Inbound.
Next lesson
07 — Measuring hit rate and cost per verified contact, the numbers that make this course defensible.
Reference for this lesson: find_linkedin_from_work_email, find_linkedin_from_personal_email, linkedin_profile_enrich, Find LinkedIn from work email.