What should you automate with AI first in a newsletter business?

When operators ask me where to start with AI, they usually mean writing. I point them at everything else first.

"It's not even necessarily just writing newsletters, although AI can help there too. It's the grunt work and the really annoying tasks."

Why automate tasks that aren't even hard?

Because hard isn't the problem. Time is. Almost nothing in running a local media brand is difficult. It's time consuming, so nobody does it. Automate it and people actually do it. When they do it, they get more value. When they get more value, they get more excited.

The other reason is output per person. When I set my team's goals for one month, the single top goal was figuring out how to automate things: newsletters, SEO articles, and lots of the steps in building and managing Meta ad creative. What I want is for one person's eight-hour day to produce two days of output, or five, because the tools and systems carry the rest.

How do I decide what to automate?

One question: will a reader or advertiser experience this output?

• Yes: keep a human in the loop. AI can draft, but a person approves.
• No, it's internal: default to automating it.

I run multiple local brands with a small team, so AI behind the scenes is the whole game. But against a flood of AI content, my differentiator is that a real person is behind the brand. Automate the wrong layer and you destroy that while chasing efficiency.

Which tasks pay off most?

The recurring, per-newsletter steps. They look small for one brand and add up across a portfolio. My effort gate rejects a lot of ideas because they're too much work to do by hand for every brand. Those rejected ideas are exactly the automation candidates.

"If it's hard, it's not worth doing, but if it's easy, you should absolutely do it."

Two rules that go with it:

1. Ask "can we automate this?" as the follow-up to every idea you rejected for being too much effort.
2. Once a task is one click, stop re-arguing whether it's worth doing. Just do it.

This applies to recurring operational work, not one-time builds. Because things are so much easier now, I'm optimizing things that were never worth the effort before.

Also worth one slot: a "lotto ticket" with upside that costs you no time. I want a content agent that records, edits, titles, thumbnails and posts podcast clips end to end, fully automated. If it hits, great. If not, it took none of my time.

Where does AI save the most time in local newsletters?

Gathering data and finding content. Time is the biggest operating problem in local newsletters, and most of it goes to finding events, news and local info, because every town is its own island. Writing is the part everyone already knows how to speed up. See using AI to pick stories.

Events are the hardest part. Meta doesn't want you scraping, so you have to be really good to do it. The direction I'm building toward:

• While you're asleep, the AI scrapes what's happening locally: which businesses filed permits, all the news sites, the Facebook pages of the city council and the police.
• It writes drafts from that and leaves them in your queue: here are articles you could write today.
• It never sends. A person goes in and verifies everything first.

What shouldn't I fully automate?

• Anything that sends to readers without a check. Drafts can be automatic. Verification stays human.
• Instagram posting. I don't fully automate it. My belief (not a tested result) is that if Instagram knows a bot is posting, it suppresses the post. The setup I want is automation that produces the draft, and a human posts it.

How do I know an automation is still working?

Check on a schedule. Automated SEO article pipelines across several of my sites went silently dead for about a month, and nobody caught it. The fix was human: I gave an operator direct access and set a recurring check every three to five days.