75 Cold Email Subject Lines for B2B Sales (2026)

75 Cold Email Subject Lines for B2B Sales (2026)

Useful cold email subject lines are usually short and written in one of two registers: lowercase-casual ("quick question about the rebrand") that reads like a colleague's internal email, or specific-benefit ("how [CLIENT] cut [METRIC]") that previews something concrete. Both avoid the opposite: clickbait that overpromises, ALL CAPS, fake urgency, and vague marketing-speak ("Unlock Your Growth Potential"). A reliable starting point is referencing something the prospect already knows — their company, a competitor, a mutual connection, or a recent event — because the body can immediately substantiate it. Below are 75 subject lines drawn from patterns we use at our cold email agency, grouped by use case, plus the ones to avoid and a defensible way to test your own. The full how to write a cold email guide shows where the subject line fits into research, relevance, proof, and the CTA. Want variants generated for your exact offer? Use our subject line generator.

Replace [BRACKETED] tokens with prospect-specific details — a token left generic undoes the whole effect.

Curiosity subject lines

Curiosity earns the open only when the email pays it off. Open a loop the first line of your body closes.

1. quick question, [FIRST_NAME] — the workhorse; still performs because it's indistinguishable from an internal email
2. weird question about [COMPANY] — "weird" breaks the pattern without breaking trust
3. did you see what [COMPETITOR] did? — curiosity plus competitive anxiety
4. something I noticed on your site — implies specific effort; the body must deliver the observation
5. you're doing this differently — flattery-flavoured curiosity; works on operators proud of their setup
6. the [INDUSTRY] stat nobody talks about — data-backed curiosity; have the stat ready
7. wrong assumption about [COMPANY]? — invites correction, and people love correcting
8. this took me 20 minutes — signals work already done on their behalf
9. before you hire another [ROLE] — interrupts a decision they're plausibly mid-way through
10. [FIRST_NAME], odd overlap between us — works when there is one: shared investor, market, alumni network

Personalized and company-specific subject lines

These put the prospect's own company, work, or context at the centre of the message.

1. [COMPANY]'s pricing page — naming a specific asset proves you looked
2. congrats on the Series [X] — trigger events give the email a reason to arrive today
3. saw your post on [TOPIC] — only if you did; reference a detail in the body
4. [MUTUAL_CONNECTION] said we should talk — borrowed context; use it only when the connection genuinely made the introduction
5. your [PODCAST/TALK] appearance — creators and execs always open mentions of their own content
6. question about [COMPANY]'s move into [MARKET] — shows you track their strategy, not just their name
7. [COMPANY] + [YOUR_COMPANY] — plain, corporate, effective; reads like a partnership email
8. for [FIRST_NAME], not the info@ inbox — acknowledges the noise problem directly
9. the new [JOB_TITLE] hire — hiring signals are public, current, and relevant to your pitch
10. [CITY] next week — you around? — geography is personalization; only send if you'll be there

Pain-point subject lines

Name the problem, not your product. The prospect opens to see if you actually understand it.

1. still doing [PROCESS] manually? — mild provocation aimed at a known time-sink
2. the hidden cost of [PAIN_POINT] — reframes a tolerated problem as an expensive one
3. [METRIC] slipping? — two words; works when the metric is one they report on
4. why [ICP_PLURAL] lose [NUMBER] hours/week — quantified pain with a benchmark feel
5. your team hates [TASK] — blunt, human, usually true
6. [PAIN_POINT] isn't a headcount problem — challenges the default fix they're considering
7. the [Q3] pipeline gap — timely pain; swap in the current quarter
8. what [PROCESS] costs you per lead — unit economics framing for ops and growth roles
9. churn before it shows in the dashboard — speaks to the fear of lagging indicators
10. fixing [PAIN_POINT] without switching tools — removes the biggest objection in the subject itself

Meeting request subject lines

Honest asks with the friction stated up front. Low mystery, high clarity.

1. 15 minutes, Tuesday? — the ask, the cost, the date; nothing to decode
2. worth a quick call? — soft, low-pressure, easy yes
3. coffee at [EVENT]? — event tie-ins make meetings feel like logistics
4. agenda for a 15-min call — the body lists it; kills the wasted-hour objection
5. intro call — [YOUR_COMPANY] + [COMPANY] — formal register for enterprise prospects
6. can I get 15 minutes in [MONTH]? — booking ahead reads as respectful of their calendar
7. two time slots, your pick — choice architecture in five words
8. skip the call — 3 bullets instead? — the anti-meeting meeting request; disarms call-fatigued buyers
9. [FIRST_NAME] ↔ [YOUR_NAME], 15 min — visual, scannable, unambiguous
10. before [DEADLINE/EVENT] — quick sync? — attaches your ask to their existing deadline

Follow-up subject lines

Never "just checking in." Every follow-up needs new information or a new angle — pair the cold email follow-up guide with an adaptable structure from the cold email template library. The worked cold email examples show how the subject and body support the same reason for writing.

1. re: my note last week — a legitimate re: on your own thread (never fake one)
2. the case study I mentioned — follow-up as delivery, not as nag
3. one more data point for you — adds value instead of pressure
4. bad timing? — two words that get honest answers
5. should I stay or should I go? — light touch for later in the sequence; know your audience
6. closing the loop, [FIRST_NAME] — a clear subject for the final email in the sequence
7. since I emailed: [NEW_DEVELOPMENT] — something changed, which is why you're back
8. still the right person for [AREA]? — routing question disguised as a follow-up
9. 3rd email = last email — transparent sequence honesty; polarizing but effective
10. your file: keep open or close? — multiple-choice framing that takes five seconds to answer

Sales subject lines

The best email subject lines for sales lead with outcomes, numbers, and named proof — commercial intent stated plainly.

