The issue, assembled from what you already wrote
The writing is done. The twenty minutes of copying titles, writing a line about each one and fighting an email template is what makes the newsletter slip. This does that part.
Get the issue built in the time it takes to pick
Tick the posts, in the order you want them read. Each blurb is that post's own summary, written when it was drafted, so nothing needs re-checking.
Send it from the list you already pay for
Email HTML for a sender that takes it, Markdown for one that prefers it, plain text for the version that always works. Your subscribers stay where they are.
Stop an issue falling apart in the one client that breaks it
Tables and inline styles, with the two dark-mode traps handled — backgrounds pinned as gradients, text pinned with a text-fill, because Outlook rewrites the plain versions of both.
The parts that do the work.
Screenshots from the recording
Frames pulled from a recording when an issue is built off a talk or an episode rather than off posts.
Your brand on every draft
Your colours, typefaces, byline, footer and written voice — carried into the issue as well as the articles it is built from.
Internal links that exist
Links are placed deterministically from pages actually crawled on your own site. The model is never asked to invent a URL.
The SEO fields, filled in
Title, meta description and headings written with the draft rather than bolted on after, and editable before anything publishes.
Publish where you already publish
The issue comes out as email HTML, Markdown or plain text, and the articles behind it go into WordPress, Ghost or Webflow.
Nothing invented
Numbers, names and quotations are preserved or the variant is discarded. Every claim traces back to the source.
Newsletters, answered.
No, deliberately. Your list, your deliverability and your unsubscribe handling live in Mailchimp, Kit, Ghost or beehiiv. Recast builds the issue and hands it over; becoming a sending platform would mean taking on your subscribers, and that is a different product.
Each post's own meta description — the one-line version written when the draft was made. Nothing is generated fresh, so there is nothing new to fact-check.
No credits. Composing an issue is assembly rather than generation, so there is nothing to bill for.
It is included and flagged, shown as plain text rather than a link — a link to nowhere in an email cannot be recalled. Publish it or paste the address in.
Not yet. beehiiv and Mailchimp both do RSS-to-send, and this is the manual version: you choose what goes in. An automation that mails the wrong post is worse than two minutes of picking.
Same workspace, different job.
Start with something you have already made.
A recording, a link or a transcript. It comes back as a draft you can read, edit and publish — on your brand kit, in your words.