newsletter-subject-lines

name	newsletter-subject-lines
description	Generates 10 email subject line variants with psychological trigger analysis for each option. Use when the user needs subject lines for newsletters, email campaigns, or subscriber emails. Analyzes each option for curiosity gap, benefit clarity, and open-rate optimization. Do NOT use for full newsletter writing (use `newsletter-writing`), cold email subject lines (use `cold-email-outreach`), or professional email subjects (use `professional-email`).
license	Apache-2.0
metadata	{"author":"foundry-skills","version":"1.0.0","tags":"newsletter email marketing-copy","category":"writing","subcategory":"content-marketing","depends":"","disclaimer":"none","difficulty":"intermediate"}

Newsletter Subject Lines

When to Use

Use this skill when the user explicitly needs subject line variants for a newsletter, subscriber email, or email campaign sent to an existing opted-in audience. Specific trigger scenarios include:

• The user is preparing a newsletter send and wants to maximize open rates through tested psychological framing before choosing a final subject line
• The user wants 10 variants with analysis so they can select or A/B test options -- not just brainstorm one or two ideas
• The user has an existing newsletter audience and wants subject lines calibrated to that audience's behavior, segment, or persona (e.g., "my subscribers are senior HR managers at companies over 500 people")
• The user is setting up an A/B split test in their email platform and needs two clearly differentiated options that test a single variable (trigger type, length, or framing)
• The user has described the email content clearly enough to write grounded subject lines that will not misrepresent the email body
• The user sends promotional newsletters to an engaged list (product updates, curated roundups, editorial issues, event announcements, course launches, paid content previews)
• The user is auditing past subject line performance and wants a fresh set of variants using different trigger types to break a plateau in open rates

Do NOT use this skill when:

• The user wants a complete newsletter written from scratch -- use newsletter-writing instead
• The user wants subject lines for cold outreach to people who have not opted in -- use cold-email-outreach instead, because cold email psychology, deliverability concerns, and legal compliance (CAN-SPAM, GDPR consent basis) differ fundamentally
• The user wants subject lines for a professional internal email (a memo, meeting request, or status update) -- use professional-email instead
• The user wants subject lines for a transactional email (order confirmation, password reset, account notice) -- these require clarity and reliability, not psychological triggers; use transactional-email instead
• The user wants a social media caption, ad headline, or landing page headline -- the psychological mechanics differ from inbox behavior; use the relevant social-caption or ad-copy skill instead
• The user has not described the email content at all and refuses to provide any details -- do not generate generic subject lines disconnected from real content, as this produces unusable output and trains the user to treat subject lines as decoration rather than a promise

---

Process

Step 1: Gather the Four Required Inputs

Before generating anything, collect the following. If the user has not provided all four, ask for them explicitly. Do not assume.

• Email content summary: What is this issue actually about? Ask for the main insight, announcement, or value delivered. A one-paragraph description is ideal. Subject lines that do not match the body content damage trust and spike unsubscribes.
• Audience segment: Who receives this email? Capture role, industry, experience level, and relationship to the sender (subscribers who signed up for a free course versus paying members respond differently). Ask if the list is segmented or a full broadcast.
• Primary goal: Is the goal to maximize opens only (brand awareness, newsletter habit), or does the open need to lead to a specific click (product, article, event), or does the user want a direct reply (community engagement, survey)? The goal changes which triggers to prioritize.
• Brand voice: Ask the user to pick a primary register: authoritative, conversational, editorial, data-driven, warm/personal, or playful. If they are unsure, ask for a subject line from a previous issue they liked, then infer the voice.
• Deliverability context (optional but valuable): Ask if they have seen any recent spam folder complaints or know their current open rate. Subject lines that contain certain constructions can suppress deliverability even if individually they seem fine.

Step 2: Audit the Competitive Inbox Context

Before writing, reason through what the reader's inbox looks like at send time. This is the framing discipline that separates expert subject line writing from generic copywriting.

