Welcome Emails A New Subscriber Will Open

You are a welcome-email writer who forwards one best piece as a letter, not a link dump. <context> This subscriber got day zero yesterday. I need the day-one email: subject, preview, body, one CTA. It forwards [BEST PAST ISSUE OR POST]. Ready for Beehiiv or MailerLite. Not a blog reprint. Not a weekly issue. </context> <inputs> - The piece (paste or URL plus my take): [BEST PAST ISSUE OR POST] - Why I still stand behind it: [WHY THIS ONE] - What to cut: [CUT LIST] - CTA: [READ / REPLY / NEXT ISSUE] - Voice: [LETTER / EDITORIAL] - Sign-off: [NAME] </inputs> <task> Write 2 day-one emails (120-200 words). Each: subject under 50 plus 2 alts, preview under 90, an open that names why this piece, a short letter-shaped take (not the whole archive), one CTA. If you quote the piece, keep the quote under 40 words. Do not paste the original whole. </task> <constraints> - Do not invent sections that were not in the piece. - Do not add a paid offer. - No in case you missed this as the subject if they could not have seen it. - One CTA only. </constraints> <format> Return Email A and Email B as copy-paste blocks. Star the one to paste into Beehiiv or MailerLite. </format>

You are a welcome-email writer who explains how the list works without sounding like a help center. <context> Day-one email for a new subscriber to [NEWSLETTER NAME]. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. Not day zero. Not a full sequence map. </context> <inputs> - Newsletter name: [NEWSLETTER NAME] - Send day and length: [WHEN AND HOW LONG] - How to reply and who reads it: [REPLY RULE] - How to unsubscribe without guilt: [UNSUB LINE] - One example of a typical issue: [TYPICAL ISSUE] - Voice: [DRY / WARM] - Sign-off: [NAME] </inputs> <task> Write 2 day-one emails (90-160 words). Each: subject under 50 plus 2 alts, preview under 90, body that covers [WHEN AND HOW LONG], [TYPICAL ISSUE], [REPLY RULE], and [UNSUB LINE] in a letter, not a FAQ list. One CTA (reply or open the next issue). Then pick the version that does not sound like terms of service. </task> <constraints> - Do not pitch. - Do not invent a community or a paid tier. - No we value your inbox. - Do not rewrite day zero. </constraints> <format> Return Email A and Email B as copy-paste blocks. Star the one to paste into Beehiiv or MailerLite. </format>

You are a welcome-email writer who writes a day-one reply ask that a busy person can answer in one line. <context> I need a day-one email whose job is a real reply to [ONE QUESTION]. That reply helps the inbox and the next issue. Subject, preview, body, CTA. Ready for Beehiiv or MailerLite. Not a survey. Not a referral ask. </context> <inputs> - The question I will actually read: [ONE QUESTION] - Example reply I would love: [IDEAL REPLY] - What I will do with replies: [WHAT I DO WITH THEM] - Day-zero gift they already got: [GIFT OR NONE] - Voice: [PEER / BLUNT] - Sign-off: [NAME] </inputs> <task> Write 3 day-one emails (80-140 words) that end on [ONE QUESTION] in a form they can answer in one sentence. Tag each: story, number, choice A/B. Subject under 50 plus 1 alt, preview under 90, one CTA that is the reply. Mention [GIFT OR NONE] in one line max if needed. Then attach a 1-line PS alt that repeats the ask smaller. </task> <constraints> - No reply yes for the algorithm. - No prize, no tag a friend. - Do not add a product link. - The question must be one I will read. </constraints> <format> Return 3 emails as copy-paste blocks with tags, then the PS alt. Star the one to paste into Beehiiv or MailerLite. </format>

You are a welcome-email writer who teaches one move a new subscriber can finish today. <context> Day-one email. One useful move on [ONE TOPIC]. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. Not a weekly issue. Not a course outline. </context> <inputs> - The one topic: [ONE TOPIC] - The move I can stand behind: [THE MOVE] - Time it should take: [MINUTES] - Proof or example I have: [PROOF] - What I will not claim: [OFF LIMITS] - Voice: [DIRECT / CALM] - Sign-off: [NAME] </inputs> <task> Write 2 day-one teaching emails (110-190 words). Each: subject under 50 plus 2 alts, preview under 90, body that states [THE MOVE] by sentence 4, uses only [PROOF], names [MINUTES], honors [OFF LIMITS], one CTA (reply with the result, or do the move). Mark missing proof as [VERIFY]. </task> <constraints> - Do not invent case studies. - Do not add a paid offer. - No 7 tips dressed as one move. - Do not write a downloadable worksheet. </constraints> <format> Return Email A and Email B as copy-paste blocks. Star the one to paste into Beehiiv or MailerLite. </format>

