How to Pull the Cold Email Statistics That Matter (From Your Own Audience)

The cold email statistic that moves your results most is not a benchmark. It is the share of your audience you can safely email. You can measure that for free before you send a single message.

TL;DR

• Industry reply-rate averages describe other people's lists. Your mailable rate and email status mix are the numbers you can measure today.
• It takes about 10 minutes and four count queries.
• It spends 0 LeadOcean records. Counts are free on every plan, including Free.

Prerequisites

• A LeadOcean account on the Free plan (no card): https://app.leadocean.io/register
• An API key exported as $LEADOCEAN_API_KEY
• curl and jq, or any MCP client connected to https://api.leadocean.io/mcp

For reply-rate benchmarks from other sources, see cold email response rate. This page covers the part benchmarks cannot: your own list.

Step 1: Size the whole audience

Start with the filter set you would actually send to. Here it is US VPs in sales. A count with count=true and limit=1 is free. Send count=true as a query parameter, not in the JSON body.

curl -s -X POST "https://api.leadocean.io/v1/people/search?count=true" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jobLevel": ["VP"],
    "jobFunction": ["Sales & Business Development"],
    "country": ["US"],
    "limit": 1
  }' | jq '.meta'

With no emailStatus in the body, you get everyone who matches the other filters. Enum values are exact strings. Check them with leadocean_list_enum_values or GET /v1/enums.

meta.total is capped at 100,000 on the REST search, so a total of 100,000 is a floor. For larger audiences use the MCP tool leadocean_count_leads (Step 4), which returns an exact total.

Step 2: Count the slice worth sending to

Pass the three statuses worth sending to: verified, catch_all_valid and catch_all. This is the same set leadocean_count_leads uses by default.

curl -s -X POST "https://api.leadocean.io/v1/people/search?count=true" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jobLevel": ["VP"],
    "jobFunction": ["Sales & Business Development"],
    "country": ["US"],
    "emailStatus": ["verified","catch_all_valid","catch_all"],
    "limit": 1
  }' | jq '.meta.total'

Divide this by the Step 1 total. That ratio is your mailable rate. It is a real statistic about your audience, and no blog benchmark can give it to you.

Step 3: Split out the strict slice

Catch-all domains accept any address, so a catch-all result is a weaker promise than verified. Narrow to verified to see how much of your list is high confidence.

curl -s -X POST "https://api.leadocean.io/v1/people/search?count=true" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jobLevel": ["VP"],
    "jobFunction": ["Sales & Business Development"],
    "country": ["US"],
    "emailStatus": ["verified"],
    "limit": 1
  }' | jq '.meta.total'

A search count of verified is an upper bound: enrichment confirms each address, and the enriched status is the correct one. Run it again with ["risky"] to see the slice you should not send to by default. Read email_status on each record before sending. There is no refund for bounced emails.

Step 4: Run it from an MCP client

The same four counts work from Claude, ChatGPT or any MCP client. leadocean_count_leads is free and returns totalAll beside the mailable total, so the gap is visible in one call.

Use leadocean_count_leads with jobLevel VP, jobFunction
"Sales & Business Development", country US, facets false.
Then repeat with emailStatus ["verified"], then ["risky"].
Report each total and its share of totalAll.

What you get

These are live results from leadocean_count_leads on 2026-10-21. Facets were off, and every call spent 0 records.

Three things stand out:

• Only 36.9% of this audience is mailable under the default definition. A list quoted as "350k VPs" is a third of that for sending.
• Verified alone is 8.9% of all people, or 24.0% of the mailable slice. The rest of the mailable slice is catch-all.
• The mailable count spans an estimated 58,121 distinct employers (distinctCompanies, not exact at that size).

A count with emailStatus is labelled by what you filtered. It is a size of a slice, not a promise of inbox placement.

Response shape from the API reference (placeholder values), for a REST count call that hit the 100,000 cap:

{
  "success": true,
  "data": [],
  "meta": {
    "total": 100000,
    "totalIsExact": false,
    "distinctCompanies": 12345,
    "countOnly": true
  }
}

Troubleshooting

FAQ