How to Sell to a DevOps Engineer (with the LeadOcean API)

To sell to a DevOps engineer, lead with a specific operational problem, keep the message short, and write to the engineer who owns the pain, not only the VP above them. This guide shows how to size the market by region for free, pull a first batch of contacts, and write first lines that fit.

TL;DR

• DevOps engineers recommend and veto tools. They rarely hold the budget, so you sell to them and to the VP of Engineering who signs.
• LeadOcean counted 61,152 mailable DevOps Engineers worldwide on 2026-10-21. The counts are free.
• The whole recipe takes about 20 minutes and spends 11 records: 10 search rows and 1 enrichment.

Prerequisites

• A LeadOcean account on the free plan (1,000 records for life, no card): app.leadocean.io/register.
• An API key exported as $LEADOCEAN_API_KEY.
• curl and jq.
• A one-sentence description of the problem your product fixes for an infrastructure team.

Step 1: Learn what a DevOps engineer cares about

A DevOps engineer cares about uptime, deploy speed, on-call load and the cost of the tool they have to maintain. They judge your product by how it behaves at 3 a.m., not by the demo.

Write these four questions on one page before you write a single email:

1. What breaks or slows down in their pipeline today that we fix?
2. How long does it take to install, and what does it touch (agents, IAM, network)?
3. What does it cost to run, and who pages when it fails?
4. Can they trial it without a call?

If you cannot answer all four in one sentence each, the email is not ready. DevOps buyers also dislike gated pages, so link to docs, not to a form.

Most DevOps engineers also ignore three things: vague claims about "efficiency", sales jargon, and any message that asks for 30 minutes before it shows value. They read the first line on a phone between alerts. If that line does not name a problem they have, the email is gone.

Match your proof to how they work. They trust a public changelog, a status page, a docs site and an open repo more than a case study. Link one of those in every email, and make sure the pricing page is public. A hidden price reads as a future headache.

Step 2: Place them in the buying committee

A DevOps engineer is usually the champion or the technical evaluator, not the economic buyer. The budget sits with a Director or VP of Engineering, or with a Head of Platform or Infrastructure.

Map the committee before you pull contacts:

Sell to the evaluator first when the tool costs less than a typical team budget line. Go to the VP first when the tool changes how the whole team ships. For the VP angle, read how to sell to a VP of Engineering.

Step 3: Count the mailable DevOps Engineers by region

Count first, because a count spends no records. Send count=true as a query parameter with limit=1. The data comes back empty and meta.total holds the number (capped at 100,000).

for region in NORAM EMEA APAC LATAM; do
  echo -n "$region: "
  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\": [\"DevOps Engineer\"], \"salesRegion\": [\"$region\"], \"emailStatus\": [\"verified\", \"catch_all_valid\", \"catch_all\"]}" \
    | jq '.meta.total'
done

The MCP tool leadocean_count_leads returns the same numbers and also the distinct employers. It is free too. Counts below are mailable: verified, catch_all_valid or catch_all email status, title "DevOps Engineer", run on 2026-10-21.

Titles vary, so run the count for each title you plan to target before you decide. The same call works for "Site Reliability Engineer", "Platform Engineer" and "Cloud Engineer". Each count is free, so compare them and pick the one with the best mailable total for your region.

Scope the list to companies that fit. A seed-stage team of five does not have a DevOps function, and a 50,000-person enterprise has a procurement process. Add employeeRange to the same body to test this:

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": ["DevOps Engineer"], "salesRegion": ["EMEA"], "employeeRange": ["201-500", "501-1000"], "emailStatus": ["verified", "catch_all_valid", "catch_all"]}' \
  | jq '.meta.total'

A REST count with emailStatus set counts only the statuses you passed. Label it by those statuses in your plan, and do not call it the size of the whole market.

Step 4: Pull a first batch of 10 contacts

Pick one region and pull a small batch. Ten rows is enough to test your message before you spend more.

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": ["DevOps Engineer"],
    "salesRegion": ["NORAM"],
    "emailStatus": ["verified"],
    "limit": 10
  }' | jq '.data | length'

This spends 10 records. To get more, pass the cursor from meta to the next call. One search pages to 10,000 rows, so narrow by country, employeeRange or technologies instead of walking the whole index.

Then enrich one person by person_id to read their current role and career history:

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_SEARCH", "reveal_email": true}'

That is 1 record. The response includes resume_data with past roles, so you can open with something the engineer actually did. For the email-finding side, see how to find a DevOps engineer's email.

Step 5: Write first lines that fit

Open with the problem, name the stack, and ask one small question. Keep the whole email under 80 words. Placeholders below use Acme and Jane.

Subject: on-call pages at Acme

Hi Jane,

Teams running Kubernetes at Acme's size usually spend their worst
on-call hours on config drift between staging and prod. We catch
that drift before the deploy, with a read-only agent.

Worth sending you the 2-minute install doc?

Three more first lines to adapt:

• "You list Terraform and ArgoCD on your profile. We plug into both without a new agent."
• "Most pipeline tools add a step. Ours removes one. Can I send the config diff?"
• "Saw you moved from platform to DevOps at Acme. Who owns incident review there now?"

Use the technologies and keywords filters in the search to match the stack you name. Do not claim a result you cannot show. Engineers check.

Plan for the replies you will get. Most are short and blunt, so answer in kind:

Keep a record of which problem line got replies in each region. After the first 10, pull the next 25 from the same search with the cursor, change one variable, and compare. That is how a message gets better without a larger list.

Send the first 10 to test replies, then widen. For the marketing equivalent of this recipe, see how to sell to a VP of Marketing.

Step 6: Plan the sequence and the follow-up

Send four short touches over three weeks, and stop after the fourth. DevOps engineers punish persistence that adds nothing, so each touch must bring something new.

Day 1:  problem + one-line fix + docs link
Day 4:  a 3-line config or command they can run without you
Day 10: a short note on a failure mode you hit and how you handle it
Day 18: one question: who owns this at Acme, you or platform?

Send from your own sending tool. LeadOcean supplies the contacts, and the app exports a CSV with a column picker if you prefer to load a file. Check email_status before you send, because bounced emails are not refunded.

Track replies by role. If the engineer answers and points to a VP, write to the VP with the engineer's name in the first line. That is the shortest path through the committee.

What you get

The free count calls returned these figures on 2026-10-21. Title "DevOps Engineer", mailable (verified, catch_all_valid or catch_all), by salesRegion:

EMEA has the most mailable DevOps Engineers. APAC has the most matches overall but a lower share with a usable email, so start with NORAM or EMEA.

A search row looks like this (response shape from the API reference, 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": 10, "nextCursor": "CURSOR" }
}

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

Troubleshooting

FAQ