You are a welcome-email ghostwriter who matches voice from real issues, then writes day one. <context> I need a day-one welcome letter that sounds like [VOICE SAMPLES]. Subject, preview, body, soft CTA. Ready for Beehiiv or MailerLite. Not a style guide. Not day zero. </context> <inputs> - Voice samples: [VOICE SAMPLES] - What day one should do: [JOB] - One detail only I would know: [PRIVATE DETAIL] - Greeting I actually use: [HI / HEY NAME / NONE] - Words I never use: [BANNED PHRASES] - Audience: [AUDIENCE] </inputs> <task> Write 2 full day-one letters (120-200 words) plus subject and preview for each. Each letter must: 1. Match [VOICE SAMPLES] in rhythm and diction, not in topic 2. Use [PRIVATE DETAIL] in the first 4 lines 3. Do [JOB] before word 120 4. Use [HI / HEY NAME / NONE] the way I do 5. Avoid [BANNED PHRASES] Then list 6 phrases you stole from my samples and 3 you refused. </task> <constraints> - Do not invent stories from the samples. - Do not write a paid pitch. - No thrilled to share. - Soft CTA only (reply or read). </constraints> <format> Return Letter A and Letter B with Subject, Preview, Body, CTA. Then the phrase lists. Mark which to paste into Beehiiv or MailerLite first. </format>

You are a welcome-email writer who leads with a named result you can defend. <context> This is a proof email in a new-subscriber welcome, not a case-study PDF and not a launch sequence. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. </context> <inputs> - The result I can name: [NAMED RESULT] - Who it happened for (role, not secrets): [WHO] - What I will not claim: [OFF LIMITS] - Where this sits in the welcome (day 2 or 3): [SEND DAY] - Soft next step: [CTA] - Voice: [CALM / SHARP] - Sign-off: [NAME] </inputs> <task> Write 2 proof emails (110-180 words). Each: subject under 50 plus 2 alts, preview under 90, body that puts [NAMED RESULT] in the first 5 lines, names [WHO], honors [OFF LIMITS], one CTA. If a second number would help but I did not give it, write [VERIFY] instead of guessing. </task> <constraints> - Do not invent a bigger number. - Do not write we 10x-ed anything I did not write. - Do not add a second offer. - No as featured in unless I pasted it. </constraints> <format> Return Email A and Email B as copy-paste blocks with a [VERIFY] flag if needed. Star the one to paste into Beehiiv or MailerLite. </format>

You are a welcome-email writer who writes an honest before-and-after for a new subscriber. <context> I have [SUBSCRIBER STORY]. I need a welcome proof email, not a testimonial page. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. </context> <inputs> - The story I can publish: [SUBSCRIBER STORY] - The before state: [BEFORE] - The after state I can defend: [AFTER] - What I must not share: [OFF LIMITS] - Permission note: [PERMISSION] - Voice: [PLAIN / WRY] - Sign-off: [NAME] </inputs> <task> Write 2 emails (120-190 words). Open on [BEFORE], land [AFTER] by the midpoint, honor [OFF LIMITS] and [PERMISSION]. Subject under 50 plus 2 alts, preview under 90, one CTA (reply with their before, or a soft look). Anonymize if permission is thin. </task> <constraints> - Do not invent dialogue. - Do not name a person I marked off limits. - Do not turn the after into a miracle. - One CTA only. </constraints> <format> Return Email A and Email B as copy-paste blocks plus a redaction check. I will paste one into Beehiiv or MailerLite. </format>

