How to Sell to an Engineering Manager (and Count the List by Region)

TL;DR

• An engineering manager is judged on shipping, team health and incidents. Sell time back or fewer pages at night, and say which in the first line.
• Count first, send second. On 2026-10-21 LeadOcean showed 206,163 mailable people with "Engineering Manager" in their title worldwide, 102,083 of them in the US.
• 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 an engineering manager actually cares about

An engineering manager runs a team of engineers and answers for what it ships. They sit between the people who write code and the people who set the roadmap.

They care about five things, roughly in this order.

1. Delivery. Did the team ship what it said it would, on the date it said. Anything that slips a sprint needs a good reason.
2. Team time. Every tool the team adopts costs onboarding and context switching. A tool that saves hours wins. One that adds a dashboard to check loses.
3. Reliability. Incidents land on their team first. They remember the vendor that caused a 3 a.m. page.
4. Hiring and retention. Good engineers are hard to hire and easy to lose. Anything that makes the team's day better, or less painful, counts.
5. Budget they can actually spend. Most can approve a small tool or a team seat. Bigger spend goes up a level.

They do not read marketing pages. They read docs, a changelog and a short note from someone who knows the job.

What kills the deal

Engineering managers say no for predictable reasons. Answer them before they ask.

• "My team does not have time to evaluate this." Offer a 30-minute setup with a real endpoint they can call from curl. No call, no slide deck.
• "We will build it ourselves." Often true. Give them the build cost in weeks, then the price. Do not argue the point.
• "Security has to review it." Send the data you touch, the auth method and the endpoint list in the first email.
• "This is not on the roadmap." Ask which goal the roadmap does cover, and tie the tool to that.
• "Talk to my director." Good. Give them one paragraph to forward, with the count, the filters and the use case.

Where an engineering manager sits in the buying committee

An engineering manager is usually the evaluator and sometimes the approver. For tools under a team budget they decide alone. For anything larger they write the case and hand it up.

• Engineers on the team try the tool and tell the manager if it works. A senior engineer can kill a deal with one comment.
• The director or VP of Engineering signs when spend crosses a threshold. See how to sell to a VP of Engineering.
• The product manager joins when the tool changes what ships. See how to sell to a product manager.
• IT or security reviews access and data handling. See how to sell to an IT manager.
• Finance or procurement handles terms, often with a vendor list you must be on.

Write to the engineering manager as the person who needs to justify the tool upward. Give them the one sentence they will forward.

Step 1: Count engineering managers by 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 titles that contain "Engineering Manager". That includes "Senior Engineering Manager" and "Software Engineering Manager", and also manufacturing and process engineering managers. Run it from any MCP client.

{
  "tool": "leadocean_count_leads",
  "arguments": {
    "title": ["Engineering Manager"],
    "country": ["US"]
  }
}

Repeat with IN, GB, CA and DE, or leave out country for the worldwide figure. Add employeeRange: ["1001-5000"] to see mid-enterprise 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: ["Engineering Manager"] and the default mailable email statuses.

Read three things from this. The US is about half of the worldwide mailable list (102,083 of 206,163). India is second at 21,427, ahead of GB at 9,444. And the last column shows how much you would mail blind: in the US, 207,282 people match but only 102,083 are mailable.

The industry mix tells you who to write to. In the US count, Software Development leads with 21,456, then Financial Services (4,538) and IT Services and IT Consulting (3,773). Motor Vehicle Manufacturing (3,569) and Semiconductor Manufacturing (3,635) also appear. A manufacturing engineering manager is a different buyer from a software one, so filter by industry before you write.

Seniority is almost all one band. Of the 206,163 mailable worldwide, 198,877 are at manager seniority. Only 543 are at VP and 699 at director, so this list is the manager layer and not the layer above it.

Company size skews large. Of the worldwide list, 81,657 work at companies with 10001+ employees, the largest single band. That is a long list for named-account work and a short one if you only sell to startups.

Step 3: Pull a sample from your best region

Pull 25 rows from the region you picked. 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": ["Engineering Manager"],
    "country": ["GB"],
    "emailStatus": ["verified"],
    "limit": 25
  }' | jq '.data | length'

Page with the cursor value from meta. 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. Use the meta.source_ids.person_id from a step 3 row.

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": "PERSON_ID_FROM_STEP_3", "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 manager who was a senior engineer last year still thinks like one, so lead with how the tool works. One who has led teams for a decade cares about delivery and headcount. One who joined the company in the last six months is setting up the team's tools and open to a short note.

Step 5: Write the first line

The first line must show you know the job. Pick one of these four angles and keep the email under 90 words.

1. Time: "Your team probably loses hours each sprint to {task}. Here is a curl command that does it in one call. Want to try it?"
2. Reliability: "Here are the rate limits per plan and the error codes, so you can judge the on-call risk before you read anything else."
3. Build vs buy: "You could build this in a few weeks. Here is what we run so you can compare it to your estimate."
4. Territory: "I counted {N} mailable engineering managers in {industry} on {date}. Want the list?"

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.

Match the angle to the industry. Software teams want the time and build-versus-buy angles. Manufacturers and banks run longer reviews, so lead with reliability and send the security details early.

These are starting points from how the segments are shaped, 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 rows 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": "GB engineering managers",
    "filters": {
      "title": ["Engineering Manager"],
      "country": ["GB"],
      "emailStatus": ["verified"]
    },
    "limit": 5000
  }'

filters takes the same filters as people search, and limit is the number of rows (each row is one record). Use the search preset for rows without contact points.

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: ["Engineering Manager"] and country: ["GB"], returned:

{
  "total": 9444,
  "totalIsExact": true,
  "totalAll": 29697,
  "distinctCompanies": 3520,
  "credits": 0
}

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

A search row follows the response shape from the API reference, shown here with placeholder values.

{
  "success": true,
  "data": [
    {
      "profile_data": { "profile_full_name": "Jane Doe" },
      "contact_data": {
        "has_email": true,
        "email_status": "verified",
        "email_type": "work"
      },
      "meta": { "source_ids": { "person_id": "1234567890" } }
    }
  ],
  "meta": { "count": 1, "limit": 25, "nextCursor": "CURSOR" }
}

Search rows carry identity, current role, company and the email flags, but no addresses. The person_id for enrich sits at meta.source_ids.person_id.

Troubleshooting

FAQ