Do customers who ask for a feature find out when it ships?
Almost never, at least not on a call. In our analysis of over 1,000 hours of sales and customer calls, accounts that asked for a feature and then had another call after it shipped heard about it only 10% of the time. 90% of the time, the customer who asked for the thing sat on a call with your team after it shipped and nobody mentioned it.
Across all requesting accounts, including the ones with no later call at all, only 2% heard about the feature on a call after launch.
This comes from a bigger study, with the full numbers and methodology in Launched But Never Sold: The 2026 State of Feature Sales Coverage. This piece is about what it means for product marketing.
Isn't that just a sales problem?
Partly. But it's the most expensive gap in the launch, and it usually falls between teams. Product marketing owns the launch. Sales or Account Management owns the account. It's hard to track a feature request throughout the entire cycle. So the corporate game of telephone corrupts the request and customers don't get told.
The surprising part: features do get talked about after launch
I expected the opposite. My guess was that customers would ask about a feature a lot before launch and then everyone would go quiet once it shipped. Instead, features came up in more meetings after launch than before. That means product marketing is working. It just doesn't reach the customers who asked. Those are the ones most likely to buy based on the product changes!
It's all about relevance. It's about knowing who the right account is, not the channel. Or as someone once told me, relevance eats personalization for lunch.
Why launches miss the people who asked
- Requests aren't tied to accounts: The ask lives in a call recording, spreadsheet, or a ticket. Even those building with Claude have a snapshot picture that is siloed from the rest of the company. Keep in mind that the businesses we studied for this are AI pilled.
- Launches go to everyone: A release note or an all-hands demo doesn't tell a rep "three of your accounts asked for this."
- Half of launches never come up at all. 50% of launches were never mentioned by the sales team in the 90 days after shipping, and the first mention for the rest came a median of 17 to 29 days after launch.
- Volume keeps going up: With AI speeding up engineering, there are more launches every month and the same number of PMMs. More on that in PMM can't keep up with AI feature velocity.
What should product marketing do?
- Tie every request to an account: When a customer asks for something on a call, record who asked and what deal or renewal it touches.
- Assign revenue to every request: How much revenue can be made by building this request? Then track it and improve.
- Close the loop on purpose: When it ships, tell the account owner which of their customers asked, and tell the customer directly. Here's how to notify prospects when a feature they asked for ships.
- Measure who heard, not what you sent: Track the share of requesting accounts that heard about the launch within 30 days. That's a much better launch metric than email opens. I wrote more about this in how to measure product marketing success.
- Fix the low-adoption launches first.:If a feature shipped and adoption was flat, check whether the people who asked ever found out. Often that's the whole problem.
This is what Arkweaver does: it pulls feature requests out of your calls, ties them to the accounts that asked, and tells the right reps and customers when the thing ships.
FAQ
What percentage of customers hear that their requested feature shipped?
On calls, very few. Only 2% of accounts that asked for a feature heard about it on a later call after it shipped. Among accounts that did have another call after launch, 10% heard about it, which means 90% didn't.
Why don't customers find out when their feature request ships?
Because requests usually aren't tied to accounts, and launches are broadcast to everyone instead of routed to the people who asked. By the time a feature ships, nobody remembers who wanted it.
How do I close the loop on feature requests?
Record who asked for each feature and which deal or account it affects. When it ships, notify the account owner with the list of requesters and reach out to those customers directly.
Do features get talked about more before or after launch?
In our data, after. Features came up in more meetings after launch than before. The gap isn't how much they're discussed, it's whether the customers who asked are part of those conversations.