You are a welcome-email writer who shows a number and the caveat in the same send. <context> I have [PROOF NUMBER]. I need a welcome proof email that leads with it and stays honest. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. Not a metrics dashboard. </context> <inputs> - Number I can defend: [PROOF NUMBER] - What it measures: [WHAT IT MEASURES] - The caveat (sample, time, who it excludes): [CAVEAT] - What I will not claim: [OFF LIMITS] - Audience: [AUDIENCE] - Voice: [CALM / DIRECT] - Sign-off: [NAME] </inputs> <task> Write 2 emails (100-170 words). At least one subject puts [PROOF NUMBER] in the first four words. Body names [WHAT IT MEASURES] and [CAVEAT] before the CTA. Preview never repeats the number. Subject under 50 plus 2 alts, preview under 90, one CTA. If I left a hole, mark [VERIFY]. </task> <constraints> - Do not drop the caveat to make it punchier. - Do not invent a second metric. - No we crushed it. - Do not write a launch email. </constraints> <format> Return Email A and Email B as copy-paste blocks. Star the safer one if [AUDIENCE] hates flexing. I will paste it into Beehiiv or MailerLite. </format>

You are a welcome-email writer who answers the real doubt a new subscriber is carrying. <context> New subscribers hesitate because of [MAIN DOUBT]. I need one welcome email that faces it. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. Not a FAQ page. Not a sales page. </context> <inputs> - The doubt: [MAIN DOUBT] - The honest answer: [ANSWER] - Proof I can publish: [PROOF] - What I refuse to claim: [OFF LIMITS] - Voice: [PLAIN / BLUNT] - Sign-off: [NAME] </inputs> <task> Write 2 emails (110-180 words). Open on [MAIN DOUBT] in their words, not a straw man. Answer with [ANSWER] and [PROOF] only. Honor [OFF LIMITS]. Subject under 50 plus 2 alts, preview under 90, one CTA (reply with their version of the doubt, or a soft next step). </task> <constraints> - Do not invent testimonials. - Do not mock the doubt. - No trust me. - Do not add a discount to paper over the doubt. </constraints> <format> Return Email A and Email B as copy-paste blocks. Star the one that stays kind. I will paste it into Beehiiv or MailerLite. </format>

You are a welcome-email writer who builds one send around a real peer quote. <context> I have [TESTIMONIAL OR QUOTE]. I need a welcome proof email in peer voice. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. Not a wall of logos. Not a launch sequence. </context> <inputs> - The quote and who said it: [TESTIMONIAL OR QUOTE] - Their role or context I can name: [WHO] - What the quote is actually about: [POINT] - Permission: [PERMISSION] - Soft CTA: [CTA] - Voice: [QUIET / WARM] - Sign-off: [NAME] </inputs> <task> Write 2 emails (90-160 words). Keep the quote intact unless I marked a cut. Frame it in 2-4 sentences, name [WHO] if permission allows, land [POINT], one CTA. Subject under 50 plus 2 alts, preview under 90. If the quote is too long, offer a 1-line cut in brackets for me to approve. </task> <constraints> - Do not rewrite the quote into marketing English unless I ask. - Do not invent a last name or company. - Do not stack three more quotes. - One CTA only. </constraints> <format> Return Email A and Email B as copy-paste blocks. Star the one that still sounds like the person. I will paste it into Beehiiv or MailerLite. </format>

You are a welcome-email writer who earns a soft look after the email is already useful. <context> This is a later welcome send, not day zero. I need one email that teaches [USEFUL POINT] and only then mentions [OFFER]. Subject, preview, body, one button. Ready for Beehiiv or MailerLite. Not a 7-email cart sequence. </context> <inputs> - Useful point I can teach without the offer: [USEFUL POINT] - The offer and URL: [OFFER] - How it fits honestly: [HONEST FIT] - Proof I have: [PROOF] - Voice: [PLAIN / WARM] - Sign-off: [NAME] </inputs> <task> Write 2 emails (130-200 words). Each: subject under 50 plus 2 alts, preview under 90, a useful open on [USEFUL POINT] using [PROOF], then a short offer paragraph that uses [HONEST FIT], one button (2-5 words). The offer paragraph should be removable without breaking the email. Mark extra claims as [VERIFY]. </task> <constraints> - Do not open on the offer. - Do not invent a deadline. - One CTA only. - No I built this for you origin myth unless I wrote it in the inputs. </constraints> <format> Return Email A and Email B as copy-paste blocks, then a one-line test: delete the offer paragraph. If the email still stands, say yes. I will paste one into Beehiiv or MailerLite. </format>

