newsletter-writing

name	newsletter-writing
description	Writes email newsletters with subject line options, section structure, calls-to- action, and subscriber-friendly formatting. Use when the user wants to write an email newsletter, create subscriber content, draft a recurring email update, or compose a newsletter edition. Do NOT use for subject line generation only (use `newsletter-subject-lines`), cold outreach emails (use `cold-email-outreach`), or one-off professional emails (use `professional-email`).
license	Apache-2.0
metadata	{"author":"foundry-skills","version":"1.0.0","tags":"newsletter writing email","category":"writing","subcategory":"content-marketing","depends":"","disclaimer":"none","difficulty":"intermediate"}

Newsletter Writing

When to Use

Use this skill when the user needs to produce a complete newsletter edition -- a structured, multi-element email sent to a subscribed audience with the intent to inform, engage, retain, or occasionally promote.

Trigger scenarios:

• User asks to write a newsletter edition with multiple content items (a story, a recommendation, a product update, a CTA)
• User needs help structuring a recurring email format (weekly, biweekly, monthly) for a named or unnamed newsletter
• User wants a complete draft including subject line, body copy, sign-off, and preview text for subscriber distribution
• User is launching a newsletter for the first time and needs a first-edition template that establishes voice and format
• User has a topic they care about and wants to package it into a newsletter-appropriate format with proper email conventions
• User wants to convert a blog post, social thread, or memo into newsletter content formatted for subscriber reading
• User needs a reengagement or "come back" edition to reconnect with a dormant list

Do NOT use when:

• The user only needs subject line options for an existing draft -- use newsletter-subject-lines instead
• The user wants to cold-prospect strangers via email -- use cold-email-outreach instead
• The user needs a single transactional or professional email (a meeting follow-up, a client update, an invoice email) -- use professional-email instead
• The user wants a LinkedIn article or long-form published essay -- use linkedin-article instead
• The user wants an automated drip sequence or onboarding email series -- use email-sequence-writing instead
• The user needs to write the full text of a product launch announcement sent by email -- use product-launch-email instead
• The user wants to write an internal all-hands or company-wide update memo -- use internal-communications instead

---

Process

Step 1: Gather Foundational Context

Before writing a single word, establish the four anchors of every newsletter: audience, relationship, goal, and format. Ask the user for the following if not already provided:

• Newsletter name and frequency -- "The Prepared" vs. an unnamed project; weekly vs. monthly shapes length norms, familiarity level, and how much recap to include
• Subscriber relationship -- paying members, free subscribers, customers, internal employees, or community members. A paid Substack subscriber has different expectations than someone on a free brand email list
• Primary goal of this edition -- inform (new knowledge), promote (product or service), engage (replies, community interaction), retain (reduce churn by delivering value), or celebrate (milestone, anniversary)
• Content items to include -- the raw material: 2-5 topics, stories, links, or announcements the user wants in this edition
• Tone register -- ask for a reference point if the user cannot describe tone: "Think of three newsletters you actually enjoy reading. What do they have in common?" Common registers: personal and confessional, smart and opinionated, warm and encouraging, dry and precise, enthusiastic and high-energy
• Audience size and context -- 100 subscribers and 100,000 subscribers require different voice calibration. A small, tight-knit list supports intimacy and inside references; a large list needs context for everything
• Any links, resources, or products to feature -- if there is a CTA, identify what it is before designing the structure around it

If the user cannot answer these, default to: conversational first-person, 500-word target, single-topic or 3-section format, one CTA at the end.

---

Step 2: Choose the Right Newsletter Architecture

Newsletter structure is not decorative -- it determines what gets read and what gets skipped. Match the architecture to the content and audience relationship.

The five core newsletter formats:

• Single-topic deep dive (400-700 words): One subject explored with setup, insight, and implication. Best for thought leadership, opinion, and educational content. High retention because it feels like a complete thought. Common in creator newsletters, strategy newsletters, and research digests.

