Research note
How Long Should a Cold Email Be? Long Enough for One Decision
2026-09-10 · Julian Hartwell
A cold email should be as long as the evidence needed to make one credible next-step decision, not as short as a generic word-count rule permits. A cold email should be long enough to justify one next-step decision and no longer. A universal word limit cannot tell you whether the recipient has enough evidence to understand the relevance and respond.
Let the decision set the length
A cold email should contain the evidence required for one credible next-step decision and no more. That may be a few compact sentences when the trigger and ask are simple, or a somewhat longer note when a technical distinction must be established. A universal word count ignores proof burden, recipient familiarity, and the cost of the requested action.
- Name one recipient decision.
- Include one defensible reason for contact.
- Supply only the proof needed for that decision.
- Ask for one bounded response.
- Retain required identity and opt-out information outside the persuasion count.
- Mark every claim that would require a recipient to trust the sender. If the sentence lacks a source or does not help the one requested decision, remove it; if it is essential, make the evidence inspectable.
- Read the draft aloud once, then summarize its requested decision in ten words. If the summary contains two actions or an unstated assumption, split the sequence or narrow the first message.
Short is a result of editing
The right message often becomes short after unsupported claims, repeated context, and premature feature detail are removed. Starting with a number can instead compress away the evidence that makes the request credible. A routing email begins at 168 words because it carries company background, three features, a meeting request, and generic proof. The editor identifies one recipient decision: whether a two-field routing example belongs with this role.
Estimate the proof burden
Before drafting, score the distance between what the recipient can verify now and what the CTA asks them to accept. A request to route the email may need little proof. A request to evaluate an unfamiliar integration, share sensitive context, or book several stakeholders needs clearer substantiation—or a smaller first step.
- Low burden: confirm ownership or relevance.
- Moderate burden: inspect one use case or documented example.
- High burden: evaluate architecture, security, or operational change.
- Reduce the ask when the necessary proof would overwhelm an unsolicited message.
- Use OKKI Go company context only after reviewing candidates and sources.
- Mark every claim that would require a recipient to trust the sender. If the sentence lacks a source or does not help the one requested decision, remove it; if it is essential, make the evidence inspectable.
- Read the draft aloud once, then summarize its requested decision in ten words. If the summary contains two actions or an unstated assumption, split the sequence or narrow the first message.
Length follows the smallest honest ask
If a concise email cannot support the proposed meeting, shrink the decision rather than stacking claims. A referral or permission to send a relevant document may be the appropriate first action. The proof burden now requires a dated operations posting, a cautious ownership question, and the promised example. Because the evidence cannot justify a product tour, the CTA shrinks from a 30-minute meeting to permission to send the artifact.
Edit with a sentence-by-sentence test
Give every sentence one job: context, consequence, proof, or next step. Delete greetings that perform no relationship work, benefits unsupported by evidence, duplicated problem statements, and feature lists unrelated to the decision. Keep transitions only when they prevent a false inference.
- Context: why this recipient, now?
- Consequence: what business question might follow?
- Proof: what can the recipient verify?
- Request: what exact response is needed?
- Compliance: what identity or preference information must remain?
- Mark every claim that would require a recipient to trust the sender. If the sentence lacks a source or does not help the one requested decision, remove it; if it is essential, make the evidence inspectable.
- Read the draft aloud once, then summarize its requested decision in ten words. If the summary contains two actions or an unstated assumption, split the sequence or narrow the first message.
Before-and-after example
Before: “We are a leading platform with innovative capabilities that help teams improve efficiency across many workflows, and I would love to schedule 30 minutes to show you everything.” After: “Your operations posting mentions manual distributor assignment. Is that process owned by revenue systems? If so, I can send the two-field routing example.” The revision is shorter because it replaces generic breadth with a sourced question. Sentence review removes leadership claims, repeated context, feature breadth, and false urgency. The 91-word version keeps the source, uncertain bridge, bounded capability, one CTA, and an easy close; shortening follows reasoning rather than a target count.
Check the mobile reading path
Read the draft on a narrow screen without relying on an image. The recipient should reach the reason for contact and next decision without wading through biography, social proof, or a miniature proposal. Paragraph breaks can improve scanning, but chopping one long argument into fragments does not reduce its cognitive load.
- Put the account-specific observation early.
- Limit each paragraph to one reasoning move.
- Keep the CTA visible without scrolling through a feature catalogue.
- Link optional proof rather than pasting it all.
- Confirm recipient, subject, and body in OKKI Go before sending.
- Mark every claim that would require a recipient to trust the sender. If the sentence lacks a source or does not help the one requested decision, remove it; if it is essential, make the evidence inspectable.
- Read the draft aloud once, then summarize its requested decision in ten words. If the summary contains two actions or an unstated assumption, split the sequence or narrow the first message.
Do not measure characters alone
A dense 70-word paragraph may feel longer than a clear 110-word note. Evaluate the reasoning path, not just the counter. On a phone, the subject, first two lines, and CTA remain visible without a dense block. A 70-word alternative removes the source context and becomes harder to trust, so the team retains the clearer 91-word version.
Test functional variants
Compare an evidence-calibrated version with a genuinely leaner alternative for the same cohort. Hold the subject, audience, offer, sender, and timing stable. Judge the result through qualified replies, useful referrals, objections, and opt-outs, not open rate alone. Read the reasons behind each disposition.
- Record delivered recipients for each version.
- Show counts beside rates.
- Review whether the shorter version creates more clarification requests.
- Review whether the longer version adds unsupported persuasion.
- Keep jurisdictional accuracy and opt-out duties in both variants.
- Mark every claim that would require a recipient to trust the sender. If the sentence lacks a source or does not help the one requested decision, remove it; if it is essential, make the evidence inspectable.
- Read the draft aloud once, then summarize its requested decision in ten words. If the summary contains two actions or an unstated assumption, split the sequence or narrow the first message.
The practical answer
There is no magic length. Stop writing when the recipient has enough verified context to make one proportionate decision, and stop cutting before that context disappears. The bounded cohort compares the 91-word email with a 118-word variant that includes one necessary technical qualification. Clarification replies determine whether the added proof helps; no universal ideal length is inferred from the result.
A cold email should be long enough to justify one next-step decision. A copied word-count rule cannot replace that evidence test.
Frequently asked questions
How long should a cold email be?
Long enough to support one next-step decision and no longer. There is no universal word limit that can tell you whether the recipient has enough evidence.
When is a short email too short?
When the CTA asks the reader to accept more than the visible proof. A routing request may need two sentences; a technical claim usually needs the observation that supports it.
How should length be tested?
Compare an evidence-calibrated draft with a leaner alternative for the same cohort. Hold subject, audience, offer, sender, and timing stable.
Should you write to a mobile-first length?
Read the draft on a narrow screen. The reason for contact and the next decision should appear before any biography or inventory.