email & outbound · playbook
Cold email subject lines: 36 examples and how to test them
The best cold email subject lines are short, specific and honest. 36 B2B examples by type, what actually triggers spam filters, and how to test at low volume.
Key takeaways
- The best cold email subject lines are short (usually two to six words), specific to the recipient's problem, and honest about what is inside.
- Write the email first, then the subject line; a subject that promises something the body does not deliver costs trust and can break the law.
- Spam-word lists are mostly myth: sender reputation, authentication, complaint rate and list quality drive inbox placement far more than any single word.
- Never use a fake Re: or Fwd: on a first email; Google's sender guidelines and the FTC's CAN-SPAM guide both rule out misleading subject lines.
- Test subject lines on replies, not opens, and only compare variants once each has a few hundred sends.
Good cold email subject lines are short, specific, and honest: two to six words that name the recipient’s problem, a real trigger, or something useful inside the email, written in lowercase or sentence case like a note from a colleague. The best cold email subject lines do not try to win the open with a trick. They make the right person think “this is about something I own,” and the body then confirms it.
For B2B outreach, especially to technical buyers, boring and precise usually beats clever. This page expands the subject line section of the cold email campaign guide with principles, 36 examples grouped by type, an accurate look at spam filters, and a way to test at small volume.
What makes a good cold email subject line?
Five principles cover almost every case:
| Principle | What it means | Example |
|---|---|---|
| Specific | Names a concrete problem, system, or initiative | ClickHouse query costs beats quick idea |
| Short | Readable at a glance on a phone; inbox apps show only the first few words, depending on device and settings | Two to six words |
| Honest | Accurately reflects the body; no fake urgency or fake familiarity | migration checklist only if the email offers one |
| Internal-sounding | Looks like something a colleague might send, not a newsletter | lowercase, no punctuation tricks |
| Connected | The first line of the body continues the subject’s thought | Subject search relevance debt, opener about relevance |
Two practical rules follow from these. First, write the email before the subject line: the subject should summarize the one idea in the email, and you only know that idea once the email exists. Second, read the subject next to the sender name and the preview text, because that is how the recipient sees it. A strong subject paired with “I hope this email finds you well” as preview text wastes the open.
Cold email subject line examples by type
All 36 examples below are illustrative. Swap in the recipient’s real systems, initiatives, and triggers. Square brackets mark the parts to replace.
Problem-led subject lines
Use when you know a specific pain the recipient’s role usually owns.
search relevance debt[tool] cost visibilityAPI latency during scale-upflaky test suitesreview queue bottleneckson-call load after the migration[system] schema drift
Trigger-led subject lines
Use when there is a public, recent signal. Reference the trigger, not the fact that you watched them.
the platform engineering rolesafter the [product] launchquestion on the [system] migration[company]'s move to [region]post-acquisition data consolidationyour [conference] talk on [topic]
Role-specific subject lines
Use when the email is for a function, and forwarding is a valid outcome.
for your data platform teaminfra questionsecurity review workflowfor whoever owns searchquestion for engineering ops
Asset and value subject lines
Use when the email offers something useful before asking for time. Only promise what the body delivers.
migration checklistbenchmark notes: [A] vs [B]audit template for [system]3 things in your public docs[topic] teardowncost model for [initiative]
Question subject lines
Use sparingly; a question works when it is easy to answer.
who owns [problem area]?tune or migrate?[system] still on [version]?worth a look?
Direct and low-key subject lines
Use for short emails to senior people, where the body does the work.
quick questionpossible fitidea for [team][company] + [your company](only when there is a real integration or partnership angle)
Referral and relationship subject lines
Use only when the relationship is true. Implying a referral that did not happen is deceptive.
[mutual contact] suggested I reach outfollowing up from [event]fellow [real shared community, e.g. an open source project] contributor
Follow-up subject lines
Follow-ups in the same thread keep the original subject with an honest Re:. A new subject is for a genuinely new angle (see cold email follow-up).
different angle on [problem]
Which cold email subject lines should you avoid?
| Avoid | Why |
|---|---|
Fake Re: or Fwd: on a first email | Google’s sender guidelines say not to start a subject with Re: or Fwd: unless the message really is a reply or forward, and the FTC’s CAN-SPAM guide requires subject lines that accurately reflect the content |
False urgency (time-sensitive, final notice) | Misleading, and technical buyers discount you immediately |
Clickbait (you won't believe...) | Wins an open, loses the reply and invites spam reports |
Over-personalized weirdness (loved your dog photo) | Feels like surveillance, not relevance |
Long marketing claims (Cut cloud costs 40% with our AI platform) | Reads as an ad; unverifiable numbers erode trust |
| All caps, excessive punctuation, emoji | Looks like bulk marketing; Google’s guidelines also discourage using emoji or special characters to imitate graphic elements in a deceptive way |
First name only (Sarah) or Hi | Overused pattern in automated sequences; adds no information |
Implied prior contact (as discussed, our call) | Deceptive if no conversation happened |
Do spam trigger words in subject lines actually matter?
Mostly no, with some important exceptions. The idea that a list of forbidden words (“free,” “guarantee,” “act now”) decides whether you reach the inbox is a myth, or at least badly outdated.
What the major mailbox providers actually emphasize. Google’s and Yahoo’s sender requirements focus on authentication (SPF, DKIM, and for bulk senders DMARC), spam complaint rates (below 0.3%, with Google recommending under 0.1%), easy unsubscribes, and accurate headers. Neither publishes a list of banned words. Gmail’s filtering uses many signals, and how recipients react to your mail (reading, replying, reporting spam) is part of what builds or damages sender reputation.
Where content does matter:
- Deception. Google’s guidelines say message headers and content should not be misleading, and specifically call out fake Re:/Fwd: and putting subject content in the display name. A misleading subject is a policy problem and, under CAN-SPAM, a legal one.
- Rule-based filters. Some corporate gateways and open source filters such as SpamAssassin score individual patterns (for example an all-caps subject). One pattern rarely blocks a message on its own, but a stack of them on a weak domain can.
- Bulk-mail fingerprints. Heavy HTML, tracking-heavy links, hidden text, and images-only bodies make a one-to-one note look like a campaign. Google’s guidelines explicitly warn that hiding content with HTML and CSS can get messages marked as spam.
The reality check. A subject line with “free” sent from a warmed, authenticated domain to a well-targeted list will usually land fine. A perfectly worded subject sent from a brand-new domain to a scraped list will not. Note too that Google’s guidelines are written for opt-in mail and say not to send to people who did not sign up; cold outreach operates in tension with that, which is why tight targeting, modest volume, and a near-zero complaint rate matter more than wordsmithing.
If you send at volume, also know the hard requirements. Gmail treats anyone sending roughly 5,000 or more messages a day to personal Gmail accounts as a bulk sender (permanently, once reached), which adds DMARC, From-domain alignment, and one-click unsubscribe for marketing messages. Yahoo has matching bulk-sender rules, and Microsoft began enforcing SPF, DKIM, and DMARC for high-volume senders to Outlook.com consumer addresses in May 2025.
How long should a cold email subject line be?
Short enough to read in full on a phone. In practice that means two to six words, or roughly under 40 characters, though how much is visible depends on the device, the app, and the sender name length. There is no magic number; a seven-word subject that is specific beats a three-word subject that is vague.
Sentence case or all lowercase both look natural. Title Case Looks Like A Newsletter.
How to test cold email subject lines with small volumes
Cold campaigns rarely have the volume for statistically clean A/B tests, so test in a way that respects that.
- Pick one variable. Test subject line only; keep the body, sender, list segment, and send window identical.
- Measure replies, not opens. Open tracking is unreliable: Apple Mail Privacy Protection preloads images and many security gateways open messages automatically, which inflates opens. Positive replies (or meetings booked) are the metric that matters.
- Split randomly within one segment. Alternate variants across the same list rather than sending A on Monday and B on Thursday.
- Wait for enough sends. With reply rates in the low single digits, a few dozen sends per variant tells you almost nothing. Aim for a few hundred sends per variant before calling a winner, and treat small differences as noise.
- Prefer big swings. Test meaningfully different approaches (problem-led vs asset-led) rather than one-word tweaks. Big differences show up at small volume; small ones never will.
- Watch the negatives. If a variant draws more unsubscribes, annoyed replies, or spam complaints, kill it even if it gets more replies.
- Log and reuse. Keep a simple record of subject, segment, sends, positive replies, and negative signals so the next campaign starts from evidence.
| Volume per variant | What you can conclude |
|---|---|
| Under 100 | Nothing reliable; use judgment and read the replies |
| 100-300 | Only very large differences are meaningful |
| 300-1,000 | Moderate differences start to be readable |
| 1,000+ | Rare in targeted cold email; if you have this, check whether the list is too broad |
Subject line checklist
- Does it name a specific problem, trigger, role, or asset?
- Is it two to six words and readable on a phone?
- Does the body deliver exactly what it suggests?
- No fake Re:/Fwd:, no implied prior contact, no false urgency.
- No all caps, no emoji, no excessive punctuation.
- Does the preview text (first line of the body) continue the thought?
- Would you be comfortable if the recipient forwarded it to their boss?
This page covers best practice and summarizes rules from Google, Yahoo, and the FTC; it is not legal advice. Requirements differ by country, especially in the EU and UK.
Generating and testing subject line variants
If you write campaigns regularly, GTM Hacker includes an Email Subject Line Optimizer agent alongside its other email agents, which adds ten or more subject line and preview text options to a draft campaign, with suggested A/B pairings. The variants land on the draft for a human to pick and approve; nothing is sent automatically. Judge its suggestions on replies, as above, not on predicted opens.
For the full campaign framework, see the cold email campaign guide. For complete emails built around these subject lines, see B2B cold email examples.