Thanks for your comment. I can see where you are coming from, but at the same time I think it's a bit harsh to suggest that dApp operators are incapable of understanding how to run their project in ways that lead to growth - even with significant help.
If Hive's whales mostly want businesses to grow on Hive and to bring money in to the system instead of it constantly leaving, then there's no way around the fact that the projects need to become as directed towards growth as possible - which requires access to good data.
The proposal here is intended to advise everyone on Hive, including the people who vote for proposals, so that there is some way to understand whether projects are heading in helpful directions.
It's definitely true that dApps can all ignore everything that is discovered/shared, but I'd be pretty surprised if they did that. I spoke to several of the big dApp operators before writing the proposal and they all said essentially the same thing, that they really need something like this proposal in order to help their own strategy.
As with the Ignite proposal and other marketing proposals, there is no way to know whether the results will be powerful or not, without going ahead and trying it. I had expected that Ignite would produce research and reports of the kind I am suggesting here, but (partially) since they didn't we are still mostly in the dark as to how to navigate this situation.
We are due - this year (allegedly) - to see substantial improvements to Hive's feature set, so now is the perfect time to be laying a foundation for growth based on real world data. :)