• Multi-section curated digest (300-600 words total): 3-5 items at 80-150 words each, each with a brief editorial commentary. Best for aggregators, industry observers, and anyone covering multiple beats. The risk: shallow coverage that adds no perspective on any item. Each item must have the writer's point of view, not just a summary.

• Story + lesson (350-650 words): Opens with a personal anecdote or case study (150-250 words), transitions to a replicable lesson (150-200 words), closes with a CTA. High relatability. Best for coaches, consultants, educators, and service providers.

• News + commentary (400-700 words): 2-4 headlines or industry developments, each followed by a 2-4 sentence take from the author. Distinguishes the newsletter from RSS feeds -- the value is the commentary, not the news. Requires the author to have genuine opinions.

• Product-focused editorial (300-500 words): 60-70% useful editorial content, 30-40% promotion, structured so the promotion feels earned by the value delivered first. Common for e-commerce brands, SaaS companies, and creator product launches.

Decision framework:

• If the user has one strong story or insight: single-topic deep dive
• If the user has 4+ items of similar weight: multi-section curated digest
• If the user is a coach, consultant, or personal brand: story + lesson
• If the user is a media or research brand: news + commentary
• If the user has a product announcement but also wants to deliver value: product-focused editorial

---

Step 3: Design the Subject Line and Preview Text

The subject line and preview text together determine whether the newsletter gets opened. A great newsletter with a weak subject line fails its readers.

Subject line principles:

• Target 35-50 characters for mobile preview (Gmail clips at 77 characters in mobile, but the visual weight at 40 chars is stronger)
• The goal is earned curiosity or a specific, concrete promise -- not vague intrigue ("You won't believe this") or false urgency ("Don't miss this")
• Effective formulas: the unexpected number ("The 7-minute user test"), the named tension ("Why your welcome email is failing"), the specific outcome ("How I cut churn by 22%"), the honest tease ("Something I got wrong last year")
• Avoid: excessive punctuation, ALL CAPS, trigger words (Free, Win, Guaranteed, Act Now, Limited Time), and anything that sounds like it was written for a social media caption rather than personal correspondence
• Subject lines that feel written to one person ("A question I keep getting") outperform broadcast-style subject lines ("This month's design roundup") on average by 15-25% open rate in studied creator newsletter data

Write 3 options per edition:

1. Curiosity-driven -- implies a story, reveals something partially, or names a tension
2. Benefit-driven -- states the concrete takeaway or outcome the reader will get
3. Direct/descriptive -- names the content plainly; best for audiences who want to know exactly what they are getting (often better for established, loyal lists)

Preview text (pre-header):

• 85-100 characters is optimal -- enough to complete the subject line's thought but short enough to avoid truncation on most clients
• Must NOT duplicate the subject line -- it should add information, extend the tease, or add context
• Treat it as the second line of the open invitation: subject line hooks, preview text deepens
• If the user's email platform renders preview text from the first line of the email body when no preview text is set, the first sentence of the email becomes critical (another reason not to open with "Welcome to this week's edition of...")

---

Step 4: Write the Opening Hook

The first 1-3 sentences of a newsletter have one job: earn the continued read. Fifty percent of readers who open a newsletter do not finish it. The opening hook is the gate.

What works:

• Drop into a specific scene, observation, or moment without preamble ("Last Thursday I made a mistake that cost a client three weeks of work. Here is what I learned.")
• State a counterintuitive claim and immediately signal you will explain it ("The most-read section of most newsletters is the P.S. Here is why.")
• Name the reader's situation with precision ("If you have ever spent two hours on a design only to hear a stakeholder say 'can we just move the logo?', this one is for you.")
• Ask a specific question that the rest of the newsletter answers ("What is the actual difference between a strategy and a plan?")

What fails:

• "Welcome to this week's edition of [Newsletter Name]" -- this is administrative, not editorial
• "Happy Monday/Friday!" -- signals filler before content
• "I hope this finds you well" -- signals a form email, not a personal one
• Any sentence that is about the newsletter itself rather than the subscriber's world

---

Step 5: Write the Body Content

With the structure chosen and the hook written, develop each section with the following discipline:

