Newsletter email templates

The templates

Replace everything in [square brackets] with your own details. Words in double curly braces, like {{name | 'there'}}, are Lumail variables: they are filled per subscriber at send time, and the value after the pipe is the fallback when the field is empty.

1. 01Issue 1 · on your regular send day

   Issue #1

   The first issue a new list receives, which sets the format.

   Subject lineCopy

   Issue #1: [the topic of this issue]

   Preview textCopy

   Why this newsletter exists, and the first thing worth your time.

   Variables:{{name}}built-in field

   BodyCopy

   Hi {{name | 'there'}}, Welcome to the first issue of [Newsletter name]. Every [day of week] you'll get [one sentence on the format, e.g. "one idea about pricing, with an example you can steal"]. That's it. This week: [topic] [Two or three short paragraphs making one point, with one concrete example.] The takeaway: [one sentence the reader can act on this week]. If someone forwarded this to you, you can subscribe here: [signup link]. Until next [day], [Your name]

   Why it works: The first issue teaches the format. Stating the promise in one sentence makes it easy for readers to decide they want the second issue.

2. 02Weekly · same day and time each issue

   The single-essay issue

   One idea, argued well. Works for writers and founders.

   Subject lineCopy

   [A specific claim, e.g. "Your pricing page is too long"]

   Preview textCopy

   [The tension in one line, e.g. "Three sections do the work. The rest is noise."]

   Variables:{{name}}built-in field

   BodyCopy

   Hi {{name | 'there'}}, [Open with a specific scene or observation, two or three sentences.] Here's what I think is going on: [your argument in one sentence]. [Point one, with an example.] [Point two, with an example.] [The counter-argument, and why you still hold your view.] What to do with this: [one action the reader can take this week]. Reply and tell me if you disagree. The best replies end up in a future issue. [Your name]

   Why it works: A subject line that states a claim gives readers a reason to open. Ending with the counter-argument and an action keeps it from reading like a blog post pasted into an email.

3. 03Weekly · same day and time each issue

   The curated digest

   A short list of links with your take on each.

   Subject lineCopy

   [Number] things worth your time this week

   Preview textCopy

   Starting with [the most interesting item, in a few words].

   Variables:{{name}}built-in field

   BodyCopy

   Hi {{name | 'there'}}, Here's what I read, used or bookmarked this week. 1. [Title] — [link] [Why it matters to the reader in one or two sentences.] 2. [Title] — [link] [Your take, not the article's summary.] 3. [Title] — [link] [One sentence on what to do with it.] 4. [Title] — [link] [Your take.] 5. [Title] — [link] [Your take.] One thing from us: [one line on your product or offer, or delete this section]. See you next [day], [Your name]

   Why it works: Your commentary is the product. A digest that only lists links is replaceable, one that says why each link matters is not.

4. 04Monthly · first week of the month

   The product update newsletter

   Ships what changed this month to users and subscribers.

   Subject lineCopy

   What's new in [Product]: [headline feature]

   Preview textCopy

   [Headline feature], plus [number] smaller improvements.

   Variables:{{name}}built-in field

   BodyCopy

   Hi {{name | 'there'}}, Here's what shipped in [Product] in [month]. [Headline feature] [Two sentences: the problem it solves and how to use it.] [Button: Try it] Also new: - [Improvement] — [one line on why it matters] - [Improvement] — [one line] - [Fix] — [one line] Coming next: [one item you're confident about]. The full changelog is here: [link]. Reply with what you'd like us to build next. [Your name] [Product]

   Why it works: Leading with one headline feature and its use case drives clicks. The rest stays as a scannable list so the email does not turn into a changelog.

5. 05Monthly · last week of the month

   The monthly roundup

   Collects the month's content for readers who missed it.

   Subject lineCopy

   [Month] in review: the [number] posts worth reading

   Preview textCopy

   In case you missed them, plus what's coming next month.

   Variables:{{name}}built-in field

   BodyCopy

   Hi {{name | 'there'}}, Here's everything we published in [month], in case some of it slipped past you. Most read: [Title] — [link] [One line on why readers liked it.] Also worth your time: - [Title] — [one-line hook] — [link] - [Title] — [one-line hook] — [link] - [Title] — [one-line hook] — [link] Next month we're covering [topic]. If there's a question you want answered, reply and I'll add it to the list. [Your name]

   Why it works: Roundups give a second chance to content subscribers missed and are easy to produce, since the writing already exists.

Best practices

Send it with Lumail

• Send it as a campaign

  Write the issue in the editor, use @ to insert variables, check the live deliverability pre-flight, then send now or schedule it for your regular slot.

  • Content pre-flight
  • Send or schedule via API

• Draft it from your AI tools

  Connect Claude, Cursor, ChatGPT or Codex through MCP and turn notes or a changelog into a saved campaign you review before sending.

  • Send a newsletter from Cursor
  • Lumail MCP

• Keep the list healthy

  Automatic list cleanup unsubscribes people who have not opened or clicked for 30, 90 or 180 days. It is off by default and you can preview who it affects.

  • Automatic list cleanup