Current Subscriber

Current Subscriber (Free) Email

This skill produces emails for the free Every subscriber — the largest segment, the people who get the daily Chain of Thought editorial send, the 9-part onboarding sequence, product launch announcements, and content promotions. The reader is curious but not yet paying. The goal is rarely to convert in any single email; it's to compound trust through editorial consistency until paid feels obvious.

When to invoke

• When writing editorial newsletter sends (Chain of Thought, Vibe Check, Mini-Vibe Check)
• When building or editing the 9-part onboarding drip sequence
• When drafting product launch announcements to the free list
• When writing content promotions or free-tier camp announcements
• When the brief mentions "newsletter," "free list," "the send," "Vibe Check," "Mini-Vibe Check," "Chain of Thought," "weekly send," "onboarding email," "drip," "welcome sequence," or "product launch email"
• When the audience is any send to subscribers who have not yet upgraded to paid (main hello@every.to list)

Audience model

The free subscriber is intelligent, sophisticated, and skeptical. They read Stratechery, Platformer, Lenny's, Not Boring. They've signed up for dozens of newsletters and stay subscribed to ten. They smell hype before they open. They like being treated as the analyst in the room, not the lead.

Write to that person. Not to "marketers." Not to "AI enthusiasts." To someone who already knows the basics and wants the synthesis.

Voice — house rules

Direct and declarative. State the thing, then qualify. "OpenAI's new model is a top-end senior engineer — and easy to talk to." Never bury the lede in a windup paragraph.

Smart, not clever. Every's voice trusts the reader's intelligence. No "buckle up." No "let me tell you a story." No "here's the thing." If a sentence could open a LinkedIn post, delete it.

First-person plural for the company, second-person for the invitation. "We built Cora." "You joined Every at the right time." Mix is intentional — it positions Every as a collective intellect addressing an individual reader.

No hype words. Banned: amazing, incredible, game-changing, revolutionary, mind-blowing, unprecedented, world-class, cutting-edge. If the thing is genuinely new, the writing should make that obvious without the adjective doing the work.

Active over passive. "Cora drafts replies in your own voice" beats "Replies are drafted by Cora in your voice."

Specificity > superlatives. "14,000+ stars on GitHub" beats "wildly popular." "Save an average of 4.3 hours per week" beats "save tons of time." Every uses concrete numbers wherever they exist.

No em-dash overload. One per email maximum, ideally zero. Reach for a period or a comma first.

No "it's not just X, it's Y" construction. Never. This is the tell of bad AI prose. If you find yourself reaching for it, rewrite the sentence to make the point directly.

Structural anatomy

Subject line

Two house formulas, never anything else.

Formula A: The declarative concept. A 2-5 word phrase that is the thesis of the piece. The subject is the takeaway, not the tease.

• "Living Software"
• "The Folder Is the Agent"
• "The Missing Layer in AI Adoption"
• "You're the Manager Now"
• "Model Wars"
• "We Need to Talk About AI Autopilot"

Formula B: Series tag + payoff. Recurring branded prefixes that build pattern recognition. The colon is a signal: "this is a piece in our [series] format."

• "Vibe Check: Opus 4.7 Stopped Reading Between the Lines"
• "Vibe Check: GPT-5.5 Has It All"
• "Mini-Vibe Check: Claude Design Isn't for Designers — Yet"
• "Introducing Monologue Notes: Record Every Meeting, Call, and Voice Memo"

Length target: 3-7 words for Formula A, 6-11 for Formula B (including prefix).

