Somewhere in your newsroom, someone is copying a headline out of your CMS and pasting it into an email tool. Right now. Today. They're resizing an image that was already the right size in the article. They're rebuilding a link that already worked on the website. They're previewing the same newsletter on three devices because last Tuesday the footer clipped in Gmail and nobody caught it until a reader replied.

This person is probably one of your best editors. And this is not editing.

The invisible department

Every publisher with a newsletter has a production team they never hired. There's no line item for it. No job title. No budget. But the work exists, and it adds up.

A single daily newsletter edition takes 30 to 90 minutes of manual production. That's not writing (your editors already did that in the CMS). That's the other work: copying content into Mailchimp or your ESP, reformatting it, fixing what broke in the transfer, running QA, and hoping the whole thing holds together when it hits inboxes.

Let's do the math on a mid-sized publisher sending one daily newsletter:

45 minutes per edition (conservative average)
5 editions per week
50 weeks per year
187 hours per year, on one newsletter

That's nearly five full working weeks. Spent on copy-paste, reformatting, and manual QA. For one newsletter.

Now multiply. The Wall Street Journal runs 40+ newsletters. Axios Local publishes across 34 cities, expanding to 43. Condé Nast was managing newsletters across 65 teams in 9 languages before they had to consolidate because the operational model was breaking.

At that scale, you're not hiding a person inside other people's jobs. You're hiding a department.

The work nobody talks about

The strange thing about newsletter production is that it's completely invisible in industry conversations. Publishers talk about editorial strategy, subscriber growth, open rates, monetization. They don't talk about the 45 minutes between "stories selected" and "newsletter sent."

It's not glamorous work. It doesn't show up in conference talks. Nobody writes case studies about how they optimized their copy-paste workflow. But it's the bottleneck that determines how many newsletters you can realistically sustain, and how fast each one goes out.

An operations analysis of scaled newsletter programs put it bluntly: the limiting factor isn't content or audience. It's operations. At scale, the ability to manage production with precision becomes critical. Adding more people doesn't solve it if the process is manual. You just get "a larger team performing the same manual tasks with even more points of failure."

Why it's getting worse

Here's the thing: you probably need more newsletters, not fewer.

Facebook referrals to news sites have dropped 48%. Google's AI Overviews are killing click-throughs, with searches for news that result in zero clicks to publisher websites jumping from 56% to nearly 69% in 2025. The Reuters Institute reports that publishers are forecasting a 40% decline in search referrals over the next three years.

Meanwhile, newsletters convert readers at 5x the rate of search and social traffic. Newsletter sponsorships generate $15 to $150+ CPM. Publishers expect newsletter revenue to keep growing. Newsletters aren't a nice-to-have anymore; for many publishers, they're becoming the primary direct channel to readers.

So the pressure is to launch more newsletters, send more frequently, reach more segments. Which means more manual production. More copy-paste. More QA. More invisible hours from your best people doing work a system should handle.

What Patch learned the hard way

Patch, the Axios-owned hyperlocal platform, is probably the clearest example of what happens when manual newsletter production meets scale.

Their model was human curators producing each daily newsletter in one to three hours, at $15 to $25 per edition. It worked until it didn't. The model couldn't scale beyond a certain number of communities without becoming operationally unsustainable. Patch eventually transitioned to AI-generated newsletters covering 30,000 communities.

The lesson isn't that AI replaces humans. It's that manual production has a ceiling. When you hit it, your options are: stop growing, lower quality, or automate.

The question nobody's asking

Most publishers treat newsletter production the way they treated print layout 20 years ago, as an inevitable cost of doing business. The workflow is manual because it's always been manual. The tools don't talk to each other because they were never designed to.

But here's the question worth asking: what if the work between "stories selected in the CMS" and "newsletter delivered to the right audience" simply didn't require a human doing manual labor?

Not the editorial judgment. Not the writing. Not the story selection. Those are irreplaceable. But the copying, reformatting, link-rebuilding, image-resizing, template-wrangling, device-previewing, QA-checklist-running part? What if that just happened?

The content already exists in your CMS. The subscriber list already exists in your ESP. The gap between them is pure overhead.

That's the problem we built Embrin to solve.

Embrin is a newsletter production platform for publishers. It pulls content from your CMS, gives your team a workspace to shape each edition, and sends it to the right audience in about 90 seconds. Book a demo with your own content.