Stop sending the same blast to everyone.
Members ignore generic digests. Key AI newsletters are composed per reader from activity, library saves, events, polls, and trending threads — so every send feels relevant.
marketing/newsletter. Production
routes will continue to serve the inline .astro file until
scripts/finalize-phase3.mjs --type=marketing deletes it.
Kai drafts a different version for every member — by role, interests, and activity. Same effort for operators; far higher relevance for readers.
Strong open rates when every line maps to what someone is working on right now.
Members ignore generic digests. Key AI newsletters are composed per reader from activity, library saves, events, polls, and trending threads — so every send feels relevant.
The VP and the intern should not get the same picks. Static templates cap engagement and train members to skim.
Curating manually does not scale. Merge fields are not personalization — they are mail-merge theater.
Job title alone misses what someone cares about this quarter. Newsletters need live behavior, not CRM snapshots.
Reads, votes, questions, attendance, and intros feed a signal graph so the digest matches what someone is doing this quarter.
Pair with Connectors for delivery where people already work. Included with Key AI communities.