Most cold emails fail before anyone judges the offer. The reader sees a greeting with their first name pasted in, a compliment about their "impressive growth," and a paragraph that could have been sent to ten thousand other people. Because it was. They delete it in about two seconds.
This guide breaks a first email into its working parts, shows what to keep and what to cut, and clears up a few persistent myths about spam words. It assumes your infrastructure is already sound. If it is not, no amount of copywriting will save you, so check the basics in the pre-send DNS checklist first.
Why template copy fails
People have seen every cold email pattern by now. "Hope this finds you well." "I came across your profile." "Quick question." "Would you be open to a 15-minute call?" Stacked together, they say a sequence wrote this and the sender knows nothing about the reader.
Template copy also hurts you quietly on the deliverability side. Mailbox providers watch how recipients react. Mail that gets deleted unread or marked as spam teaches the filter it is unwanted; replies do the opposite. So "reads human" is not a style preference. It feeds straight into where your next email lands.
The anatomy of a first email
A first touch has four jobs, and each part of the email does one of them.
Subject line
The subject's only job is to get the email opened by the right person. Short, lowercase-friendly, and specific beats clever. Two to five words that sound like something a colleague would send work well: "northwind's ap backlog" or "question about your sdr hiring." Avoid fake reply prefixes like "Re:" on a first touch. Sanity-check options with the subject line tester.
Opener
The first line shows up in the inbox preview, so it decides whether the email gets read. Skip the pleasantries and lead with something that proves you looked: a recent hire, a product change, a job post, a public number. One sentence is enough.
Reason for reaching out
Connect that observation to a problem you solve. This is the hinge of the email. "You are hiring three AP clerks" becomes "teams usually hire for AP when invoice volume outgrows the process, which is the thing we fix." No feature list. One problem, one outcome.
One ask
End with a single, low-effort question. "Worth a look?" or "Is this on your radar this quarter?" is easier to answer than a calendar link and a request for 30 minutes. Two asks in one email split attention and usually get zero.
Plain text, links and images in a first touch
Send first touches as plain text or very light HTML that looks like plain text. No banners, logos, or signature images. A one-to-one email from a real person has no header graphic, and filters know what marketing mail looks like.
Links deserve the same restraint. Zero or one link in a first email is a good rule. Every link is another domain that gets evaluated, and link shorteners or domains with a poor history can drag down a clean message. If you use click tracking, make sure the tracking domain is a custom one you control, not a shared one used by thousands of other senders. Many teams turn open and click tracking off for first touches entirely and judge results by replies instead.
Personalization that is actually relevant
Inserting {{first_name}} and {{company}} is mail merge, not personalization. Real personalization answers one question: why this person, right now?
- Weak: "I see you are the Head of Finance at Northwind." They know.
- Weak: "Loved your recent LinkedIn post!" with no detail. Obviously generated.
- Useful: "Northwind posted two AP roles last month." It is specific and it ties to the problem you solve.
You do not need a custom paragraph for every prospect. Instead, segment the list by a shared trigger, such as hiring for a role, a recent funding round, or a specific tool in their stack, and write one strong email per segment. Then add a single custom line where you have something real to say.
Length, and the truth about spintax
Most effective first emails land somewhere around 50 to 125 words. That is a rule of thumb, not a law, but if your email needs scrolling on a phone it is almost certainly too long. Cut the company history and every sentence that starts with "We are a leading."
Spintax, the {option a|option b} syntax that randomizes words, is often sold as a way to avoid filters noticing identical bodies. Some variation is reasonable when you send at volume. But filters compare messages by similarity, not exact match, so swapping "hi" for "hey" does little. Heavy spintax also tends to produce awkward sentences that read worse. A better use of effort is writing two or three genuinely different versions and testing them with A/B tests.
Spam words: what is myth and what still hurts
Lists of hundreds of "spam trigger words" circulate constantly. Modern filters at Gmail and Microsoft lean far more on sender reputation, authentication, and recipient engagement than on single words. A clean domain can write "free" in an email without disaster. A burned domain will land in spam with perfect copy. More on how this works in how Gmail and Outlook filter cold email.
That said, some patterns still hurt, mostly because they look like real spam:
- ALL CAPS subject lines and stacks of exclamation marks.
- Money and urgency combined: "guaranteed," "act now," "100% free," dollar amounts in the subject.
- Image-only emails or very high image-to-text ratios.
- URL shorteners, mismatched link text, and attachments on a first touch.
- Hidden text, odd character substitutions, or invisible tracking tricks.
Run drafts through the spam checker to catch these, then focus on reputation and relevance.
A before and after rewrite
Here is a typical template email to a fictional prospect, Dana, who runs finance at a fictional company, Northwind.
Subject: Quick question, Dana!! Hi Dana, I hope this email finds you well! I came across Northwind and was really impressed by your growth. At Ledgerly, we are a leading AI-powered accounts payable automation platform trusted by innovative companies to streamline workflows, cut costs and boost efficiency. Our features include OCR invoice capture, 3-way matching, approval routing, ERP sync and much more. Would you be open to a 30-minute call this week? Here is my calendar: [link] You can also see our case studies: [link] Best, Sam
And a rewrite that does the four jobs and nothing else:
Subject: northwind's ap hiring Hi Dana, Saw Northwind posted two AP clerk roles in the last month. Usually that means invoice volume has outgrown the approval process. We automate the matching and routing part, so the team you have handles more invoices without the extra headcount. Is this something you're looking at this quarter, or is hiring the plan? Sam
The rewrite is half the length, has no links, makes one observation, names one problem, and asks one easy question.
A self-review checklist before you send
- Could this exact email be sent to someone at a different company without edits? If yes, it is a template.
- Does the first line prove you know something specific about them?
- Is there exactly one problem and one ask?
- Is it under roughly 125 words and readable on a phone without scrolling?
- Zero or one link, no images, no attachments?
- No fake "Re:" prefixes, no ALL CAPS, no stacked urgency words?
- Read it aloud. Would you send this to a peer from your own inbox?
Good copy and good infrastructure work together. Sendbox handles the second half with dedicated IPs, warmup, and per-mailbox health monitoring, but the first half is still on you, and it is the half recipients actually read.
