What should a B2B SaaS customer newsletter include?

One thing another customer did that worked, one product change tied to an outcome, and one question that asks for a reply. Send it monthly, in plain text, from a person. The goal is replies, and opens don't tell you much. Every reply is a customer telling you what they need next, and some of those turn into expansion and referrals.

Why do most customer newsletters get ignored?

Because they're product announcements in a template.

The typical customer newsletter is a logo header, three feature updates, a webinar invite, and a footer. Customers skim it or filter it. It reads like marketing because it is marketing. They already see your product updates in the app and in the changelog. They don't need a third copy.

What they can't get anywhere else is what other customers like them are doing with your product.

What should go in each issue?

Three parts, about 300 words total.

1. A customer play. One customer, one problem, what they set up, and the result, shared with their permission. A headline like "How a 12-person ops team killed their Friday export" works because it's specific enough to copy.
2. One change worth their time. Skip the release list. Pick the one change that saves them time this month, and say how to turn it on.
3. One question. "What's the report you still build by hand?" Ask something they can answer in a sentence.

That's the whole issue. If you have more to say, save it for next month.

Who should send it?

A person with a name and a real reply-to address.

Early on, the founder. Later, a customer success lead or whoever runs customer marketing. A no-reply address tells customers you don't want to hear from them, and the replies are the reason you're sending it. Plain text from a person gets read like a note. A designed template gets read like an ad.

What do I do with the replies?

Treat each one as an account signal and route it within a day.

• "We need X." A product request or an expansion conversation. Log it on the account and tell the account owner. It's the same move as turning support tickets into expansion.
• "We tried this and it didn't work." A churn risk. Put it next to your other churn leading indicators.
• "A friend at another company has this problem." A referral. Ask for the intro while it's fresh. Here's when to ask for a B2B referral.
• "Here's what we did." Next month's customer play.

The newsletter becomes a loop. Customers answer, you feature their answers, other customers copy them. Net revenue retention grows when customers get more value from what they already bought, and this is one of the cheapest ways to spread what's working.

How often should I send it?

Monthly works for most B2B SaaS.

Weekly needs more news than most products have, and quality drops fast. Quarterly is too slow for replies to become a habit. Pick a day and keep it. Skipping a month is fine. Sending filler isn't.

How do I measure it?

Count replies and the conversations they start.

Measure	What it tells you
Replies per issue	Whether the question worked
Replies logged as expansion or referral	The pipeline it creates
Renewal rate of accounts that replied	Whether engaged customers stay
Unsubscribes per issue	A spike means the issue was filler

Open rates got less reliable after Apple launched Mail Privacy Protection in 2021. Apple says it stops senders from seeing whether a recipient opened their email. A reply can't be faked that way.

What mistakes kill a customer newsletter?

• Sending from a no-reply address.
• Listing every release.
• Featuring a customer without asking first.
• Asking a question and never answering the replies.
• Pushing an upgrade in every issue.

What should I do this week?

1. Pick one customer who did something clever with your product and ask if you can share it.
2. Pick the one change from last month that saves the most time.
3. Write one question customers can answer in a sentence.
4. Send it in plain text from your own address.
5. Log every reply on the account within a day.

A customer newsletter earns its spot when customers reply to it. Ask one good question and answer every reply.

Start Signals, Convert, Grow

FAQ

How is a customer newsletter different from a changelog?

A changelog records what shipped. A customer newsletter shows what other customers did and asks for a reply. Link the changelog in the newsletter instead of repeating it.

Should the newsletter go to every user or only admins?

Start with admins and champions, the people who own the account. Add active users once you have customer plays aimed at their daily work.

Can I use AI to write the customer newsletter?

Use it to tighten the draft or pull quotes from a customer call. Write the customer play and the question yourself. Customers reply to a person, not a template.

What if nobody replies?

Change the question. Make it easier to answer in one line and more specific to a task they do every week. If replies stay at zero after three issues, ask a few customers directly what they'd want in it.