How to Sell to a Product Manager (and Count the List by Region)

TL;DR

• A product manager buys to ship the right thing sooner and to spend less time on manual work between a customer signal and a decision. Name one of those in your first line.
• Count first, send second. On 2026-10-21 LeadOcean showed 176,780 mailable people with "Product Manager" in their title in North America, 105,239 in EMEA, 61,541 in APAC and 14,306 in LATAM.
• The recipe takes about 25 minutes and spends about 26 LeadOcean records. Every count is free.

Prerequisites

• A free LeadOcean account and an API key from app.leadocean.io. Free gives you 1,000 records for life, no card, 5 requests a second.
• The key in your shell as $LEADOCEAN_API_KEY.
• curl and jq.
• Optional: Claude or any MCP client connected to https://api.leadocean.io/mcp, which has 13 tools including free counts.

What a product manager actually cares about

A product manager owns one product area: its backlog, its metrics and the case for what ships next. They answer to a Head of Product or VP of Product, and they work daily with engineering and design.

They care about five things, roughly in this order.

1. Their metric. Activation, retention or revenue for their area. If you do not move it, you are noise.
2. Time. A PM is the person who writes the spec, runs the sync and answers support. Anything that removes manual work gets a look.
3. Customer signal. Tools that shorten the path from feedback to a decision earn attention.
4. Engineering cost. A PM must ask engineers for time. A tool that works from one request, with no sprint to integrate, is easy to say yes to.
5. Evidence to forward. They defend choices upward. Give them a number or a working example they can paste into a doc.

They do not read feature lists. They read one sentence tied to their metric, then check whether they can try it alone.

What kills the deal

PMs say no for predictable reasons. Answer them in the first email.

• "I do not own the budget." True in most companies. Offer something a free plan covers, so no budget line is needed.
• "Engineering is full." Show how little engineering time a trial takes. Name the hours.
• "Not on the roadmap." Tie the first line to a metric already on it.
• "Send it to my manager." Good. Write the paragraph your PM can forward in one click.

Where a product manager sits in the buying committee

A product manager is usually an evaluator and champion, not the signer. They run the trial, form the opinion and carry it upward. In small companies they also hold the budget.

• The Head of Product or VP of Product approves anything that touches the product team. See how to sell to a head of product.
• Engineering managers and the CTO review integration cost and can block it. See how to sell to a CTO and how to sell to an engineering manager.
• IT joins when the tool needs access to company systems. See how to sell to an IT manager.
• Procurement joins when spend needs a contract. See how to sell to a procurement manager.
• Hiring managers matter if your product helps PMs build their team. See how to sell to a hiring manager.

Write to the PM as the person who has to explain your idea to someone else. Make it easy to explain.

Step 1: Count product managers by sales region (free)

Start with a count. It spends zero records and tells you whether the segment is worth a campaign.

leadocean_count_leads counts mailable people by default: verified, catch_all_valid and catch_all addresses. This count filters on title text, so it matches every title that contains "Product Manager". That includes "Senior Product Manager", "Group Product Manager" and also "Product Marketing Manager". Treat the totals as an upper bound for pure PMs.

{
  "tool": "leadocean_count_leads",
  "arguments": {
    "title": ["Product Manager"],
    "salesRegion": ["NORAM"],
    "facets": false
  }
}

Repeat with EMEA, APAC and LATAM. Add employeeRange: ["51-200", "201-500"] to see growth-stage companies only.

Step 2: Read the count for each region

Put the counts in one table before you pick a market. These ran on 2026-10-21 with title: ["Product Manager"] and the default mailable email statuses.

Read three things from this. The four regions hold 357,866 mailable people. NORAM is the largest at 176,780, which is 49%, ahead of EMEA at 105,239 (29%). LATAM is small enough to work as a named-account list.

The last column shows how much you would mail blind. In EMEA, 335,573 people match but only 105,239 are mailable. And at about five mailable PMs per employer in NORAM, you will often write to a company with several PMs. Pick the one whose area fits your product.

