Why this matters
Raw feature-request counts overweight noisy accounts and underweight strategic customers. Revenue weighting gives product a better signal without turning the roadmap into a sales queue.
What you get
- Feature requests ranked by account value
- Request count by customer segment
- Expansion or renewal context for each request
- A short list of roadmap items to investigate
Walk through it
You
Which feature requests matter most commercially?
Agent
I’ll group request events by request key and weight them by account value and customer health.
POST /v1/projects/:project_id/analytics/query {
project_id: "default",
hogql: "SELECT properties.request_key AS request, count(DISTINCT properties.account_id) AS accounts, sum(toFloat(properties.opportunity_value)) AS opportunity_value FROM events WHERE event IN ('feature_requested','expansion_opportunity_created') AND timestamp > now() - INTERVAL 180 DAY GROUP BY request ORDER BY opportunity_value DESC, accounts DESC LIMIT 25"
}The output
The agent returns a ranked roadmap input, not an automatic roadmap. It should include request volume, revenue context, customer risk, and the next discovery question.
Setting it up
Emit feature request events from support, sales, feedback forms, or CRM sync. Use a normalized request key so the same request is not split across wording variants.
Variations
- “Show requests from renewing accounts only.”
- “Which requests block expansion?”
- “Compare revenue-weighted requests to usage pain.”