# How to Announce a New SaaS Feature > How to announce a new SaaS feature effectively, including deciding launch tier, messaging, in-app announcements, emails, changelogs, sales enablement and measurement. Source: https://comppound.com/blog/how-to-announce-a-new-saas-feature (published 2026-08-12) A new feature only creates value when customers know about it and start using it. That sounds obvious, yet many SaaS companies ship genuinely useful features that go almost entirely unnoticed. The announcement is buried in a changelog that few customers read, or it goes out as a generic email listing six updates that nobody opens. Months later, a customer asks support whether the product can do something it has been able to do since the spring. A good feature announcement explains why the feature matters, who it is for and how to start using it. It reaches the right people through the right channels, and it is sized to match the importance of the feature. This article covers how to decide how big a launch a feature deserves, how to craft the message, which channels to use, how to prepare internal teams and how to measure whether the announcement worked. We will use the example of a customer onboarding platform for [B2B SaaS](/blog/what-is-programmatic-seo-a-b2b-saas-guide-to-scaling-organic-traffic) companies. Its product team has just shipped automated task assignment, which assigns onboarding tasks to the right person on the customer's side and the vendor's side the moment a new customer signs up. ## Decide how big the launch should be Not every feature deserves a major launch, and treating every update as a big announcement trains customers to ignore your announcements. A simple tier system helps match effort to importance. The first tier is a major launch. It covers significant new capabilities that affect your positioning, open up a new use case or are likely to attract new customers. A major launch typically includes a blog post, an email to all users and relevant prospects, an in-app announcement, a social media campaign, enablement for the sales team, and sometimes outreach to press, partners or industry newsletters. The second tier is a notable feature. It covers useful improvements that many existing customers will appreciate but that do not change the product's core story. A notable feature usually gets a changelog entry, an in-app announcement for relevant users, a section in the customer newsletter or a short dedicated email, and a social post. The third tier is a small improvement. It covers minor enhancements and fixes. These belong in the changelog and release notes, where interested customers can find them, without a wider announcement. Automated task assignment is a notable feature for the onboarding platform. It saves customer success teams real time, but it extends an existing capability rather than changing what the product is. That decision shapes everything that follows. ## Craft a message that answers the customer's questions A good announcement answers five questions. What is it? Who is it for? What problem does it solve? How does it work? How do I start? Lead with the customer benefit rather than the technical description. "We have added rule-based task assignment to the onboarding engine" describes the feature from the inside. "Now you can automatically assign onboarding tasks the moment a new customer signs up, so no setup step gets missed" describes it from the customer's point of view. The second version tells the reader immediately why they should care. Be specific about who benefits. If the feature mainly helps customer success managers who handle many accounts at once, say so. People are more likely to pay attention when an announcement clearly speaks to their situation. Keep the explanation of how it works short, and point to a help article or short video for detail. Then make the next step obvious, whether that is a button to try the feature, a link to a setup guide or a template that shows the feature in action. ## Use in-app announcements for existing users In-app announcements reach customers at the moment they are using the product, which makes them one of the most effective channels for driving adoption. Show a short message that explains the benefit and links directly to the feature or a guide. Target these messages carefully. Show them to users whose role, plan or usage suggests the feature is relevant. A customer success manager who sets up onboarding plans should see the task assignment announcement; a finance user who only reviews invoices should not. Untargeted in-app messages quickly become noise that users dismiss without reading. Time them sensibly too. An announcement that interrupts a user in the middle of a task is likely to be closed immediately. Placing it on a dashboard, or showing it when a user visits the relevant area of the product, tends to work better. ## Email the customers who will benefit Email reaches customers who are not currently in the product. For a notable feature, send a short email to customers who would benefit, or include a clear section in the regular customer newsletter. Include a screenshot or a short video showing the feature in action, since seeing it is often more persuasive than reading about it. Keep the email focused on one feature rather than a long list, if the feature deserves dedicated attention. For major launches, a dedicated email to all users and relevant prospects makes sense, often with a follow-up a week or so later for those who did not engage. ## Keep a changelog A changelog documents every update, large and small. It serves customers who want to stay informed, helps support and sales teams answer questions about what has changed, and provides a reference when someone wants to know when a capability was added. Write changelog entries in plain language, focused on what changed for the customer. Link from them to help articles and, for bigger features, to the blog post or announcement. ## Write a blog post for major features For major launches, a blog post gives you space to explain the problem the feature solves, how it works and how different customers can use it, with examples and screenshots. A good launch post reads like a useful article rather than a press release. It explains the context, shows the feature solving a real problem and helps readers decide whether it is relevant to them. Launch posts can also attract new visitors through search if they address questions people are already asking. A post about automating onboarding task assignment, for example, might rank for searches from customer success leaders looking for ways to reduce manual setup work. Writing launch content with search in mind is part of what a structured [SEO growth program](/services/seo-growth) covers. ## Share on social media Social posts help reach prospects and customers who follow your company, and they give the people who built the feature a chance to share their work. A short video or animated screenshot often performs better than text alone. For notable features, a single post may be enough. For major launches, plan several posts over a week or two, covering different angles and use cases. ## Prepare sales, support and success teams Internal teams need to know about a feature before customers do. Sales needs to know how to position it, which prospects care about it and how it compares with competitors. Support needs to know how it works and what problems customers might run into. Customer success needs to know which accounts would benefit, so they can mention it in check-ins and quarterly reviews. Provide a short internal brief covering what the feature does, who it is for, how to explain it, common questions and where to find documentation. For major launches, a short internal demo session is worthwhile. Customers lose confidence quickly when they ask a support agent about a feature the company just announced and the agent has never heard of it. ## Announce to prospects where it helps Features can be useful in marketing to prospects as well as customers. For major launches, update the relevant product pages on your website, mention the feature in sales outreach to prospects who have shown interest in that capability, and consider including it in nurture emails. For notable features, update product pages and sales materials so the feature becomes part of how the product is described. ## Follow up to drive adoption An announcement is the beginning of adoption, not the end. A few weeks after launch, check which customers have started using the feature and which have not. Follow up with relevant non-adopters through a targeted email, an in-app prompt or a mention by their customer success manager. Share examples of how early adopters are using the feature, with their permission, since real examples encourage others to try it. For the onboarding platform, customer success managers mention automated task assignment in their next check-in with any account that onboards more than a few new customers a month, since those accounts stand to save the most time. ## Measure whether the announcement worked Track a few metrics to judge the announcement's success. The most important is adoption: the share of relevant customers who start using the feature within a set period. Look at engagement with each channel, such as in-app message clicks, email opens and clicks, and blog post traffic, to see which channels drove awareness. Watch for retention or expansion effects among customers who adopt the feature. And track support questions about the feature, which can reveal confusion that the announcement or documentation should address. Compare results across launches over time. You will learn which channels work best for your customers and how to size announcements appropriately. ## Avoid the common mistakes The mistakes in feature announcements are predictable. Teams bury important features in changelogs that few people read. They announce every minor update with the same fanfare, so customers stop paying attention. They describe features in technical terms instead of customer benefits. They send untargeted messages to everyone. They forget to prepare internal teams. And they stop at the announcement without following up to drive adoption. ## Bringing it together Announcing a new SaaS feature well means sizing the launch to the feature, writing a message that explains the benefit, the audience and how to start, choosing channels that reach the right people, preparing internal teams, following up to drive adoption and measuring results. The onboarding platform's automated task assignment reaches the customer success managers who need it, through in-app messages, a focused email and their regular check-ins, and within a few weeks it has become part of how many of those teams set up every new customer. ## Keep reading - [What New Feature Page Ranking Means for Google and AI](/blog/new-feature-page-ranking-google-vs-ai-answers) ## Frequently asked questions ### How should SaaS companies announce new features? Choose a launch tier, explain benefits clearly, use relevant channels like in-app messages and email, and enable sales and support. ### Do all features need an announcement? No. Small improvements may only need changelog entries, while major features deserve broader launches. ### How do I measure feature launch success? Track announcement engagement, feature adoption, usage and impact on retention or expansion. ## About Comppound Comppound runs SEO and AI search for B2B SaaS companies: a person sets the plan and reviews samples and every high-risk page, and AI speeds up production. - [Check a page free](https://comppound.com/tools/seo-checker): Check one of your pages before you change anything else - [See pricing](https://comppound.com/pricing): Want the content written, reviewed and published for you?