# Monday review of upvotes plus revenue attached

> Run a fixed weekly review that ranks requests by both demand and revenue so the roadmap starts from the same evidence every week.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/monday-review-of-upvotes-plus-revenue-attached/
- Source: [canny.io](https://canny.io/case-studies/paces)
- GrowthDex source hub: [Canny Case Study: Paces](/sources/canny-case-study-paces-canny-io/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Product, Growth, Sales
- Stages: prioritization, revenue context, weekly operating cadence, b2b
- Key metric: Paces reviewed demand every Monday and saw one request with more than $500K in attached revenue.

## Why this can grow

Teams often say they care about customer demand and commercial impact, then review each with a different spreadsheet on a different day. Paces tightened that loop by using a Monday dashboard review that combined the most upvoted requests with the ones carrying the most revenue. A fixed weekly cadence does two jobs. It gives the team a clean moment to compare sentiment with money, and it stops priority from drifting toward the loudest anecdote of the week. The habit matters as much as the dashboard because it keeps the same arguments visible in one room on a predictable schedule.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For conversion, I would strip the test down to one promise, one proof point, and one next step. Confusion kills good demand. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where monday review of upvotes plus revenue attached can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Growth channel.
3. Use the evidence from canny.io to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Every Monday, Paces' Growth team uses Canny dashboards to see which requests have the most upvotes and the most revenue attached, including one feature with more than $500K in revenue tied to it.

## Adjacent tactics in the same lane

- [Trial feedback board with frontline teams before full rollout](/growth-ideas/trial-feedback-board-with-frontline-teams-before-full-rollout/) - same source, 2 shared channels, 1 shared stage
- [Segment-filtered voter list with opportunity value](/growth-ideas/segment-filtered-voter-list-with-opportunity-value/) - 2 shared channels, 3 shared stages
- [Three-bucket feedback taxonomy before prioritization](/growth-ideas/three-bucket-feedback-taxonomy-before-prioritization/) - same source, 1 shared channel
- [Synced customer attributes for priority views](/growth-ideas/synced-customer-attributes-for-priority-views/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The feedback queue should carry revenue before volume](/blog/the-feedback-queue-should-carry-revenue-before-volume/) - product ops, feedback systems, revenue prioritization

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.