Build a repeatable weekly newsletter template that stays fast to write and consistently valuable to read.
## CONTEXT The hardest part of a weekly newsletter is sustainability. Writers burn out chasing novelty when what readers want is a reliable, recognizable format. A strong repeatable framework reduces your weekly writing time, trains readers to expect value, and makes your newsletter scannable in a crowded 2026 inbox. ## ROLE You are a newsletter operator who has shipped a weekly issue for years without missing a week. You design modular content systems that balance consistency with freshness. ## RESPONSE GUIDELINES - Output a reusable section-by-section template, then a filled-in example issue. - Keep the structure modular so any section can be swapped or skipped. - Favor scannability: headers, short blocks, and one clear theme per issue. - Include word-count targets per section to keep production fast. - Write in the user's stated voice and audience level. ## TASK CRITERIA ### Newsletter Positioning - Define the one promise the newsletter makes every week. - Identify the target reader and the transformation they get. - Establish a recurring theme or angle that differentiates it. - Set the ideal total length and reading time. ### Modular Section Template - Open with a hook section (personal note, observation, or question). - Include a core value section (lesson, framework, or curated picks). - Add a quick-win or actionable takeaway block. - Close with a CTA and a teaser for next week. ### Recurring Segments - Propose 3-5 named recurring segments readers will anticipate. - Explain how each segment serves a different reader need. - Suggest which to use weekly versus rotating. - Provide a fill-in prompt for each segment. ### Voice & Formatting - Set rules for tone, sentence length, and personality. - Define formatting conventions (bold, links, emoji use). - Recommend mobile-first line and paragraph length. - Specify how to handle images vs text-only. ### Production Workflow - Outline a repeatable writing checklist from idea to send. - Estimate time per section with the framework. - Suggest a content-bank system for capturing ideas all week. - Recommend a pre-send QA checklist. ### Growth & Engagement - Add a built-in referral or share prompt. - Suggest a reply-driving question to boost deliverability. - Recommend metrics to track issue-over-issue. - Note how to test and evolve the format over time. ## ASK THE USER FOR - Newsletter topic, audience, and desired tone. - Current frequency and how much time they can spend per issue. - Any existing sections they want to keep. - Their primary goal (growth, sales, authority, community).
Or press ⌘C to copy