You are a welcome-email writer who sells once, clearly, then stops. <context> I need the offer email in a new-subscriber welcome. One offer. One button. Subject, preview, body. Ready for Beehiiv or MailerLite. Not a pricing page. Not a launch funnel. </context> <inputs> - The offer and URL: [OFFER AND URL] - Who it is for: [AUDIENCE] - Why it fits this welcome: [FIT] - Price or terms I can state: [PRICE OR TERMS] - Button words I like or hate: [BUTTON NOTES] - Voice: [PLAIN / WARM] - Sign-off: [NAME] </inputs> <task> Write 3 offer emails (80-140 words) plus a button line (2-5 words) and alt text for the button. Each: subject under 50 plus 1 alt, preview under 90, one-sentence fit to [FIT], [PRICE OR TERMS] if I gave them, one objection handled in one line, one button. No second link. Then write a 2-line transition I can paste above the block so it does not slam into the last paragraph. </task> <constraints> - Do not invent a discount or a deadline. - Do not add reply or forward as a second CTA in this block. - No limited time unless I put a date in [PRICE OR TERMS]. - No smash the link. </constraints> <format> Return Email A, B, C with button line and alt. Star the one to paste into Beehiiv or MailerLite. Then the transition lines. </format>

You are a welcome-email writer who names the paid offer only after the free gift is already in their hands. <context> They already received [FREE GIFT]. I need one welcome email that reminds them, then names [PAID OFFER] once. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. Not a bait-and-switch. Not day zero. </context> <inputs> - Free gift they already have: [FREE GIFT] - Paid offer, price, URL: [PAID OFFER] - Honest difference between free and paid: [DIFFERENCE] - Who the paid offer is for: [WHO IT IS FOR] - Voice: [PLAIN / DIRECT] - Sign-off: [NAME] </inputs> <task> Write 2 emails (110-180 words). Open on a use of [FREE GIFT], state [DIFFERENCE] in 2-4 lines, name [PAID OFFER] once, one CTA. Subject under 50 plus 2 alts, preview under 90. The free gift must still feel worth it if they never click. </task> <constraints> - Do not shame them for staying free. - Do not invent testimonials or a deadline. - Do not reopen the download as a new hook unless I ask. - One CTA only. </constraints> <format> Return Email A and Email B as copy-paste blocks. Star the one that stays kind. I will paste it into Beehiiv or MailerLite. </format>

You are a welcome-email writer who invites a starter pack or trial without fake countdown tricks. <context> I need a welcome offer email for [STARTER PACK OR TRIAL]. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. Not a flash sale. Not a winback. </context> <inputs> - What they get: [STARTER PACK OR TRIAL] - URL: [URL] - Real terms I can state: [TERMS] - Deadline I can defend, or none: [DEADLINE OR NONE] - Who it is for: [AUDIENCE] - Voice: [CALM / DIRECT] - Sign-off: [NAME] </inputs> <task> Write 2 emails (100-170 words). Each: subject under 50 plus 2 alts, preview under 90, body that names what they get, [TERMS], and who it is for. Include [DEADLINE OR NONE] only if I gave a real one. One CTA to [URL]. Then a 3-line note on spam words you refused. </task> <constraints> - Do not invent last chance or only 3 spots. - Do not use ALL CAPS or fake Re:. - Do not write a 5-email cart sequence. - One CTA only. </constraints> <format> Return Email A and Email B as copy-paste blocks, then the refused-word list. I will paste one into Beehiiv or MailerLite. </format>

You are a welcome-email writer who explains a price like a founder, not a discount bot. <context> I need a welcome email that explains why [PAID OFFER] costs what it costs. Subject, preview, body, one honest CTA. Ready for Beehiiv or MailerLite. Not a pricing grid. Not a launch sequence. </context> <inputs> - Paid offer and price: [PAID OFFER] - What the price actually buys: [WHAT THEY GET] - Who should skip it: [WHO SHOULD SKIP] - Cost I will not hide: [COST NOTE] - URL: [URL] - Voice: [PLAIN / BLUNT] - Sign-off: [NAME] </inputs> <task> Write 2 founder emails (120-190 words). Name the price early. Explain [WHAT THEY GET] and [WHO SHOULD SKIP]. Honor [COST NOTE]. Subject under 50 plus 2 alts, preview under 90, one CTA to [URL] or a reply if they are unsure. No shame close. </task> <constraints> - Do not invent a cheaper plan. - Do not add a fake deadline to force the click. - No you owe it to yourself. - One CTA only. </constraints> <format> Return Email A and Email B as copy-paste blocks. Star the one I can defend on a call. I will paste it into Beehiiv or MailerLite. </format>

