Thanks, so after reading over the post, one thing I noticed was how to take a specific category, for example, configurability — and build it out based on real c

Thanks, so after reading over the post, one thing I noticed was how to take a specific category, for example, configurability — and build it out based on real customer demand. While might not be what you meant, one example would be reporting systems that basically let an end user build a report for anything. If you’re asking customers if they want it, frequently they well say yes, but regardless of if they know how to use it, frequently only build fix set of reports and never make adhoc reports. So, not expecting you to answer, but the question is, how do you identify if XYZ request is real, validate it, onboarding for customer success is appropriate, and kill it off correctly if users don’t use it to avoid pilling on tech debt. Next, actually remember seeing customer feature request trackers and found a few, though have tried to find someone actively managing these in the open: https://sourceforge.net/software/compare/Canny-vs-UserVoice-vs-productboard/ https://sourceforge.net/software/compare/Canny-vs-UserVoice-... Again, thanks — good luck getting your startup going!