Product Management Feature Validation Service

While working on one of the projects, we have built an internal system for the discovery and validation of new features. It obviously does much more then that, however, if I'd to summarize its value for a Product Manager that would be:

1. Would the feature ABC be used by the customer? Every feature comes as a visual (UI) element, documentation/guide/instructions, and functionality to it.

2. How the feature ABC would be used? E.g. how often is explored (customer curious about, but decided not to use), how often is used, a cohort of customers, phase/timeline of the product interaction lifecycle.

3. Is the hypothesis about feature ABC is correct? We believe feature ABC is needed, so we make the first step at presenting the opportunity to visually use the feature, however, let the customer describe his/her expectations first. E.g. clicking on the "arrow" next to the input field may cause one customer to expect a file upload option, while another customer to expect to use internal UI for data entry.

4. Lifecycle phase abandonment, but used for price experimentation mostly. Define the abandonment scenarios that collect feedback. We use it for price testing, however, I assume that might have different use cases also.

All of that is enabled through Google's Tag Manager, "NoCode" (requires no engineering time) with basic Zapiet-like integrations, captures as many variables as visible on the screen (to build a customer segmentation), and feature-flagged.

The team is thinking of productizing it as a service and allowing Product Managers to use in their early-stage products and experiments.

I'd appreciate your feedback on whether you find it useful for your products. The poll is quite simple, so it would be great if you can elaborate in the comments.