How do I cut newsletter production time without hurting quality?
Short answer
Ask what readers would do differently if an input were merely good instead of the best, and default to the fast version. Price each manual task across every newsletter you run, cut low-value recurring sections, and automate the rest. Writing 20 newsletters at two to three hours each is why I built my own software.
Every week, writing 20 of these was taking two to three hours each, even with a VA. They made mistakes, and my wife spent a lot of time on them. It was a nightmare. That's why I spent 18 months building software to do it.
Which question cuts the most time?
"If instead of finding the absolute 10 best events, we put in six pretty good ones that we found quickly, right? What changes?"
Isolate the input and ask what the reader would actually do differently. Default to the fast version of a recurring task and make the polished version justify itself. Separate what readers can compare from what they can't.
If the team keeps doing it the expensive way anyway, that's inertia. Fix the workflow instead of arguing about it. This is about curation depth, by the way. It isn't an argument for cutting the events section.
How do I decide if a task is worth doing at all?
Price it across the whole portfolio. Eighteen newsletters times every send adds up.
Like a lot of things, if it's hard, it's not worth doing, but if it's easy, you should absolutely do it. We had a recurring task that wasn't worth doing by hand for a year and a half. Then we built the automation into our software, and it became a great idea, because now it's easy. A hard-but-good idea isn't dead. It's waiting on automation.
What should I cut when the team is stretched?
Subtract on purpose. In a July 2026 operating review we removed hard-news sections from newsletters without dedicated editors and moved at least eight newsletters to biweekly, to free time for higher-impact Instagram work. We didn't measure the time saved or the audience reaction, so treat that as a judgment call, not a study.
How much time can automation actually save?
A lot, on the right task. My realtor's VA probably spends five hours a week making a home-tour GIF. I can do it in 10 minutes with one drag and drop. That kind of gap is what I built lightbreak to close.
My team is me, my wife and two VAs, one more advanced who manages and one writer. With a team that size, every manual minute gets questioned. The QA side is in how to set up newsletter QA.
Answered by TJ Larkin. From February 2026 Local Media HQ podcast episodes, a July 2026 operating review and a September 2026 call with a newsletter operator. Last updated .