Feature requests
What customers keep asking you to build.
Thirty-one customers have asked for bulk export. Together they are worth a substantial share of your revenue, the first request was in May, and the rate is rising. That is a business case rather than a support comment.
Bulk export
Requested across support, counted automatically.
Customers asking
31
Combined value
€184,000
First requested
May
Trend
Increasing
The value of the customers who asked — not a projection of what building it would earn.
Counted across every conversation
Requests arrive scattered through support, buried in messages about something else. Collecting them automatically is the only way the count is ever accurate.
Value attached, honestly
How many customers, what they are worth, which segments, whether the rate is rising. Shown as the revenue of the customers who asked — not as a projection of what building it would earn.
Frequency is not priority
The most-requested thing is often not the most valuable. The page presents demand as evidence for a decision rather than as the decision, which matters because ranked lists get treated as roadmaps.
The requesters stay attached
When something ships, the customers who asked can be told. That is the highest-return message a company can send and it is almost never sent, because the link was never kept.
Questions this answers
The things you currently have to ask somebody.
Each of these is a question an owner asks regularly and currently answers from memory, a spreadsheet, or by interrupting whoever is nearest.
What are customers asking us to build?
Who asked for this, and what are they worth?
Is demand for this growing?
Which requests come from customers at risk?
Who should we tell now that this has shipped?
Where this stops
What it does not do.
This measures what customers asked for, which is not the same as what they need or would pay for. Customers routinely request a specific solution when they have a different underlying problem, and the page keeps the original wording so you can see that rather than hiding it behind a count. Resolivo is not a product-management tool: there is no roadmap, no scoring model and no prioritisation framework here.
Take better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]