A cold email to an IT director has to get past two filters before a human sees it: the mail gateway their own team configured, and the habit of a person who treats every unexpected link as a phishing test. IT directors are pitched by every SaaS vendor, every MSP, and every reseller in their region, and they have been burned by enough 'quick sync' emails that turned into procurement fights that the default response to a stranger is suspicion. Writing to them means writing like a colleague from another department would: plain text, no links in the first email, a subject line that would not trip a Bayesian filter, and an observation about their actual environment, which is more visible than most reps realise from job postings and public compliance pages. The three templates below follow those rules and stay under 90 words. The Claude prompt underneath reads the public footprint of their stack before you write a word.
What a IT Director is measured on, and what they delete
An IT director is measured on uptime, ticket volume and resolution time, audit findings, and staying inside a budget that finance treats as a cost center, with license sprawl and shadow IT as the problems that get them blamed for other people's decisions. They read in Outlook, on a desktop, in the morning before tickets pile up, and their own gateway rejects a large share of vendor mail before it arrives: tracking pixels, link shorteners, and marketing-domain senders all count against you. What survives gets read for risk first. They delete 'digital transformation', anything that arrives with a calendar link, emails from a domain that does not match the sender's company, and any pitch that ignores procurement and security review as if a director could just buy something. They reply to emails that name a system they run and a problem they already have a ticket for.
Cold email to an IT director: the three templates
Send these as plain text from a named mailbox on your company domain, with no links, images, or calendar invites in the first message. Add the link only after they reply.
Subject: {{system}} at {{company}}
{{First name}}, your posting for a {{role, e.g. systems administrator}} lists {{system}} and {{system}} in the same stack, which usually means the {{integration or migration}} is being held together by one person and a runbook.
That is a ticket volume problem long before it is a security one.
I work with IT teams on exactly that handoff. No links here on purpose; reply and I will send the two-page summary, or tell me it is already handled.Subject: license count vs headcount
{{First name}}, at {{company}}'s size the gap between paid seats and active users on {{tool category}} tends to be wide, and finance finds it during budget season before IT does.
Getting ahead of that is a spreadsheet nobody has time to build.
I can show you how {{customer}}'s IT team built it once and reclaimed the budget for things they actually wanted. Worth a reply?Subject: {{customer}}'s audit, {{year}}
{{First name}}, {{customer}}'s IT director ran a {{team size}}-person team supporting {{user count}} users on {{system}}, similar to your footprint from what is public.
Their {{audit or certification}} findings went from {{before}} to {{after}} in {{timeframe}}, mostly by {{one-line change}}, and ticket volume dropped with it.
I can send the summary as plain text. Would that be useful before your next renewal cycle?{{system}} at {{company}}
license count vs headcount
{{customer}}'s audit, {{year}}
your {{role}} posting
{{tool}} renewal in {{month}}
one runbook, one personCheck your own domain's SPF, DKIM, and DMARC before sending anything to an IT director; they will, and a failing record ends the conversation before your first line does.
Personalize these to the account, not just the persona
An IT director's environment is more public than they think: job postings name the stack, compliance pages name the frameworks, the careers page names the tools. Turning that into a specific observation without guessing takes reading. Paste the URL and the templates into the prompt below and Claude builds the picture and flags what it could not confirm.
You are writing a cold email to the IT Director at {{company}} ({{company URL}}).
Read the careers page and any open IT, security, or systems roles: list every named system, tool, and certification. Read the security or trust page for compliance frameworks. Note company size and any recent acquisition, office move, or system migration mentioned publicly. Build a one-paragraph picture of the environment and mark each item Confirmed or Inferred.
Rewrite the three templates below around the most specific confirmed item. Each body under 90 words, plain text, no links, no calendar invites, no words a spam filter would flag. Acknowledge that procurement and security review exist. One idea, one soft ask.
Finish with the subject line least likely to look like marketing mail and why.
MY PRODUCT: {{one-line description}}
PROOF: {{customer, metric, before, after, timeframe}}
TEMPLATES:
{{paste the templates above}}Write cold email at scale with Claude
- B2B cold email templates skill →The Claude skill that writes cold email in your brand voice with the banned-word list and the one-idea rule baked in.
- Cold email from a value prop prompt →The copy-paste prompt version: one value prop in, one specific email out.
- Personalize cold email with Clay and Claude →The use case that runs these templates across a whole list with real enrichment data.
Frequently asked questions
How do you write a cold email to an IT director that does not get filtered?
Send plain text from a real person's mailbox with no links, no images, no tracking pixel, and no calendar invite in the first email. Name a system you know they run, which their own job postings will tell you, and tie it to a problem that generates tickets. Say outright that you know procurement and security review exist. Keep it under 90 words and ask for a reply rather than a meeting. An IT director's gateway and their own habits reject anything that looks like marketing mail.
What subject lines work for IT directors?
Subject lines that look like an internal ticket or a renewal reminder: the name of a system plus the company, 'license count vs headcount', or a tool name with a month. They open mail that reads like operations and skip mail that reads like promotion. Avoid exclamation marks, percentages, 'free', 'transformation', and anything in title case with more than five words; those trip both the filter and the person. Lowercase, specific, and boring beats clever every time in this inbox.
Should you cold email the IT director or the CIO?
Email the IT director when your product lands in day-to-day operations: endpoints, identity, licensing, help desk, backups, network. They feel the ticket volume and can run a pilot without a board conversation. The CIO owns strategy and large budgets, and reads through a chief of staff. If the company has both, start with the director and let them bring the CIO in when the pilot has numbers. At companies under a few hundred people the director often is the top of IT, so there is nobody above to escalate to anyway.