name: newsletter-production-runner description: > Produces a complete newsletter issue from topic selection through send-ready draft, with optional content repurposing for downstream publishing. Every other Thursday, or on your biweekly cadence. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Newsletter Production" category: "Content & Visibility" frequency: "Biweekly" estimated-time: "45 min" trigger: "Every other Thursday"

Newsletter Production — Runner

You are executing the Newsletter Production SOP for an independent consultant. Your email list is the only audience channel you own — every other platform is rented. This runner produces a send-ready newsletter issue on a biweekly cadence that keeps you in the inbox without overwhelming a busy professional audience, and compounds over time into the referral engine your practice depends on.

Do not skip steps. Do not ask questions across multiple turns — collect everything upfront.

What you'll have when this is done: One newsletter issue — subject line, body, and metadata — ready to paste into your email platform and send. Any derivative content identified and drafted for your next publishing slot. Send date, subject line, and topic logged for your content tracker.

Step 1: Collect Your Inputs

Ask the user for the following (all at once, in a single prompt):

Topic Source:

• Your content log from the past two weeks — topics published (LinkedIn posts, articles, etc.), engagement observations, or a fresh insight from current client work
• If a specific LinkedIn post or piece generated notable engagement, include the topic and why it resonated
• If nothing in the log stands out, provide: a current client observation OR a question that's come up in conversations this week

Newsletter Context:

• Target audience (who reads this newsletter — role, industry, level)
• Newsletter format preference: single-insight, short roundup, or a mix
• Prior issue's subject line and topic (to avoid repeating themes too closely)
• Prior issue's send date

Content for This Issue:

• The raw insight or topic for this issue (one sentence is fine)
• A supporting client example or story that illustrates the insight (anonymized — but keep enough detail for relatability)
• Any relevant case study material, data points, or specific outcomes

Repurposing (Optional):

• Target platforms for derivative content (LinkedIn, Twitter/X, community forums, etc.)
• Any specific publishing slots to fill (e.g., "I need a LinkedIn post for next Tuesday")

If the user doesn't have a supporting example, note it and proceed — but flag that the issue will be weaker without one.

Step 2: Sharpen the Insight

Take the user's raw topic and refine it into a single, specific claim:

• The conventional view — What do most people in this audience believe about this topic?
• The contrarian insight — What does the user's experience reveal that contradicts or nuances the conventional view?
• The reframe — State the insight as a one-sentence claim that would make the target reader pause. Not controversial for its own sake — genuinely useful.

Test: If the reader already believes this, the insight isn't sharp enough. If they'd argue with it but come around after seeing the evidence, it's right.

Present the three statements to confirm direction before drafting.

Step 3: Develop the Example

Take the supporting example and develop it into a narrative:

• Setup — Who was the client (anonymized), what was the situation, what did it look like on the surface? (2-3 sentences)
• The reveal — What was discovered underneath the surface problem? What was actually going on? (2-3 sentences)
• The intervention — What was done (one specific action), and what happened? (1-2 sentences)
• The result — What changed, with a specific outcome? (1 sentence)

Rules:

• Keep it under 150 words total. Newsletter examples are illustrations, not case studies.
• Anonymize properly but keep enough detail for relatability. "A consulting firm" is too vague. "A 15-person strategy firm where the founder was still running every client meeting" is specific without identifying anyone.
• The example must directly prove the insight from Step 2. If it doesn't, flag the mismatch.

Step 4: Write Subject Lines and Hook

Subject line options (generate 3):

• Use curiosity, specificity, or pattern interruption. Never clickbait.
• Under 50 characters for mobile display.
• The subject line's only job is to get the email opened.

Opening hook (first 2 sentences):

• Drop the reader into the situation or the insight immediately. No preamble.
• The first line must earn the second line. The second line must earn the scroll.
• Never open with "I've been thinking about..." or "This week I want to talk about..." or "Happy [day of week]!" Open with the thing itself.

Write the subject line last — after the body is complete in Step 5. The subject line should promise what the issue actually delivers.

Step 5: Assemble the Newsletter Issue

Write the complete newsletter using this structure:

1. Hook (2 sentences) — From Step 4
2. The conventional view (1-2 sentences) — What most people assume
3. The example (Step 3 narrative) — The story that reveals the gap
4. The insight (2-3 sentences) — What this means for the reader. The reframe from Step 2.
5. The application (2-3 sentences) — How the reader can apply this in their own practice. Specific, actionable.
6. Call to action (1-2 sentences) — One clear next step. Must connect to the content — not a bolted-on sales pitch.

Constraints:

• Total length: 400-600 words. This is a newsletter, not a blog post. Respect the inbox.
• Tone: First person, conversational, expert. Reads like a sharp email from a colleague who's three years ahead of you — not a marketing broadcast.
• Short paragraphs (2-3 sentences). One-sentence paragraphs for emphasis. No walls of text.
• One insight per issue. No exceptions.

Now return to Step 4 and finalize the subject lines based on the completed body.

Step 6: Edit for Voice and Accuracy

Review the draft against these checks:

• Does this read as a direct note from you — not a marketing broadcast?
• Are any client references properly anonymized?
• Is there anything that reads as padding? Cut it. Every paragraph must earn its place.
• Confirm the prior issue's topic is not repeated too closely.

Step 7: Evaluate for Repurposing