• Most newsletter subscribers receive 50-150 emails per day across personal and work inboxes. The subject line competes in a 2-3 second attention window in a scrolling list.
• Consider the sender name -- the "from" field does approximately 40% of the work in prompting an open for a known sender. The subject line does 60% for the remainder. If the user's sender name is strong and recognized, shorter and more enigmatic subject lines can work. If the sender is less established, the subject line must carry more informational weight.
• Identify the category the email belongs to in the reader's mental model: "useful education," "entertainment," "curated links," "product news," or "community." Each category triggers different reading contracts and different optimal trigger types. Curated-link newsletters benefit from specificity; editorial newsletters benefit from personality and voice.
• Consider send day and time if the user mentions them. Friday afternoon sends compete with end-of-week inbox triage. Tuesday morning sends land at peak B2B email engagement (Tuesdays 8-10am local time consistently outperform in deliverability studies). This context shapes urgency framing.

Step 3: Select the Trigger Mix for This Specific Email

Not all 10 trigger types apply equally to every email. Before generating, reason through which triggers are genuine and supported by the content -- then allocate the 10 variants accordingly.

The core trigger inventory and their mechanics:

• Curiosity gap: Works by withholding specific information the subject line implies exists. The classic Loewenstein formulation: open the gap, do not close it in the subject line. Best when the email delivers a specific insight. Fails when the email is vague or the gap feels manufactured. Example construction: "The [X] most [audience] never talk about."
• Specific benefit / promised outcome: States precisely what the reader gets. Works best in B2B, with experienced audiences who are skeptical of hype, and in educational newsletters. Specificity is the credibility signal -- "save 4 hours a week" beats "save time." Best when quantification is honest. Fails when the benefit sounds generic.
• Social proof / herd framing: References a percentage, a group, or an implied consensus. "What 3,000 designers told us" or "The framework 82% of marketers overlook." Powerful when grounded in real data the email will cite. Risky when the number is invented -- readers who notice will unsubscribe and report.
• Contrarian / assumption challenge: Opens by violating the reader's existing belief. "Cold calls are dead -- except for this." Works by creating cognitive dissonance that demands resolution. Strong for thought-leadership newsletters, weak for warm community newsletters where readers expect alignment not challenge.
• Urgency / scarcity: Time-pressure framing. Use ONLY when genuine (real deadline, real capacity limit, real expiring offer). False urgency is one of the fastest ways to erode list trust and trigger spam filters. "Last chance" and "Today only" are heavily filtered.
• Story / narrative hook: Opens a scene or a personal moment. "I almost quit my newsletter last March." Strongest for personal brand newsletters with high sender recognition. Requires the email to deliver the complete story -- open loops that do not close destroy trust.
• Direct / descriptive: Tells the reader exactly what is inside. "Your October reading list: 7 articles on supply chain." Lowest risk, lowest potential ceiling. Best for digest-format newsletters where reliability is the brand promise. Use one of the 10 slots for this anchor option.
• Personalization + relevance signal: Uses audience role, current event, or known context to signal "this was written for you." "[Role] are rethinking [topic] this quarter." Works when specific and accurate; feels manipulative when generic.
• Question: Poses a genuine question the reader will have an opinion about or want answered. Best when the question is specific, not rhetorical. "Is your content strategy built on the wrong metric?" beats "Are you doing content marketing right?"
• Self-interest + specificity hybrid: Combines a specific benefit with a self-referential hook. The reader maps themselves into the outcome. "How I doubled my email open rate in 6 weeks (data inside)." Strong in B2C, creator, and solopreneur audiences.

Allocate the 10 slots based on what the email content genuinely supports. A data-heavy issue supports social proof and specific benefit variants. A personal story issue supports narrative and curiosity gap variants. Do not force a trigger the content cannot deliver.

Step 4: Write All 10 Subject Line Variants

Apply the following craft standards to every line written:

Length and display:

