What Is a B2B SaaS Newsletter Actually For?

What is a B2B SaaS newsletter actually for?

It exists to stay in front of people who are not ready to buy yet, in a channel you own, with something they would miss if it stopped. That is the entire job. It is not a distribution channel for your blog and it is not a nurture sequence with a nicer name.

Most SaaS newsletters fail because nobody answered this question before the first issue went out. Someone decided a newsletter was a good idea, the format defaulted to a roundup of recent posts, and within four months it was a chore producing nothing.

I have written a few hundred articles and sent a fair number of emails about them, and the honest lesson is that a newsletter and a blog are different products with different jobs. Treating one as a wrapper for the other wastes both.

Why do most SaaS newsletters fail?

Because they contain nothing that was not already published. A links roundup asks a busy person to click away to read something they could have found anyway, which is a bad trade for them. If the email itself is not worth the two minutes, the click rate is not the problem, the format is.

The second failure is inconsistency. A newsletter that arrives monthly, then not for seven weeks, then twice in a fortnight, never becomes a habit for anyone. The reader cannot form an expectation, so they never develop the small anticipation that makes an email get opened rather than archived.

The third is that nobody owns it. Newsletters get assigned to whoever has capacity, which means the voice changes issue to issue and the standard drifts downward. An email from a named person who sounds the same every time is a relationship. An email from a company that sounds different every time is a broadcast.

What should go in one that a blog post cannot do?

Three things. What you are seeing across customers that has not been written up yet. What you changed your mind about. And what you decided not to do, and why. None of those work as public articles and all of them are interesting to someone evaluating you.

The in progress observation is the most valuable and the least used. A blog post has to be finished and defensible. An email can say that you have noticed something three times this month and are not sure what it means yet, and that half formed observation is often more useful to a reader than a polished conclusion.

The change of mind is the one that builds trust fastest. Saying publicly that you used to advise something and no longer do, with the reason, tells a reader more about your judgment than any case study. It also pre-empts the objection that you are simply repeating whatever you said last year.

How often should it go out?

As often as you genuinely have something for it, on a fixed schedule you can hold for a year. For most B2B SaaS companies that is monthly. Weekly is a real commitment and it will show as thinness within two months if the substance is not there.

Pick the cadence by looking backwards rather than forwards. Ask how many genuinely useful observations your team produced in the last three months, divide, and use that number. Almost everyone plans a cadence based on their most energetic week, which is the wrong sample.

Fixed beats frequent. A monthly email that arrives on the first Tuesday for two years does more for you than a weekly one that lasts a quarter. The value is in the accumulation of being present, and that only happens when you can sustain it through a busy month.

Who should write it?

A named person who is close to the work, ideally a founder early on. The signature is not decoration. It determines whether the email reads as a person thinking out loud or as a company pushing content, and readers can tell the difference within a sentence.

The instinct to hand it to the newest marketing hire is understandable and usually wrong at small scale, because the person closest to customers has the raw material and the person furthest away does not. The newer person is often the right editor and the wrong author.

When the company gets big enough that the founder cannot keep writing it, do not silently swap the byline. Hand it over explicitly, in the email, to another named person. A newsletter whose author changes without acknowledgement reads as ghostwritten, and once a reader suspects that, the trust does not come back.

What should you measure?

Replies and unsubscribes, ahead of opens and clicks. A reply means someone thought the email was a conversation, which is the outcome you actually want. Unsubscribes tell you when you have broken the implicit deal, especially when they cluster around a particular issue.

Open rates have become a soft number for reasons outside your control, and clicks measure whether the links were compelling rather than whether the email was. Neither is useless, but neither should be the number you optimise, because optimising them pushes you toward clickbait subject lines and link heavy issues.

The measurement that matters most is slow and qualitative. When a prospect arrives and mentions something you wrote in an email six months ago, the newsletter is working. Keep a note of those moments, because they are the only real evidence and they will not show up in any dashboard.

When should you shut one down?

When you have missed two consecutive scheduled sends, or when you cannot name a thing worth saying without going to look at your own blog. Both are signals that the underlying supply of observations has dried up, and no amount of process fixes an empty well.

Shutting down is not a failure and it is far better than the alternative, which is an email that limps along being resented by the person who has to write it and ignored by everyone who receives it. Send a final issue saying you are stopping and why. People respect it and some of them will reply.

The same honesty applies to what you ask for in exchange for signing up. If the newsletter is no longer the useful thing it promised to be, the signup form on your site is now making a claim you are not meeting, which is the gating question I wrote about in what should go behind a signup wall.

How does a newsletter interact with AI search?

It does not, directly, and that is precisely the point. Email is the one channel where your relationship with a reader is not mediated by a model deciding whether to mention you. As more discovery moves into assistants, an owned channel becomes more valuable rather than less.

There is an indirect effect worth noting. If you publish a web archive of your newsletter, those issues become ordinary pages that can be crawled, cited, and retrieved like anything else. Many companies send genuinely good thinking into inboxes and never let it exist anywhere a search engine or an assistant can see it.

My recommendation is to publish the archive unless an issue contains something genuinely private. You lose nothing, because the subscriber got it first and that timing was the actual value, and you gain a body of specific, opinionated writing that is exactly the sort of thing answer engines retrieve well.

What should you do next?

Before writing another issue, write one sentence describing what a reader would miss if your newsletter stopped tomorrow. If you cannot finish the sentence without referring to your blog, the newsletter does not have a job yet, and the first task is giving it one.

Then pick a named author, a cadence you could hold through your worst month, and a format that contains something unpublished every time. Those three decisions determine almost everything about whether it survives its first year, and they should be made deliberately rather than inherited from a template. The same principle applies to the first automated email a new user receives, which I covered in what a lifecycle email should do in week one.

If you are trying to work out whether a newsletter is worth starting, or worth continuing, I am happy to give you a straight read on it. Reach out and tell me who you would be writing to.