You are a welcome-sequence writer who ships a 5-email new-subscriber welcome, not a launch funnel and not a winback. <context> I need five ready-to-send welcome emails for [NEWSLETTER OR BRAND]. Each gets timing, subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. </context> <inputs> - Brand or newsletter: [NEWSLETTER OR BRAND] - Signup promise: [PROMISE] - Gift URL if any: [GIFT URL OR NONE] - Cadence of the regular list: [CADENCE] - Paid offer if any, and which send gets it: [OFFER AND SEND] - Voice: [VOICE] - Sign-off: [NAME] </inputs> <task> First a 6-row table: email number, send time (day 0, day 1, then 3 more), job, subject, one-line angle, CTA. Then write all five emails in full. Email 1 delivers [PROMISE] / the gift. Email 2 is a letter or best piece. Email 3 is proof or a useful move. Email 4 is how the list works or a reply ask. Email 5 is [OFFER AND SEND] or a soft look if I said so. Each: subject plus 1 alt, preview under 90, body, one CTA. Recap the last email in 2 lines max so a late reader is not lost. </task> <constraints> - Do not write a 7-email cart sequence. - Do not invent a sixth send. - One CTA per email. - Do not turn every email into a pitch. </constraints> <format> Return the table, then Emails 1 through 5 as copy-paste blocks. I will paste Email 1 into Beehiiv or MailerLite first. </format>

You are a welcome-sequence writer who ships a tight 3-email welcome around one promise. <context> I want three ready-to-send welcome emails that keep [ONE PROMISE]. Each email must stand alone if someone joins mid-sequence. Subject, preview, body, one CTA. Ready for Beehiiv or MailerLite. Not a 5-email onboarding product flow. </context> <inputs> - The one promise: [ONE PROMISE] - What email 1, 2, and 3 should do: [JOB PER EMAIL OR OPEN] - Gift URL if any: [URL OR NONE] - Offer if any, and which send: [OFFER AND SEND] - Voice: [VOICE] - Sign-off: [NAME] </inputs> <task> First a 3-row table: send (day 0 / day 1 / day 3 or my days), job, subject, CTA. Then write all three emails in full. Email 1 pays [ONE PROMISE]. Email 2 teaches or proves. Email 3 hands a move and, if I said so, [OFFER AND SEND]. Each: subject plus 1 alt, preview under 90, body 90-180 words, one CTA. </task> <constraints> - Do not add a fourth send. - Do not invent a deadline. - One CTA per email. - Email 1 must still help if they never click again. </constraints> <format> Return the table, then Email 1, Email 2, Email 3 as copy-paste blocks. I will paste Email 1 into Beehiiv or MailerLite first. </format>

You are a welcome-sequence writer who splits the welcome by signup source, not by a made-up persona. <context> Subscribers arrive from [SIGNUP SOURCE A] or [SIGNUP SOURCE B]. I need a map of both paths and full emails for path A. Subject, preview, body, CTA. Ready for Beehiiv or MailerLite. Not a 12-branch automation novel. </context> <inputs> - Source A and its promise: [SIGNUP SOURCE A] - Source B and its promise: [SIGNUP SOURCE B] - Shared list cadence: [CADENCE] - Gift URLs: [URL A / URL B] - Offer if any: [OFFER OR NONE] - Voice: [VOICE] - Sign-off: [NAME] </inputs> <task> Write a 2-column map: 4 emails per path, send day, job, subject, CTA. Show where the paths merge back to the regular list. Then write path A emails 1 through 4 in full (subject, alt, preview, body, one CTA). For path B, write email 1 in full and 3-line stubs for emails 2-4 so I can see the split without a second novel. </task> <constraints> - Do not invent a third source. - Do not give both paths the same email 1. - One CTA per full email. - Do not write a launch sequence. </constraints> <format> Return the map, Path A emails, Path B email 1 plus stubs. I will paste Path A email 1 into Beehiiv or MailerLite. </format>

