Canny voter export for beta recruitment
Recruit beta users from the people who already voted on the exact request instead of rebuilding the list from CRM notes after the feature is nearly done.
Why this can grow a startup
Beta recruiting is usually treated like a separate project, which means it starts late and pulls the team back into manual account archaeology. Appcues used one Canny post as the starting point: open the voter list, export it, and email the people who asked for the thing. Canny's help docs make that workflow explicit. The advantage is not just speed. The cohort is cleaner because it is made of users who already raised their hand on the same problem.
Source-backed example
Appcues said beta recruiting became easier because they could export the voter list for a feature request and email that exact group; Canny documents voter-list export directly from the post.
Source-reported evidence
Source: Appcues Case Study | Canny · Browse Appcues Case Study | Canny tactics
Canny lets teams export the voter list for any post, and Appcues used that workflow to recruit beta testers.
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 30, 2026
When to use it
Use this when Product, Lifecycle, Retention is relevant to beta testing, activation, feedback loop 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 Product and Lifecycle, using evidence from Appcues Case Study | Canny as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value action. 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
Connect activation, customer value, retention, and referral into one measurable loop.
SOURCE HUB
More tactics from Appcues Case Study | Canny
Explore related GrowthDex examples and evidence connected to Appcues Case Study | Canny.
Open Appcues Case Study | Canny source hub