Write me a cold email to a head of operations that does not sound like a template
Keep it to 50 to 100 words, name one operational problem in their words, use a plain short subject, and offer something useful instead of a meeting.
Smalt AI team ·
Keep it between 50 and 100 words, with a subject line of one to four plain words. Open with one specific operational problem the person owns, written the way they would say it, and end by offering something useful (a one-page process, a benchmark, a checklist) instead of asking for a meeting. Leave out pitch language, buzzwords and claims about return on investment.
What the data says about emails to executives
The best public numbers come from sales-call analytics vendors, so treat them as directional. They are large samples, but the companies selling the analysis have a stake in the conclusions, and none of the figures below are about heads of operations specifically.
Gong Labs analysed more than a million executive sales cycles (published January 2026) and found that C-level executives were 30.2% less likely to reply than non-executives. Emails of 50 to 100 words performed best, and reply rates dropped sharply above 100. Executives spent about nine seconds at most reading an email they opened. Subject lines of one to four words had the best open rates, although open rates are an unreliable measure on their own. Gong also found that a call to action framed as an offer of value worked better than a request for a meeting.
A separate Gong analysis of more than 28 million cold emails (July 2025, done with Outbound Squad and promotional in context) reported that pitch-heavy emails cut reply rates by up to 57%. Buzzwords and numbers in subject lines cut open rates by up to 17.9%. The same study put the average at 344 cold emails per meeting booked, which is a useful reminder that a well-written email still gets ignored most of the time.
Neither source measures how much personalization lifts replies, so this post does not claim a figure for it. What the data supports is brevity, plain subject lines and a low-pressure ask.
How to write it
- Find a real problem before you write a word. A head of operations owns throughput, handoffs, vendors, scheduling and the processes nobody has documented. Look at the company’s open job posts, a recent news item or a public complaint, and pick one thing that points to a specific operational problem. “Three open dock supervisor roles” tells you more than “fast-growing logistics company”.
- Write the subject as a label, not a hook. Use one to four words, with no numbers, no buzzwords and no tricks. The company name plus the topic works: “Dock scheduling at Harlow”.
- Open with the problem, in their words. One sentence about the situation you noticed, phrased the way an operations lead would say it. Skip “I hope this finds you well” and any sentence about your own company.
- Ask a question you could be wrong about. It shows you are guessing from the outside and invites a one-line correction.
- Offer something to read, not time to spend. Gong’s data favours an offer of value over a meeting request. A one-page description of how similar teams handle the problem is enough.
- Cut to the limit. Count the words. If you are above 100, remove the sentence that explains your product.
An illustration
This is a made-up example with a made-up company, written to show the structure. It is not a template to paste, and the details are invented.
Subject: Dock scheduling at Harlow
Hi Dana,
Harlow Freight has had three dock supervisor openings listed since August. In some warehouses, trucks end up scheduled from a shared spreadsheet that one person owns.
Is that roughly how it works at Harlow? If so, I can send a one-page write-up of how a few warehouses split that spreadsheet so it survives a sick day. No call needed.
Priya
It runs to about 70 words, names one problem, asks a question and offers a document. Nothing in it describes the sender’s product.
Rules that still apply to a one-to-one email
A single email sent by hand still falls under email law, and there is no business-to-business exemption. The FTC’s CAN-SPAM compliance guide says the rules cover all commercial messages, including those sent to other businesses. You need accurate From, To and routing information, a subject line that is not deceptive, a valid postal address, and an opt-out that works and is honoured within 10 business days. Penalties can reach more than $53,000 per violating email (the FTC adjusts the exact figure each year, currently $53,088).
Google’s sender guidelines add technical requirements. The strictest ones apply to bulk senders, defined as 5,000 or more messages a day to Gmail addresses: SPF, DKIM and DMARC authentication, one-click unsubscribe on marketing mail, and a spam rate under 0.30% (Google advises aiming for under 0.10%). Most people writing a handful of emails a day will not reach that volume, but a high spam-complaint rate is what a pitch-heavy template tends to produce.
Doing it with an AI coworker
With Smalt, you can hand over the research and the first draft and keep the decision. Ask it to find the head of operations at a company you name, to search the web for recent news and open roles that point to an operational problem, and to write a short email of under 100 words with a plain subject line and an offer of something to read.
You connect Gmail or Outlook, and it prepares the email there. Emails wait for your approval before anything is sent, so you can send, edit or discard each one. If you want more than one, give it a list of companies and the same instructions, and read each draft before approving it.
What to check before you rely on it
Check the problem you named. A job post or a news item is a signal, not a fact about how that company runs, and a confident but wrong guess about someone’s process is worse than a generic opener. Phrase it as a question, and confirm the detail against a second source.
Check that the person is current. Titles change, and “head of operations” varies by company: some call it COO, VP operations or director of supply chain. Confirm the role before you send.
Check the word count and the offer. If the email is over 100 words, or if the offer is a call in disguise, rewrite it. If you promise a one-page document, have it ready before you send.
Check the legal basics for where you and the recipient are. CAN-SPAM is a US law, and other countries set stricter rules for emailing business contacts without prior consent. Ask whoever handles compliance in your company if you are unsure.
Last, keep expectations modest. Even with a well-written email, the 344-per-meeting average suggests most will get no reply, and the figures here come from vendor analyses, not independent research.
Smalt is an AI coworker that takes jobs like this end to end and hands back the finished file.