YsteriPrime · Sales KitGet the $47 kit

B2B SaaS · Outbound

Cold Email Word Count for B2B: How Long Should Outreach Actually Be?

Short enough to read on a phone. Specific enough to prove you did homework. Here are ranges that hold up for Seed–Series B SaaS — not vanity “best practices.”

By Sean Oh · Updated Sep 27, 2026 (KST)

“How long should a cold email be?” is the wrong first question. The first question is: can this person reply in under 30 seconds without a meeting? Word count is the constraint that forces that design.

Worked example: Metriclane (fictional analytics API, $18k ACV) writing Jordan Hale, RevOps @ Cobalt Labs. Examples are teaching copy — not real sends or testimonials.

Recommended word counts (body only)

Email typeTarget wordsHard ceilingJob
First touch50–90110Earn a reply or a soft no
Bump (2–4 days later)25–4560One new angle, not a rewrite
Value bump40–7090One insight or mini-asset, then ask
Break-up30–5070Permission to close the file
Subject line3–7 words~45 charactersOpen without sounding like ads
Rule of thumb: If you cannot say the ask in one sentence under 20 words, the email is not ready — cut the pitch, not the ask.

What to cut first when you’re over 90 words

  1. Company biography. They can skim your site. Lead with their problem.
  2. Feature lists. One job-to-be-done beat > five capabilities.
  3. Fake personalization. “Loved your LinkedIn post about…” without a point wastes 25 words.
  4. Double CTAs. Pick reply or calendar link — not both in email one.
  5. Apology / hedging. “Sorry to bother / if this isn’t relevant” burns trust and length.

First-touch anatomy (~70 words)

  • Line 1 (observation): one specific, verifiable detail about their world
  • Line 2 (problem hypothesis): the costly workaround you suspect
  • Line 3 (soft relevance): how teams like theirs handle it — no demo dump
  • Line 4 (ask): one low-friction question they can answer in a sentence
Subject: Friday activation→paid joins? Jordan — saw Cobalt Labs’ RevOps hiring and the public talk about warehouse-first analytics. Curious: is activation still joined to paid revenue in a Friday sheet, or did you already kill that? Teams in a similar spot use a thin API on the warehouse so CRO forecast stops surprising on Mondays. Worth a 2-line reply either way?

~78 words. Observation → hypothesis → relevance → ask. No “I’d love 15 minutes of your time.”

Bump and break-up (stay under the ceiling)

Bump (~35 words): one new fact or question. Do not resend the pitch.

Quick bump — if the Friday join is already solved, I’ll close the loop. If not: is Head of Data the right person for a 20-min workflow check, or should I leave you alone?

Break-up (~40 words): make silence a valid answer.

Last note from me — I’ll assume the sheet is good enough for now and close the file. If the CRO forecast pain comes back, reply “reopen” and I’ll send a one-pager — nothing else.

Mobile and reply-rate physics

  • Most B2B opens happen on phones. Past ~110 body words, skimming collapses.
  • Paragraphs over 3 lines look like marketing. Prefer 1–2 line blocks.
  • Links: zero or one in email one. Attachments on first touch often hurt deliverability.
  • Count words in the draft you will send — not the Google Doc with comments.

When longer is OK

Warm intros, RFP responses, and post-meeting recaps can run longer. Cold first touch should not. If you need depth, send a short email that offers a one-pager on reply — then deliver length after they opt in.

Next steps after they say yes

A booked call is not a win until you run real discovery. Bring a tight question bank (15 discovery questions) and score the call the same day (discovery call scorecard template). Price pushback later uses their impact number — see objection handling.

Need structures, not just word counts?

Five cold email frameworks with length guardrails: Cold Email Pack — $17. Full discovery + objections + outbound: Sales Enablement Kit — $47. Free sample (no email required): impact-before-budget dialogue.

Get the $17 cold email pack Explore the $47 kit