Length and density targets by format:

• Single-topic: 400-700 words total, with sections no longer than 250 words each before a break
• Multi-section digest: 80-150 words per item; 4-5 items maximum before the format becomes exhausting
• Story + lesson: 150-250 words for the story, 150-200 words for the lesson
• News + commentary: 60-100 words per news item including the commentary
• Product-focused editorial: 200-350 words of editorial value, then 100-200 words of clean promotion

Paragraph construction:

• 1-3 sentences per paragraph, maximum. Email is read on phones in portrait orientation; dense paragraphs cause readers to lose their place
• Every paragraph should either advance the story, add a new piece of information, or shift the perspective -- no paragraph should just restate the previous one differently
• Use white space aggressively -- blank lines between paragraphs are not wasted space, they are cognitive breathing room

Voice consistency:

• "I" for solo creators and personal brands; "we" for brand teams
• Address the reader as "you" (singular), never "you all," "everyone," "folks," or "readers"
• If the user has an established voice, match it precisely. Identify three voice markers in their previous writing (e.g., short declarative sentences, rhetorical questions, em dashes for asides) and reproduce them
• Avoid throat-clearing phrases: "It goes without saying," "As we all know," "Now more than ever," "In today's fast-paced world"

Subheadings in newsletters:

• Use sparingly -- 1-2 subheadings maximum per 600-word newsletter, or none at all for story-format newsletters
• Bold a key phrase rather than using a full subheading for shorter sections
• Avoid H1/H2 heading-style formatting -- it makes the newsletter look like a web article, not a letter

---

Step 6: Write the CTA

Every newsletter edition should have one primary CTA and no more. Multiple CTAs create decision paralysis; studied email data shows that adding a second CTA can reduce click-through on both by 30-50%.

CTA taxonomy -- choose one:

• Reply CTA: "Reply and tell me your answer" -- the highest-engagement CTA for small lists; builds relationship; replies improve deliverability by signaling to email providers that real people want this email
• Click CTA: Drives traffic to an article, product page, registration form, or resource -- requires a clear benefit statement in the link text ("Read the full case study," not "click here")
• Share CTA: Ask readers to forward to one specific person ("If you know someone building their first newsletter, forward this to them") -- more effective than generic "share this newsletter"
• Purchase/signup CTA: For product-focused editions -- state the offer, the value, and the specific action cleanly in 2-3 sentences
• Community CTA: Join a Slack, Discord, community forum, or membership space -- works best when the newsletter has demonstrated enough value that the reader wants more

CTA placement and framing:

• Always after the value delivery, never before
• Set it up with a one-sentence transition that connects the content to the ask ("If the 5-second method above sounds useful, the workshop next week goes three layers deeper.")
• Write the CTA as a sentence, not a button label -- in plain-text email style, a bolded sentence outperforms generic "CLICK HERE" formatting
• Keep it to 2-3 sentences maximum -- the CTA is not the place to re-sell the value; the content already did that

---

Step 7: Write the Sign-Off and P.S.

The sign-off and P.S. are the two most-read elements of any newsletter after the subject line. They are consistently under-used.

Sign-off:

• Personal closer that matches the newsletter's register -- formal ("Until next time"), warm ("Talk soon"), personal ("Be well, and thanks for reading"), or informal ("Later")
• Author name or pen name -- first name only for personal newsletters, full name for brand-style newsletters
• Optional one-line bio or context on first editions only: "Jordan -- UX designer and occasional over-tester"

P.S. line:

• Use the P.S. for one secondary item: a personal note, a soft CTA, a related resource, a link to an archive, or a joke that only loyal readers will appreciate
• Never use the P.S. for a second primary CTA -- it dilutes the one you already made
• Keep it to one or two sentences
• Specific P.S. formats that work: "P.S. -- If someone forwarded this to you and you want in, [subscribe link text]" / "P.S. -- I got several replies about last edition's topic. Here is the follow-up I am writing based on that." / "P.S. -- A question I have been sitting with: [genuine question related to the edition's theme]"

---

Step 8: Review Against Email-Specific Constraints

