It’s Sunday afternoon and the first newsletter is done. You liked writing it. The opening landed on the second try, you cut a story that wasn’t earning its place, and the closing line came out warmer than you’d planned.
Then you open the second publication.
The sentences arrive faster now. You’re warmed up, in rhythm, and the words come without much resistance. Twenty minutes later you’ve got a draft that reads clean.
It reads clean because you’re still writing the first newsletter.
That’s the half of writing multiple newsletters no calendar shows you. My cofounder Cagri priced the other half this week: the hours that refuse to consolidate no matter how many publications sit behind one login. His arithmetic is right, as usual. Underneath it sits a quieter question about who exactly showed up to write the second issue.
Nothing in that draft is wrong. The topics belong to this list, the stories are the right stories, every sentence is defensible. The person writing them is the person the last publication needed, and that person never left the room.
That’s a merge, and nobody signed off on it.
Why Do Your Newsletters Start Sounding the Same?
There’s a version of this problem agencies have, and it works differently. When a small team writes for ten client brands, one client’s rhythm leaks into another’s draft on a tired Friday. I’ve written about that specific failure before, and the craft it demands is essentially impression work: holding a voice that isn’t yours, then handing it back without fingerprints.
Running your own publications is the inverse problem, and it’s harder in a way nobody warns you about.
Every voice is yours. There’s no second brand to bleed in from, no client register to accidentally borrow. There’s one source, and everything flows out of it.
Which sounds like an advantage right up until the moment you need two publications to be genuinely different from each other. A solo writer’s instincts are usually the protection. They keep one voice steady across a hundred issues without conscious effort, and that automatic quality is exactly what makes a long-running newsletter feel like a person.
Point those same instincts at three publications and they’ll do what they’ve been trained to do. They’ll pull everything toward the center they know.
Your instincts are a loyal editor who only ever learned one publication. Hand them a second one and they’ll quietly file it under the first.
You’re not being lazy when this happens. Fluency is supposed to feel like this. The whole reason writing gets easier over years is that the choices stop being choices, and a writer who has to deliberate over every sentence isn’t a writer with a voice yet.
The trouble is that fluency has a direction. Yours points at the publication you’ve written most.
Your Style Was Never Yours Alone
Here’s the part that reframes the whole problem, and it comes from a field that has nothing to do with newsletters.
In 1984, the sociolinguist Allan Bell published a paper arguing that style is fundamentally a speaker’s response to their audience. Not to the topic. Not to how much attention you’re paying to your own words. To whoever is listening.
He called it audience design, and the evidence behind it came from radio.
Bell studied newsreaders in New Zealand who read bulletins on more than one station. Same person, same day, same studio building, different audiences. A review of his later work on media language describes the finding plainly: the same newscaster broadcasting on two stations with different audiences shows different phonological and grammatical features. The voice moved, measurably, and the only variable that moved with it was who was on the other end.
Surprising? Only until you notice you do this every day without trying. You explain your work differently to your mother than to a client. You don’t rehearse either version.
Style was never something you own privately. It’s an agreement between you and a specific reader, and a second reader was never part of that agreement.
So the goal of running several publications isn’t to perform three characters. You already have the equipment. What you’re missing is the thing that makes the equipment fire, and it’s simpler than talent.
You need each audience to actually be present when you write.
What Keeps Two Audiences Apart
Erving Goffman gave us the vocabulary for this in 1959, decades before anyone had an inbox. In The Presentation of Self in Everyday Life, he described social life as performance, and noticed that people give specific performances to specific audiences, keeping those audiences separated so each performance holds. He called it audience segregation. The teacher and the friend are the same person doing different, equally sincere things, and both work partly because the two rooms stay separate.
Then the internet arrived and broke the walls. Researchers Alice Marwick and danah boyd named what happened: technologies that collapse multiple audiences into a single context, leaving people without the techniques they’d always used to handle multiplicity face to face. Context collapse. One post, every audience at once, and the speaker flattens toward whatever register offends nobody.
Give that a second before you keep going, because your production workflow probably does this to you on purpose.
A batch writing session is a context collapse machine you built yourself. Three publications, one afternoon, one chair, no gap between them. Cagri listed batch production as one of three shortcuts operators reach for, and he’s right that it saves real hours. What it also does is put three audiences in the same room and ask you to address them in sequence without ever changing who you are.
By the third publication you’re four hours into a register that was set by the first one. The audiences collapsed before you typed a word.
A shared voice across two publications is a decision you make once and your readers pay for it weekly.
Purpose Is the Easy Half. Stance Is the Half That Fails.
The standard advice is sound as far as it goes. Guides on running several publications tell you to give each newsletter a distinct purpose so the content doesn’t overlap, and that’s genuinely the first move. Two publications covering the same beat for the same people is a strategy problem.
But purpose is a topic boundary, and topic boundaries hold up fine on a Sunday. You’ll never accidentally put a fintech story in the gardening newsletter. That’s the easy half.
Stance is the half that fails. Purpose tells a reader what an issue is about. Stance tells them who’s talking, and it’s built from three things you almost never write down.
What you’re allowed to assume. In one publication, your reader already knows what a churn cohort is and would be insulted by the definition. In another, the same sentence needs a plain gloss. Assumed knowledge is a relationship, and it shows up in every paragraph whether you thought about it or not.
What you’re arguing toward. Two publications can cover the identical story and want different things from it. One wants the reader to act by Thursday. The other wants her to see her own situation differently and do nothing about it for a month. That difference lives in the verbs.
What’s out of bounds. Every real publication has sentences it would never publish. The joke that lands in one room and reads as flippant in the other. The certainty you’d claim for an audience that hired you for opinions and would never claim for an audience that came for the reporting.
Purpose is a line on a strategy doc. Stance is a person, and people are the thing readers subscribe to. A reader can tell within two paragraphs whether you knew which room you were standing in.
The reader on both your lists already knows the answer for your publications. She just hasn’t told you.
The Same Story, Twice: A 20 Minute Test
Remember that second draft that came out fast? This finds out what was actually happening in it. You need one story, twenty minutes, and the willingness to compare two things you wrote yourself. No tool required.
Step 1: Find the overlap story. Pick one story from this week that could legitimately run in two of your publications. Most weeks have one, and the weeks that have three are the weeks this test matters most.
Step 2: Write both openings back to back. Draft the opening paragraph as it would run in publication A. Then immediately, with no break and no coffee, draft the opening as it would run in publication B. Ten minutes each. No editing, and no peeking at the first one while you write the second.
Step 3: Sort every difference into two piles. Read them side by side and underline everything that changed. Surface pile: the names, the examples, the industry noun, the length, the emoji. Stance pile: what you assumed the reader knew, what you were pushing her toward, how much certainty you allowed yourself, what you left out.
Step 4: Weigh the piles. A fat surface pile with almost nothing in the stance pile means you wrote one opening twice and swapped the nouns. Both sets of readers are receiving a translation of the same issue, and the one who subscribes to both can feel it even if she’d struggle to explain why.
Step 5: Write the forbidden sentence. For each publication, write down one sentence that publication would never let you publish. It can be perfectly true and still be wrong for that room. If you can’t name a forbidden sentence for one of your publications, that publication doesn’t have a stance yet, and it’s the one currently receiving a copy of your main newsletter.
The test takes twenty minutes because writing two openings takes twenty minutes. What you get back is a picture of how far apart your publications actually stand, drawn by the only person who can draw it.
Run it once a quarter and something small happens. You start hearing which room you’re in while you write, and that awareness costs nothing to maintain once it arrives.
Who Holds the Stance on a Bad Week?
Knowing all of this changes nothing on the Sunday when you’re tired and the second publication still needs an issue. Craft you can’t sustain is a hobby with extra steps, and the stance goes first when the week gets hard.
This is the problem HeyNews was built around, so treat what follows as an interested party describing his own work.
Each publication gets its own AI Writer, and each writer learns from that publication’s own archive. Connect a beehiiv or Kit newsletter and it becomes its own publication. Point HeyNews at a public archive on Substack, Ghost, Mailchimp, or Medium and those past issues train the writer for the publication you’re already in, no API key involved.
The draft for each one starts from the patterns that belong to that list, well away from the statistical middle of every newsletter online. Two publications, two archives, two starting points.
The stance gets written down, which is the part most operators never do. HeyNews Style Rules let you attach up to 20 lasting preferences to a specific writer, applied to the whole issue or to a single section. What you assume, what you’re arguing toward, what’s out of bounds. All of it becomes a standing instruction attached to the right publication, so it holds at 9pm when your memory won’t.
Sources stay separated too, and this matters more than it sounds. Each publication keeps its own feeds, saved pages, and followed profiles, and incoming stories are scored for relevance against the publication they belong to. Cagri makes the case that a shared source pool guarantees convergence at the output stage. Separate libraries are how you refuse that trade while still monitoring everything at once.
Then automations hold the cadence per publication. Set the issue days, the timezone, and the schedule, and drafts arrive ready for review on their own rhythm. Nothing sends without your approval, on any publication, ever. You keep the last read, which is the only arrangement that makes sense when judgment is the thing being protected.
Plans run from Starter at $99 a month for 2 publications to Pro at $299 for 4 and Team at $499 for 10, with publication packs available if your portfolio sits between the tiers. Yearly billing takes 30% off. The 14-day trial covers one publication and five drafts, so it’ll show you the voice work on your main list. Testing the multi-publication case honestly means being on a plan, and I’d rather say that than sell you a trial that can’t answer your actual question.
It All Comes Down To…
- Writing multiple newsletters is an identity problem wearing a workload costume. Every publication is yours, which removes the bleed an agency deals with and replaces it with something quieter: your instincts averaging all of them toward the one you know best.
- Style is a response to an audience. Bell’s newsreaders shifted measurably between stations, and you already do the same thing when you talk to your mother and then your client. The equipment is installed. The audience has to be in the room for it to fire.
- Batch production collapses your contexts on purpose. Three publications in one afternoon means three audiences in one room and one register serving all of them.
- Distinct purpose is the easy half. Stance is what fails, and it’s made of what you assume, what you’re arguing toward, and what’s out of bounds. Write those down per publication.
- Run The Same Story, Twice this week. One overlap story, two openings back to back, every difference sorted into surface or stance. Then name each publication’s forbidden sentence. No tool required.
Back to the Second Draft
Go back to that Sunday and the draft that came out in twenty minutes. The writing in it was competent, clean, defensible. It was also addressed to a reader who wasn’t in the room, produced by a version of you who’d already gone home to a different publication.
Your readers picked each of your newsletters separately. Somebody subscribed to the second one on its own terms, for its own reasons, and never agreed to receive the first one in different clothing.
The distance between your publications is the whole reason more than one exists. Protect it on the good weeks by writing it down, and put the mechanical half somewhere it can hold on the bad ones.
See how each publication keeps its own writer, sources, and rhythm inside HeyNews