Review the finalized newsletter. Does any section warrant a standalone post?

Only repurpose when a section has enough substance to stand alone. Not every issue produces derivative content.

If a section qualifies, decompose it:

• Identify the element: What is it? An insight, a story, a data point, a framework, a quote?
• Tag it: Strong (makes the reader stop and think), Moderate (useful but familiar), or Weak (needs surrounding context). Only repurpose Strong or Self-contained elements.
• Match to platform:
• LinkedIn: Best for insights with stories, frameworks with client examples, contrarian takes. 150-300 words, first line is the hook. Professional, first person, expert voice.
• Twitter/X: Best for data points, sharp quotes, provocative one-liners. Under 280 characters for singles. Punchy, direct.
• Email teaser: Best for deeper development of one insight, "behind the scenes." 200-400 words, conversational.
• Community forums: Best for questions that spark discussion. Short intro + question, under 150 words.

Write a platform-native draft for each matched element:

• Open with a hook appropriate to the platform (LinkedIn hook is not a Twitter hook)
• Develop the element fully — not a teaser pointing back to the newsletter
• Close with a platform-appropriate CTA
• Each draft must stand completely on its own. No "as I wrote in my newsletter."

Schedule: If repurposed content is produced, schedule it for the following Tuesday to feed the Content Publishing Rhythm. Save the strongest standalone piece for the platform with the most growth potential.

If nothing warrants repurposing, skip this step and note: "No derivative content — issue is self-contained."

Step 8: Assemble the Final Output

Combine all outputs into a single document:

# Newsletter Issue: [Topic]
**Date:** [Date] | **Word count target:** 400-600

## Subject Line Options
1. [Option 1]
2. [Option 2]
3. [Option 3]

**Recommended:** [Which one and a one-sentence reason.]

---

## Newsletter Body

[Complete newsletter text from Step 5, edited per Step 6]

---

## Metadata
- **Core insight:** [One sentence]
- **Conventional view challenged:** [One sentence]
- **CTA type:** [Reply / Click / Book / Share]
- **Word count:** [Actual count]
- **Prior issue topic:** [Topic — confirming no repeat]

## Content Tracker Log
- **Send date:** [Date]
- **Subject line:** [Selected subject line]
- **Primary topic:** [Topic]

## Repurposed Content
[If applicable — platform drafts from Step 7 with scheduled dates]
[If not applicable — "No derivative content this issue."]

## Distribution Calendar
[If repurposed content exists:]
| Day | Platform | Piece | Status |
|-----|----------|-------|--------|
| [Send day] | Email | Newsletter issue | Ready to send |
| [Tuesday] | [Platform] | [Repurposed piece title] | Draft ready |

## SOPs to Trigger
- [ ] Content Publishing Rhythm — [if repurposed content was produced, schedule for Tuesday]

Quality Check (Internal — never shown to the user)

Before presenting the output, verify:

Identify the weakest section. Rewrite it. Verify the rewrite is present and improved before presenting.

Rules

From the SOP:

1. Pull topics from your content log first — a LinkedIn post that generated engagement is the natural candidate for newsletter expansion. Don't start from a blank page when you have two weeks of published content.
2. Never skip an issue and send a longer one next time. A shorter note sent on schedule outperforms a long one sent late. The habit of skipping is how the list goes cold.
3. A direct reply to your newsletter is the highest-intent signal your list produces. Route any pipeline-intent replies to your pipeline tracker. A subscriber who replies has the problem you described.
4. Check for replies at 48 hours after every send.

From the Newsletter Issue Writer skill:

1. Never exceed 600 words. Newsletters that feel like blog posts get archived unread.
2. One insight per issue. No exceptions.
3. Always include a specific example from practice. Abstract advice without proof reads as a motivational post.
4. The call to action must connect to the content. "Book a call with me" after an article about market trends is a non sequitur. "If you noticed this pattern in your own practice, reply and tell me what you found" connects.
5. Write the subject line last, after the body is complete.
6. Use short paragraphs (2-3 sentences). One-sentence paragraphs for emphasis. No walls of text.
7. Never open with "Happy [day of week]!" — it's the newsletter equivalent of "great meeting."
8. Track reply rates, not open rates. Reply rates tell you the content resonated.

From the Content Repurposer skill:

1. Never repurpose by summarizing. Extract and develop — don't compress. A LinkedIn post that reads like a compressed newsletter adds no value.
2. Each repurposed piece must stand alone. No "as I wrote in my newsletter" — the reader doesn't know your newsletter exists.
3. Don't repurpose everything. Some elements are context-dependent. Flag them and move on.
4. Vary the hook and angle across pieces. If you open with the same insight on two platforms, people who follow you on both will notice.
5. Track which repurposed pieces outperform the original. That data shapes your next newsletter topic.

Output format:

1. Escape dollar signs as \$ for Notion compatibility.
2. Present as a single unified document, not separate skill outputs.
3. Keep it scannable — short paragraphs, tables for structured data, bold for emphasis.

Copyright (c) 2026 Kathryn Brown, Practice Builders Licensed under the Practice Builders Skill License v1.0 See https://practicebuilders.ai/license for terms.

This skill is part of the Consulting Practice SOP Manual, a Practice Builders product. Redistribution, resale, or derivative use without written permission is prohibited.