A cold email to a VP of operations gets judged the way they judge a process: does it waste a step. This is the reader who owns cycle time, cost per unit, and the SLA the customers actually feel, and who spends the day between a floor walk, a vendor escalation, and a meeting where finance asks why margin moved. They read fast, they distrust adjectives, and they have sat through enough 'operational transformation' pitches to know that most vendors have never watched a shift change. The good news is that operations leaves a public trail: a new facility announced, a WMS or ERP migration mentioned in a job posting, a new region on the coverage map, a hiring surge for analysts or supervisors. Each one comes with a predictable problem that shows up ninety days later. The three templates below name the trail, make one point, and stay under 90 words. The Claude prompt underneath reads the postings and the press page so the trail is real.
What a VP of Operations is measured on, and what they delete
A VP of operations is measured on cost per unit or per order, cycle time, on-time performance against the SLA, and gross margin, reviewed monthly with finance and weekly with whoever runs the floor or the fleet. They read on a phone between walks and a laptop at 7am, they respond to email that looks like a decision and ignore email that looks like reading, and they have almost no tolerance for words that do not point at a process. An executive assistant may filter at larger companies, and that person forwards what is short and specific. They delete 'transformation', 'full visibility', anything that describes software before describing the problem, and any pitch that does not know the difference between their industry's operations and everyone else's. They reply to emails that name the facility, the system, or the hire and the problem it will create.
Cold email to a VP of operations: the three templates
Swap in the unit they actually count (orders, pallets, tickets, deliveries, jobs) before sending; 'cost per unit' in the abstract reads as a vendor who has not visited the floor.
Subject: the new {{city}} facility
{{First name}}, saw {{company}} opened the {{city}} site in {{month}}. Around day 90 the new site's cost per {{unit}} usually still runs well above the mature sites, and nobody can say whether it is labor, layout, or the {{system}} configuration.
That question eats a quarter if the data is not set up to answer it.
I can send how {{customer, e.g. Harlow Logistics}} instrumented a new site to answer it in weeks. Useful?Subject: {{system}} migration, month three
{{First name}}, your posting for a {{role, e.g. WMS analyst}} mentions {{system}}, which suggests you are mid-migration or just past it. Month three is usually when the exceptions the old process absorbed quietly start showing up in the SLA numbers.
Most ops teams find them by hand, one escalation at a time.
I help teams find them from the data instead. Worth a reply on where you are in the rollout?Subject: {{customer}}'s cost per {{unit}}
{{First name}}, {{customer}} runs {{number}} sites with a {{team size}}-person ops team, roughly your footprint.
They took cost per {{unit}} from {{before}} to {{after}} in {{timeframe}}, without adding headcount, by {{one-line change}}. On-time performance held through it, which is the part their VP was worried about.
I can send the numbers on one page. Would that be useful ahead of your next budget review?the new {{city}} facility
{{system}} migration, month three
{{customer}}'s cost per {{unit}}
the {{city}} site at day 90
{{month}}'s on-time number
where the exceptions wentSend at 6:45am local to the facility, not to headquarters; a VP of operations reads before the first walk, and an email that arrives mid-shift is read after the shift, if at all.
Personalize these to the account, not just the persona
A VP of operations respects an email that knows their footprint: how many sites, which systems, what just changed. That is public in press releases and job postings, and stitching it together is the part reps skip. Paste the URL and the templates into the prompt below and Claude builds the footprint and marks what is confirmed.
You are writing a cold email to the VP of Operations at {{company}} ({{company URL}}).
Read the press or news page for new facilities, regions, acquisitions, or partnerships in the last 12 months. Read open operations, supply chain, and analyst roles for named systems (WMS, ERP, TMS, MES) and for clues about what is being rolled out. Build a short footprint: sites, systems, recent changes, and what each change will predictably break at the 90-day mark. Mark each item Confirmed or Inferred.
Rewrite the three templates below around the most concrete confirmed change. Each body under 90 words, one process problem, one idea, one soft ask. Use the vocabulary of their industry rather than generic operations language. No 'transformation', no 'visibility'.
Finish with the subject line you would send first and the process metric you expect them to reply about.
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 a VP of operations?
Name something in their footprint that just changed, a new facility, a system migration, a hiring surge for supervisors, and say what usually breaks ninety days after it. Then make one point tied to cost per unit, cycle time, or on-time performance, and ask for a reply rather than a meeting. Keep it under 90 words and use the vocabulary of their industry. A VP of operations judges an email the way they judge a process, so every sentence that does not move toward a decision counts against you.
What words should you avoid in a cold email to operations leaders?
'Transformation', 'visibility', 'optimize', and any description of software that comes before a description of a process problem. Operations leaders have heard every vendor promise a single pane of glass and most of them have lived through the rollout that followed. Also avoid claims that treat all operations as the same; a fulfillment VP and a field-service VP share a title and almost nothing else. Use their unit of work, their system names, and their SLA language, and let the product come second.
Should you email the VP of operations or the COO?
Email the VP of operations when the problem lives in a specific process: a site, a fleet, a warehouse, a service queue. They own the metric day to day and can run a pilot at one location without a board conversation. The COO owns the whole system and the budget, and reads through an assistant. If both exist, start with the VP and let the pilot's numbers earn the COO introduction. At companies under a few hundred people the VP of operations often reports straight to the CEO and there is no COO to escalate to.