How to write a cold email: length, structure and examples

Decide who should receive the email

Define the audience and the purpose before writing. A relevant topic does not automatically make an address eligible for contact. PlainMailer's acceptable-use policy requires permission-based use and excludes purchased or harvested lists. These writing principles also apply to opted-in business introductions and subscriber messages; reading a cold-email guide is not permission to contact anyone.

Choose one offer for one audience. If you need several paragraphs to explain why the recipient might care, the audience or offer may be too broad. Replace generic praise with a factual observation that you can stand behind. Do not pretend to have used a product, attended an event or spoken with a colleague if you have not.

How long should the draft be?

For a simple introduction, use roughly 80–150 words before the signature and required footer as an initial editing target. This is an editorial suggestion, not a deliverability rule or a guaranteed response formula. A technical question may need more detail; a requested document may need only a short covering note.

Use short paragraphs with one purpose each. Remove repeated benefits, a long company history and features unrelated to the reader. Keep necessary terms and explanations even if they make the message longer. Brevity should make a message easier to understand, not hide a condition.

Use a simple five-part structure

1. Relevant opening: explain the real context for writing.
2. Identity: name yourself and the organization you represent.
3. Specific value: describe what you can offer without an unsupported guarantee.
4. One request: ask a question that is easy to answer.
5. Signature and opt-out: provide accurate contact details and a clear way to stop future messages.

Keep the subject aligned with this structure. If you promise a checklist, include it or clearly explain how to receive it. Avoid asking for a meeting, a questionnaire, a website visit and a referral all in the same first message.

An example to adapt when the context is true

This is a fictional example based on an actual request being present. It makes a modest suggestion rather than promising increased revenue. Replace the sample identity, context and observations with accurate information and retain your working unsubscribe mechanism.

Check the finished message

Preview the subject, body and signature with real field values. Missing names, incorrect organizations and unresolved template variables make a draft harder to trust. Use descriptive links whose destination matches the text. Include attachments only when they are expected and needed; a large brochure rarely helps someone answer a simple question.

Yahoo's sender guidance emphasizes wanted mail and easy unsubscribe handling. Make the reader's choices clear, including the choice to decline. For the technical preparation behind the draft, read the deliverability checklist.