task icon Task

Plan Newsletter Series

Requirements
Newsletter purpose, target audience, content sources available, desired frequency (weekly, bi-weekly, monthly)
3

Gather newsletter context:

  • What's the purpose? (Educate, engage, nurture, sell)
  • Who's the audience? (Customers, prospects, community)
  • What content do you have access to? (Blog, product updates, industry news, original insights)
  • How often can you realistically send? (Weekly, bi-weekly, monthly)
  • What's the desired length? (Quick hits vs deep dives)

Consistency beats frequency—better to do monthly well than weekly poorly.

4

Define the Newsletter Format:

## Newsletter Format: [Name]

**Frequency:** [Weekly/Bi-weekly/Monthly]
**Send Day/Time:** [Best based on audience]
**Length:** [~500 words / ~1000 words / Variable]

### Standard Sections
1. **[Section 1]:** [Description, ~X words]
   Example: "Main Story" — One deep topic, 300-400 words

2. **[Section 2]:** [Description, ~X words]
   Example: "Quick Hits" — 3-4 bullet points of news/tips

3. **[Section 3]:** [Description, ~X words]
   Example: "Resource of the Week" — One recommended link

4. **[Section 4]:** [Description, ~X words]
   Example: "What We're Working On" — Product update or behind-the-scenes

### Recurring Elements
- Intro: [Personal note / TLDR / Hook question]
- CTA: [Primary action each issue]
- Sign-off: [Consistent closer]
5

Generate 4-Week Content Calendar:

## Newsletter Content Calendar

### Issue 1: [Theme]
**Subject Line Options:**
1. [Option 1]
2. [Option 2]

**Main Story:** [Topic and angle]
**Quick Hits:** [3-4 items]
**Resource:** [What to feature]
**CTA:** [This issue's action]

### Issue 2: [Theme]
[Same structure]

### Issue 3: [Theme]
[Same structure]

### Issue 4: [Theme]
[Same structure]

Themes should vary—don't repeat the same type of content back-to-back.

6

Create a Newsletter Template:

## Newsletter Template

**Subject:** [Format: consistent prefix or variable]
**Preview Text:** [40-90 chars]

---

[Optional: Personal intro / 1-2 sentences]

## [Main Story Headline]
[Content]

---

## Quick Hits
• [Item 1]
• [Item 2]
• [Item 3]

---

## [Resource Section]
[Description + link]

---

## [Product/Company Section]
[Update or behind-the-scenes]

---

[Sign-off]
[Name/Team]

---

[Footer: Unsubscribe, preferences, social links]
7

Provide operational recommendations:

  • Best send time for the audience type
  • Subject line A/B testing approach
  • Metrics to track (opens, clicks, replies, unsubscribes)
  • Content sourcing process (where to find stories each week)
  • Batching strategy (write multiple issues at once)

Offer to save the format and calendar to uiEmail Sequence Library.

                    To run this task you must have the following required information:

> Newsletter purpose, target audience, content sources available, desired frequency (weekly, bi-weekly, monthly)

If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.

---

You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).

Add all steps to your todo list now and begin executing.

## Steps

1. [Read Email Sequence Patterns]: Read the documentation in: `./skills/sauna/[skill_id]/references/marketing.email.patterns.md` (Get newsletter timing and structure guidance)

2. [Read Email Sequence Library]: Read the file at `./documents/marketing/email/sequences.yaml` and analyze its contents (Check for existing newsletter templates)

3. Gather newsletter context:
- What's the purpose? (Educate, engage, nurture, sell)
- Who's the audience? (Customers, prospects, community)
- What content do you have access to? (Blog, product updates, industry news, original insights)
- How often can you realistically send? (Weekly, bi-weekly, monthly)
- What's the desired length? (Quick hits vs deep dives)

Consistency beats frequency—better to do monthly well than weekly poorly.


4. Define the Newsletter Format:

```markdown
## Newsletter Format: [Name]

**Frequency:** [Weekly/Bi-weekly/Monthly]
**Send Day/Time:** [Best based on audience]
**Length:** [~500 words / ~1000 words / Variable]

### Standard Sections
1. **[Section 1]:** [Description, ~X words]
   Example: "Main Story" — One deep topic, 300-400 words

2. **[Section 2]:** [Description, ~X words]
   Example: "Quick Hits" — 3-4 bullet points of news/tips

3. **[Section 3]:** [Description, ~X words]
   Example: "Resource of the Week" — One recommended link

4. **[Section 4]:** [Description, ~X words]
   Example: "What We're Working On" — Product update or behind-the-scenes

### Recurring Elements
- Intro: [Personal note / TLDR / Hook question]
- CTA: [Primary action each issue]
- Sign-off: [Consistent closer]
```


5. Generate 4-Week Content Calendar:

```markdown
## Newsletter Content Calendar

### Issue 1: [Theme]
**Subject Line Options:**
1. [Option 1]
2. [Option 2]

**Main Story:** [Topic and angle]
**Quick Hits:** [3-4 items]
**Resource:** [What to feature]
**CTA:** [This issue's action]

### Issue 2: [Theme]
[Same structure]

### Issue 3: [Theme]
[Same structure]

### Issue 4: [Theme]
[Same structure]
```

Themes should vary—don't repeat the same type of content back-to-back.


6. Create a Newsletter Template:

```markdown
## Newsletter Template

**Subject:** [Format: consistent prefix or variable]
**Preview Text:** [40-90 chars]

---

[Optional: Personal intro / 1-2 sentences]

## [Main Story Headline]
[Content]

---

## Quick Hits
• [Item 1]
• [Item 2]
• [Item 3]

---

## [Resource Section]
[Description + link]

---

## [Product/Company Section]
[Update or behind-the-scenes]

---

[Sign-off]
[Name/Team]

---

[Footer: Unsubscribe, preferences, social links]
```


7. Provide operational recommendations:
- Best send time for the audience type
- Subject line A/B testing approach
- Metrics to track (opens, clicks, replies, unsubscribes)
- Content sourcing process (where to find stories each week)
- Batching strategy (write multiple issues at once)

Offer to save the format and calendar to `./documents/marketing/email/sequences.yaml`.