Step 3: Pull a sample from your best region

Narrow before you pull. Add a seniority or company-size filter, then take 25 rows. This spends 25 records. Search is a flat JSON body, filters are arrays, and limit runs from 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": ["Product Manager"],
    "salesRegion": ["NORAM"],
    "employeeRange": ["51-200", "201-500"],
    "emailStatus": ["verified"],
    "limit": 25
  }' | jq '{rows: (.data | length), next: .meta.nextCursor}'

Page by sending meta.nextCursor back as cursor. One search pages to 10,000 rows, so narrow the filters instead of walking the whole index.

Step 4: Enrich one record to read the career history

Before you write, read one profile. Person enrich returns career history: past roles, education, certifications and awards. Past employers carry no company_id yet.

Enrich takes exactly one of linkedin_url, email, phone or person_id. Each search row carries its id at meta.source_ids.person_id.

curl -s -X POST https://api.leadocean.io/v1/people/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_id": "1234567890", "reveal_email": true}' \
  | jq '.data.resume_data.experiences[0:3]'

This costs one record. A person we hold nothing for returns a 404 and costs nothing.

Look for the path. A PM who came from engineering cares about delivery cost. One who came from design cares about the user. One who joined in the last six months is still forming opinions and open to a short note.

Step 5: Write the first line

The first line must show you know the job. Pick one angle and keep the email under 90 words.

1. Metric: "Your area has a number to move this quarter. Here is how one request saves you an afternoon a week."
2. Time: "Specs, syncs, support. This removes one manual task from that list. Here is the curl."
3. Effort: "No SDK, one header. Your engineer does not need to be involved to try it."
4. Territory: "I counted {N} mailable product managers in {region} on {date}. Want the list?"

Send lines 1 to 3 only if they are true for your product. The territory line works because it is checkable. You ran a free count, so the number is real. Send it with the count and the date.

These are starting points, not measured results. Do not claim a reply rate you have not measured. Test two angles on 100 contacts each and keep the winner.

Step 6: Save the list as a CSV

When the sample converts, export the list. Bulk CSV export is not on the Free plan. Solo ($97 a month) includes it, and Agency ($497 a month) exports 50k rows a file. The ceiling is 50,000 rows a request and 500,000 a day.

curl -s -X POST https://api.leadocean.io/v1/exports \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Product managers NORAM 51-500",
    "filters": {
      "title": ["Product Manager"],
      "salesRegion": ["NORAM"],
      "employeeRange": ["51-200", "201-500"],
      "emailStatus": ["verified"]
    },
    "limit": 5000,
    "preset": "full"
  }'

The body takes filters (any people-search filter set), limit (rows) and a column preset. Poll GET /v1/exports/{id} until it returns a downloadUrl.

You can build the same export in the app at app.leadocean.io. The Exports page has a filter builder, a column picker and a price preview before you download.

What you get

The count in step 1, run on 2026-10-21 with title: ["Product Manager"] and salesRegion: ["EMEA"], returned:

{
  "total": 105239,
  "totalIsExact": true,
  "totalAll": 335573,
  "distinctCompanies": 29924,
  "credits": 0
}

total is the mailable count. totalAll is everyone matching without the email filter. The call cost no records.

A search row, response shape from the API reference, with placeholder values:

{
  "success": true,
  "data": [
    {
      "profile_data": { "profile_full_name": "Jane Doe" },
      "contact_data": {
        "has_email": true,
        "email_status": "verified",
        "contact_current_experiences": [
          { "job_title": "Product Manager", "company_name": "Acme", "company_domain": "acme.com" }
        ]
      },
      "meta": { "source_ids": { "person_id": "1234567890" } }
    }
  ],
  "meta": { "count": 1, "credits": 1, "nextCursor": "..." }
}

Troubleshooting

FAQ