how to announce a new feature without sounding salesy

“We’re thrilled to announce our new dashboard feature that empowers teams to streamline their workflow and drive better outcomes!”

Nobody is reading that. Nobody is engaging with that. It sounds like a press release written by a committee.

Feature announcements are one of the easiest content types for founders — you literally just shipped something. But most founders announce features the wrong way: corporate tone, vague benefits, zero personality.

Here’s how to do it better.

Why most feature announcements fail

They fail for three reasons:

1. They describe the feature, not the story. “We added CSV export” is a feature. “3 users screenshotted our analytics to share with their teams, so we built CSV export” is a story. Stories get engagement. Features don’t.

2. They use corporate language. “We’re excited to announce” / “empowering teams to” / “driving better outcomes” — this is the language of companies, not humans. Your audience follows a founder, not a brand.

3. They don’t explain why it matters. Your user doesn’t care about CSV export. They care about saving 20 minutes copying data into spreadsheets. Lead with the outcome, not the feature.

The 4-part feature announcement framework

1. Start with the problem or the trigger

What caused you to build this? A customer request? A pain point you observed? Your own frustration?

“I watched a customer screen-share last week and noticed they were copy-pasting data from our dashboard into Excel. Row by row. For 15 minutes.”

2. Show what you built (briefly)

One sentence about the feature. Don’t over-explain.

“So we built CSV export. One click, all your data, formatted and ready.”

3. Share the impact or expected outcome

Why does this matter? What changes for users?

“That 15-minute manual process is now 3 seconds.”

4. Add a human element

A reflection, a lesson, or a question that invites engagement.

“Building features is easy. Watching users struggle and figuring out which struggles are worth solving? That’s the actual job.”

Real examples of good feature announcements

The “user feedback” angle

“our most-requested feature for 6 months: dark mode.

shipped it this morning.

the funny thing? it took 2 days to build but 6 months to prioritize. there was always something ‘more important.’

lesson: if your users keep asking for something, it IS the important thing.”

The “metrics” angle

“added a search filter to our dashboard.

before: users clicked through 4 screens to find what they needed. average time to answer: 47 seconds.

after: one search bar. average time to answer: 6 seconds.

8x faster. the best features aren’t new capabilities — they’re faster paths to existing ones.”

The “behind the scenes” angle

“this feature took 3 rewrites.

v1: overcomplicated. tried to solve 5 problems at once. v2: too simple. solved the wrong problem. v3: just right. one problem, one solution, clean implementation.

shipping isn’t always linear. sometimes the shortest path to good is through two bad versions.”

What to avoid

• Don’t use the word “excited.” It’s the most overused word in feature announcements.
• Don’t list every technical detail. Save that for the changelog.
• Don’t make it about you. Make it about the user’s problem and how it’s now solved.
• Don’t add a hard sell. “Sign up now!” after a feature announcement kills the authenticity.

Let your shipping speak for itself

Ravah generates feature announcements from your product context — the feature, the user problem, and the story behind it. No corporate language, no “we’re thrilled” — just founder-authentic content.

Related reading: How to Write Changelog Posts, Turn Shipping Into Content, Product Launch Post Guide, What Is Changelog Content?, What Is Product-Aware Content?