Newsletter Intro Hook Prompt

What this prompt does

Newsletters live or die in the first 50 words. If your opening paragraph doesn't pull people forward, they skim to the links and close. This prompt generates opening hooks that are specific to your content, grounded in something real (a stat, observation, or story), and lead naturally into whatever the newsletter covers.

Works across email platforms — doesn't depend on any formatting tricks, just strong writing.

The prompt

Write 3 different opening hooks for a newsletter issue about [NEWSLETTER TOPIC / THIS WEEK'S MAIN STORY].

Newsletter context:
- Newsletter name/brand: [NAME — or describe the audience if no name, e.g., "a weekly email for mid-career professionals"]
- This issue covers: [MAIN TOPIC OR 2–3 TOPICS — be specific]
- One real detail I can anchor the opening to: [A STAT, OBSERVATION, STORY, OR RECENT EVENT — e.g., "Google announced a new search algorithm update this week," "I've spent 40 hours testing AI writing tools this month," "a student asked me a question I didn't have an answer to"]
- Tone: [conversational / professional / warm / funny-casual]
- Target length for each hook: 40–80 words

For each version, use a different hook style:
1. **Story opener** — starts with a specific moment or observation
2. **Stat or data opener** — leads with a surprising or counterintuitive number
3. **Question opener** — poses a question the reader likely has

End each version with a natural bridge sentence that leads into the rest of the newsletter.

How to use it

1. Give it one real anchor — the more specific the detail you provide, the more the hook will feel earned. "I noticed something this week" is a weak anchor; "Substack just killed its recommendation algorithm" is a strong one.
2. Run all three versions and pick the strongest — sometimes the question version lands best, sometimes the story does. Don't commit to a style before you see the options.
3. Test the stat version carefully — if you're using a number, make sure it's accurate. AI will sometimes invent plausible-sounding stats.
4. Trim the bridge sentence — the transition line sometimes feels forced. If it does, cut it and write your own.

Example output

Newsletter topic: This week's roundup covers ChatGPT's new memory feature, a tool for summarizing long PDFs, and why most people are using AI wrong for research.

Anchor: "I tested the new ChatGPT memory feature every day this week."

Version 1 — Story opener:

Every morning this week, I started my session with ChatGPT the same way: no recap, no re-explaining my context, just picking up where we left off. By day three, it remembered I was working on a product launch and referenced it without prompting. This week I'm breaking down what that means for how you work — and two other tools worth knowing about.

Version 2 — Stat opener:

ChatGPT has roughly 400 million weekly active users as of early 2026. And most of them restart every conversation from scratch. This week's issue is about memory, context, and why giving AI a longer runway changes the quality of everything it produces.

Version 3 — Question opener:

What if you didn't have to re-explain yourself every time you opened ChatGPT? That's what the new persistent memory feature is trying to solve — and this week I tested whether it actually works. Plus: a PDF summarizer that might replace three tools you're currently using.

Variations

For classroom newsletters (teachers)

"Write a hook for a classroom newsletter to parents. Topic: [WHAT STUDENTS ARE LEARNING THIS WEEK]. One real detail from class this week: [SPECIFIC MOMENT OR ACTIVITY]. Tone: warm and personal, like a note from the teacher, not a school announcement."

For product/SaaS newsletters

"Write a hook for a product update newsletter. Topic: [NEW FEATURE]. One real benefit early users reported: [SPECIFIC FEEDBACK]. Keep it short — this audience reads on mobile."

Common pitfalls

• Don't: Start with "Welcome to this week's edition of…" — this is a space-waster that tells the reader nothing they don't know.

• Try instead: Jump into the hook immediately. They subscribed; they know what newsletter this is.

• Don't: Use the stat version if the stat is vague ("many users report…"). Stats only work if they're specific and verifiable.

Who uses this prompt

• Marketers: Weekly roundups, product updates, campaign newsletters
• Freelance writers: Personal newsletters and Substack editions
• Small business owners: Customer email newsletters, promotions with context
• Teachers: Classroom parent newsletters with weekly learning updates
• Content creators: YouTube, podcast, and blog update emails