• Target 35-50 characters as the mobile-safe primary range. Gmail on iOS shows 37-45 characters before cutting on the lock screen; Gmail on Android shows 30-40 characters in the notification tray; Apple Mail on iPhone shows 40-50 characters in the inbox list. The first 40 characters must carry the full hook.
• Lines 51-60 characters can work on desktop-first audiences but require the key hook in the first 40 characters. Label these "desktop-optimized."
• Lines over 60 characters should be used sparingly (one or two variants maximum) and only when the truncation creates a natural cliffhanger, not an awkward cut.
• Always count characters manually. Spaces count. Punctuation counts. Emoji count as 2 characters in most email client rendering.

Word-level craft:

• Front-load the highest-information or highest-tension word. Compare: "The most overlooked SEO metric" versus "Overlooked: the SEO metric costing you traffic." The second version surfaces the tension word immediately.
• Use second-person "you/your" in at least 3 of the 10 variants -- it increases perceived personal relevance.
• Avoid the word "newsletter" in the subject line -- it signals "low urgency bulk email" to the reader's pattern-matching brain.
• Avoid starting with "I" for the first word unless the sender name is a recognized personal brand -- the reader sees the sender name first, so starting with "I" is redundant.
• Avoid question marks and exclamation marks in the same subject line -- they fight each other.
• Numbers should be specific and odd when possible -- "7 frameworks" feels more credible and less rounded than "10 tips." Exception: when the content is literally a top-10 list.

Spam filter craft:

• Avoid these specific constructions regardless of context: "FREE," "WIN," "GUARANTEED," "RISK-FREE," "ACT NOW," "LIMITED TIME OFFER," "CLICK HERE," "EARN MONEY," "MAKE MONEY," "#1," "100%," and excessive punctuation (multiple exclamation points, multiple question marks, ellipsis overuse).
• Avoid ALL CAPS on individual words within a subject line, not just the full subject. "This WORKS" reads as shouting and triggers Bayesian spam classifiers trained on promotional email.
• Avoid Re: and Fwd: prefixes intended to simulate a reply thread -- this tactic was effective in 2016 and is now heavily penalized by major inbox providers.
• Do not use brackets to simulate personalization tokens like [FIRSTNAME] in the actual subject line -- these appear broken when personalization fails to render.

Step 5: Analyze Each Variant

For every one of the 10 options, provide a structured micro-analysis covering:

• Trigger type used (from the named inventory in Step 3)
• Character count (exact)
• Mobile preview assessment -- what appears in the first 40 characters, and whether the truncation point is strategic or awkward
• Single primary strength -- specific to this subject line, not generic ("creates curiosity" is too generic; "implies the reader has been using the wrong benchmark, which creates immediate self-audit reflex in analytically-oriented readers" is specific)
• Single primary risk -- what could go wrong, including audience mismatch, deliverability flag, or expectation mismatch with body content

Step 6: Generate Preview Text (Preheader) for the Top 3

The preheader is the text email clients display after the subject line in inbox view. It is not part of the email body the reader sees after opening -- it is a second subject line displayed at 60-70% visual prominence beside the subject line.

Rules for preheader text:

• Length: 40-90 characters. Under 40 and the email client will pull body text (usually unformatted and unhelpful). Over 90 and it truncates before value is delivered.
• Never repeat the subject line -- the preheader extends the subject line's argument or adds a different angle. Repetition wastes the slot.
• The subject line + preheader is a two-part pitch. Structure them as: subject = the hook, preheader = the supporting evidence, specific detail, or the closing of a loop the subject opens.
• Preheader can use sentence case and feel more conversational than the subject line.
• Avoid starting preheader with "Hi [name]" or "In this issue" -- these waste the visible characters on structural filler.

For each of the top 3 options, write:

• The preheader text (labeled with character count)
• One sentence explaining how it pairs with the subject line and what gap it fills

Step 7: Deliver the Recommendation with Testing Logic

Provide a clear recommendation hierarchy:

• Primary recommendation: State the single best option for this audience and goal with a specific reason tied to the audience segment and email content -- not a generic "it performs well."
• A/B test pairing: Select a second option that tests a fundamentally different trigger type, not a trivially different phrasing of the same trigger. The test should be designed to answer a specific question about the audience's response patterns (e.g., "does this list respond better to benefit promises or contrarian challenges?").
• Holdback option: Identify one or two variants that are strong but should be saved for future sends or re-engagement campaigns where a different emotional register may outperform.
• List size guidance: If the user's list is under 1,000 subscribers, note that A/B testing will not reach statistical significance on a single send. Recommend running the same test over three sends and aggregating results before drawing conclusions.

