In particular, you'd probably want to know how a feature would impact future sales, survivorship curves for current customers, and survivorship curves for whichever kind of customer would sign on with the new feature (treating a single feature in isolation for simplicity). This is especially important when comparing multiple features to put on the roadmap because it's easy for one idea to be simple to imagine and better than the status quo (hence asked for by many customers) but be nowhere near an optimal solution to whichever problem is being solved.
Having that kind of customer insight is better than not having it, as long as such data is used appropriately -- without additional data it can't do much more that guide or refine gut feelings and insights, and attempting to do otherwise is a recipe for an inferior product.
A: We should definitely do X!
B: Why? Why not Y?
A: Because I'm the authority in the room
B: Well we talked to sales and customers and Y clearly has Z impact, on the other hand we saw no evidence of customers needing X.
than
A: We should definitely do X!
B: Why? Why not Y?
A: Because I'm the authority in the room
B: Whelp, ok I guess
Even imperfect shifts towards data-driven decision making can be valuable as well (eg maybe you have great data for optimizing your onboarding flow, even if knowledge of which features most improve retention or database performance are still black boxes).