Cold Email Subject Lines: Examples and Rules

A subject line has one job: get the email opened by someone who'd benefit from reading it. It does not need to be clever. Most weak subject lines fail by being vague, salesy or obviously mass-produced. Below are the principles, then examples you can adapt.

Principles that matter

• Be specific. A subject that references the person's work or a concrete topic beats a generic benefit claim.
• Keep it short. Many email apps truncate subjects on mobile. Aim for something readable in a glance, roughly three to six words.
• Sound like a colleague. Lowercase, plain wording and no exclamation marks look like a personal email, not a campaign.
• Be honest. The subject must match what's inside. Fake "Re:" or "Fwd:" prefixes are deceptive, can violate laws like CAN-SPAM, and destroy trust the moment they're opened.
• Avoid spam triggers. ALL CAPS, "FREE", "guaranteed", and heavy punctuation hurt both opens and deliverability.
• The preview text counts. The first line of your email appears next to the subject. Don't waste it on "Hope you're well."

Examples by approach

Reference something specific they did

• your post on onboarding emails
• question about your Rust migration
• loved the pricing teardown
• your talk at [event]
• re your hiring post for a designer (only if it's a genuine reply to something public)

Name a shared context

• fellow [community] member
• [mutual contact] suggested I write
• both on [alumni network]
• [mutual contact] mentioned you

Only use a mutual contact's name if they have actually agreed to it.

Ask a short question

• quick question about [tool or topic]
• how do you handle [specific problem]?
• who owns [function] at [company]?
• is [problem] on your radar?

Name the problem

• [company]'s onboarding drop-off
• idea for [company] support queue
• cutting manual research time

For recruiting

• your open source work on [project]
• senior backend role, remote
• building [product] and your work caught my eye

For follow-ups

• following up on [original subject] (replying in the same thread)
• one more thought on [topic]
• closing the loop

Rewriting weak subject lines

• "Partnership opportunity for Acme" becomes "your Acme integrations page". It names something you actually looked at.
• "Quick call this week?" becomes "question about your hiring process". It states the topic and asks for nothing yet.
• "Boost your sales with AI!" becomes "how are you handling lead research?". It reads like a question from a peer, not an ad.
• "Following up" becomes "re: your Rust migration post" when it is genuinely a follow-up in the same thread.

What to avoid

• "Quick call?" with a stranger. It's vague and presumptuous.
• "Partnership opportunity." This is a signature of mass outreach.
• The recipient's first name alone in a mail-merge style.
• Emoji overload and fake urgency such as "Last chance."
• Long benefit-stacked lines like "Increase revenue and cut costs with our AI platform."

Test properly

If you want to test subject lines, change one variable at a time and compare across enough sends that a difference isn't random noise. With small lists, you'll learn more by reading replies than by chasing open rates, which can also be distorted by email privacy features that prefetch messages. Focus on reply rate as the real outcome.

The subject line is the easy part

The subject gets the open, but the first lines and the ask decide the reply. Read how to write a cold email that gets replies for the full structure, and the follow-up sequence guide for what comes after.

To generate subjects that reference real details, run the prospect through Avian first. It researches the person and drafts complete message variants, including subject lines, around what it finds. Start free and see which angle fits.