Open your product changelog and count the entries from the last full quarter. For most SaaS teams, the list runs 15 to 40 items. New features, new integrations, improvements customers asked for by name.
Now open your email platform and count the sends that explained any of those items to your full customer list, including the accounts that haven’t logged in since onboarding. For most SaaS companies, that second number sits between zero and two.
A SaaS customer newsletter closes that gap, and it’s worth more than most teams assume. Engineering produces value every sprint. The news about that value stops at a changelog page and a launch post that fades by Thursday. A changelog is a museum with no signage: complete, accurate, and visited by nobody.
What your customers don’t know you built, they can’t use, can’t renew on, and can’t upgrade toward. The cost shows up in three dashboards, and the first one is adoption.
Why Don’t Customers Use the Features You Ship?
Pendo analyzed feature usage across 615 software products and published the result in its 2019 Feature Adoption Report: 80% of features in the average software product are rarely or never used. The same report priced the waste at roughly $29.5 billion in cloud software spend flowing into features that are barely used.
Pendo’s later benchmarking sharpened the picture. The median product sees only 6.4% of its features drive the bulk of usage, and even products in the top 10% reach just 15.6%.
Four in five features. Built, shipped, invisible.
Product teams usually frame low adoption as a design or prioritization problem. Sometimes it is. A meaningful share of it’s a distribution problem wearing a product costume, because a feature can’t get adopted by an account that never learned it exists. Most SaaS companies have exactly one mechanism for telling customers what shipped: announcements inside the product.
Play it out with a concrete case. Your team ships the reporting feature your churned customers kept citing in exit surveys. Power users find it within a week because they read everything. The mid-market account that’s been wobbling for two quarters never sees it, because their team stopped logging in daily back in spring, and the announcement banner expired before their next session.
Those announcements have a structural flaw. They only reach users who log in. The accounts drifting toward churn log in the least, so the customers who most need a fresh reason to come back are the ones your announcement banner reaches last, or never. Email is the one channel you own that still reaches an account after the logins stop.
A feature your customer never heard about performs exactly like a feature you never built. The engineering bill is the only difference.
What Does the Silence Cost at Renewal?
B2B SaaS renewals carry a quirk that makes silence expensive. The person who signs the renewal is rarely the one who uses the product every day. The buyer watched a demo 14 months ago, approved the invoice, and moved on to other budget lines. Their mental picture of your product froze on the day they bought it.
Renewal season evaluates that frozen picture. Your daily users might be aware of the six capabilities you’ve shipped since the contract started. The budget holder doesn’t, and budget holders don’t read release notes. They read email, in the same inbox where the budget conversation already lives.
There’s a second version of the same problem. Champions change jobs. The person who fought to buy your product leaves, and their successor inherits a line item with no context and no loyalty. Every issue you send is an automatic onboarding for that successor, running in the background before you even learn the champion left.
Surprising? Only if you’ve never sat on a renewal call where the buyer requested a feature you shipped in 6 months ago.
Renewal is a memory test, and the person taking it was never in the product. The account renews on what the buyer can recall.
I covered the research on buyer memory and timing in the 95:5 rule breakdown, and the mechanics get sharper in SaaS: the renewal date is known, the decision maker is identifiable, and the channel that reaches them is sitting in your stack already.
Why Is Expansion Revenue the Cheapest Revenue You’re Ignoring?
The strongest argument for a SaaS customer newsletter sits in a survey most SaaS operators can quote and few act on. The 2016 Pacific Crest SaaS Survey, published by David Skok at Matrix Partners, measured what companies spend to acquire one dollar of annual contract value.
A new customer dollar cost a median of $1.13. An upsell dollar cost $0.27. An expansion dollar cost $0.20, and a renewal dollar cost $0.13.
The survey is a decade old and remains the canonical reference because the shape of the findings still holds. Paddle’s analysis of expansion revenue cites the same figures and adds the payback math: recovering the cost of a new customer takes most companies over a year, while an upsell pays for itself in about a quarter.
Let the spread sit for a second. Then check which dollar your marketing budget chases.
Expansion has one hard dependency the spreadsheets skip: the customer must know the bigger plan, the add-on, or the new capability exists. Every upgrade is an informed decision, and you control the flow of information. An account that hears from you monthly knows what the next tier unlocks long before the need arrives. An account that hears from you annually learns about your roadmap from your invoice.
Picture the alternative running for six months. Your March issue explains the new API tier through a customer who automated their weekly export. Your June issue shows the add-on that removes a manual step your mid-tier accounts complain about in support tickets. By the time an account hits the ceiling of their plan, the upgrade conversation is a confirmation, because the sales work happened one useful email at a time.
No judgment. Nobody staffs the announcing. Every SaaS org chart has owners for building and owners for selling, and the job of telling existing customers what got built falls into the crack between product marketing and lifecycle email. At a company under 50 people, that crack usually contains nobody.
The cheapest revenue in SaaS requires zero new leads. It requires existing customers who know what you shipped, and almost no company assigns that job to anyone.
What Should a SaaS Customer Newsletter Contain?
The default move is a blog digest with three links and a banner. Customers delete it in one second, the open rate sinks, and the channel takes the blame the content earned.
A SaaS customer newsletter that moves adoption and expansion runs on four ingredients:
- One shipped feature, explained through the job it does. A screenshot, two sentences on the pain it removes, three steps to try it. The full tour belongs in your docs. The newsletter sells the moment the feature earns its click.
- One customer story or use case. The fastest adoption trigger available is proof that an account like the reader’s already gets value from the thing they’ve been ignoring.
- One roadmap signal. A single sentence on what’s coming keeps the buyer’s frozen picture in motion and hands your internal champions ammunition for the next budget meeting.
- One genuinely useful industry insight. This earns the open on months when the release cycle was quiet, and it’s the section that turns the email into a publication people expect.
Cadence follows the same rule I laid out for every business list in the cheapest growth channel breakdown: the right frequency is the one you can hold for a year. For SaaS specifically, monthly is the floor, because the buyer’s memory and your release velocity both decay faster than a quarterly send can repair.
Your Ship number, which you’re about to calculate, is a marketing calendar you’ve been throwing away every quarter.
The Ship-to-Tell Ratio
You can price your own silence in about fifteen minutes with two browser tabs. Run the five steps in order.
Step 1: Count what you shipped. Pull the changelog for the last full quarter and count every item a customer would care about. Features, integrations, meaningful improvements. Skip the bug fixes. That total is your Ship number.
Step 2: Count what you told. In your email platform, count the sends from that same quarter that explained at least one of those items to the full customer list. Sends to a segment of active users don’t count, because the accounts at risk live outside that segment. That total is your Tell number.
Step 3: Divide Tell by Ship. A team that shipped 24 meaningful items and sent two announcement emails runs a Ship-to-Tell Ratio of 8%.
Step 4: Read the result as inventory. Everything under 100% is value you paid to build and declined to distribute. Expect a single digit. The ratio has no owner at most SaaS companies, and unowned numbers drift toward zero.
Step 5: Pick the three shipped items with the clearest revenue relevance. The ones tied to a paid tier, a renewal argument, or a churn objection. Those three lead your first issue.
Rerun the ratio quarterly. A newsletter on a monthly rhythm pushes it toward 100% without a single heroic launch email, and the quarterly number tells you whether the channel is actually carrying your roadmap.
Who Runs It, and in Whose Voice?
The reasons company newsletters die are documented, and all three are production failures: no owner, no system, no voice. The first reflex under deadline pressure is handing the draft to a generic model, and the output reads like a mediocre vendor wrote it. My cofounder Eren has cataloged what that erases on the craft side, and customers feel the swap even when they can’t name it.
This is the problem the HeyNews Company Newsletter was built for, and SaaS companies are its cleanest fit, because your raw material is already digital. HeyNews learns how your company sounds from your site, your docs, and your past sends. Point it at your own changelog feed and your blog, and every shipped feature becomes a candidate for a scored story. On your cadence, a full issue arrives drafted in your voice, and nothing goes out without your team’s approval, on every single issue.
There are two ways to run it. Run it in-house, with HeyNews as the production tool: connect your platform and ship your next issue this week. Or delegate the recurring production to our team, keep the final review, and spend your minutes on the approve button. Either way, the judgment stays where the liability lives: with you.
In a Nutshell
- Most shipped features go unseen. Pendo’s data puts rarely or never used features at 80% of the average product, and the distribution share of that number is fixable with a send button.
- Renewals run on the buyer’s memory, and the buyer isn’t in your product. A monthly issue keeps their picture of your product up to date and automatically onboardes successor champions.
- Expansion revenue costs a fraction of new revenue per the Pacific Crest survey, and every upgrade depends on customers knowing the upgrade exists.
- Run the Ship-to-Tell Ratio this week: quarterly shipped items versus full list announcements. The diagnostic works with any toolchain and takes fifteen minutes.
- A cadence you can hold beats a launch email you can admire. Monthly is the floor for SaaS.
Go back to the two numbers from the top of this post: the changelog count and the sent count. The distance between them is marketing you already paid for, sitting in a warehouse. Your engineers funded the newsletter. The only missing piece is the send.
The next step takes fifteen minutes: run the ratio, pick your three features, and put a recurring issue on the calendar. If you want the production carried out for you while your team keeps the judgment, see how the Company Newsletter works.