Banned: Question-mark hooks. Curiosity gaps ("You won't believe what we found"). All-caps. Numbers gimmicks ("7 ways to..."). Emojis in subject (✨ allowed once on celebratory product emails like Sparkle's "You made it Sparkle ✨", never elsewhere).

Preheader

Two house patterns:

"Plus: [secondary content stack]" — for newsletter sends that bundle a primary piece with related links. Reads as: "this is the meal, here are the sides."

• "Plus: Trust batteries, and how many agents we'll have in the future"
• "Plus: Vercel and Lovable's security woes, and how to make your agent your watchdog"
• "Plus: How Every runs on four agents — and what happens when everyone gets one"

Single-sentence elaboration — a fragment that completes or extends the subject. Reads as: "here's the one-line version."

• "Anthropic's latest Opus is more precise, more literal, and the best coding model we've tested on well-specified tasks — but it won't fill in the gaps for you anymore"
• "AI has made software disorienting. It doesn't have to be."
• "I'm running 44 AI agents across multiple projects. Each one is just a model pointed at a folder."

Length: 8-25 words. Never repeat the subject.

Greeting

• Editorial newsletter (Chain of Thought / Vibe Check): No greeting. Open straight into the lede paragraph. The masthead does the orientation work.
• Onboarding sequence: "Hi Douglas," (or "Hey Douglas," for the welcome email — slightly warmer for first contact).
• Product launch / drip nurture: "Hi Douglas,"
• Camp announcement: "Hi Douglas,"

Comma after the name. Never "Dear." Never "Hello there." Never "What's up." Never an emoji wave.

Body

Three sub-modes, three different structures.

Mode 1: Editorial newsletter (Chain of Thought, Vibe Check, etc.)

The email is a shell around an article. The reader's job is to click through. The body's job is to make the click feel inevitable.

• Open with the thesis sentence. Same one as the preheader, often.
• One paragraph of stake-setting (why this matters, what's new, what changed).
• Pull-quote or single sharpest line from the underlying piece.
• "Read on" link.
• Then "Plus, this week:" with 3-5 bulleted secondary links (other articles, podcast episodes, tools, etc.).
• Sign-off.

Total length: 100-180 words around the links. Tight. The editorial work happens at every.to, not in the inbox.

Mode 2: Onboarding drip (X/9 sequence)

Every numbers their welcome series — 1/9, 2/9, etc. — explicitly in the subject. This signals progression and sets expectations. Each email in the sequence does one job:

• 1/9: Welcome + paradigm primer + "here's how to get the most out of your subscription" with structured Step 1 / Step 2 / Step 3 sections.
• 2/9: Editorial guide deepening the paradigm.
• 3/9: Podcast intro (different content modality).
• 4/9 through 7/9: Each Every product, one per email (Monologue, Cora, Sparkle, Spiral).
• 8/9 and 9/9: Reserved for tier upgrade asks and "what's next."

Each email follows the same skeleton:

1. Greeting ("Hi Douglas,")
2. One-sentence hook that names the problem the recipient already feels ("We all dread email." / "We know how overwhelming it can be when your Mac starts to feel like a digital junk drawer.")
3. Intro the thing being introduced (product, guide, podcast).
4. 3-5 bullet points of concrete features or behaviors. Always with verbs at the start. Never marketing-speak.
5. CTA in the format --→Action verb.
6. One closing line of warmth or framing.
7. Sign-off — almost always "—The Every team" for sequence emails.

Length: 200-300 words.

Mode 3: Product launch / standalone announcement

Bigger swing than a drip email. The reader needs to understand what this is, why it exists, and what to do.

• Greeting + one-line product positioning.
• One short paragraph on origin or context (why we built this).
• Bulleted feature list (3-5 items, scannable).
• Optional social proof (one credible-name quote).
• CTA.
• Optional second CTA for upgrade-to-paid if the product has a paid tier.
• Sign-off.

Length: 250-400 words.

CTAs

Format: --→[Action verb phrase] followed on its own line by the link or button. Examples from Every's actual sends:

• --→Upgrade to paid
• --→Try Spiral
• --→Start your free trial
• --→RSVP for Compound Engineering Camp
• --→Reserve your spot

Action verb. Never "Click here." Never "Learn more." Never "Find out." The CTA names the action the reader is taking, not the act of clicking.

Maximum two CTAs per email. If there are two, the second is for a different action (e.g., primary = try the free product, secondary = upgrade to paid for full access).

Sign-off

Three options based on email type:

• "—The Every team" — default for newsletters, drip sequence emails, most marketing.
• "—Dan Shipper and the Every team" — when the editorial point of view is doing the work, or when launching something founder-led.
• Named individual — for onboarding moments where accountability matters. Format: full name, role, optional reply-CTA. Example: "—Mike Taylor, Head of tech consulting at Every" or "Hope to see you there, Naveen & team Monologue."

P.S.

Optional, used sparingly. Best for behavioral nudges the body shouldn't carry, not for sales. Real Every example:

P.S. Mark this email as important so you don't miss the camp invites.

Never use P.S. for "Don't forget!" or "Hurry, only 24 hours left!" The P.S. is for utility, not pressure.

Length budget

If an email runs longer than the upper bound, it's almost always because it's saying the same thing twice. Cut.

Worked example: Onboarding email 5/9 (Cora)

Subject: 5/9: Spend less time in your email—join Cora Preheader: [first line of body]

Hi Douglas,

We all dread email. It's an endless to-do list written by everyone else, all at once. That's why we built Cora. It's the most human way to manage your email, turning your inbox into a story.

Here's how Cora works:

1. See only the messages that truly need your reply. Everything else is auto-archived and summarized in two concise daily briefs.
2. Get replies drafted in your own voice. Cora writes context-aware responses you can send with one tweak — or none at all.
3. Tell Cora Assistant exactly how to handle the rest:
   • Create custom categories ("Make a folder called Investment Ops and file all stock recommendations there").
   • Set forever rules ("Always keep emails from @every.to in my inbox").
   • Or teach it specialized replies ("When a cold email asks to be on my podcast, thank them and send this form").

Join the cofounder of Instagram and CPO of Anthropic Mike Krieger in freeing yourself from email and reclaim 1–2 hours every day — and a calmer mind.

--→Start your free trial

—The Every team

Why this works:

• Hook is a universal complaint stated as fact ("We all dread email") — no preamble.
• Product positioning is one line ("the most human way to manage your email").
• Features are written as behaviors the reader will perform, not abstract capabilities.
• Includes a concrete time savings claim ("1–2 hours every day") and one piece of social proof (Mike Krieger, named).
• Single CTA. Sign-off is "The Every team."
• 175 words.

Worked example: Free-tier course urgency push

Subject: Claude Code for Absolute Beginners: 12 hours left to register—20% off for teams

Hi Douglas,

Registration for Claude Code for Absolute Beginners closes tonight.

People who take this course almost always come back wishing they'd brought a colleague. So for the next 12 hours, we're making that easier: five seats for $5,000 instead of $6,250. Use this link to sign up. If you've been thinking about bringing your colleagues, this is a good moment to do it.

The course runs Tuesday, April 14, 10 a.m.–5 p.m. ET on Zoom. It's led by me, Mike Taylor (Every's head of tech consulting), with Dan Shipper as a guest instructor. In one day, you go from never having opened the terminal to building something real you can use at work — and leaving with a workflow you can repeat on your own. Read on for more details.

This is for true beginners. If you've been curious about Claude Code and haven't known where to start, April 14 is your day.

--→Reserve your spot

Hope to see you there, Mike Taylor Head of tech consulting at Every

Why this works:

• Urgency is real and stated, not manufactured. "Closes tonight" is a fact, not a hype.
• The discount has a reason behind it (bring a colleague), not a fake "for you specifically" pretense.
• Signed by Mike personally. Trust transfer for the urgency moment.
• Concrete details: time, date, instructor names, what the reader will leave with.
• 195 words.

Anti-patterns — never do these

1. The hype open. "AI is changing everything." "The future of work is here." Cut and start with the actual point.
2. The empathy windup. "We know how busy you are..." "In today's fast-paced world..." Delete.
3. The fake exclusivity. "Only for our most dedicated readers." "Just for VIPs like you." Every doesn't talk this way.
4. Stacked CTAs. Three or more buttons in a single email. The reader picks none.
5. Emoji clutter. ✨🚀💡🎉. One emoji max, only when it carries genuine signal (the Sparkle ✨ is the product's mark; nothing else qualifies).
6. The faux-personal. "Hey friend!" "Hi there [first_name]!" — if personalization isn't real, drop it.
7. The "as discussed." Implying a relationship that doesn't exist. The reader knows you didn't discuss anything.
8. Reverse-tease subject lines. "You're not going to believe..." Every never does this.
9. The em-dash sandwich. "Cora — the AI-native email assistant — turns your inbox — finally — into a story." One em-dash maximum per email.
10. Marketing throat-clearing in the P.S. "P.S. Don't miss this!" The P.S. is for utility, not anxiety.

Dependencies

• foundation/marketing-os
• brand-voice/{relevant brand} (loaded dynamically)
• positioning/{relevant brand} (loaded dynamically)
• craft/copywriting
• craft/editing

Quick checklist before sending to review

• Subject is a thesis or a series tag, not a tease
• Preheader extends, not repeats, the subject
• First sentence states the actual thing
• No hype words (amazing/revolutionary/game-changing/etc.)
• Zero or one em-dash
• Zero "it's not just X, it's Y" constructions
• CTA is an action verb, not "click here"
• Sign-off matches email type (team / Dan / named individual)
• Length fits the budget for this mode
• No more than two CTAs total