06-reference

backfill discovery every 2026 04 12

Sat Apr 11 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·discovery-note ·source: hello@every.to
newslettereverybackfillai-ops

Every Newsletter — Backfill Discovery

Summary

Content Mix

The 109 messages break down into roughly three categories:

  1. Editorial articles (~60%): Long-form essays on AI strategy, coding with AI, management, product design
  2. Promotional/event emails (~25%): Camp registrations, demo days, product launches, discount codes
  3. Onboarding sequence (~10%): 10-part (1/9 through 10/9) welcome drip sequence

Promotional and onboarding emails are lower-value for vault filing — the processing tasks should triage these out during backfill.

Author Observations

Every is a multi-author publication. The From field is always generic (“Every hello@every.to”), so author identification requires reading each message body. Authors confirmed from sampled messages:

AuthorRolePublications / Columns
Dan ShipperCEO, cofounder”Chain of Thought”, “On Every” — company strategy, AI ops, product announcements
Katie ParrottStaff writer, AI editorial lead”Working Overtime” — AI writing process, editorial craft
Eleanor WarnockWriter/journalistStandalone articles — careers, knowledge work
Tina HeExternal writer (Pace Capital)Guest articles — AI business strategy, boring businesses
Alex DuffyExternal writerGuest articles — AI data markets, training data
Evan ArmstrongWriter (known Every contributor)Articles on AI business models (not yet confirmed in sample but historically present)
Every teamCollectiveVibe Check reviews, model comparisons, event announcements

Key gotcha: Author bylines are embedded in HTML <p class="byline">by <a>Author Name</a></p> or in plain-text footers. The processing skill will need to parse this from each message body — cannot rely on email headers alone.

Additional staff mentioned across messages

Vault files already present

Processing notes