Write a newsletter issue

Learning objectives

Write a subject line that earns the open without clickbait
Draft a full issue in your voice in one sitting
Know which CF tool runs each step, and which two still live outside CF today

Step 1 — Subject line (Spark)

explain

The subject line is the whole game for open rate. Spark generates a batch of honest, specific subject lines — curiosity that the issue actually pays off, not bait. Pick one you'd open yourself.

Try this

Run Spark for 10 subject lines. Pick the one that isn't a lie.

Step 2 — Draft the issue (outside CF today)

explain

Honest gap: there is no CF tool that drafts a full newsletter issue in your voice yet. Press drafts book chapters and Push drafts social posts, but neither is built for an email issue's shape. Draft it yourself from the subject line and your notes — the opener, the one idea, the takeaway, the sign-off. We'll flag it here when that changes.

Try this

Draft the issue yourself from three bullet points and the subject line you picked.

Step 3 — One visual (Design)

explain

One good image lifts an issue. Design's Graphic mode builds a header graphic — bold type and shapes, or a photo you upload yourself (no AI photo generation live yet). Don't over-decorate — newsletters are mostly words.

Try this

Build one header image in Design for this issue.

Step 4 — Send it (outside CF today)

explain

Second honest gap: actually sending the email — list management, deliverability, the send infrastructure — lives outside CF today. There's no CF email-sending tool yet, so we don't pretend your list lives here. Send through your email platform; bring the performance back to inform the next one.

Try this

Schedule the send in your email platform. Note your open rate next issue.

Step 5 — Repurpose (Spark + Push)

explain

One issue is three posts. Spark pulls the sharpest line as a social hook; Push drafts the repurposed post and actually auto-posts it on schedule today to Telegram, Discord, LinkedIn, and Bluesky, so the writing works twice.

Try this

Let Spark pull one quotable line; have Push draft and schedule it as a post.

Two real gaps

recap

Spark writes the subject line and Design makes one visual, and Push repurposes and ships the follow-on post. Drafting the full issue body, and actually sending the email, both still live outside CF today — named in the register.

Key takeaways

Spark writes an honest subject line and pulls the repurposed hook.
Design adds one visual — keep it mostly words.
Drafting the full issue AND sending/deliverability are both outside CF today — in the gap register.
Push drafts and actually auto-posts the repurposed line to your live channels; Alfred holds your voice.