# Open roadmap comments for beta-tester recruiting

> Keep feature requests and roadmap discussion public so the people who comment become the next interview list, beta cohort, and launch ring.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/open-roadmap-comments-for-beta-tester-recruiting/
- Source: [newsletter.posthog.com](https://newsletter.posthog.com/p/the-hidden-benefits-of-being-an-open)
- GrowthDex source hub: [PostHog: The hidden benefits of being an open-source startup](/sources/posthog-the-hidden-benefits-of-being-an-open-source-startup-newsletter-p/)
- Last checked: 2026-05-29
- Rarity: uncommon
- Budget: free
- Channels: Community, Product, Research
- Stages: beta recruiting, feedback loops, community-led growth, launch readiness


## Why this can grow

A public roadmap is more useful when it behaves like a recruiting surface instead of a static wish list. People who comment on the feature they want are already telling you where demand is concentrated. That makes it easier to find interviewees, invite beta users, and keep follow-up tied to visible context. The loop improves research quality and gives the commenter a clearer path back into the product story.

## 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 open roadmap comments for beta-tester recruiting 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 newsletter.posthog.com 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

PostHog keeps feature requests and roadmap discussion open, asks people to comment on what they want next, and uses that activity to identify potential interviewees and beta testers.

## Adjacent tactics in the same lane

- [External docs PR path for community knowledge growth](/growth-ideas/external-docs-pr-path-for-community-knowledge-growth/) - same source, 1 shared channel, 1 shared stage
- [Issue or PR link instead of status handwave](/growth-ideas/issue-or-pr-link-instead-of-status-handwave/) - same source, 1 shared channel
- [Community wireframe email with inline comments](/growth-ideas/community-wireframe-email-with-inline-comments/) - 2 shared channels, 1 shared stage
- [Roadmap stage notifications for feature requesters](/growth-ideas/roadmap-stage-notifications-for-feature-requesters/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The trust surface should show the work](/blog/the-trust-surface-should-show-the-work/) - brand trust, community-led growth, SEO

## Advisory

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