How to Find a Small Business Owner's Email and Phone Number (and Check They're Real)

Why small businesses are different

Data providers are built around companies with LinkedIn pages, org charts and many employees. A three-person plumbing company, a dental practice or a family restaurant often has none of that. The owner's email may never appear in a B2B database, and what does appear can be years old. That's why people building SMB lists from Google Maps or local directories end up asking how to get the owner's contact, not the generic one.

The good news: small businesses publish more than you'd think, and their email patterns are simple.

Step 1: get the owner's name

Try these in order:

1. The website. About, Team, "Meet the owner" and Contact pages. Footer copyright lines and blog bylines sometimes name the owner too.
2. Google Business Profile. Owner responses to reviews are often signed ("Thanks, Maria"). The profile also gives you the website and phone listed by the business.
3. State business registries. In many US states, the Secretary of State business search lists officers, members or a registered agent for an LLC or corporation. A registered agent may be a filing service, not the owner, so check the role. Other countries have equivalents, such as Companies House in the UK.
4. LinkedIn, for businesses big enough to have staff on it. See find an email from a LinkedIn profile.
5. Licensing boards for regulated trades (contractors, real estate, healthcare), which often list a responsible person.

Note the source for each name. If two sources disagree, the most recent one usually wins.

Step 2: get what the website publishes

Many small businesses list a direct address on the site. The website email extractor pulls published addresses from a site's pages. If you already have a CSV of businesses with websites, emails and phones scattered across columns, extract email and phone from CSV pulls them into clean columns.

You'll usually find one of three things:

• a named address (maria@, mike.jones@): best case; verify and use it
• a role address (info@, office@, hello@, bookings@): real, shared, often read by the owner
• nothing, or a contact form only: go to step 3

Step 3: work out the pattern and build guesses

If you found any named address at the domain, it tells you the pattern. The email format finder suggests the likely format for a domain. For tiny teams, firstname@ is common, followed by firstname.lastname@, first initial plus last name, and firstname plus last initial.

Feed the owner's name and the domain into the email permutator to generate the candidates, then check them. Don't send to every permutation: that's how you collect bounces. Verify first, send to the one that comes back valid.

The email finder does the generate-and-check step for you from a name and a domain.

Step 4: verify, and understand catch-all

Upload the candidates to verify. A mailbox check asks the domain's mail server, during the SMTP conversation, whether the address exists, without sending a message. Results:

• Valid: the server confirmed the mailbox. Use it.
• Invalid: the server rejected it. Drop it.
• Catch-all / risky: the server accepts every address at the domain, so no single address can be confirmed. Some hosting setups used by small businesses are configured this way. Here, prefer an address you saw published, send in small numbers, or fall back to info@.
• Unknown: the server didn't give a clear answer, often temporarily. Retry later.

Also check the domain is still alive. Small businesses close, rebrand and let domains lapse; a domain with no mail server can't receive anything.

info@ vs the owner

Situation	Use
Named owner address found and valid	The owner address
Owner known, guess valid on a non-catch-all domain	The guessed address
Owner known, domain is catch-all	Published address if any; otherwise info@ or a small test
No owner name	info@ with an opener that asks to be pointed to the owner

Role addresses carry more risk in bulk: they're shared, sometimes forward to several people, and some lists treat them differently. See role-based email addresses. Personal Gmail or Yahoo addresses of the owner are a judgement call: use them only when the business publishes them as its contact.

Phones: validate before you dial

Local listings mix mobile numbers, landlines, call-tracking numbers and old numbers in display formats like (555) 123-4567 ext 2. Before calling or texting:

1. Normalise and validate with the bulk phone number validator, which returns status, E.164 format, country and type where the numbering plan defines it.
2. Separate mobiles from landlines before any SMS, and check your consent obligations for texting.
3. Dedupe: chains and multi-location businesses share the same number across listings.

Scaling it to a list

If you're starting from a Google Maps export or a directory scrape, verify Google Maps leads covers the cleanup. The flow is the same as above at scale: extract published contacts, find owner names, build and verify the missing addresses, validate phones, and keep the source of each field.

What it costs

• Pro, $39 a month: Unlimited email verification.*
• Starter, $9 a month: 2,500 emails a month.
• Free: the first 100 checks with a Google sign-in, no card.

*Fair use: the first 100,000 checks a month at full speed, then slower, never cut off.

Pro also includes the email finder, phone format checks, an API with 10,000 calls a month included and an MCP server for AI agents. The API, phone checks and the finder are not part of Unlimited. See pricing.

More reading: personal emails in a B2B lead list, catch-all emails: what to do.