After drafting, run through this checklist before delivering the output:

• Subject line is under 50 characters and passes a basic spam trigger check (no all-caps words, no excessive punctuation, no "free" or "guaranteed")
• Preview text is 85-100 characters and does not duplicate the subject line
• The newsletter opens with something other than a greeting, welcome, or day-of-week phrase
• Total word count is within the chosen format's target range (400-800 words for most formats)
• No paragraph exceeds 3 sentences
• There is exactly one primary CTA
• All link text is descriptive (no "click here" or "learn more" without context)
• No content requires images to be understood (images may be blocked by email clients)
• The entire email reads coherently in plain text (no formatting that depends on HTML rendering)
• The P.S. is present and adds genuine value or personality

---

Output Format

Deliver the complete newsletter in the following structure. Populate every field with real content -- do not leave placeholders in the output.

SUBJECT LINE OPTIONS
--------------------
A. [Curiosity-driven -- under 50 characters]
B. [Benefit-driven -- under 50 characters]
C. [Direct/descriptive -- under 50 characters]

PREVIEW TEXT
------------
[85-100 characters -- complements but does not duplicate the subject line]

---

[Opening hook -- 1-3 sentences. Drops directly into content. No greetings.]

[Section 1 body -- main content, story, or first item. 150-300 words depending on format.]

[Section 2 body -- second item or supporting insight. 80-200 words.]

[Section 3 body -- third item, quick hit, or curated recommendation. 50-150 words. Omit if single-topic format.]

---

[CTA transition sentence]

[CTA body -- 2-3 sentences maximum. One specific action. Descriptive link text.]

[Personal sign-off word or phrase]
[Author name]

P.S. [One to two sentences. Secondary note, soft CTA, or personality moment.]

Supplementary notes block (optional -- include if useful):

Element	Decision Made	Rationale
Format chosen	[e.g., Story + lesson]	[e.g., One strong story with universal takeaway]
Word count	[e.g., 520 words]	[e.g., Within biweekly newsletter norm for this audience]
CTA type	[e.g., Reply CTA]	[e.g., Small list; replies improve deliverability]
Tone register	[e.g., Personal/conversational]	[e.g., Solo creator, established list]

---

Rules

1. Never open with a greeting, welcome, or day-of-week phrase. "Welcome to this week's edition," "Happy Monday," "I hope this finds you well," and "Thanks for being here" are wasted first sentences. The opening hook must begin with content, not courtesy.

2. One primary CTA per edition, no exceptions. A newsletter with three CTAs does not get three times the action -- it gets one-third the action on each. If there are multiple things to promote, choose the most important one for this edition and reserve the others for future editions or the P.S. as a soft secondary reference only.

3. Subject lines must be under 50 characters. Not 60, not "50-ish." Mobile email clients preview approximately 30-40 characters in the subject line column. Every character over 50 is invisible to a meaningful portion of the audience. Count the characters.

4. Never use "click here," "learn more," or "find out more" as link text without descriptive context. Link text must tell the reader where they are going or what they are getting: "download the template," "read the full case study," "register for the March 15 workshop." Naked calls to action are both less effective and worse for screen reader accessibility.

5. Respect the 400-800 word target. Research from email analytics platforms consistently shows that newsletters under 200 words feel like teasers and newsletters over 1,000 words see sharply reduced completion rates. The 400-800 word range respects the subscriber's attention while delivering enough substance to feel worth the open. If the user insists on more content, use the multi-section format with clear visual breaks so readers can navigate.

6. Never use the newsletter to apologize for absence or explain gaps. If a user is restarting a newsletter after six months of silence, the instinct to apologize is understandable but counterproductive. Subscribers who open a relaunch edition do so because they want the content -- not because they want an explanation. Write a great edition and mention the new frequency going forward without commentary on what came before.

7. No more than one exclamation mark in the entire newsletter. Exclamation marks in newsletters are like salt -- one pinch enhances flavor, the full shaker makes everything inedible. Reserve the single exclamation mark for a moment of genuine enthusiasm, not procedural courtesy.

