Most newsletters fail because they’re treated as a channel instead of a product. The thinking goes: we have an email list, we should send them things, let’s call it a newsletter. A junior marketer is assigned to fill it. They round up some blog posts, add a greeting, paste in a CTA, and hit send on a schedule that was determined by someone who read that “consistency matters” on a marketing blog. The result is something nobody asked for, nobody remembers, and nobody would miss if it disappeared.
I’ve seen this pattern across dozens of B2B SaaS companies. At PipelineRoad, newsletters are a core part of what we build for clients, and the single biggest shift in quality comes when we stop asking “what should we send this week?” and start asking “what are we building here?”
The Product Mindset
A product has a purpose. It has a user. It has a value proposition. It has a feedback mechanism. It evolves.
A newsletter should have all of these things. Before a single edition is drafted, you should be able to answer: Who is this for? What do they get from it that they can’t get elsewhere? Why would they open this on a Wednesday morning when their inbox has forty other unread messages? What does success look like — not in open rates, but in reader behavior?
These are product questions. And they require product thinking. When you treat a newsletter as a product, the editorial decisions become clearer. You stop including things because you have them. You start including things because they serve the reader. The difference in quality is immediate and dramatic.
Voice as Architecture
One of the most neglected aspects of newsletter design is voice. Not tone — every brand brief includes a section on tone. Voice. The actual personality that comes through in the writing. The rhythm of the sentences, the level of formality, the ratio of information to opinion, the way the author addresses the reader.
The newsletters that work — the ones people actually forward to colleagues, the ones that build genuine affinity — have a voice that is specific and consistent enough to be recognizable. You could strip the header and the logo and a regular reader would still know whose newsletter it is by the second paragraph.
This is incredibly hard to manufacture. It requires a real point of view, which means it requires a real author or at least a real editorial sensibility behind the curtain. The worst newsletters are the ones written by committee, where every sentence has been sanitized through so many rounds of approval that the voice has been replaced by corporate ambiance.
When we develop newsletters for clients, we spend a disproportionate amount of time on voice before writing a single edition. We study how the founder or subject-matter expert actually speaks — in meetings, on calls, in casual Slack messages. We find the phrases they reach for naturally, the cadence they fall into when they’re being honest rather than performing. That’s the raw material. The newsletter voice is a refined version of that, not a departure from it.
The Feedback Loop
Products improve because they have feedback loops. Newsletters almost never do. The typical “analytics” conversation is about open rates and click rates, which tell you almost nothing about whether the content is good. A subject line can drive opens. A single well-placed link can drive clicks. Neither tells you whether the reader finished the email, thought about it afterward, or changed how they think about your company.
The feedback loop I care about is qualitative. Are readers replying to the newsletter? Are they mentioning it in sales calls? Is the sales team hearing “I read your newsletter” from prospects? Are the right people — the actual ICP, not just the full list — engaging with it?
These signals are harder to measure, but they’re the ones that correlate with business outcomes. A newsletter with a 25% open rate that regularly generates inbound conversations is infinitely more valuable than one with a 45% open rate that generates nothing.
The Roadmap
If a newsletter is a product, it should have a roadmap. Not in the sense of a Gantt chart or a quarterly OKR — in the sense of intentional evolution. The newsletter you publish in month one should not be identical in structure and depth to the one you publish in month twelve. It should grow. New sections should be tested and either kept or killed. The format should adapt to what you learn about how readers engage with it.
I think of a newsletter’s first ten editions as a beta. You’re testing hypotheses about format, length, voice, and content mix. You’re watching which sections get engagement and which get scrolled past. You’re listening for the signal that tells you what this thing actually wants to become — which is often different from what you initially planned.
The newsletters that stagnate are the ones where the team settled on a template in week two and never revisited it. The ones that thrive are the ones where someone is paying attention to how the product is performing and making deliberate adjustments.
The Stakes
In B2B, a newsletter is often the single most intimate touchpoint a company has with its audience. It arrives in someone’s personal inbox. It competes with messages from friends, family, and colleagues. That’s a privilege, and it comes with a standard. If your newsletter isn’t good enough that a reader would choose to read it over checking their other messages, you’re not just wasting their time. You’re training them to ignore you.
Treat it like a product. Build it like something that deserves to exist. The bar is not “did we send something this week.” The bar is “would someone pay for this.” You don’t have to charge for it. But the question is worth asking, because it changes everything about how you make it.