How to Find a CRO's Phone Number (2026)

The fastest way to find a CRO's phone number is to search a people database for Chief Revenue Officers flagged with a phone, then pull the direct dial by person id. A switchboard gets you a gatekeeper. A direct dial or mobile gets you the CRO.

TL;DR

• Search for CROs with hasPhone: true, size the list for free, then pull numbers only for people you will call.
• Time: about 15 minutes for one CRO, about 30 for a list of 500. Cost: 1 LeadOcean record per number pulled.
• Check the calling rules first. The API returns a number, not permission to dial it.

Prerequisites

• A LeadOcean account on the free plan: app.leadocean.io/register. Free gives you 1,000 records for life, every feature and 5 requests a second.
• An API key from the app, exported as $LEADOCEAN_API_KEY.
• curl and jq.
• A target: a company domain for one CRO, or a filter set for a list.

Step 1: Pick the right "CRO" and the right kind of number

CRO means Chief Revenue Officer here. The same three letters also mean Chief Risk Officer and Chief Research Officer, so spell the title out in your filter.

A main line rings reception. A direct dial or mobile rings the person. Revenue leaders are busy and screened, so the main line rarely works.

LeadOcean returns each number with the source's own type label, such as mobile, direct, office or unknown. Take mobile and direct first. Treat office as a fallback. Many CROs sit at companies of 11 to 200 people, where the number you want may simply be a mobile.

Step 2: Size the CRO list for free

Count before you spend. A count costs 0 records. Ask the MCP tool leadocean_count_leads, or send count=true with limit=1 as query parameters on the search endpoint.

curl -s -X POST "https://api.leadocean.io/v1/people/search?count=true&limit=1" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": ["Chief Revenue Officer"],
    "country": ["US"],
    "hasPhone": true
  }'

meta.total is capped at 100,000 on this call. Enum values are exact strings, so check them with leadocean_list_enum_values before you filter by jobLevel or employeeRange.

Step 3: Search for CROs who have a phone on file

Search returns people, one record per row. Filters are arrays, the body is flat JSON, and limit runs 1 to 100.

curl -s -X POST "https://api.leadocean.io/v1/people/search" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": ["Chief Revenue Officer"],
    "country": ["US"],
    "employeeRange": ["51-200"],
    "hasPhone": true,
    "limit": 25
  }' | jq '.meta, (.data | length)'

Page on with meta.nextCursor. One search stops at 10,000 rows (meta.depthCapped), so narrow by industry or headcount instead of paging deeper. To find one named company's CRO, use GET /v1/companies/{domain}/people and read the title column.

Step 4: Pull the direct dial

Spend records last. Each phone pull is one record, so a 25-person test batch costs 25 records on the free plan.

Take the person id from meta.source_ids.person_id on a search row and ask for the phone. This costs 1 record per call, including a call that finds nothing.

curl -s "https://api.leadocean.io/v2/people/phone?person_id=1234567" \
  -H "x-api-key: $LEADOCEAN_API_KEY" | jq

Numbers come back best first, and best points at the top one. In Claude or any MCP client, the tool leadocean_find_phone does the same job.

For a list over a few hundred people, skip the loop. Start an export with POST /v1/exports. One export takes up to 50,000 rows, and an account gets 500,000 a day. Bulk CSV export is not on Free: it comes with Solo ($97 a month) and Agency ($497 a month, 50k rows a file).

curl -s -X POST "https://api.leadocean.io/v1/exports" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "us-cros-with-phone",
    "filters": { "title": ["Chief Revenue Officer"], "country": ["US"], "hasPhone": true },
    "limit": 500,
    "preset": "full",
    "reveal": "email_phone"
  }'

Poll GET /v1/exports/{id}, then fetch GET /v1/exports/{id}/download. You can build the same export in the app: filter builder, column picker, price preview, then download.

Step 5: Check what you may call before you dial

Having a number is not the same as being allowed to call it. The rules differ by country, by whether the line is a mobile, and by whether you use an autodialer or a recorded message.

• The API does not return a do-not-call flag. The v2 phone endpoint omits dnc because the field is unpopulated at source. Its absence is not clearance.
• Run your own list through the registries that apply to you before a campaign.
• In the US, the FTC's Telemarketing Sales Rule exempts most calls to a business, including from its Do Not Call provisions. The exemption does not cover calls selling nondurable office or cleaning supplies, and the ban on misrepresentation still applies (16 CFR 310.6(b)(7), checked October 2026).
• A CRO at a small firm may give out a personal mobile as the business line. Ask your counsel, and keep a suppression list.

This is not legal advice.

What you get

Expect a short list, not a dump. Every row in the slice below has a phone flag, and some pulls will return an office line rather than a direct dial. Sort by type and call direct and mobile first.

A free count run on 2026-10-21 with leadocean_count_leads (title Chief Revenue Officer, hasPhone true, no email filter). It is a phone-flag count. It is not a verified-number count.

{
  "total": 16219,
  "totalIsExact": true,
  "distinctCompanies": 13911,
  "credits": 0,
  "facets": {
    "country": [
      { "value": "US", "count": 11934 },
      { "value": "GB", "count": 527 },
      { "value": "CA", "count": 438 }
    ],
    "company_size": [
      { "value": "11-50", "count": 4184 },
      { "value": "51-200", "count": 4088 },
      { "value": "1-10", "count": 2693 }
    ]
  }
}

The phone call returns this shape. It is the response shape from the API reference, with placeholder values.

{
  "success": true,
  "data": {
    "found": true,
    "phones": [
      { "phone": "+1 415 555 0133", "type": "direct" },
      { "phone": "+1 415 555 0134", "type": "office" }
    ],
    "best": { "phone": "+1 415 555 0133", "type": "direct" }
  }
}

The title match is a keyword match, so some rows will be a deputy or a "Chief Revenue Officer" of a one-person firm. Read the title column before you dial.

Troubleshooting

FAQ