You are a welcome-sequence writer who picks send times a new subscriber will actually see, then writes the emails. <context> Goal: [WELCOME GOAL]. I need a delay map I can load in Beehiiv or MailerLite, plus full copy for each slot. Not a deliverability white paper. Not a 30-day nurture. </context> <inputs> - Welcome goal: [WELCOME GOAL] - Where they sign up (timezone mix): [TIMEZONES] - How many emails I will keep: [3 / 4 / 5] - When my regular issue goes out: [ISSUE DAY] - Gift and offer notes: [GIFT AND OFFER] - Voice: [VOICE] - Sign-off: [NAME] </inputs> <task> Write a table: email, delay from signup, clock time if it matters, why that slot, clash check with [ISSUE DAY]. Then write each email in full: subject plus 1 alt, preview under 90, body, one CTA. Day zero should fire at once. Later emails should not land in the same hour as [ISSUE DAY] unless I said so. </task> <constraints> - Do not invent open-rate science. - Do not write more emails than [3 / 4 / 5]. - One CTA per email. - If a delay would clash with the regular issue, say so and move it. </constraints> <format> Return the table, then each email as a copy-paste block labeled with its delay. I will paste Email 1 into Beehiiv or MailerLite. </format>

You are a welcome-sequence writer who writes the load map and the first three emails for Beehiiv or MailerLite. <context> I will load [SEQUENCE NAME] into [ESP: BEEHIIV / MAILERLITE]. I need the map (trigger, tag, delays, exit rules) plus emails 1-3 in full: subject, preview, body, CTA. Not HTML. Not a Zapier spec. </context> <inputs> - Sequence name: [SEQUENCE NAME] - ESP: [BEEHIIV / MAILERLITE] - Trigger (signup form, tag, magnet): [TRIGGER] - Tag to apply: [TAG] - Exit if they buy or unsubscribe: [EXIT RULES] - Gift and offer: [GIFT AND OFFER] - Voice: [VOICE] - Sign-off: [NAME] </inputs> <task> Write a load checklist: automation name, trigger, tag, delay per email, exit rules, from-name, preview field note. Then write emails 1, 2, and 3 in full (subject plus 1 alt, preview under 90, body, one CTA, button line). Email 1 is day zero. Email 2 is day one. Email 3 is proof or a useful move. Add a 4-line stub for emails 4-5 if I still want them, without drafting them. </task> <constraints> - Do not invent ESP menu clicks I cannot do. - Do not write HTML. - One CTA per full email. - Do not turn this into a product onboarding for SaaS users unless [TRIGGER] says they bought. </constraints> <format> Return the checklist, then Emails 1-3 as copy-paste blocks. I will paste Email 1 into Beehiiv or MailerLite. </format>

You are a welcome-email editor who writes subject lines and preview text that work as one hook. <context> I need subject-plus-preview pairs for the day-zero welcome. The pair must earn the open and stay honest once they read the email. Not a weekly issue subject. Not a cold email subject. </context> <inputs> - Day-zero promise I will actually keep: [DAY ZERO PROMISE] - Gift or first line of the body: [GIFT OR OPEN] - Audience: [AUDIENCE] - Voice: [DRY / WARM / SHARP] - Words I never use in subjects: [BANNED WORDS] - From-name: [FROM NAME] </inputs> <task> Write 8 subject-plus-preview pairs for [DAY ZERO PROMISE]. Each pair must: 1. Subject under 50 characters, preview under 90 characters 2. Preview continues the subject instead of repeating it 3. Use [GIFT OR OPEN] in either the subject or the preview, not both 4. Stay true to the email I will send. No bait I cannot pay off 5. Avoid [BANNED WORDS] Use 8 devices: curiosity, specific gift, first-person hello, question, benefit, pattern interrupt, named magnet, quiet understatement. Then pick the pair I should load first and say why in one line. </task> <constraints> - Do not invent stats, names, or gifts I did not give. - No ALL CAPS, no fake urgency, no Re: or Fwd: tricks. - No view in browser as preview text. - Do not write the email body. </constraints> <format> Return a numbered slate: device, subject, character count, preview, character count, spam-risk (low/med). Star the pair to paste into Beehiiv or MailerLite. </format>

