# Canny seed known requests before opening the board

> Preload the board with the requests you already hear every week so early visitors react to a useful forum instead of an empty room.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/canny-seed-known-requests-before-opening-the-board/
- Source: [canny.io](https://canny.io/case-studies/hapily)
- GrowthDex source hub: [hapily Case Study | Canny](/sources/hapily-case-study-canny-canny-io/)
- Last checked: 2026-05-30
- Rarity: uncommon
- Budget: free
- Channels: Community, Product, Onboarding
- Stages: cold start, feedback portal, duplicate reduction, launch setup


## Why this can grow

New request boards often fail because the first users arrive before the team has given the space any shape. hapily seeded the board with known requests during setup, which made product discussions more focused from the start. That matters because an empty forum asks users to do all the interpretation work alone. A seeded board shows that the team already understands the recurring problems, and it gives fresh voters a faster way to join an existing thread instead of creating near-duplicates.

## 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. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. 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 seed known requests before opening the board can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community 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

hapily said they seeded the boards with known requests during setup, and then used those boards for more focused product discussions.

## Adjacent tactics in the same lane

- [Prospect vote required before feature promise](/growth-ideas/prospect-vote-required-before-feature-promise/) - same source, 1 shared channel
- [Community template copy lands in your personal drafts](/growth-ideas/community-template-copy-lands-in-your-personal-drafts/) - 3 shared channels
- [Airtable interface form keeps contributors out of the backend](/growth-ideas/airtable-interface-form-keeps-contributors-out-of-the-backend/) - 3 shared channels
- [Teams default install scope matches the first job](/growth-ideas/teams-default-install-scope-matches-the-first-job/) - 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.