Work Email to Company Lookup: Enrich Signups by Domain

A work email to company lookup extracts the domain after the @ sign, discards free-mail providers, and sends the domain to a company data API that returns the employer’s firmographics. It lets you route and score a signup the moment it arrives, without asking the visitor to fill in extra form fields.

Why do it at signup

Every extra form field costs conversions. Resolving the company behind a work email gives you name, industry and size band without asking. That data can drive routing (enterprise to sales, small teams to self-serve), scoring and personalised onboarding. It is one of the headline use cases listed on the BusinessMCP Company Data API page, which describes enriching signups from work email domains, and the endpoint accepts a work email directly as input.

The pipeline

1. Validate syntax. Reject obviously malformed addresses.
2. Extract the domain. Lowercase the part after the last @.
3. Check the blocklist. Skip gmail.com, outlook.com, yahoo.com, icloud.com and similar free providers. Maintain the list yourself or use a maintained open one.
4. Check the cache. A colleague from the same company signed up yesterday? Reuse that result.
5. Look up. Call the API; branch only on whether the company was found.
6. Store. Save fields, a source label and a date.
7. Route. Apply rules based on size band, industry and country.

Key takeaway: route on the size band and country you got back, but never block or reject a signup because the lookup missed. A miss means “unknown”, not “bad”.

What the result tells you and what it does not

You learn	You do not learn
Employer name, industry, size band, location	The person’s role or seniority
Whether the domain belongs to a real organisation	Whether the person is a decision maker
Company website status, if the endpoint provides it	Revenue, funding or buying intent (not provided, per the vendor)

For role information you would need a people-data product, which carries different privacy and legal considerations.

Routing examples

• Size band 1-10, unknown industry: self-serve onboarding email.
• Size band 201+, in your core country: flag to sales with the enriched summary.
• Domain not found: treat as small or new; default to self-serve and retry the lookup later.
• Free-mail domain: no enrichment; ask optionally for company name in onboarding.

Do not hard-code size thresholds from a blog post; derive them from your own win data.

Handling misses and edge cases

• Consultants and agencies using a client’s domain may resolve to the wrong employer.
• Universities and public bodies often have domains with unusual naming; results may be partial.
• Subdomain emails ([email protected]) should be rolled up to the registrable domain before lookup.
• Alias and forwarding domains may resolve to the wrong company or to nothing.
• Brand platforms. The provider says domains such as google.com return name only, so do not expect rich data there.

See domain to company API for the cleaning routine that applies equally to email-derived domains.

Privacy and compliance

An email address is personal data in many jurisdictions. Even if the company lookup itself returns only company-level data, your processing of the email falls under your own privacy rules. Questions to settle with counsel: your lawful basis, what your privacy notice says about enrichment, retention periods and whether any regional restrictions apply. BusinessMCP’s comparison page notes its people data excludes the EU, EEA, UK, Switzerland and certain US states; that concerns a different dataset from the company lookup, but it shows why reading terms matters. This is a general pointer, not legal advice, and you should check current rules for your market.

Cost and volume

Signup volume is usually modest, so a pay-per-hit model suits it. At the stated $0.02 per found lookup, a thousand work-email signups with a 60 percent hit rate would be about $12, though your hit rate will differ. Caching by domain cuts repeats sharply, since many users share a company. Our pricing guide has the estimation formula.

Next steps

If you also want the format a company uses for email addresses, see company email pattern lookup, which is a separate and distinct task. For pushing results into your customer database, continue with the CRM integration guide.

Building the free-mail blocklist

Your blocklist matters more than it seems. Start with the obvious providers and add region-specific ones, since local mailbox providers vary by country. Review the list quarterly by looking at the most frequent domains among your signups that returned not-found; any that are clearly mailbox providers belong on the list. Keep the list in version control and apply it in one shared function so every pipeline behaves the same way.

Measuring whether it works

Track four numbers over time: share of signups with a work email, share of work-email domains that resolve to a company, share of resolved companies in your target size band, and conversion from signup to paid for each routing branch. If enrichment-driven routing does not improve conversion, simplify it. Resolve rates will differ by audience; a developer-tool audience often uses personal addresses, so the first number may be low, while a product sold to finance teams will see more work addresses.

Combining with other signals

A resolved company is one signal. Combine it with product usage, plan chosen and referral source before sending anything to a human. For example, a signup from a 500-person firm that uses three features in the first day is far more interesting than a signup from the same firm that never logs in. The lookup narrows the field; behaviour confirms. Our CRM integration guide explains how to store and combine these fields.

Try it before you build

You do not need an integration to see what you will get. Paste a handful of your recent signup domains into the free company lookup tool and note what comes back. Then read the endpoint description on the BusinessMCP Company Data API page, which says the endpoint accepts a work email directly. If results look useful on a dozen real domains, run the 300-domain test described in how to get company data through an API to size the hit rate and cost.

Fallbacks when the lookup fails

If the API times out, create the account and enrich in the background. If the domain is not found, ask one optional onboarding question about company name or size. If the user gave a free-mail address, do the same. Never block signup on enrichment, and never show the user data you could not verify.