Open the dashboard where you manage multiple newsletters and count the publications. Two, maybe four. Now open last week’s calendar and count the hours each one actually took.
The dashboard implies the second publication was nearly free. One login. One billing relationship. Same templates, same analytics view, same send infrastructure, and the upgrade cost you a tier.
Your calendar disagrees. The second publication took roughly what the first one takes, and on bad weeks it takes more, because you reach it already tired.
Both readings are accurate. They measure different layers of the same operation, and only one of those layers ever consolidated.
Why Does the Second Newsletter Cost More Than the First?
Because you consolidated the cheap half.
Sending consolidates beautifully. Templates, domains, list hygiene, deliverability, billing, analytics dashboards and team permissions all genuinely merge. Do the work once and every publication benefits.
That’s real, and it’s why platform pages for managing multiple newsletters lead with the dashboard. beehiiv’s multi publication feature page is honest about what it delivers, and what it delivers is delivery.
Editorial work refuses to merge the same way. Each publication needs its own source library, because the sites worth watching for one audience are noise for another. Each needs its own sense of what counts as a story. Each needs its own voice, its own section structure, and its own rhythm of what goes first.
None of that amortizes. You build it once per publication, and you rebuild it every week per publication.
Your publications don’t share a brain, and the brain is the expensive part.
That’s a tax, and no line item shows it.
What Actually Merges, and What Never Will
Worth being precise, because the split is cleaner than it looks.
Merges across every publication you run: deliverability setup, template systems, image libraries, subject line testing methodology, analytics tooling, billing, scheduling infrastructure, and your own accumulated skill at the craft.
Merges for exactly one publication and no others: the source library, relevance judgment, voice, section architecture, cadence, the running memory of what you covered three weeks ago, and the specific reason a given story matters to that specific list.
Look at the second column and notice something uncomfortable. Almost everything on it is the part you’d describe as the actual work.
Surprising? Only if you’ve never watched a Sunday disappear into the second publication after you’d already finished the first.
The source library deserves its own note, because operators consistently underestimate it. A feed that reliably surfaces useful material for one audience is a feed you built by watching what landed and what died over dozens of issues. That judgment lives in the specific pairing of source and audience.
Point the same feed at a different list and you get plausible stories that nobody asked for. The library looks portable. The knowledge inside it isn’t.
So the first column is where tooling has been competing for a decade. The second column is where almost nobody has built anything, which leaves most operators running several publications to solve it the way people always solve unsolved problems. Improvisation, and hours.
The Three Shortcuts That Turn Two Newsletters Into One
Faced with editorial work that won’t consolidate, every operator reaches for the same three moves. Each one works. Each one has the same side effect.
Shortcut one: the shared source pool
You maintain one feed list and pull from it for everything. Cheaper to maintain, faster to scan, and now both publications draw from an identical pond.
A shared source pool is two newsletters agreeing to read the same internet and hoping they’ll disagree about it.
They won’t, reliably. Story selection converges long before anyone notices, and convergence at the input stage guarantees convergence at the output stage.
Shortcut two: the house voice
You develop one register that works acceptably everywhere. It’s efficient and it’s defensible, and the readers who subscribe to two of your publications will find out first.
No judgment on this one. It’s the most rational shortcut available when one person holds every voice, and my cofounder Eren wrote about the version of this problem that shows up across a roster of brands.
Shortcut three: batch production
You write everything in one sitting because context switching is expensive. So publication three gets written by someone four hours deeper into the day than publication one, in whatever register the previous two established.
You’ve read the output of this. It’s the newsletter that arrives technically competent and somehow anonymous.
Each shortcut trades distinctiveness for hours, and the trade is often correct in the moment. The problem is that it compounds silently. The invoice arrives as churn on whichever publication you’d rank second, eighteen months later.
Every shortcut that makes two newsletters cheaper to run makes them harder to tell apart. That’s the entire trade, and nothing in your stack prices it.
Which Publication Gets Your Best Hour?
There’s a resource allocation problem underneath all of this that shows up nowhere in any tool.
Attention isn’t fungible across a day. The first publication you touch gets your sharpest editorial judgment, your patience with a stubborn intro, and your willingness to throw out a story that almost works. The last one gets whatever survived.
You’ve already ranked your publications. Your calendar did it for you, quietly, months ago, and the ranking has held every week since.
That ranking would be defensible if it matched your strategy. Usually it matches something else entirely: which publication has the earliest send time, which one you launched first, or which one has the sponsored content.
Watch what happens over a year. The publication that consistently gets your best hour improves, because attention compounds into better story selection and sharper writing. The publication that gets your last hour flattens, and then you conclude that its audience is harder to serve.
The audience was fine. Your allocation had already decided the outcome before anyone opened an email.
This is the strongest argument for pulling mechanical work out of the cycle. Every minute you reclaim from feed scanning and formatting is a minute that can go to the publication currently living on scraps.
The Market Is Betting Against the Middle
This would be an academic concern if audiences were getting less discerning. They’re getting more.
The Reuters Institute’s Journalism, Media and Technology Trends and Predictions 2026, built on a survey of 280 executives across 51 countries, found publishers moving effort decisively toward original reporting, contextual analysis and human stories, and away from evergreen content and general news. The reasoning is blunt. General coverage is becoming something a chatbot answers, so the publishers making the bet are doubling down on whatever a summariser can’t flatten.
The report’s authors describe the likely outcome as a barbell. Human distinctiveness at one end, heavy automation at the other, and the undifferentiated middle finding its audiences and revenues squeezed.
Read that as an operating instruction if you run more than one publication. Three shortcuts applied across a portfolio move every one of your publications toward that middle simultaneously.
The same report carries the other half of the answer. It profiles Velora Cycling, a newsroom of one producing specialist news and data that would previously have required a full team, with AI handling drafts, image selection, tagging and social posts under the oversight of a former Cycling News editor who supplies the expertise and commentary. It also documents Newsquest deploying more than 30 reporters working with AI assistance across its titles, drafting stories that staff then check and supplement.
Both examples automate the same layer. Neither one automates the judgment. That’s the pattern worth copying.
Separation Is the Product
Morning Brew is the clearest case study available, because the company treated separation as valuable enough to rename itself over.
Axios reported in 2024 that the company rebranded its corporate identity to Morning Brew Inc. specifically to distinguish its consumer brands from its professional ones. Those professional brands, seven newsletters spanning tech, marketing, retail and other verticals, were driving $25 million in annual revenue, with subscriber counts doubled since 2022. An eighth, Revenue Brew, launched the following June.
Notice what they didn’t do. They never merged seven professional newsletters into one larger business newsletter, even though all of them draw from overlapping business coverage and the consolidation would have been trivially easy.
Let that sit for a second. The company with the most operational reason to merge its publications spent a corporate rebrand making sure nobody confused them.
Separation is what makes each vertical sellable. A marketing newsletter that also covers healthcare is worth less to both advertisers and less to both audiences. The distinctiveness that costs you hours is the same distinctiveness that makes a portfolio worth more than the sum of its lists.
You didn’t launch a second newsletter. You launched a second editorial operation and handed it the first one’s leftovers.
The Merge Line
You can size this in about thirty minutes with a spreadsheet and one production cycle of honest notes. No tool required.
Step 1: Log one full cycle. Take a week where every publication shipped. Write down every recurring task and the minutes it took, per publication. Include the small ones: feed scanning, story triage, subject line drafting, image hunting, formatting, and the ten minutes rereading the last issue to remember where you left off.
Step 2: Sort each task into two columns. Column A is work where doing it once served every publication. Column B is work where doing it once served exactly one publication and did nothing for the others. Be strict. If you had to redo it per publication, it belongs in column B.
Step 3: Draw the line and total the hours. The boundary between the columns is your merge line. Add up column B. That’s your true cost per additional publication, and it’s the number your billing page has never shown you.
Step 4: Find the tasks you merged anyway. Go back through column B and flag every task you’ve been handling once across all publications: the shared feed list, the single voice, the batch writing session. Each flag marks a place where two publications are quietly becoming one.
Step 5: Price the flags. For each one, ask a blunt question. If a reader subscribed to two of your publications this week, would they notice both came from the same operation? Every yes is a distinctiveness leak you traded for hours, and now you know the exchange rate.
A small column B would be a bad outcome. Column B is supposed to be big, because column B is the reason each publication exists. The useful result is knowing exactly which parts of it you’ve been merging by accident.
What This Means for Your Stack
Back to the two columns, because they point at two conclusions and the first one costs nothing.
Stop trying to shrink column B by merging it. Shrink it by automating the mechanical work inside it and keeping the judgment separate per publication.
Source monitoring is mechanical. Deciding which of the monitored stories belongs in Tuesday’s issue is judgment. Formatting is mechanical, and the order you put things in is judgment.
That distinction survives across any tooling you choose, including none at all.
Second, evaluate tools on whether their architecture keeps publications apart. I’ll declare an interest here, because it’s the problem HeyNews was built around. Every publication gets its own AI Writers, sources, stories, analytics and settings, held separately by design.
Connecting a beehiiv or Kit newsletter creates its own publication. You can also connect your public archive to create another publication.
The mechanical layer is where consolidation actually happens. Sources get monitored on a schedule across every publication at once, incoming stories get scored for relevance against the publication they belong to, and automations create drafts on whatever cadence each publication runs.
Nothing sends without a human reading it first, which is the only arrangement that makes sense when the judgment is the part you’re protecting. If you’d rather approach this from the staffing angle, I worked through the case for automating before hiring in an earlier post.
Whether you build that yourself or buy it, the architectural requirement holds. Merge the mechanics, isolate the judgment.
What to Do With This
- The delivery layer consolidates and the editorial layer doesn’t. Your second publication’s real cost lives entirely in the second layer, and no dashboard displays it.
- Three shortcuts turn a portfolio into a template with several logos: the shared source pool, the house voice, and batch production. Each one buys hours by spending distinctiveness.
- Attention isn’t fungible. Whichever publication you touch last has already been assigned its ceiling, and the ranking usually reflects send times over strategy.
- Publishers are moving toward original, distinctive work and away from general coverage, and the undifferentiated middle is the position getting squeezed. A portfolio running on shortcuts occupies exactly that middle.
- Run the Merge Line this week with a spreadsheet and one production cycle. It costs thirty minutes, requires no tool, and tells you which of your publications are quietly becoming the same publication.
Back to the Dashboard
Go back to the count you did at the start. Two publications, or four, sitting in one sidebar behind one login.
The sidebar was always telling you the truth about infrastructure and lying to you about work. The infrastructure merged. The work stayed exactly where it was, multiplied by the number of publications you own, waiting for a Sunday.
You can keep paying that in hours, or you can automate the mechanical half and spend what’s left on the part that made each publication worth starting.
See how publications stay separate inside HeyNews while source monitoring runs across all of them
