issue tag / run 22 · free workflow
Fit a Newsletter Issue Into Its Word Budget Before Drafting — Free
Set the budget and list the sections with their word counts; the tag totals them so an overrun is a visible number before you have drafted any of it.
What this replaces
Advice about newsletter length is advice about tone. This adds up the sections you planned against the budget you set, so the decision to cut is made on a number while the cost of cutting is still just deleting a row.
Tool note. This runs entirely in your browser — no account, no upload, no paid API key. Google NotebookLM is named as the free source-grounded reading path for the material you paste; its published free-tier terms were checked on 2026-09-13 and can change.
The four passes
Collect the smallest useful input
A word budget on the first line, then one section per line with its count.
Let the tag total them
Each section is counted and the final row is the issue against the budget.
Cut the largest section first
It has the most to give without changing the shape of the issue.
Draft to the plan
The tag sets the length; the writing is still yours.
Try it on the issue tag / run 22
The board below runs in your browser. It opens with a worked sample so the result is visible before you paste anything; switch scenarios, edit the text, or reset to the sample.
running the sample…
first-load · sample values are illustrative, not verified facts
Everything you paste stays in this browser tab. Nothing is uploaded, there is no account, and no request leaves the page to generate the result; clearing site data removes anything saved locally.
What breaks, and what to do
Budget omitted
Nothing to compare against; state it on the first line.
Sections with no count
Read as zero, which flatters the total.
Art and pull quotes
Only words are counted; keep your own allowance.
Go deeper — Issue Tag
The free board above is the whole loop. The paid tier keeps the arranged output so you do not rebuild it.
- Printable tag with each section boxed at its real length — estimate: 13 minutes saved per issue, basis: 4 sections re-measured at ~3.25 minutes each
- Saved local history across runs — estimate: 7 minutes saved per issue, basis: re-entering 4 sections plus budget at ~105 seconds each
$4 one-time