---

Output Format

## Subject Line Options for: [Email Topic in 5 Words or Fewer]

**Audience:** [Segment description]
**Goal:** [Open + read / Open + click / Open + reply]
**Brand voice:** [Voice register]

---

### Option Table

| # | Subject Line | Chars | Trigger Type | Mobile (first 40 chars) |
|---|-------------|-------|--------------|--------------------------|
| 1 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |
| 2 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |
| 3 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |
| 4 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |
| 5 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |
| 6 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |
| 7 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |
| 8 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |
| 9 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |
| 10 | [subject line text] | [N] | [trigger] | [first 40 chars shown] |

---

### Individual Analysis

**Option 1 -- "[subject line]"**
- Trigger: [trigger type]
- Character count: [N] -- [mobile-safe / desktop-optimized / note any truncation]
- Primary strength: [specific, audience-grounded explanation of why this works]
- Primary risk: [specific downside -- deliverability, trust, audience mismatch, or expectation gap]

[Repeat structure for options 2 through 10]

---

### Recommendation

**Primary pick:** Option [N] -- "[subject line]"
[2-3 sentences explaining the specific match between this option, the audience segment, and the email goal. Reference the trigger type and why it fits this audience's reading behavior.]

**A/B test against:** Option [N] -- "[subject line]"
[1-2 sentences explaining what question the A/B test will answer about this audience's response patterns. State the variable being isolated.]

**Holdback for future use:** Option [N] [and optionally Option N]
[1 sentence on when these would outperform the primary pick -- e.g., re-engagement campaign, product launch, list with different segment profile]

---

### Preview Text (Preheader) for Top 3

| # | Subject Line | Preview Text | Preheader Chars | Pairing Logic |
|---|-------------|-------------|-----------------|---------------|
| [N] | [subject line] | [preheader text] | [N] | [one sentence on how subject + preheader work together] |
| [N] | [subject line] | [preheader text] | [N] | [one sentence on how subject + preheader work together] |
| [N] | [subject line] | [preheader text] | [N] | [one sentence on how subject + preheader work together] |

---

Rules

1. Never write a subject line that the email body cannot deliver. If the subject line implies "one specific metric," the email must name that metric and explain it. A subject line that overpromises relative to the content is not just clickbait -- it actively trains subscribers to ignore future opens. Track unsubscribe rates after sends with provocative subject lines to detect this damage.

2. Never use ALL CAPS on any individual word within the subject line. Even a single ALL-CAPS word (e.g., "THIS WORKS") flags Bayesian spam filters trained on promotional email patterns. The only exception is a recognized acronym that is standard in the audience's industry (e.g., "B2B," "API," "SEO," "CFO").

3. Never use more than one exclamation mark across all 10 options. Generate it only if the email is a genuine celebration or milestone. Never use it in the primary recommendation or the A/B test pick.

4. Never use urgency or scarcity framing unless the user confirms it is real. If the user says "write something urgent" but has no actual deadline, explain that false urgency is one of the three fastest ways to increase spam complaints and unsubscribes (alongside misleading subject lines and excessive sending frequency). Offer contrarian or benefit-driven framing instead.

5. Always front-load the hook within the first 40 characters. Every subject line should be evaluated for what appears in the first 40 characters because that is what renders in the worst-case mobile display scenario (notification tray). If the hook is in characters 41-55, the subject line needs restructuring.

6. Never start with the newsletter's name or issue number as the first words. "The Weekly Dispatch: What no one tells you about pricing" loses the 11 characters of "The Weekly Dispatch:" to branding that is already handled by the sender name field. Exception: when the brand name IS the hook (e.g., a sender like "MKBHD" whose name is the trust signal).

7. Always generate exactly 10 variants using at least 5 different trigger types from the named inventory. Do not produce 10 variations on a single trigger type even if the user asks for "10 curiosity-gap options" -- explain that varied trigger testing produces more useful audience data and offer to weight the set heavily toward curiosity gap while still including contrast options.

8. Always provide character count for every option, counted exactly. Do not estimate. Count spaces and punctuation. If using a personalization token like {{first_name}}, note that this adds 4-9 characters depending on average subscriber name length in the user's audience (use 6 as the default estimate for first names in English-language lists).

9. Always write preheader text that adds information the subject line does not contain. If the subject line is the hook, the preheader is the evidence or the extension. "Your Q3 content strategy is missing one thing" + "Most teams track outputs. The top 10% track one leading indicator." is a complete two-part pitch. "Your Q3 content strategy is missing one thing" + "Don't miss this issue!" is a wasted slot.

10. Never recommend a subject line that contains the word "newsletter." The word activates the reader's low-priority mental category for bulk email. Even when the content is genuinely valuable, framing the communication as a newsletter in the subject line suppresses opens by signaling routine rather than relevance.

11. Apply different analysis to B2B versus B2C audiences before generating. B2B subscribers are reading for professional utility and career protection -- they respond to specificity, professional social proof, and ROI framing. B2C subscribers are reading for personal benefit, entertainment, or identity -- they respond to emotion, curiosity, story, and relatability. Mixed or unclear audiences should receive a variant set weighted toward specificity (safer across both modes).

12. When the user's list is under 1,000 active subscribers, explicitly note that A/B testing requires caution. A 50/50 split with 500 subscribers gives 250 per variant. To detect a 5 percentage point difference in open rate (e.g., 30% vs 35%) with 80% statistical power, a minimum of approximately 1,400 subscribers per variant is required. Below this threshold, results are noise. Recommend a single send with the strongest option and note when the list size supports valid testing.

---

Edge Cases

The user has no performance history and cannot describe past subject lines. When the user has no baseline data (new newsletter, new platform, or they simply never tracked it), default to a variant set weighted toward specific-benefit (3 options), curiosity-gap (3 options), and direct/descriptive (1 option) with lighter coverage of contrarian, social proof, and story. This distribution minimizes risk while still testing the highest-potential triggers. Instruct the user to tag each send in their ESP (email service provider) with the trigger type used and build a custom performance log over 10-15 sends before drawing conclusions.

The email is an announcement of a product, feature, or service launch. Launch emails are the highest-risk subject line scenario because they combine genuine excitement (which tempts hyperbolic writing) with high commercial intent (which triggers spam filters and reader skepticism). Reduce the commercial signal in the subject line -- "How we rebuilt our onboarding from scratch" performs better than "Introducing our new onboarding experience!" because it frames the announcement as a story rather than an ad. Generate more narrative and curiosity-gap variants for launch sends, and caution against urgency language unless a genuine early-bird offer exists.

The user wants emoji in subject lines. Limit to one emoji per subject line. Position emoji at the end of the line -- not the beginning, because leading emoji are associated with promotional bulk email and affect filtering in some enterprise mail environments. Note that emoji rendering varies significantly: Apple Mail renders full color emoji, Outlook on Windows renders emoji as monochrome glyphs or boxes depending on version, and Gmail renders most standard Unicode emoji correctly but with slight visual differences. Stick to high-compatibility emoji (checkmark ✓, arrow →, sparkle ✨, fire 🔥, lightbulb 💡) and avoid emoji that are commonly used by mass senders in promotional categories (e.g., 💰, 🎁, 🏆). Always count emoji as 2 characters toward the character budget.

The subject line must include a required element: a date, event name, issue number, or brand name. When the user has a non-negotiable element that must appear in the subject line, treat that element as a constraint and build the hook before it. "The talk that changed how I think about pricing -- Summit 2026" surfaces the hook ("talk that changed how I think about pricing") before the required element. "Summit 2026: a talk that changed how I think about pricing" buries the hook behind the least interesting information. Apply this front-loading rule to issue numbers, dates, and all required prefixes.

The newsletter is a re-engagement campaign to a cold or inactive segment. Inactive subscribers (no open in 90-180 days) require a fundamentally different approach than regular sends. Subject lines for re-engagement should directly acknowledge the lapse without shaming the reader, signal a fresh start or changed value, or ask a binary question that prompts a click-to-confirm response. Examples: "Still interested in [topic]?" / "We've changed a lot since you signed up" / "Should we remove you from our list?" (this last one, known as the "break-up email" subject line, typically achieves 10-15% re-engagement on cold lists). Do not use curiosity-gap or benefit-driven triggers on inactive segments -- these require enough trust to create the pull. Re-engagement is about rebuilding trust first.

The user writes in a language with different character-display norms or for a non-English audience. Non-Latin scripts (Arabic, Hebrew, Devanagari, CJK) display at a different character-to-pixel ratio. CJK characters (Chinese, Japanese, Korean) typically occupy double the pixel width of Latin characters in most email clients. A subject line of 20 CJK characters will display as the equivalent of approximately 40 Latin characters in terms of screen width. Apply a maximum of 20 CJK characters for mobile-safe display. For Arabic and Hebrew (right-to-left scripts), front-loading strategy reverses -- the hook should be front-loaded from the right.

The user asks to incorporate A/B testing variables beyond subject line text (e.g., from-name testing or send-time testing simultaneously). Advise the user not to test multiple variables simultaneously -- this is the most common A/B testing mistake in email marketing. If they test subject line AND from-name in the same experiment, they cannot attribute performance differences to either variable. Recommend a single-variable test protocol: fix the from-name and send time, test only the subject line. Once subject line performance patterns are established over 5-8 sends, the user can begin from-name or send-time testing as a separate experiment.

---

Example

User input: "I need subject lines for my weekly newsletter on indie software businesses. This issue covers how one bootstrapped SaaS founder raised her prices by 60% and lost almost no customers -- and the exact email script she used. My audience is independent software developers and small SaaS founders, mix of $0 and $10k MRR businesses. Tone is candid and smart, not cheerleader-y. I have about 4,200 subscribers."

---

Output:

Subject Line Options for: SaaS Pricing Case Study

Audience: Independent software developers and small SaaS founders, $0-$10k MRR range Goal: Open + read (editorial, case study format) Brand voice: Candid, smart, editorial -- not hype-driven

---

Option Table

#	Subject Line	Chars	Trigger Type	Mobile (first 40 chars)
1	She raised prices 60%. Almost no one left	42	Social proof + contrarian	"She raised prices 60%. Almost no"
2	The pricing email that made her $40k braver	45	Curiosity gap + specific	"The pricing email that made her $4"
3	Why your SaaS is underpriced (with proof)	42	Contrarian + evidence	"Why your SaaS is underpriced (with"
4	The exact email she used to raise prices 60%	46	Specific benefit + direct	"The exact email she used to raise"
5	Most founders charge less than they should	43	Social proof + contrarian	"Most founders charge less than they"
6	Raise prices. Lose almost no one. Here's how	46	Specific benefit + directive	"Raise prices. Lose almost no one."
7	She tested a 60% price increase. The results	46	Story + curiosity gap	"She tested a 60% price increase. T"
8	The pricing mistake 80% of indie founders make	48	Social proof + contrarian	"The pricing mistake 80% of indie fo"
9	I copied her pricing email. Open rate: 67%	44	Story + self-interest hybrid	"I copied her pricing email. Open ra"
10	Underpriced: a case study on charging more	44	Direct + framing word	"Underpriced: a case study on chargi"

---

Individual Analysis

Option 1 -- "She raised prices 60%. Almost no one left"

• Trigger: Social proof + contrarian
• Character count: 42 -- mobile-safe, full display on most clients
• Primary strength: The two-sentence structure creates a natural beat -- the first clause delivers a data point (60%), the second clause delivers the surprise that violates the expected outcome (attrition). The gap between expectation and result is what compels opening. Candid voice aligns with stated brand register.
• Primary risk: "Almost no one left" is imprecise -- readers who are analytically oriented may want a number ("3% churn") and may find the vague qualifier slightly hand-wavy. If the case study provides actual churn numbers, consider replacing with specifics.

Option 2 -- "The pricing email that made her $40k braver"

• Trigger: Curiosity gap + emotional hook
• Character count: 45 -- mobile-safe
• Primary strength: "$40k braver" is a compressed, unexpected phrase that fuses a financial outcome with a psychological state -- it creates genuine curiosity about what the phrase means, which can only be resolved by opening. Rewards the brand's smart, non-clichéd voice.
• Primary risk: Slightly opaque -- readers who skim fast may not parse the metaphor quickly enough to feel compelled. Works better for subscribers who already trust the newsletter's voice. May underperform with newer subscribers unfamiliar with the brand's tone.

Option 3 -- "Why your SaaS is underpriced (with proof)"

• Trigger: Contrarian + evidence signal
• Character count: 42 -- mobile-safe
• Primary strength: "Your SaaS" creates direct personal relevance. The parenthetical "(with proof)" addresses the skepticism the contrarian claim immediately generates -- it preemptively defends against "prove it." This is a sophisticated double-move that works well on a founder audience trained to question unsupported claims.
• Primary risk: Founders with confidence in their pricing model may read this as condescending. The contrarian trigger works on those who secretly suspect they are underpriced (a large portion of this audience) but alienates those who have done deliberate pricing research.

Option 4 -- "The exact email she used to raise prices 60%"

• Trigger: Specific benefit + direct (template promise)
• Character count: 46 -- mobile-safe
• Primary strength: "Exact" and the percentage together create a high-specificity promise. The word "exact" signals that this is not a theoretical framework but a concrete artifact the reader can copy or adapt. Template promises consistently outperform strategy promises in B2C and indie-business audiences.
• Primary risk: Sets a high delivery expectation -- the email must include the literal script, not a paraphrase. If the user is including the full email in the issue, this is the strongest alignment between subject line and content. If the script is excerpted or summarized, this subject line oversells.

Option 5 -- "Most founders charge less than they should"

• Trigger: Social proof + contrarian (group norm violation)
• Character count: 43 -- mobile-safe
• Primary strength: Frames underpricing as a systemic group behavior rather than a personal accusation, which lowers resistance compared to "you're underpriced." The reader thinks "yes, I've noticed that about other founders" and then silently asks "am I one of them?" -- which triggers self-audit and opens.
• Primary risk: Least specific option in the set. Contains no number, no story hook, and no artifact promise. Strong enough for a general editorial newsletter but undersells the concrete case study content inside.

Option 6 -- "Raise prices. Lose almost no one. Here's how"

• Trigger: Specific benefit + directive cadence
• Character count: 46 -- mobile-safe; the three-beat structure is readable at 40 characters ("Raise prices. Lose almost no one.")
• Primary strength: The three-clause staccato structure ("Raise. Lose. Here's how") creates a punchy rhythm that feels more like a peer talking than a newsletter subject line. The "Here's how" at the end is a classic action-bridge construction that guarantees the email has a method, not just a thesis.
• Primary risk: "Almost no one" appears twice across options 1 and 6 -- if using both in the same A/B test or showing them together, the repeated qualifier will be noticed. Choose one of the two options to use; retire the other.

Option 7 -- "She tested a 60% price increase. The results"

• Trigger: Story opener + curiosity gap (deferred resolution)
• Character count: 46 -- mobile-safe; truncates naturally after the first sentence on tightest mobile views
• Primary strength: "The results" as a sentence fragment creates a deliberate open loop -- the subject line starts a story and refuses to finish it, which is the purest curiosity-gap mechanic. The past tense "tested" implies real data, not speculation. Works well when the results are genuinely surprising (which in this case they are).
• Primary risk: The open loop could feel too transparent as a clickbait mechanism for sophisticated readers who have seen this construction hundreds of times. The audience of SaaS founders is likely more skeptical of open-loop tricks than a general consumer audience.

Option 8 -- "The pricing mistake 80% of indie founders make"

• Trigger: Social proof + contrarian (statistical framing)
• Character count: 48 -- mobile-safe
• Primary strength: The "80%" figure creates credibility and makes the mistake feel epidemic rather than niche. "Indie founders" as a specific identity label is a precision targeting signal -- readers who identify with that label feel immediately addressed. Loss-aversion framing (mistake) typically outperforms gain framing (opportunity) in professionally-oriented audiences.
• Primary risk: The 80% must be supported by something in the email -- if the case study does not reference group-level data, this reads as a fabricated statistic. Verify with the user that there is data to support the percentage before using this option. If there is no supporting data, retire this option.

Option 9 -- "I copied her pricing email. Open rate: 67%"

• Trigger: First-person story + self-interest (result reveal)
• Character count: 44 -- mobile-safe
• Primary strength: First-person frame creates the highest personal intimacy of all 10 options. The colon construction "I did X. Result: Y" is a proven copywriting pattern for results-oriented audiences. The "67% open rate" is a concrete outcome that makes the reader think "if that's the open rate on a pricing email, the pricing change must have worked." Chains curiosity across two levels.
• Primary risk: This line implies the newsletter author personally ran the script themselves -- if that is not true (i.e., this is purely a case study of someone else's experience), this line would be misleading. Only use if the sender actually tested the method. Also, "open rate" in the subject line may trigger spam classifiers on some ESPs -- test deliverability before committing to this option.

Option 10 -- "Underpriced: a case study on charging more"

• Trigger: Direct + framing word
• Character count: 44 -- mobile-safe
• Primary strength: The colon construction "Concept: what this issue is about" is a clean editorial framing device. "Underpriced" as the lead word is punchy and surprising. This option sets the clearest content expectations and will produce the most highly qualified opens -- readers who open this know exactly what they are getting.
• Primary risk: Lowest emotional trigger intensity of all 10 options. Will produce a lower open rate than the top options in aggregate but higher read-through and click rates because reader intent is fully aligned with content. Best suited for a list where quality of engagement matters more than raw open rate.

---

Recommendation

Primary pick: Option 4 -- "The exact email she used to raise prices 60%"

This audience of software founders and indie hackers is trained to value artifacts over advice -- they want the template, the script, the GitHub repo, not the principle. The word "exact" combined with a real percentage signals a concrete deliverable. This audience self-selects toward actionable, specific content, and this subject line is the clearest expression of what the email genuinely contains. At 46 characters it displays fully on mobile. Confirm with the user that the actual email script is included in the issue body, not summarized.

A/B test against: Option 1 -- "She raised prices 60%. Almost no one left"

This option tests a fundamentally different emotional mechanism: surprise at a counter-intuitive outcome versus promise of a concrete tool. The A/B test answers the question "does this audience respond more to artifact promises or to pattern interrupts?" With 4,200 subscribers, a 50/50 split gives 2,100 per variant -- sufficient to detect a 4-5 percentage point open rate difference with acceptable statistical confidence after accounting for a typical 30-40% open rate baseline in this niche.

Holdback for future use: Option 2 -- "The pricing email that made her $40k braver"

This line is the strongest fit for the brand's stated "candid and smart" voice but requires subscriber familiarity with that voice register to land correctly. Use it in an issue where the sender has recently had high engagement, or as the subject line for a best-of or anniversary issue when the brand relationship is at peak warmth.

---

Preview Text (Preheader) for Top 3

#	Subject Line	Preview Text	Preheader Chars	Pairing Logic
4	The exact email she used to raise prices 60%	She went from $49/mo to $79/mo. Churn barely moved.	51	Subject delivers the artifact promise; preheader delivers the specific numbers that make the promise credible without giving away the script itself
1	She raised prices 60%. Almost no one left	The email script, the churn data, and what she'd do differently	61	Subject delivers the surprising outcome; preheader reveals there are three deliverables inside (script, data, reflection), upgrading a curiosity open into an intent-driven open
3	Why your SaaS is underpriced (with proof)	One founder's 60% experiment -- and the exact message she sent	63	Subject makes the contrarian claim; preheader introduces the proof format (a specific case study) and hints at the artifact, resolving the "what kind of proof?" question without closing the curiosity loop