How to Sell to an IT Director (and Count the List by Region)

You sell to an IT Director by solving one operational problem in their stack and making the risk of trying you close to zero. This guide covers what an IT Director cares about, who sits beside them, how to count them by region, and four first lines.

TL;DR

• An IT Director buys uptime, security and fewer tickets. Skip the feature tour. Lead with one risk you remove or one task you take off their team.
• Count first, send second. On 2026-10-21 LeadOcean showed 20,450 mailable IT Directors across four sales regions, 15,226 of them in NORAM.
• 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 IT Director actually cares about

An IT Director keeps the business running and gets blamed when it stops. Every vendor email gets read through that lens.

They care about four things.

1. Uptime. Outages reach the CEO fast. Anything that adds a new failure point needs a clear reason.
2. Security. A new tool is a new attack surface. Expect questions on access, data handling and who else uses it.
3. Team load. Their people are already stretched. A tool that adds admin work loses to one that removes it.
4. Integration and cost. It must fit the current stack, and the spend must survive a budget review.

They do not respond to "transform your IT". They respond to a specific problem named in their words, such as patch backlog, license sprawl or onboarding tickets.

What kills the deal

IT Directors rarely reject the idea. They reject the friction. Answer these in the first two emails.

• "Send it to security." Normal. Ask who, and offer a short security summary they can forward.
• "We already have a tool for that." Do not argue. Ask what the current tool does not cover.
• "No time this quarter." Offer a small pilot with a clear end date and no migration.
• Vague claims. "Improve efficiency" is deleted. A named problem and one number get read.

Where an IT Director sits in the buying committee

An IT Director is usually an evaluator and a blocker, sometimes the budget owner. They can stop a deal with a security or integration objection more easily than they can start one.

• The CIO or CTO owns the budget and the strategy, and signs large contracts. See how to sell to a CIO.
• The CISO or security lead reviews risk before anything touches company data. See how to sell to a CISO.
• The business sponsor (a marketing, sales or HR leader) often starts the request and needs IT to approve it. See how to sell to a marketing director, a sales director and an HR director.
• Engineers and admins run the pilot and tell the IT Director if it works.
• Finance and procurement check the contract at the end.

The mix changes with company size. In a company under 200 people the IT Director may be the only technical voice, and they often decide alone. In an enterprise they are one of several signatures, and procurement owns the final timeline.

If a business team brought you in, write to the IT Director as a helper, not a gatekeeper. If you started in IT, ask who else needs to sign and make the forward easy.

Step 1: Count IT Directors by region (free)

A count spends zero records and tells you whether a region is worth a campaign.

leadocean_count_leads counts mailable people by default: verified, catch_all_valid and catch_all addresses. The filter below uses jobLevel Director and the title keyword "IT Director". Title matching is keyword based, so "Director of IT" may not match the phrase "IT Director". Check a sample before you trust the total.

{
  "tool": "leadocean_count_leads",
  "arguments": {
    "jobLevel": ["Director"],
    "title": ["IT Director"],
    "salesRegion": ["NORAM"],
    "facets": false
  }
}

Repeat with EMEA, APAC and LATAM. Enum values are exact strings. Check them with leadocean_list_enum_values if a count comes back empty. For one country, use country with an ISO code such as ["DE"]. To catch "Director of Information Technology" as well, add a second title value, or filter on jobFunction Information Technology with jobLevel Director.

Step 2: Read the count for each region

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

Read two things from this. NORAM is about three quarters of the mailable list (15,226 of 20,450), so start there. And the last column shows how much you would mail blind: in NORAM, 41,001 people match but only 15,226 are mailable. A count with default email statuses is a mailable count. A count with hasEmail is not, so label it by what you filtered.

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 '{
    "jobLevel": ["Director"],
    "title": ["IT Director"],
    "salesRegion": ["EMEA"],
    "employeeRange": ["201-500", "501-1000"],
    "emailStatus": ["verified"],
    "limit": 25
  }' | jq '.data | length'

Add the company-size filter first. An IT Director at 300 people runs the whole stack. At 10,000 people they run one slice of it. Page with the cursor value from meta. One search pages to 10,000 rows, so narrow the filters instead of walking the whole index.

Do not mix levels in one count. A "Director" job level and a "VP" job level are different buyers with different budgets, so count them separately and write to each in its own words. A Director-level IT leader usually owns delivery and vendors, while a VP owns strategy and headcount.

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: .experiences[0:3], certifications}'

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

Past roles show how they got here. An IT Director who came up through infrastructure cares about stability, while one who came from security cares about control. Write the first line in that language.

Certifications are the useful part for this role. A security or cloud certification tells you what they care about. A career built in one vendor's ecosystem tells you what they will compare you to.

Step 5: Write the first line

The first line must name a problem they own. Pick one of these four angles and keep the email under 90 words.

1. Team load: "Your team probably spends hours a week on {task}. Want to see how {peer} removed it?"
2. Security: "Short security summary attached: where data lives, who can access it, how to remove it."
3. Integration: "Works with {tool in their stack} through a documented API. No migration."
4. Territory: "I counted {N} mailable IT Directors in {region} 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.

Use a peer only if you have a real, approved customer to name. If you do not, drop the peer clause. These lines are starting points, not measured results. 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 '{
    "filters": {
      "jobLevel": ["Director"],
      "title": ["IT Director"],
      "salesRegion": ["EMEA"],
      "employeeRange": ["201-500", "501-1000"],
      "emailStatus": ["verified"]
    },
    "limit": 1000
  }'

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. See pricing for the plans.

What you get

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

{
  "total": 3303,
  "totalIsExact": true,
  "totalAll": 11354,
  "distinctCompanies": 2355,
  "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