1. how [CLIENT] got [RESULT] — the case-study opener; specificity does the selling
2. [NUMBER]% more [METRIC] in [TIMEFRAME] — quantified outcome up front
3. [COMPETITOR] switched. here's why — works when true and defensible
4. a [BENEFIT] idea for [COMPANY] — "idea" sounds like a contribution, not a pitch
5. what [NUMBER] [ICP_PLURAL] told us — original data teased in seven words
6. cut [COST_CENTER] by [NUMBER]%? — question mark keeps a bold claim honest
7. [COMPANY]'s [METRIC], benchmarked — everyone opens their own ranking
8. the math on [OUTCOME] — analytic framing for CFO-adjacent buyers
9. [TOOL] users: one blind spot — segment call-out plus a gap they can't ignore
10. built for teams like [COMPANY]'s — soft fit-signal; better mid-sequence than cold
11. your Q[N] number, faster — speaks to quota holders in their own units
12. [ICP] playbook — want the PDF? — asset offer; a smaller yes than a meeting
13. stop paying for [WASTE] — loss framing beats gain framing for cost tools
14. demo in 4 minutes, not 40 — pre-empts the time objection in the subject
15. [RESULT] without [COMMON_OBJECTION] — pitch and objection-handling in one line

Subject lines to avoid (and why they fail)

Each of these patterns creates either a filter risk or a trust problem that can prompt recipients to report the message. Google advises senders to stay below 0.1% spam and never reach 0.3%. Run your draft through our spam checker before sending.

1. FREE CONSULTATION — ACT NOW!!! — caps, "free," and stacked punctuation are three classic content-filter signals in one line
2. RE: RE: our conversation — fake reply threading; recipients who notice mark it as spam, and that report costs more than the open earned
3. You won't BELIEVE these results — clickbait register; filters score it, humans distrust it
4. 🚀🔥 Grow your pipeline 10x 💰 — an unsupported multiplier plus stacked emojis reads as a mass promotion, not a relevant one-to-one message
5. Urgent: response required — false urgency from a stranger is a spam-report generator and, if misleading, a CAN-SPAM problem
6. Invoice #38291 — when there is no invoice, the subject misrepresents the message and resembles a phishing lure
7. Quick question about your health insurance renewal — bait-and-switch when the email sells something else; the FTC says commercial subject lines must accurately reflect the message
8. Hello — not a filter risk, just a wasted line: zero information, zero reason to open
9. Partnership opportunity for mutual benefit — spam-corpus boilerplate; filters have seen this exact phrase billions of times
10. $$$ Guaranteed leads — no risk $$$ — currency symbols, "guaranteed," "no risk": a bingo card of content-filter triggers

How to test subject lines

Most subject line "tests" are too small to support the conclusion attached to them. Calculate the sample size from your baseline response rate and the smallest improvement worth detecting before the campaign begins. Then use this method:

• One variable at a time. Test casual vs. benefit-led, or short vs. long — never both at once, or you won't know what won.
• Split randomly, send simultaneously. Same list, same day-parts; a Tuesday arm vs. a Friday arm is a day-of-week test, not a subject test.
• Judge on replies, not opens. Open tracking is unreliable post-Apple Mail Privacy Protection (opens are auto-fired for a large share of recipients), and an open without a reply pays nothing. Opens are a diagnostic; replies are the metric.
• Run the winner forward. Beat your control, promote the winner, test the next variable. Two or three honest tests a quarter beats twenty noisy ones.

If your audience is too small for the required sample, run the clearer option and spend the effort on list quality rather than declaring a winner from a handful of replies.

Common subject line mistakes

• ALL CAPS anywhere. Caps-heavy subjects are among the oldest content-filter features and read as shouting to humans. Sentence case or all-lowercase only.
• Fake "re:" and "fwd:" prefixes. Pretending a thread exists gets the open and then immediately burns it — the recipient feels tricked, and tricked recipients hit "report spam." Only use "re:" on genuine replies within your own sequence.
• Emoji overuse. One emoji is a style choice; two or more pushes you toward the promotions tab and mass-mail territory. When in doubt, zero.
• Misleading subjects = legal risk. CAN-SPAM prohibits deceptive subject lines: the subject must accurately reflect the content of the message. "Your account issue" on a sales pitch is not a growth hack; it misrepresents the message and trains the recipient to distrust the domain.
• Length creep. Past ~50 characters, subjects truncate on mobile. If the hook lands in word eight, it lands nowhere.

FAQ

What is the best subject line for a cold email?

There is no universal winner. Start with a line that references something the prospect already knows: their company ("[COMPANY]'s pricing page"), a competitor ("[COMPETITOR] switched. here's why"), or a genuine mutual connection ("[MUTUAL_CONNECTION] said we should talk"). When no such hook exists, use a plain line that accurately previews the question in the email.

How long should a cold email subject line be?

Three to seven words, under 50 characters. That's the length that survives mobile truncation and reads like a human wrote it. One-to-two-word subjects ("bad timing?") can outperform on follow-ups, where the thread carries the context.

Do lowercase subject lines really get more opens?

It can, because lowercase resembles the way colleagues often write to each other. But it is register-dependent: casual lowercase can suit SMB and startup audiences, while enterprise and finance prospects may read it as sloppy. Match the register to the recipient and test it only when you have enough volume for a meaningful comparison.

Should I use the recipient's name in the subject line?

Sparingly. [FIRST_NAME] in the subject was novel a decade ago; now every merge tag uses it, so it signals automation as often as attention. It still helps in specific constructions — direct questions ("quick question, [FIRST_NAME]") and follow-ups — but company-specific references ("[COMPANY]'s pricing page") now out-signal name personalization. Generate and compare variants with our subject line generator.