News

Stop Announcing Features That Aren't Live Yet

AI companies keep announcing features before they're available. Here's why pre-launch hype frustrates users and what better rollout communication looks like.

You open an app after reading a company’s blog post about a major new feature. You look everywhere for it. It’s not there. You re-read the post, and buried in paragraph four is a line about a “gradual rollout to select plans over the coming weeks.” That’s not a launch. That’s a press release cosplaying as one.

This pattern has become a quiet epidemic across AI products, and it erodes exactly the kind of trust these companies are trying to build.

The Difference Between a Launch and an Announcement

There’s a legitimate reason to announce things in advance. Hardware pre-orders, developer API access, public roadmaps — these all serve a purpose. They let people plan, build, and budget.

But that’s not what’s happening here. What’s happening is that a product team hits an internal milestone, the marketing team gets excited, and a blog post goes out with present-tense language — “feature X is now available” — when the reality is that it’s available to maybe 5% of users and rolling out slowly to everyone else.

The reader who pays for a premium tier logs in expecting to find something new and finds nothing. They feel misled, because they were.

Why This Matters More for AI Products

In most software categories, a delayed feature rollout is a mild annoyance. In AI, it compounds.

People are making real decisions about which tools to pay for based on capability announcements. Someone choosing between two $20/month subscriptions might pick one specifically because of a feature they read was “now available.” If that feature is actually weeks away, that’s a purchasing decision made on incomplete information.

It also creates a strange loop where power users — the ones most likely to read launch posts, most likely to be on expensive plans, and most likely to spread word-of-mouth — are also the most likely to notice the gap between what was announced and what’s real. You’re frustrating your best advocates.

The Rollout Problem Isn’t the Real Issue

Gradual rollouts are fine. They’re actually good engineering practice. You don’t flip a switch for millions of users at once; you ramp up traffic slowly, watch your error rates, and expand when things look stable.

The problem isn’t the rollout. The problem is the communication wrapper around it.

Compare these two approaches:

Bad: Publish a blog post titled “Feature X Is Here” on day one of a six-week rollout. Most users won’t have it. Many will feel misled.

Better: Publish the post when the rollout is complete, or at minimum write honest present-tense copy: “We’re rolling out Feature X to all Pro and Max users over the next few weeks. You may not see it yet — here’s how to know when it arrives.”

The second version takes about thirty extra seconds to write and saves thousands of support tickets and frustrated forum posts.

What Good Launch Communication Looks Like

A few things that actually work:

  • Date-anchor your posts. “Available to all users by [month]” is more useful than “rolling out now.” If you’re not sure of the date, say that too.
  • Give users a way to check their own status. A simple settings flag or a status page beats leaving people to guess.
  • Reserve present-tense launch language for when it’s actually present. “X is live” should mean a user can open their app right now and find X.
  • Send a follow-up notification when the rollout reaches someone. An in-app ping that says “You now have access to Feature X” costs almost nothing and feels like a gift instead of a broken promise.

The Trust Ledger

Every time a company publishes a “now available” post for something that isn’t available, they make a small withdrawal from their trust account. It’s not catastrophic on its own. But AI tools are proliferating fast, switching costs are low, and users are developing sharp instincts for which companies are straight with them.

The companies that will win long-term aren’t necessarily the ones with the most features. They’re the ones whose users believe what they read. That reputation is built one accurate announcement at a time.

If the feature’s not ready for everyone, the blog post can wait. Genuine launches are worth more than early press.

Related