Topic voting category for public feature requests
Keep feature requests in a dedicated voting category so demand gathers on one public thread instead of splintering across duplicate asks.
Why this can grow a startup
A public forum gets messy fast when feature requests arrive as plain conversation. The same idea gets posted three times, support cannot point prospects to one live record, and product loses the compounding signal of visible demand. Discourse Topic Voting gives a cleaner lane by letting specific categories run on votes. That makes each request page work harder. It becomes a demand counter, a place for clarifications, and a public artifact sales or success can reuse. The gain is not just prioritization. It is a more legible product story in public.
Source-backed example
Discourse's official Topic Voting plugin lets admins enable voting on topics inside specified categories.
Source-reported evidence
Source: Discourse Meta: Discourse Topic Voting
Topic Voting gives users the ability to vote on topics in a specified category.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 29, 2026
When to use it
Use this when Community, Product, Sales is relevant to feature requests, community signal, roadmap trust and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Community and Product, using evidence from Discourse Meta: Discourse Topic Voting as context—not as a promised result.
- Record a baseline for: Qualified conversations that advance to the next sales stage. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.