How to Find a Small Business Owner's Email Address (2026)

You find a small business owner's email by looking it up in a data source first and guessing from a name pattern only when the lookup is empty. A lookup returns an address someone has already checked. A guess is a coin flip you must verify.

Owner addresses come from four places. A data provider holds a work address it collected and checked. The business website lists a shared inbox such as info@, which is rarely the owner's own. A name pattern gives you a guess. A personal address sits in some records but suits business outreach poorly.

Only the first is worth building a process around. This guide follows that ranking and uses the LeadOcean API. Every step has a request you can run.

TL;DR

• It takes about 15 minutes to size the audience, find one owner's address and check its status.
• The walkthrough spends about 4 records: up to 3 from the search and 1 from the reveal. Counts are free.
• Send only to verified, catch_all_valid or catch_all. Anything you guessed gets verified first.

Prerequisites

• A LeadOcean API key from app.leadocean.io. The free plan has 1,000 records, one-off, and no card.
• The key in your shell as $LEADOCEAN_API_KEY.
• curl and jq.
• A target business domain. The examples use acme.com.

export LEADOCEAN_API_KEY="paste-your-key-here"

Step 1: Size the small business owner audience for free

Count how many owners you can mail before you spend a record. Send count=true and limit=1 as query parameters. Arrays go comma-separated.

curl -s -G https://api.leadocean.io/v1/people/search \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  --data-urlencode "title=Small Business Owner" \
  --data-urlencode "salesRegion=NORAM" \
  --data-urlencode "emailStatus=verified,catch_all_valid,catch_all" \
  --data-urlencode "count=true" \
  --data-urlencode "limit=1" | jq '.meta | {total, totalIsExact, countOnly}'

salesRegion takes NORAM, LATAM, EMEA or APAC. Swap in country=GB for one market. Add Owner to title for a wider net than our counts below. Enum values are exact strings, so check them with GET /v1/enums or leadocean_list_enum_values before you change one.

A title keyword also matches owners at large companies. To keep to small firms, add a company size filter and read the company_size facet in the MCP count. In our NORAM count below, 4,306 of 10,472 mailable owners sat in the 1-10 band.

Step 2: Find the owner at your target business

Search by company domain and seniority. The search returns a thin row with no address in it. The row carries a person_id and flags that say whether we hold an email.

curl -s https://api.leadocean.io/v1/people/search \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "domain": ["acme.com"],
    "seniority": ["owner", "founder"],
    "limit": 3
  }' | jq '.data[] | {person_id: .meta.source_ids.person_id, contact_data}'

Each person returned costs 1 record. Keep limit small. Small firms use titles such as owner, founder, proprietor, president and principal, so the seniority filter catches more than a title keyword does. Check the title before you pick one.

Step 3: Reveal the address

Send the person_id to enrich with reveal_email set to true. Enrich takes exactly one of linkedin_url, email, phone or person_id. There is no name plus domain lookup, which is why Step 2 comes first.

curl -s https://api.leadocean.io/v1/people/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_id": "PERSON_ID_FROM_STEP_2", "reveal_email": true}' \
  | jq '.data.contact_data | {email_status, contact_emails}'

This costs 1 record. A person we hold nothing for is a 404 and costs nothing. For a work address only, GET /v2/people/email/work with the same person_id returns one current-employer address or null. It costs 1 record per call, even when it finds nothing.

Step 4: Read the status before you send

The status says how far to trust the address. verified was tested. catch_all_valid means we confirmed the mailbox on a domain that accepts everything. catch_all means the domain accepts everything and the mailbox is unproven.

curl -s https://api.leadocean.io/v1/people/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_id": "PERSON_ID_FROM_STEP_2", "reveal_email": true}' \
  | jq -r '.data.contact_data
    | select(.email_status | IN("verified","catch_all_valid","catch_all"))
    | .contact_emails[0].email'

Empty output means the status failed the filter. LeadOcean gives no refund for bounced emails, so this check is your only protection. Treat catch_all as sendable at low volume, not as proof.

Step 5: Fall back to a name pattern

When the data holds no address, build candidates from the owner's name and the business domain. Very small businesses lean on the short shapes. Pick the one you can confirm from a known address at the same business.

first="jane"; last="doe"; domain="acme.com"
printf '%s\n' "$first@$domain" "$first.$last@$domain" "${first:0:1}$last@$domain" "${first:0:1}.$last@$domain"

Never send to a candidate you have not verified. Run each one through an email verifier you trust first. Many small businesses sit on a catch-all domain or a shared mailbox host, and a domain that accepts all mail cannot confirm a single mailbox. A guess there stays a guess.

What you get

Step 1 is free. We ran it on 2026-10-21 for each sales region with leadocean_count_leads, using the title Small Business Owner and no other filter. The counts are mailable owners (verified, catch_all_valid or catch_all, the tool default), not every owner we hold.

The gap between the two count columns is the point. Many owners sit in the data without a checked address, so the mailable list is the smaller, safer one. Most NORAM matches are in the US (10,053 of the mailable) with 412 in Canada.

A revealed person comes back in the shape below. This is the response shape from the API reference, with placeholder values.

{
  "success": true,
  "data": {
    "profile_data": { "...": "name, title, company" },
    "contact_data": {
      "has_email": true,
      "email_status": "verified",
      "email_type": "work",
      "contact_emails": [
        { "email": "jane.doe@acme.com", "type": "work", "status": "verified" }
      ]
    }
  }
}

Troubleshooting

FAQ