Growth idea action plan
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.
Why this can grow a startup
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.
Key metric to watch
Paces reviewed demand every Monday and saw one request with more than $500K in attached revenue.
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
- Define one narrow startup segment where monday review of upvotes plus revenue attached can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Product and Growth channel.
- Use the evidence from canny.io to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- 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.
Source: Canny Case Study: Paces (canny.io)
GrowthDex source hub: Canny Case Study: Paces
Last checked: 2026-05-29
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Trial feedback board with frontline teams before full rollout same source · 2 shared channels · 1 shared stage
- Segment-filtered voter list with opportunity value 2 shared channels · 3 shared stages
- Three-bucket feedback taxonomy before prioritization same source · 1 shared channel
- Synced customer attributes for priority views 2 shared channels · 1 shared stage
Related GrowthDex essays
- The feedback queue should carry revenue before volume product ops, feedback systems, revenue prioritization
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory