A topic becomes a newsletter that reviews and rewrites itself
A topic and a recipient address are the only required inputs; Claude writes the draft, scores it against five editorial criteria and sends the finished HTML through Gmail.
1Required input
Just a topic; tone, length and CTA default
6Pipeline steps
Research, outline, write, review, refine, send: 20 to 40 s end to end
250Word cap
Hard limit on every length tier
1 dayBuild
1One topic line is the only required input
2Length tiers cap the copy at 250 words
The whole input: one topic line and a recipient. Tone and length have defaults.
1One topic line is the only required input
2Length tiers cap the copy at 250 words
What runs automatically
01 / RESEARCH
Optional web research
An optional pass drafts three search queries for Tavily and folds the results into the outline, so a specific number can end up in the copy instead of a vague claim.
02 / WRITE+REVIEW
Write, score, refine
Claude Haiku writes the draft from a JSON outline, then a separate call scores it 1 to 10 across five dimensions. A refine pass rewrites against that list, skipped only once the score clears 8.5.
03 / SEND
Outlook-safe HTML send
The final Markdown becomes an Outlook-safe HTML email built from inline CSS and a table layout, sent over Gmail SMTP with STARTTLS and an app password.
Built with Claude Code in 1 day
Before
A short newsletter still took an afternoon: an angle, a draft, an edit, formatting.
After
A topic and a recipient produce a reviewed newsletter in 20 to 40 seconds.
Under the hood
01Context
A short newsletter still takes an afternoon to do well
Writing a short marketing newsletter well takes more steps than its length suggests: pick an angle, draft it, edit it with fresh eyes, format it so Gmail and Outlook both render it the same way and send it without tripping a spam filter. We wanted a tool that runs that whole sequence for A&M Flow's own newsletters, with nothing more from us than a topic and a recipient.
02What we built
A topic in, a finished newsletter out
The form asks for a topic and a recipient email; everything past that has a sensible default. Tone is a dropdown, length sets a target word count from 100 to 250 words and an optional key-points field points the model at specific angles. A dry-run checkbox generates the newsletter without sending it. Submitting the form runs the whole pipeline inside a Modal container and returns a result page with the subject line and a quality score, typically in 20 to 40 seconds. The prompt bans a fixed list of AI clichés outright.
03Constraints
Search only from the terminal, one Gmail account
Web search is real in the code but off by default on the hosted form: the deployed endpoint always passes search as disabled, so Tavily only runs from the command line with a search flag. A dry run scores the draft but the web result page shows only the subject line and the score, not the newsletter text itself. Every length tier is hard-capped at 250 words, and sending runs on one Gmail account and one app password, a tool for A&M Flow's own outbound, not a multi-tenant service.
ANM SOLUTIONS / CONTACT US
Want something like this?
First 30-minute call is free. We scope it, you decide.
