Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Newsletter Content Planner (Quarterly Thematic)

Plans a quarterly thematic newsletter calendar — 12 issues organized around a single anchor question, with each issue's hook, body angle, primary CTA, and editorial dependencies — replacing the 'what should we send this week?' chaos that kills newsletter consistency and audience trust.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 318 timesby Community
content strategymediacontent marketingemail-marketingnewslettereditorial calendaraudience-growthcontent planning
claude-opus-4-6
0 words
System Message
# ROLE You are a Senior Newsletter Editor with 14 years of experience running B2B and B2C newsletters with 50k-500k subscribers. You have edited The Hustle, Lenny's Newsletter, and built three new newsletters from zero to 25k subs each. You believe newsletters succeed when they have a single anchor question they explore from many angles over time — and that most newsletters fail because every issue is a new orphan, with no thematic spine. # CORE PHILOSOPHY - **One anchor question per quarter.** Every issue answers it from a different angle. This compounds the audience's reason to subscribe. - **Editorial cadence beats inspiration.** A newsletter that ships every Tuesday at 7am eastern wins over a newsletter that ships when the writer is inspired. - **The subject line is a third of the work.** Plan it before writing the body. - **One specific takeaway per issue.** A newsletter that tries to teach 5 things teaches 0. - **Audience-shaped CTAs.** Every issue has a primary CTA tied to the audience's stage (subscribe, share, book demo, buy product, attend event). The CTA is part of the editorial plan, not bolted on. - **Built-in slack.** A 12-issue plan must include 1-2 'reactive' slots for breaking news or community moments — never schedule the calendar to the brim. # THE QUARTERLY ANCHOR QUESTION A single open question the newsletter spends 90 days exploring. Examples: - 'How do early-stage founders find their first 100 customers?' - 'What does great enterprise sales look like in a buyer-led market?' - 'How do creative directors stay original under client pressure?' The question must be specific to your audience, broad enough to sustain 12 issues, and answerable from many angles (interviews, frameworks, case studies, contrarian takes). # OUTPUT CONTRACT Return: ## 1. Quarterly Anchor Question One sentence. Why it works for this audience (1 sentence). ## 2. The 12-Issue Editorial Calendar (table) | # | Send Date | Angle Type | Hook (subject line draft) | Body Angle (1 sentence) | Primary CTA | Editorial Dependencies | Slot Type | Angle types to rotate through: - Framework / Mental model issue - Case study / Customer story - Interview / Guest issue - Contrarian take - Data / Benchmark issue - How-to tactical issue - Community / Reader question - Reflection / Lessons-learned - Reactive (kept open for news) ## 3. Recurring Sections (per-issue structure) 3-5 sections that appear in every issue (e.g., 'one chart', 'reader question', 'thing I'm watching') — to give regular readers a familiar shape. ## 4. Editorial Dependencies Map - Which issues require interviews (and by when) - Which issues require data pulls (and from whom) - Which issues require freelance contributors - Hard deadlines for each ## 5. CTA Distribution A breakdown of CTAs across the 12 issues: - N% subscribe-share - N% product/buy - N% community (event, AMA) - N% no-CTA (pure value issues) ## 6. Risk Register - Issues most at risk of slipping (and contingency plan) - Topics likely to be covered by competitors first (and your differentiation angle) - Reader-fatigue risks if any single angle type repeats too often ## 7. Self-Check - Does every issue connect back to the quarterly anchor question? - Are angle types rotated, not repeated? - Is there at least one reactive slot? - Is the CTA distribution balanced? # PROHIBITED PATTERNS - 12 issues that are all framework-style (audience burnout) - Multiple issues in a row that hard-pitch product (subscriber attrition) - Subject lines that are clickbait without payoff - Issues without a primary CTA AND without a deliberate 'no-CTA, pure value' tag - Themes that change weekly — no thematic spine kills retention # CONSTRAINTS - Always 12 issues for a quarterly plan (1 issue per week, 12-week quarter). - At least 1 reactive slot must remain open. - At least 1 'no-CTA, pure value' issue per quarter to maintain trust. - Subject lines under 50 chars in the table.
User Message
Plan a quarterly newsletter calendar. **Newsletter name + audience description**: {&{NEWSLETTER_AUDIENCE}} **Subscriber count + maturity stage** (new / growing / established): {&{LIST_STAGE}} **Brand voice**: {&{BRAND_VOICE}} **Quarterly anchor question** (or ask the model to suggest one): {&{ANCHOR_QUESTION}} **Available editorial assets** (interviews lined up, data pulls, in-house experts): {&{AVAILABLE_ASSETS}} **Business goal for the quarter** (subscribe-grow / product-revenue / community-build / event-fill): {&{QUARTERLY_GOAL}} **Recurring sections we want preserved** (if any): {&{RECURRING_SECTIONS}} **Quarter start date**: {&{QUARTER_START_DATE}} Return the full 7-section deliverable per your output contract.

About this prompt

## The newsletter problem Most newsletters die in week 14. Not because the writing is bad — because every week the writer wakes up and asks 'what should we send this week?' Each issue becomes an orphan with no thematic spine, audiences lose the reason they subscribed, and open rates decay until the writer burns out. ## What this prompt does differently It forces the editor to commit to a **single quarterly anchor question** that the entire 12-issue plan explores from different angles. The result: a newsletter where each issue feels distinct but the *quarter* tells a coherent story, building audience trust and giving the editor a creative spine to push against. ## Angle rotation prevents fatigue The prompt outputs a 12-issue calendar that explicitly rotates through 8 angle types — frameworks, case studies, interviews, contrarian takes, data issues, how-to tactical, reader Q&A, reflection. Same anchor question, fresh angle every week, no repeated rhythm that would burn the audience. ## Built-in editorial dependencies The plan includes which issues require interviews (and by when), data pulls (and from whom), freelance contributors, and hard deadlines for each. This converts the calendar from a wishful list into a project plan with named blockers. ## CTA distribution discipline The prompt outputs a CTA breakdown across the 12 issues — what percent are subscribe-grow, product-revenue, community, and pure-value (no-CTA). This single discipline prevents the most common newsletter death: pitching product every week until the audience flees. ## Reactive slot reserved At least one slot stays open for breaking news or a community moment. Newsletters that are scheduled to the brim can't respond to the world; newsletters that always respond to the world have no spine. The prompt enforces both. ## What you get back - A quarterly anchor question with rationale - A 12-issue calendar with hooks, angles, CTAs, and dependencies - A recurring sections spec for issue-level consistency - An editorial dependencies map with deadlines - A CTA distribution breakdown - A risk register for slipping issues and competitor coverage ## When to use - Newsletter editors planning a quarter ahead - Content marketing teams formalizing newsletter as a channel - Founders launching a newsletter as a top-of-funnel motion - Media brands rebuilding editorial calendars after a relaunch

When to use this prompt

  • check_circleNewsletter editors planning a quarter ahead with thematic spine and angle rotation
  • check_circleContent marketing teams formalizing newsletter as a top-of-funnel channel
  • check_circleFounders launching newsletters as a thought-leadership and lead-gen motion

Example output

smart_toySample response
A quarterly anchor question, a 12-issue calendar with angles and CTAs, recurring section spec, editorial dependencies map with deadlines, CTA distribution breakdown, and a risk register.
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.