Prompt library · AI · 12 prompts
Prompts from the guide
Newsletter from Zero: Growth, Content, Automation
12 prompts from this guide. Fill in whatever sits in [square brackets] — your own context, the document text or the name of your tool. That context is exactly what separates a generic answer from a usable one.
Promise, rhythm, scope
I'm about to start a newsletter and I need this to be a decision, not a vibe. What I do: [field, who I help, how I make a living] Who I want to write to: [audience description and their situation] What I can write about long-term: [3–5 topics] How much time I have per issue: [e.g. 2 hours] What I want to happen next: [leads / course sales / a community] Propose 4 different newsletter concepts. For each: - The promise in one sentence (what the reader gets and what it does for them) - Exactly who it's for and who it's not for - Rhythm, and an estimate of how much work one issue takes - Structure of a single issue (which sections, and why) - How it differs from what already lands in my industry's inboxes - Where it breaks down after twenty issues (what will wear thin) Take the last point seriously — I want to see what's sustainable. Don't invent facts about my field; work only with what I wrote.
Three formats that work
I want to build a lead magnet — something I give people in exchange for their email. My field and what I sell: [description] Who I write to: [audience] Newsletter promise: [promise from phase 1] What I already have: [source material, notes, slides, processes, client replies, spreadsheets I use] Propose 5 lead magnets. For each: - A specific title (not “the guide to X”) - What ONE problem it solves, and for whom - Format (checklist / template / mini-course / calculator) - What existing material it can be built from - An estimate of how much work it takes - Why someone would give up their email for it — and how it beats what people can find for free with a search Rank them by value to the reader relative to my effort. Don't propose anything I'd have to build from scratch over a whole week.
Producing the lead magnet's content
I'm building a [checklist / template] called [name] for [audience]. It's meant to solve this problem: [description]. My source material — how I actually do this: [paste notes, transcripts, old client emails] Build the content: - Step-by-step structure, in the order it's actually done - For each step: what to do (imperative, one sentence), how to know it's done, and the most common mistake - Cut steps that are obvious, and don't pad it out - End with 3 check-yourself questions Work only from my source material. Where a step is missing from it, write FILL IN and exactly what I need to supply. Write in my language, not the language of marketing guides.
Phase 3: welcome sequence
Write a 4-email welcome sequence for new newsletter subscribers. Newsletter: [promise and rhythm] Audience: [who I write to] Lead magnet: [what they received] Who I am: [3–4 sentences on what I do and why I'm good at it] Best content I can point to: [links and what they're about] Sample of my writing: [paste 300–500 words of my own text] For each email, give: - when it sends (day after signup) - subject line (max 45 characters) and preheader (max 90 characters) - body copy written in my style, per the attached sample - one call to action; across all four combined, no more than one mention of what I sell Rules: - No “hope this finds you well” and no addressing a crowd. - Email 4 should end with one specific question to the reader. - Don't invent anything about me — use only what I wrote.
A style profile: have it describe how you write
Here are 5 of my own texts that I consider good and typical of me: [paste texts, 2,000–4,000 words total] Describe my writing style precisely enough that someone could use it to write a new piece that's hard to tell apart from mine. Specifically: - sentence and paragraph length, rhythm, how I mix short and long - how I address the reader (formal/casual, individual/crowd) - words and phrases I use repeatedly - words and phrases that are NOT in my writing - how I open and how I close - how I use examples, numbers, and admitting uncertainty - how much humor, and exactly what kind Write the output as instructions for another writer, not as analysis. Attach an example from my texts for every point. Don't flatter me — describe what I do poorly or repetitively too.
An issue draft from raw notes
I'm writing an issue of my newsletter. Here are my raw notes on the topic — unorganized, exactly as they occurred to me: [paste notes or a dictation transcript] My style profile: [paste the profile from the previous step] Issue structure I stick to: [sections] Length: [e.g. 700 words] Build a draft: - Keep my ideas and my examples, don't add new ones - Put them in a logical order and add transitions - Open with a specific situation, not a general statement - Where a note is unclear, write QUESTION: and ask - Where a claim would need support I don't have, write VERIFY - Don't generalize into platitudes and don't add a summarizing conclusion that just repeats what was already said At the end, list every QUESTION and VERIFY.
Subject line and preheader
Here's a finished issue of my newsletter: [paste text] Write 10 subject line variants, each max 45 characters, and for each a preheader up to 90 characters that complements the subject without repeating it. Vary the approach across them: - a specific detail from the text (a number, a tool name, a situation) - a question the text answers - a contradiction or a surprising claim from the text - a plain, descriptive subject with no hook Rules: - No all caps, exclamation points, emoji, or words like “free,” “last chance,” “you won't believe” — they trip spam filters and kill trust. - Nothing the text doesn't deliver on. A subject line is a promise, not bait. - One sentence per variant on who it's aimed at.
Check before sending
Review this text before I send it as a newsletter issue. Don't rewrite it, just list the findings with the location quoted: [paste the issue] 1. Factual claims, numbers, and names that need verifying against a source (don't judge whether they're true — just list them). 2. Passages that read as generic AI writing: stock phrases, unsupported superlatives, empty summarizing sentences. 3. Promises the text doesn't deliver on, and mismatches with the subject line. 4. Links: missing, broken-looking, undescribed, unclear where they go. 5. Personal or client information that shouldn't go out. 6. Sentences a reader without context won't understand.
Segmentation by behavior, not by gut feel
Here's an export of my subscriber list — columns and a few rows (no email addresses, just behavior and attributes): [paste header and sample rows] I send [rhythm] and I want [goal: more leads / better deliverability / course sales]. Propose 3 to 5 segments that make sense for a list my size. For each: - the condition that defines it (specific, based on the columns above) - what I'd send that segment differently - roughly how many people would be in it, based on the data provided - what goes wrong if I add this segment (more work, a small sample) Don't propose a segmentation where I'd end up sending everyone the same thing anyway.
What to measure now that open rate has lost its meaning
I have a CSV export of my issue statistics. Header and first 3 rows (semicolon delimiter, UTF-8 encoding, decimal comma): [paste rows] Write a Python script (pandas) that: 1. loads the file and handles the number formatting, 2. calculates click rate, unsubscribe rate, and complaint rate per issue, relative to delivered, not sent, 3. compares issues against each other and flags any more than one standard deviation off the average, 4. calculates net list growth by month, 5. prints the issue with the most unsubscribes and the one with the most clicks, 6. saves the result to results.csv. For each step, write a comment explaining WHY it's done that way. Don't calculate anything in your reply, I want a script to run myself.
The basics that have to be true
Build me an operating checklist for my newsletter. Tool: [Brevo / Mailchimp / other]. Domain: [my own / third-party]. List size: [count]. Rhythm: [frequency]. Build three checklists: 1. ONE-TIME SETUP — what to configure now (domain verification, double opt-in, unsubscribe link, sender address, footer with identification) 2. BEFORE EVERY SEND — reviewing the issue, checking links, test email, mobile check, correct segment 3. QUARTERLY — cleaning out inactive subscribers, checking bounced addresses, reviewing the welcome sequence, checking the stats For each item, note where it's configured in the tool and how I'll know it's working. Make each checklist fit on one screen.
Consent and GDPR
I'm setting up a newsletter sign-up form and want the consent and disclosures done properly. Who I am: [sole proprietor/company, name, location] What I'll send: [content and frequency] What else I do with the address: [nothing else / behavior-based segmentation] Tool: [sending service and where its servers are, if I know] Lead magnet: [what they get after signing up] Propose: 1. Copy for the form (what arrives, how often, how to unsubscribe) 2. Wording for the consent checkbox 3. Paragraphs about data processing for the privacy policy page 4. Confirmation email text for double opt-in 5. A list of questions I should take to a lawyer, because I can't decide them from a generic template Write in plain language, not legalese. Don't present this as legal advice.