8. Always include preview text as a distinct element. Many email platforms render the first sentence of the email as preview text by default if no explicit pre-header is set. If the newsletter opens with a strong hook and no preview text is written, the hook will be cannibalized for both jobs. Always write a dedicated 85-100 character preview text that extends or complements the subject line rather than duplicating it.

---

Edge Cases

The user has no established newsletter voice. Do not default to a generic corporate-friendly tone. Run a quick voice calibration by asking three questions: (1) "What tone do you use in your best professional text messages -- formal, casual, or somewhere between?" (2) "What newsletters do you actually read and enjoy?" (3) "If your newsletter could sound like one person you know in real life, who would it be?" Use the answers to build 2-3 voice descriptors (e.g., "precise but warm, uses specific numbers, self-deprecating about mistakes") and apply them consistently throughout the draft. If the user wants to review the voice calibration before the full draft is written, surface it explicitly.

The user wants to write a newsletter for a brand with multiple contributors but wants it to feel personal. The "personal brand of a company" problem is common. The solution is to pick one voice as the editorial voice -- usually the founder, editor, or most recognizable team member -- and write in first-person from that person's perspective, even if the content is a team effort. "I asked our product team what was taking the longest this quarter, and the answer surprised me" reads better than "The team has been focused on some exciting developments." If the brand has no single editorial voice, establish a collective first-person "we" that is still warm and opinionated, not institutional.

The user has 6 or more items to include. Resist writing 6 full sections. Use a "Quick Hits" or "Also Worth Reading" section for items 4 through 6, with one sentence per item -- a brief description plus the author's single-sentence take. Cap this section at 5 items. If there are more than 8 items, push items to the next edition or ask the user to prioritize the 3-4 that best serve the edition's theme. A newsletter trying to cover everything covers nothing well.

The user is writing a newsletter to announce a price increase, policy change, or difficult news. This is a high-stakes edition and requires different structural logic. Lead with context, not the announcement ("Here is what has changed and why we made this decision"). State the change cleanly without burying it or softening it to the point of confusion. Anticipate the two or three questions subscribers will immediately have and answer them in the body. Close with a clear statement of what the subscriber needs to do, if anything. Do not use the standard value-first structure for difficult news editions -- the reader needs the information first, then the context.

The user's newsletter has a specific recurring section format they always use (e.g., "What I'm Reading," "One Quote," "Tool of the Week"). Treat recurring sections as structural constraints, not creative choices. Populate them faithfully before adding any new sections. Readers subscribe to recurring formats partly because of the predictability -- the "One Quote" section is often the thing readers scroll to first. If the user asks for a variation from their usual format, flag it: "Your standard format includes [X section]. Do you want to include it in this edition, or are you intentionally deviating?"

The user wants a newsletter to reactivate a cold or dormant subscriber list. The structure for a reactivation email is distinct from a regular newsletter. It should: (1) open with acknowledgment of the gap, briefly and without extended apology, (2) explain what the newsletter is about for readers who may not remember subscribing, (3) deliver strong, immediate value -- the best content the user has to offer, (4) set expectations for frequency and content going forward, and (5) include a low-friction re-consent invitation ("If you want to keep getting these, you don't need to do anything -- just keep reading"). Expect 20-40% of a dormant list to unsubscribe on a reactivation email; that is a healthy purge, not a failure.

The user wants to include a survey, poll, or reader question for the first time. Reader surveys have the highest response rate when embedded in the natural flow of the newsletter rather than appended as an afterthought. The best placement is immediately after a section that relates to the survey topic. The CTA for the survey should explain why the reader's input matters in one sentence: "I am redesigning this newsletter's format and your answer will directly shape what I build." Keep survey asks to one question or a maximum of three. Never use a survey as the primary CTA if there is also a product CTA -- choose one.

