Community content. Review instructions before giving them to an AI agent — treat modules like open-source code.
Cold Email Rules
Rules for writing B2B cold outreach emails that get replies instead of being marked as spam: earning the send, subject lines that read as internal, under-120-word structure, real personalization, and follow-up cadence.
Mby @markdownersPublished August 21, 2026 · ~5 min read
0 downloads · Used by 0 stacks
A cold email is an interruption the recipient didn't ask for — it has to justify itself in the first sentence or it gets deleted before the second. Every rule here follows from treating the recipient's attention as something to earn, not something owed to the sender.
Earn the send
- Have a real, specific reason this exact person is being contacted — something true about their role, their company's recent situation, or their public work that connects to the offer. If the same email could be sent to a thousand people with only the name changed, it hasn't earned the send.
- Research enough to be right about the recipient's situation, but not so much that the email reads as surveillance — referencing something genuinely public and relevant (a recent launch, a role change, a specific piece of content they published) reads as attentive; referencing something obscure or personal reads as unsettling.
- If there's no real reason to contact this specific person, that's a signal to refine the list, not to send anyway and hope volume compensates for relevance.
Subject lines that read as internal, not promotional
- Write subject lines the way a colleague would write one: short, lowercase-casual is fine, specific to the topic — "quick question about [specific thing]" or "[shared context] — worth a look?" rather than anything that reads like a marketing blast ("Unlock Your Team's Potential Today!").
- Avoid subject lines that promise something generic ("Following up," "Great opportunity") — they signal mass outreach before the email is even opened and get filtered by experienced recipients on pattern alone.
Under 120 words
- Keep the whole email short enough to read in under 15 seconds — cold email is competing with a full inbox, not a queued task the recipient has set aside time for. Length itself signals how much of the recipient's time is being asked for.
- Cut every sentence that doesn't directly serve relevance, value, or the ask. If a sentence could be deleted without weakening the email, delete it.
Structure: relevance, value, ask
- Open with the specific relevance line — why this person, why now. This does the work of justifying the interruption before asking for anything.
- State one clear value statement — what's being offered and why it matters to them specifically, in their terms, not the sender's product terminology. This is not the place for a feature list.
- Close with exactly one small, low-friction ask — "worth a 15-minute call?" or "want me to send the one-pager?" not "let me know your thoughts on our comprehensive solution." A big ask from a stranger gets ignored; a small ask gets a yes-or-no answer.
Never fake familiarity
- Don't open with false warmth implying an existing relationship that doesn't exist ("Great catching up recently!" to someone never met) — it's immediately obvious and destroys credibility faster than an openly cold email would.
- Avoid the "quick question" opener as a trick to get a reply and then pivot to a pitch — recipients have seen this pattern enough to recognize it, and the bait-and-switch costs more trust than it gains in replies.
- Say plainly that this is a cold outreach if there's genuinely no prior relationship — directness reads better than a manufactured connection that doesn't survive scrutiny.
Real personalization vs. mail-merge tokens
- Personalization means a sentence that could only apply to this recipient — a specific detail about their work, company, or situation. A first-name token dropped into an otherwise generic template is not personalization; recipients recognize the pattern instantly.
- If genuine personalization for a given recipient can't be written, that's a sign the list is too broad — narrow it rather than sending a templated email with a fake-personal veneer.
Follow-up cadence with restraint
- Send at most two or three follow-ups, spaced several days to a week apart, each adding new information or a new angle rather than just restating "just following up" — a follow-up with nothing new is a second interruption for no added value.
- Make the final follow-up a genuine close ("I'll assume this isn't a priority right now and won't follow up again") rather than an indefinite trickle — an open-ended sequence that never stops reads as harassment rather than persistence.
- Stop immediately on any negative response, and never re-add someone to a different sequence shortly after they've declined or gone silent on the current one.
What makes email spam-filter bait
- Heavy link density, tracking pixels stacked with multiple links, ALL-CAPS or exclamation-heavy subject lines, and image-only bodies with little text all raise spam-filter risk independent of content quality.
- Sending high volume from a fresh or low-reputation domain, or reusing identical copy across a very large batch in a short window, are the patterns filters are specifically tuned to catch.
Legal basics
- Clearly identify who is sending the email and on behalf of what company — don't obscure the sender identity or use a display name designed to look like a personal contact from an unrelated context.
- Include a straightforward way to opt out of future contact and honor it immediately and permanently — this is both a legal requirement in most jurisdictions with commercial email rules (e.g. CAN-SPAM, GDPR/PECR for EU/UK recipients) and a basic trust signal.
- Don't use a misleading subject line or from-name that misrepresents the email's commercial nature — beyond the ethical issue, this is the specific pattern most email-marketing regulations target directly.
Badge
Link back to this module from your own README.
[](https://markdowners.com/m/markdowners/cold-email-rules)Discussions about this module
No discussions about this module yet.
Start a discussion
Comments (0)
Sign in to comment. Sign in
No comments yet. Be the first to add one.