# Canny top-20 MRR temperature check

> Keep a short list of the twenty requests with the strongest mix of MRR and votes so roadmap debates start from commercial reality instead of raw volume.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/canny-top-20-mrr-temperature-check/
- Source: [canny.io](https://canny.io/case-studies/appcues)
- GrowthDex source hub: [Appcues Case Study | Canny](/sources/appcues-case-study-canny-canny-io/)
- Last checked: 2026-05-30
- Rarity: epic
- Budget: mid
- Channels: Sales, Product, Analytics
- Stages: revenue prioritization, salesforce, roadmap review, commercial context
- Key metric: Appcues keeps a top 20 request list prioritized by MRR and number of votes.

## Why this can grow

Long boards create the illusion of rigor while hiding the few requests that can actually move revenue. Appcues tracks a top twenty list ordered by MRR and vote count, while their Salesforce integration pushes votes and comments back to account notes. That gives product, sales, and CX one compact review surface with enough context to make weekly calls. The useful part is not the exact number twenty. It is the discipline of forcing the team to look at a small commercial queue instead of admiring a large one.

## 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 canny top-20 mrr temperature check can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Sales and Product 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

Appcues sorts requests by MRR from Salesforce, keeps a top 20 "temperature check," and pushes Canny votes and comments into Salesforce account notes.

## Adjacent tactics in the same lane

- [Canny entrypoints across nav, app, email, and support](/growth-ideas/canny-entrypoints-across-nav-app-email-and-support/) - same source, 1 shared channel
- [Canny voter export for beta recruitment](/growth-ideas/canny-voter-export-for-beta-recruitment/) - same source, 1 shared channel
- [Microsoft Marketplace specific proof PDFs with tracked links](/growth-ideas/microsoft-marketplace-specific-proof-pdfs-with-tracked-links/) - 2 shared channels
- [Group onboarding with escape hatches and invites](/growth-ideas/group-onboarding-with-escape-hatches-and-invites/) - 2 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The feedback board should recruit the beta cohort before the roadmap meeting](/blog/the-feedback-board-should-recruit-the-beta-cohort-before-the-roadmap-meeting/) - community-led growth, product ops, brand trust

## Advisory

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