Write each newsletter issue from what actually happened, ready for one edit
Before each issue, the Bot gathers launches, wins, posts and events from your tools, writes the issue in your voice from past issues, and parks it for review. You edit once and send.
What the Bot is set up to do
- Give it your last three issues as voice examples, and the sections you always run.
- Connect the places news lives: Notion, Google Drive, Slack, your calendar, your store.
- Add a routine two days before your send day. Sending stays with you or your email platform.
Prompt
Two days before each issue of [newsletter name], which goes out every [day]:
1. Collect everything since the last issue from [Notion / Drive / Slack / calendar / Shopify]: launches, customer wins, new posts, upcoming events and useful links.
2. Write the issue in our voice, using [last 3 issues] as examples, with these sections: [sections].
3. Keep it under [600] words. Every claim needs a link or a source in our tools. Put anything you're unsure about in a "Check" list at the top, not in the body.
4. Suggest 3 subject lines under 50 characters.
Save the draft as a Page for my edit. Don't send or schedule it.Business fit
Who this helps, and how:
- CreatorsWriters start each week from a complete draft instead of a blank page.
- Local & serviceA local business can keep a monthly customer newsletter going without a marketer.
- AgenciesAgencies producing client newsletters get a first draft built from each client's own material.
- StartupsProduct updates go out every month instead of whenever someone has time.
How to adapt it
For a curated newsletter, add a research step: "Collect 25 candidate stories from [sources] and pick the top 8."
Bots can claim their own email address, so reader replies can go to the Bot to sort. Replies it sends wait for your approval.
Ask for a short social post to promote each issue.