What a cold email subject line has to do
The subject line has one job: get a stranger to open the email with the right expectation. The second part matters as much as the first. A subject line that tricks someone into opening ("Re: our call") gets the open and loses the reader, and sometimes earns a spam report that hurts every email you send afterwards.
In B2B, the reader is usually scanning a crowded inbox for messages that concern their work. The subject lines that survive that scan look like something a colleague, a partner or a well-informed peer would send: plain words, a specific topic, no marketing gloss. That is why the best cold email subject lines often look boring out of context and obvious in context.
The subject line cannot rescue a weak email. If the message is sent to the wrong person or has no real reason behind it, a better subject line only gets more people to read something irrelevant. Start with the target and the reason: see how to write a cold email and buying signals.
Seven rules for subject lines that get opened
- Short. Two to six words is a good range. Many people read email on a phone, where long subject lines are cut off.
- Specific to the reader. A topic they recognize (their product, their hiring, their post, their market) beats a generic benefit.
- Honest. The subject must match the content. In the US, the CAN-SPAM Act forbids deceptive subject lines in commercial email (FTC compliance guide).
- Plain. Lower case or sentence case, no exclamation marks, no ALL CAPS, no emojis in a first contact.
- One idea. A subject that tries to say three things says none of them.
- No fake familiarity. No "Re:", "Fwd:" or "Following up" on a first email. No first-name-only subject lines pretending to be a friend.
- Works with the preview text. The first line of the email shows next to the subject in most inboxes. Write them as a pair.
Cold email subject line examples by situation
The examples below are grouped by the reason you are writing. Brackets mark what to replace. Pick the group that matches your trigger; a subject line built on the same event as the email reads as one coherent message.
| Reason for writing | Subject line examples | Why they work |
|---|---|---|
| Someone asked for a tool recommendation | your question about [category] · re your [platform] post on [topic] · [category] options for [company] | Point straight to the request they made in public; see tool requests |
| Complaint about a competitor | switching from [tool] · [tool] alternative for [company] · the [specific issue] you mentioned | Name the problem they described; see competitor complaints |
| New product launch | congrats on [product] · [product] launch week · first users for [product] | Timely and about them, not you; see product launches |
| Hiring | your [role] opening · before your new [role] starts · [role] hire at [company] | A job post shows budget for a problem; see hiring signals |
| Funding | after the [round] · plans for [goal named in the announcement] · [company] next 12 months | Ties your offer to what the money is for; see funding |
| Expansion | [company] in [new city] · opening [new market] · second office setup | Concrete event, concrete need |
| Tech stack change | moving off [tool] · [old tool] to [new tool] · after the [tool] migration | Switches create work you can help with |
| A problem you can see | [page] on your site · [metric] on [platform] · quick note on [specific issue] | Shows you looked, without overclaiming |
| Referral or mutual contact | [mutual name] suggested I write · intro via [community] · [mutual name] and [topic] | Real referrals raise trust; only use them when true |
| A useful resource | [checklist] for [their role] · template for [task] · [number] ideas for [their goal] | Value first; the ask comes in the body |
| Direct question | question about [process] · who owns [area] at [company]? · [process] at [company] | Questions invite a short answer |
| Event or community | after [event] · your [conference] talk · [community] thread on [topic] | Shared context makes the email expected |
| Follow-up | one more idea on [topic] · [resource] I mentioned · closing the loop on [topic] | Honest about being a follow-up; see the follow-up guide |
| Breakup | should I close this? · last note on [topic] · leaving this here | Easy to answer with yes or no |
| After a call (sales email) | notes from today · next steps for [project] · [company] + [your company] recap | Clear, useful, expected |
When there is no event to point to
Sometimes you write to a company only because it fits your ideal customer profile. Without a trigger, lean on the most specific true thing you know: their category, a tool they use, a page on their site, a market they serve. "[category] teams and [problem]" or "question about [process] at [company]" will do better than a generic benefit. If you keep struggling to find anything specific to say, that is a sign the account belongs later in the list, after the ones with a buying signal.
Subject lines by the role you write to
The same event reads differently depending on who receives the email. A funding round means hiring and growth targets to a founder, pipeline pressure to a head of sales, and new tooling to an engineering lead. Adjust the subject line to the part of the event that lands on the reader's desk.
| Reader | Subject line | What it points at |
|---|---|---|
| Founder or CEO | first sales hire after the round | The plan the money is for |
| Head of sales | pipeline target for [next quarter] | The number they now own |
| Head of marketing | launch plan for [product] | The campaign they are preparing |
| CTO or engineering lead | scaling [system] after the raise | The technical work that follows growth |
| Operations or finance | tooling budget after the raise | The purchases they will approve |
Agencies and consultants writing to clients
When you sell a service, the strongest subject lines name something visible about the prospect's business that your service changes: "[page] load time", "[product] launch page", "your [city] listings". It shows the email is about them and that you looked. Our lead generation for marketing agencies playbook has more examples by service.
A worked example: from signal to subject line
Suppose a head of operations at a 40-person logistics software company posts on Reddit that their current help desk tool "falls over every time we add a new client workspace" and asks for alternatives. You sell a help desk product built for multi-client teams.
Draft five options quickly, then judge them against the rules above:
- "Help desk for multi-client teams": accurate, but it is about your product, not their problem.
- "Re: your help desk post": implies an existing conversation. Rejected.
- "Tired of your help desk crashing?": negative, and it overstates what they said.
- "new client workspaces in [tool]": specific, uses their words, matches the email. Keep.
- "your question about help desk options": honest and clear, a good backup for a test.
Reach companies with a reason to buy this week
Startories finds the buying signal, verifies the decision-maker and runs the outreach until they book a call.
Sales email subject lines for existing conversations
Sales email subject lines for people who already know you follow different rules. The reader expects your message, so clarity beats curiosity: say what the email contains and what you need from them.
- Proposal or quote: "[company] proposal: [scope]" or "revised quote for [project]".
- Scheduling: "times for [meeting purpose]" or "moving our [day] call".
- Decision needed: "decision needed on [topic] by [date]". Only use a date when it is real.
- Reactivation of a lost deal: "[product] since we last spoke" or "what changed on [topic]". Lost deals often reopen when something has changed on your side or theirs.
- Renewal or upsell: "[company] renewal options" or "[feature] for your team". Be specific about which part of their account it concerns.
Subject lines that make readers distrust you
Some patterns still circulate in "best subject lines" lists because they raise open rates in isolated tests. In B2B outreach they tend to backfire: they produce opens without replies and, worse, complaints.
| Pattern | Example | Why it backfires | Write instead |
|---|---|---|---|
| Fake reply or forward | Re: our conversation | Implies a conversation that did not happen | question about [topic] |
| Clickbait curiosity | You will not believe this | Reads like a newsletter or spam | [specific observation] at [company] |
| Urgency without a reason | Urgent: action needed | Feels manipulative and invites a spam report | Only state a deadline when one exists |
| First name only | [First name]? | Overfamiliar from a stranger | [first name], quick question on [topic] |
| All caps or exclamation marks | FREE TRIAL!!! | Spam signals for people and filters | Plain words, sentence case |
| Broken personalization | Hi {first_name} | Shows the email is automated and careless | Check your data before sending |
| Promise of results | 3x your pipeline | Claims nobody can check | Name the problem, not a number |
Preview text and sender name: the other two thirds
In most inboxes, three things show before the open: the sender name, the subject line and the first characters of the email (the preview text). Readers decide on all three at once.
Use a real person's name as the sender, the same person who signs the email. Make sure the first line of the email is useful on its own, because it is what appears next to the subject. If your email starts with "Hi Sam, I hope this finds you well", that is the preview, and it says nothing. If it starts with "Hi Sam, saw your post asking for a CRM that handles multiple brands", the preview finishes the job the subject line started.
Sending setup matters too: a subject line only gets read if the email reaches the inbox. Authentication, domain reputation and complaint rates decide that, as explained in the cold email deliverability guide and in Google's sender guidelines.
How to test cold email subject lines honestly
Open rates used to be the obvious way to compare subject lines. They are no longer reliable. Since Apple introduced Mail Privacy Protection, Apple Mail can load remote content privately, including the tracking pixel used to count opens, so many opens are recorded whether or not a person read the email (Apple: Mail Privacy Protection). Other providers and security tools also open links and images automatically.
Measure what matters instead: replies, positive replies and meetings, per subject line. Those numbers are smaller, so tests need more patience.
Change one thing
Keep the email body, the audience and the sending schedule the same. Only the subject line changes.
Split the same audience
Assign contacts to version A or B at random from the same list, not one segment each.
Count positive replies, not opens
Classify replies the same way for both versions: positive, neutral, negative, out of office, unsubscribe.
Wait for enough volume
Worked example with assumed numbers: if about 3 in 100 contacts reply positively, 200 contacts per version gives roughly 6 positive replies each. A difference of one or two replies at that size is noise. Keep testing until the gap is clear and consistent.
Keep the winner, test again
Retire the losing version, write a new challenger and repeat. Subject lines that work for one signal may not work for another.
A quick checklist before you choose a subject line
- Is it under about six words, and does it still make sense when cut off on a phone?
- Would the reader recognize the topic as theirs?
- Does it match exactly what the email talks about?
- Does it avoid "Re:", "Fwd:", false urgency, caps and exclamation marks?
- Does the first line of the email complete it as preview text?
- Is every personalization field filled for every contact?
- Would you be comfortable if the reader forwarded it to their boss?
How Startories writes subject lines
Startories starts from the event that made a company worth contacting: a request for a tool, a complaint about a competitor, a launch, a hire. The subject line and the first line both refer to that event, so the email reads as a reply to something the prospect did, not as a campaign. You can edit any subject line or approve every email before it is sent.
Each sequence stops on reply, and every reply is classified so you can compare subject lines on the outcome that matters. Read how the AI SDR works, browse the cold email templates for full emails, and compare plans on pricing.
Frequently asked questions
What is a good subject line for a cold email?
A short, specific line that names a topic the reader recognizes, such as "your question about CRM options" or "before your new SDR starts". It should match the email exactly and avoid tricks such as a fake "Re:".
How long should a cold email subject line be?
Two to six words is a good range. Many readers see email on a phone, where longer subject lines are cut off, and short lines look more like a message from a person than a campaign.
Should I personalize the subject line?
Personalize it with context, not just a first name. A subject that mentions their post, hire or launch does more than "Sam, quick question". Make sure every personalization field is filled before sending.
Are open rates a good way to test subject lines?
Not anymore. Apple Mail Privacy Protection and automated scanners load tracking pixels without a person reading the email, so opens are inflated. Compare replies, positive replies and meetings instead.
Can I use "Re:" in a cold email subject line?
Only when you are actually replying in an existing conversation. Using it on a first email misleads the reader, and in the US the CAN-SPAM Act prohibits deceptive subject lines in commercial email.
Should I put the company name in the subject line?
It can help when it adds meaning, as in "[company] in Austin" for an expansion, but a company name alone is not personalization. A topic the reader owns usually does more than their company name.
How many subject lines should I test at once?
Two at a time, on the same audience and the same email body. Testing five versions splits your volume so thinly that no difference in replies will be meaningful.
What is the difference between cold email and sales email subject lines?
Cold subject lines must earn attention from a stranger, so they lean on a specific, relevant topic. Sales email subject lines go to people who expect you, so they should state plainly what the email contains and what you need.