The user is a ghostwriter writing newsletters for a client. The fundamental rule is: write in the client's voice, not the ghostwriter's. Before drafting, read 3-5 previous editions if available. Identify the client's signature voice patterns: sentence length, vocabulary choices, preferred transitions, use of personal anecdotes, and recurring themes. If no previous editions exist, conduct a voice interview: ask the client to describe a recent professional experience in their own words, then use that transcript as a voice reference. Always include a note in the output flagging any sections where the ghostwriter made a significant interpretive choice, so the client can review and adjust.

---

Example

Input: "Write a newsletter for my UX design community called 'Design Notes.' This edition should cover: (1) a new approach to user testing I tried -- showing one screen for 5 seconds and asking three questions instead of running a full session; (2) a book recommendation -- 'Everyday Information Architecture' by Lisa Maria Marquis; (3) an upcoming workshop I'm hosting called 'Research Without a Research Team' on March 15, 90 minutes, virtual, 25 spots. Casual, personal tone. Goes out biweekly."

---

Output:

---

SUBJECT LINE OPTIONS

A. The 7-minute user test that actually worked (47 chars) B. One testing method I wish I learned three years sooner (55 chars -- trim to: Cut your testing time by 80%) (40 chars) C. Design Notes: faster testing + a book you need (48 chars)

(Note: Option B revised to meet the 50-character rule.)

PREVIEW TEXT

Plus a book that reframes content structure as a design problem, not a content problem. (88 chars)

---

Last week I ran a user test that took 7 minutes per participant instead of the usual 45. The results were more actionable than half the full sessions I have run.

Here is the exact method.

The 5-second exposure test. Show a participant one screen for exactly 5 seconds. When the timer ends, ask three questions: "What is this page for?" "What would you do first?" "What, if anything, confused you?" Seven participants, 7 minutes each, and I had clear signal on the three usability issues I had suspected for two weeks but could not get research time to confirm.

This method works because first impressions are what you are actually testing. When a real user hits your landing page, navigation, or onboarding screen for the first time, they do not get a task briefing and a moderator -- they get 5 seconds before their attention goes somewhere else. The 5-second test replicates that reality.

It does not replace task-based testing for complex interaction flows. If you are validating a checkout redesign or a multi-step form, run the full session. But for first-impression validation of a new layout, a homepage hierarchy, or a navigation change, this is the highest-signal-to-time-ratio method I have found. I used to spend three days recruiting for a test I could have run in two hours.

---

Reading this month: "Everyday Information Architecture" by Lisa Maria Marquis. Under 200 pages, which is either a feature or a warning depending on how you feel about concise books. For me it was a feature.

The section that stuck: Marquis frames information architecture not as a deliverable the content team hands off to design, but as a design constraint that shapes everything from navigation to page hierarchy to how users build a mental model of your product. If you have ever sat in a stakeholder meeting arguing about whether a menu item belongs under "Products" or "Solutions" and felt like no one in the room was asking the right question, this book gives you the language to ask it.

---

Workshop: "Research Without a Research Team" -- March 15, 90 minutes, virtual. I am running this for designers who do their own research -- no dedicated researcher, no research ops, no six-week recruiting timeline. We will cover the 5-second method above in more depth, plus two other lightweight testing approaches that require nothing more than five participants and a calendar invite.

Twenty-five spots total. Eight are already taken.

Reply to this email with "workshop" and I will send you the registration link directly.

Talk soon, Jordan

P.S. -- A question I keep getting after editions like this one: "How do you recruit participants so fast?" The answer is shorter than you expect. I will cover it in the workshop, but reply if you want the short version now.

---

Supplementary notes block:

Element	Decision Made	Rationale
Format chosen	Multi-section (3 items)	Three distinct content types of similar weight; no single item warranted a deep dive
Word count	~540 words	Biweekly cadence; audience is professionals reading during work hours; fits 2-scroll mobile read
CTA type	Reply CTA (workshop)	Small-to-mid-size community list; reply signals engagement to email providers and reduces friction vs. link click
Tone register	Personal/conversational, first-person singular	Solo creator, established community relationship; treats reader as a peer not an audience
P.S. usage	Reader question + reply invitation	Extends the workshop's value proposition; invites reply that improves deliverability; rewards curiosity