The 2026 State of Sales Enablement: Launched But Never Sold

What did 1,000+ hours of sales calls tell us about product launches?

Half of all launches were never mentioned by the sales team in the 90 days after they shipped. 

I wanted to answer a question nobody seems to have real data on: when Product ships something, does Sales actually sell it? Everyone measures the launch by what went out the door, which is why activity measure dominate. Almost nobody measures the output on whether a rep ever said the feature's name to a customer. That is ultimately the goal of sales enablement. Did it result in more reps selling more products that resulted in more revenue? We analyzed over 1,000 hours of recorded sales and customer calls to find out.

Here's what we found.

The headline numbers

• 50% of launches were never mentioned by the sales team in the 90 days after shipping
• 41% were never mentioned on any customer call by anyone
• 53% of the shipped portfolio had zero customer-call mentions in the last 90 days.
• The top 10% of features get about 65% of all feature talk on calls. This goes a long way to explaining why 80% of features are rarely or never used.
• Only 2% of accounts that asked for a feature heard about it on a later call after it shipped. Even among accounts that had another call after launch, only 10% heard about it.
• When a launch does get mentioned, the first mention comes a median of 17 to 29 days after it ships.

For sales enablement: do reps pitch what they're told about?

Mostly no which won't surprise you, but the reasons will.

1. About a quarter of alerts turn into a pitch: 24% of rep alerts were followed by that rep mentioning the feature within 30 days. 58% of alerted reps mentioned at least one feature they were alerted about. So the message lands with most reps, but any single feature only gets picked up a quarter of the time.
2. Reps talk about roughly three features per call: Reps mention 3.2 to 3.4 features per call, and about 2.3 of those are shipped features (the rest are things that don't exist yet). The spread between reps is big: top-quartile reps mention roughly 2 to 3 times as many shipped features per call as bottom-quartile reps.
3. It takes about a month: The median time from launch to first pitch was 17 to 29 days. Only about 31% of launches got mentioned within the first 30 days.
4. Half the portfolio is invisible: 53% of shipped features had zero customer-call mentions in the last 90 days. If you sell multiple products, this is the number to worry about. Your reps are selling a small slice of what you've built.
5. Targeting is the hard part, and it works. Arkweaver's alerts reached the reps who were 8x more likely to pitch the feature.
6. Reps mentioned 24% of launches they were alerted about, against 3% of other launches: The point isn't that a notification magically makes a rep sell. It's that finding the right rep for the right feature is most of the battle, and that's the part a release note to the whole team can't do. (More on this in sales enablement strategy when AI speeds up feature shipping.)

I went deeper on what this means for enablement teams in why sales teams don't pitch half of new product features.

For product marketing: does anyone hear about what shipped?

1. Half of launches get nothing: 50% were never mentioned by the sales team within 90 days of launch
2. 41% were never mentioned on a customer call by anyone at all: If you're a PMM wondering why feature adoption stays flat even when you're shipping more than ever, start here.
3. The people who asked almost never hear back: Only 2% of accounts that requested a feature heard about it on a later call after it shipped. Even when those accounts had another call after launch, only 10% heard about it. One caveat: I could only measure calls. If a customer got an email or an in-app message, that wouldn't show up here. But a call is where a rep turns "you built my thing" into a deal, and that's almost never happening. (Here's how to notify prospects when a feature they asked for ships.)
4. Features get talked about. Just not with the right people: Features actually came up in more meetings after launch than before. The talk happens, it just doesn't reach the customers who asked for them. More on that in 90% of customers who asked for a feature weren't told it shipped on their next calls.

What to do about it

1. Measure pitches: For every launch, track which reps mentioned it on relevant calls in the first 30 days. That's the real enablement metric. I wrote about this in how to measure product marketing success.
2. Route features to the right reps: A release note to the whole team gets ignored, you know this. A message to the reps whose deals need that feature gets used.
3. Close the loop with requesters: If you only remember one thing, do this. The accounts that asked are your warmest leads. Tell them it shipped, on purpose, instead of hoping it comes up.
4. Watch the silent half of your portfolio: If 50% of launches never come up, decide which ones deserve a push and which ones didn't need a launch in the first place.

This is exactly what we built Arkweaver to do: tie every feature to the customers who asked for it and the reps who should be selling it, then show you whether they did. You can see it in action in how OhMD turned 20+ new features a month into revenue.

How we did this

• Data: over 1,000 hours of sales and customer calls recorded in Gong (2,200+ calls) from Arkweaver customers, covering several months.
• Launches analyzed: 410 launches, each matched to its ship date from the customer's engineering tracker.
• Finding mentions: Arkweaver's extraction model read every transcript and pulled out each place a feature was discussed, along with the exact line that was said.
• Verifying them: a mention only counted when those exact words were found in the call transcript.
• Who said it: each speaker was matched to Gong's attendee list, which labels every attendee as internal (the selling company) or external (the customer). Internal speakers count as a team mention; external speakers count as the customer bringing it up.
• Which feature: a second AI step matched each mention to the feature on the roadmap or in the engineering tracker and recorded how confident the match was.
• Before or after launch: the call date was compared to the feature's ship date. Calls after the ship date count as post-launch mentions.
• "Sales team" means anyone from the selling company on the call (sales, account management, customer success, solutions engineering). "Anyone" also includes the customer.
• Ranges: results varied by company, so where they differed we report a range instead of a single number.
• Privacy: all data is aggregated and anonymized. No customer, rep or account is identified.

FAQ

What percentage of product launches do sales teams actually mention?

In our analysis of 1,000+ hours of sales calls, 50% of launches were never mentioned by the sales team in the 90 days after shipping, and 41% were never mentioned on any customer call by anyone.

How long does it take sales reps to start pitching a new feature?

When a launch got mentioned at all, the first mention came a median of 17 to 29 days after it shipped. Only about 31% of launches were mentioned within 30 days.

Do customers who request a feature find out when it ships?

Rarely, at least on calls. Only 2% of accounts that asked for a feature heard about it on a later call after it shipped, and only 10% of those who had another call after launch.

How can I measure whether my reps are pitching all our products?

Track, for each product or feature, which reps mentioned it on calls where it was relevant, starting from the ship date. Look at the share of reps who pitched it within 30 days and the share of your portfolio that never comes up. Content views and training completions don't tell you this; call data does.

Do rep alerts increase how often features get pitched?

Alerts in our data reached reps who were 8x more likely to pitch the feature, but that's mostly because they were sent to reps already in relevant conversations. The value is in targeting the right rep, not in the notification itself.