Growth idea action plan
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.
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 activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. 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 canny voter export for beta recruitment can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Product and Lifecycle 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
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: Appcues Case Study | Canny (canny.io)
GrowthDex source hub: Appcues Case Study | Canny
Last checked: 2026-05-30
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Canny entrypoints across nav, app, email, and support same source · 2 shared channels
- Canny top-20 MRR temperature check same source · 1 shared channel
- Adjacent-product onboarding email loop 2 shared channels · 1 shared stage
- Login-page cross-sell billboard 2 shared channels · 1 shared stage
Related GrowthDex essays
- The feedback board should recruit the beta cohort before the roadmap meeting community-led growth, product ops, brand trust
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