No subscriber list, no private analytics, no platform login, no tracking cookies.
Free tool for newsletter operators
Newsletter Automation Audit
Enter a public newsletter archive URL. We analyze recent issues for repeatable curation work, source-monitoring burden, and what automation could prepare before a human editor reviews.
Archive-first audit
Analyze your newsletter archive
We are analyzing your latest public issues.
Check your inbox for a confirmation email. Your automation-fit report will arrive after archive discovery, issue scraping, and AI analysis finish.
We confirm the archive URL and sender address right away.
The analyzer inspects public pages and reviews up to five recent issues.
You get the Monitor / Filter / Draft / Judge map, score band, confidence, and caveats.
Open a prefilled “Yes” email to our support address. Your mail app opens first, then you press send.
This button cannot send automatically. It only opens your email client.
The page captures the request, then async workers handle scraping, AI, and email.
Every audit request subscribes the email to Newsletter Tools updates by HeyNews.
The report separates production prep from taste, risk, voice, and final calls.
Emailed report format
Your result is a workflow map, not a fake instant score.
This preview shows the shape of the email. Your actual result is generated from your archive and delivered after analysis.
Monitor
Recurring sources, categories, and update types can be watched before a writer opens the doc.
Automate firstFilter
The system can rank likely stories by relevance, freshness, and section fit.
High leverageDraft
Repeatable sections can be pre-filled from selected stories and prior format patterns.
Good fitJudge
Point of view, risk, voice, taste, and final approval remain human work.
Keep humanRepeatable curated format, source-heavy issues, and clear prep work before editorial review.
Some sections can be prepared, but voice or original analysis limits full automation.
Automation may help monitoring, but the issue depends heavily on fresh human synthesis.
Too few public issues, weak archive structure, or mostly original essays with little repeatability.
Your newsletter may be a production system hiding inside an editorial product.
Curated newsletters look creative on the outside. Inside, many repeat the same operational loop: check sources, choose stories, write summaries, arrange sections, add sponsor copy, and send.
When that loop runs every week, or several times a week, the expensive part often happens before writing starts. The operator is not paying only for words. They are paying for source monitoring, judgment, and assembly.
What the analyzer looks for
- Recurring sections across recent public issues.
- High link density, source references, and repeated publication categories.
- Predictable issue structure: intro, top stories, quick takes, sponsor block, closing links.
- Clear separation between source selection and final editorial point of view.
- Enough archive depth to compare patterns across multiple sends.
What should not be automated away
The best newsletter automation does not erase taste. It prepares the table. A human still decides what matters, what is risky, what feels off, and what deserves the reader's trust.
That is why the report is organized around Monitor, Filter, Draft, and Judge. Automation is strongest when monitoring, filtering, and draft prep are repetitive, while judgment remains with the curator.
FAQ
Is this a newsletter ROI calculator?
No. ROI calculators measure revenue upside. This analyzes whether your public archive shows repeatable production work that software can prepare before a human editor reviews it.
Why do you ask for my email before the result?
Archive discovery and analysis can take a few minutes. The reliable version is async: we save the request, send a confirmation, run the analysis, and email the report when it is ready.
Why is newsletter signup mandatory?
This is a free tool. In exchange for the audit, you join the newsletter. You can unsubscribe from future newsletters any time.
What if my archive only has two or three usable issues?
The report can still be delivered with lower confidence. It should say how many issues were analyzed and avoid overstating the score.
Will this replace my writer or editor?
No. The strongest use case is removing repetitive source monitoring and first-draft prep, while keeping final judgment, voice, and accountability with the human editor.