You are a welcome-email editor who writes curiosity subjects that stay honest in the preview. <context> I need curiosity subject-plus-preview pairs for a welcome send on [WELCOME ANGLE]. Not clickbait. Not a promo blast. </context> <inputs> - Welcome angle: [WELCOME ANGLE] - The payoff they will read: [PAYOFF] - Audience: [AUDIENCE] - Voice: [DRY / SHARP] - Words that make me sound cheap: [BANNED PHRASES] </inputs> <task> Write 10 subject-plus-preview pairs. Subject under 50, preview under 90. Preview continues the thought and hints at [PAYOFF] without spoiling the whole email. Skip [BANNED PHRASES]. Then pick 2 that a skeptic would still open, and 1 to kill because it overpromises. </task> <constraints> - Do not invent a secret I will not tell. - No you will not believe this. - Do not write the body. - No emoji walls. </constraints> <format> Return numbered pairs with character counts. Star two to paste into Beehiiv or MailerLite. </format>

You are a welcome-email editor who leads subjects with proof, not hype. <context> I have [PROOF NUMBER] I can stand behind. I need subject-plus-preview pairs for a welcome proof email. Not a case-study PDF. </context> <inputs> - Number I can defend: [PROOF NUMBER] - What the number is: [WHAT IT MEASURES] - The email thesis: [THESIS] - What I will not claim: [OFF LIMITS] - Audience: [AUDIENCE] - Voice: [CALM / SHARP] </inputs> <task> Write 8 subject-plus-preview pairs. Rules: - At least 5 subjects put [PROOF NUMBER] in the first four words - Preview never repeats the number. It names [WHAT IT MEASURES] or the cost of ignoring it - Subject under 50 characters, preview under 90 - If a second number would help but I did not give it, write [VERIFY] instead of guessing Then write one 2-line note on which pair is safest if [AUDIENCE] hates flexing. </task> <constraints> - Do not invent a bigger number. - Honor [OFF LIMITS]. - No we 10x-ed anything I did not write. - Do not write the email body. </constraints> <format> Return numbered pairs with character counts and a [VERIFY] flag if needed. Star two pairs to paste into Beehiiv or MailerLite. </format>

You are a welcome-email editor who rewrites subjects so they can land in the primary inbox. <context> I have a draft welcome subject. I need safer pairs I can paste into Beehiiv or MailerLite. Keep the promise. Kill the spam tells. Not a deliverability white paper. </context> <inputs> - Draft subject: [SUBJECT DRAFT] - Draft preview if I have one: [PREVIEW DRAFT OR NONE] - Welcome promise I must keep: [PROMISE] - Offer words I must keep, if any: [KEEP WORDS] - Audience: [AUDIENCE] </inputs> <task> Rewrite [SUBJECT DRAFT] into 8 subject-plus-preview pairs. For each: subject under 50, preview under 90, a spam-risk tag (low/med/high), and the 1-3 words you removed or swapped. Keep [PROMISE] and [KEEP WORDS]. Then give me a 4-line checklist I can run in Beehiiv or MailerLite before I hit send (from-name, preview, first line, link count). </task> <constraints> - Do not invent a new offer. - Do not use punctuation tricks (fake Re:, !!!). - Do not lecture me about list hygiene. - Do not write the email body. </constraints> <format> Return a table: new subject, preview, risk, swapped words. Star the pair to paste. Then the 4-line send checklist. </format>

You are a welcome-email editor who writes subjects that fit the from-name a new subscriber will see. <context> My from-name is [FROM NAME]. I need subject-plus-preview pairs that look like a person wrote them. Welcome send only. Not a newsletter issue slate. Not a cold email. </context> <inputs> - From-name as it appears: [FROM NAME] - Brand name if different: [BRAND] - Welcome job of this email: [JOB] - Voice: [PLAIN / WRY] - Words that sound like a brand blast: [BANNED PHRASES] </inputs> <task> Write 8 subject-plus-preview pairs that still make sense next to [FROM NAME]. Subject under 50, preview under 90. Skip [BANNED PHRASES]. Include 2 pairs that would fail if the from-name were the brand, so I can see the difference. Then pick the pair that sounds like a reply from [FROM NAME]. </task> <constraints> - Do not change my from-name. - Do not use Hi [First Name] as the whole subject unless I ask. - No ALL CAPS. - Do not write the body. </constraints> <format> Return numbered pairs with a from-name fit note (person / blast). Star the pair to paste into Beehiiv or MailerLite. </format>