community-discovery
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCommunity Discovery
社区发现
When to Use
何时使用
- Founder wants to find online communities where their target customers are active
- Founder wants to identify channels for organic promotion and community-led growth
- Founder wants to build relationships in relevant communities before launching
- Founder wants to find beta testers, early adopters, or design partners
- Founder wants distribution beyond paid ads and cold outreach
- 创始人希望找到目标客户活跃的在线社区
- 创始人希望确定自然推广和社区驱动增长的渠道
- 创始人希望在产品发布前与相关社区建立关系
- 创始人希望寻找 Beta 测试者、早期采用者或设计合作伙伴
- 创始人希望探索付费广告和冷启动式外联之外的分发渠道
Context Required
所需上下文
- Target customer profile (role, industry, interests, seniority)
- Product category and the problem it solves
- What the founder wants from communities (feedback, users, partnerships, awareness)
- Founder's bandwidth for community engagement (lurk and post vs. become a regular)
- 目标客户画像(角色、行业、兴趣、资历)
- 产品类别及其解决的问题
- 创始人希望从社区获得什么(反馈、用户、合作关系、认知度)
- 创始人投入社区互动的精力(潜水观察并发帖,还是成为常规活跃成员)
Workflow
工作流
- Map the community landscape — identify where your target audience spends time online:
- Reddit: find subreddits by searching for the problem you solve, competitor names, and industry terms. Check subscriber count, post frequency, and moderation rules.
- Slack: search Slofile, Slack directories, and Google "[industry] slack community" to find relevant workspaces.
- Discord: search Disboard, Discord.me, and Google "[topic] discord server" for relevant servers.
- Forums & others: Indie Hackers, Hacker News, Stack Overflow, niche forums, Facebook Groups, LinkedIn Groups.
- Qualify each community — not all communities are equal. Score each on:
- Relevance: does your target customer actually hang out here?
- Activity: are there regular posts and discussions (not a ghost town)?
- Size: big enough to matter, small enough to stand out (sweet spot: 1K-50K members)
- Promotion tolerance: does the community allow product mentions, or is it strictly no self-promotion?
- Quality of discussion: are conversations substantive or just spam and memes?
- Categorize by engagement type — sort communities into:
- Promote: explicitly allows product sharing, launch announcements, or "Show X" posts
- Contribute-first: allows organic mentions if you're a genuine, helpful member first
- Listen-only: valuable for research and voice-of-customer, but no promotion allowed
- Build the engagement plan — for each community:
- Join and observe for 1-2 weeks before posting
- Identify the norms (how do regulars communicate? what gets upvoted/praised?)
- Plan your first 5 contributions (helpful answers, not product pitches)
- Plan when and how to introduce your product (if appropriate)
- Create the community map — output a prioritized list with engagement strategy for each.
- 绘制社区版图——确定目标受众在线活跃的场所:
- Reddit: 通过搜索你要解决的问题、竞争对手名称和行业术语来寻找相关 subreddit。检查订阅人数、发帖频率和版主规则。
- Slack: 搜索 Slofile、Slack 目录,以及 Google“[industry] slack community”,以找到相关 workspace。
- Discord: 搜索 Disboard、Discord.me,以及 Google“[topic] discord server”,以找到相关服务器。
- 论坛及其他平台: Indie Hackers、Hacker News、Stack Overflow、垂直论坛、Facebook Groups、LinkedIn Groups。
- 评估每个社区——不同社区的价值并不相同。依据以下维度进行评分:
- 相关性: 目标客户是否真的活跃于此?
- 活跃度: 是否经常有帖子和讨论,而不是一个无人问津的“鬼城”?
- 规模: 规模足够大,能够产生影响;同时又足够小,让你有机会被注意(最佳区间:1K-50K 名成员)
- 推广容忍度: 社区是否允许提及产品,还是严格禁止自我推广?
- 讨论质量: 对话是否有实质内容,还是只有垃圾信息和梗图?
- 按互动类型分类——将社区分为:
- 推广型: 明确允许分享产品、发布公告或发布“Show X”帖子
- 先贡献型: 如果你先成为真诚且乐于助人的成员,则允许自然地提及产品
- 仅聆听型: 适合用于研究和客户之声分析,但不允许推广
- 制定互动计划——针对每个社区:
- 加入并观察 1-2 周后再发帖
- 了解社区规范(常规成员如何交流?哪些内容会获得点赞或赞赏?)
- 规划前 5 次贡献(提供帮助,而不是推销产品)
- 规划何时以及如何介绍产品(如果合适)
- 创建社区地图——输出一份按优先级排序的列表,并附上每个社区的互动策略。
Output Format
输出格式
markdown
undefinedmarkdown
undefinedCommunity Map for [Product/Category]
Community Map for [Product/Category]
Tier 1 — High Priority (engage weekly)
Tier 1 — High Priority (engage weekly)
[Community Name] — [Platform]
- Link: [URL]
- Members: [count] | Activity: [posts/day or week]
- Relevance: [why your target customer is here]
- Rules: [promotion policy summary]
- Engagement type: [Promote / Contribute-first / Listen-only]
- Strategy: [specific plan — what to post, how to contribute, when to mention product]
- Key threads/channels: [specific channels or recurring threads to participate in]
[Community Name] — [Platform]
- Link: [URL]
- Members: [count] | Activity: [posts/day or week]
- Relevance: [why your target customer is here]
- Rules: [promotion policy summary]
- Engagement type: [Promote / Contribute-first / Listen-only]
- Strategy: [specific plan — what to post, how to contribute, when to mention product]
- Key threads/channels: [specific channels or recurring threads to participate in]
Tier 2 — Medium Priority (engage biweekly)
Tier 2 — Medium Priority (engage biweekly)
...
...
Tier 3 — Monitor (check monthly)
Tier 3 — Monitor (check monthly)
...
...
Engagement Calendar
Engagement Calendar
| Week | Community | Action | Goal |
|---|---|---|---|
| 1 | [name] | Join, read top 20 posts, identify norms | Understand culture |
| 2 | [name] | Answer 3 questions, no product mention | Build reputation |
| 3 | [name] | Share insight related to your space | Establish expertise |
| 4 | [name] | Soft product mention in relevant thread | Drive first traffic |
undefined| Week | Community | Action | Goal |
|---|---|---|---|
| 1 | [name] | Join, read top 20 posts, identify norms | Understand culture |
| 2 | [name] | Answer 3 questions, no product mention | Build reputation |
| 3 | [name] | Share insight related to your space | Establish expertise |
| 4 | [name] | Soft product mention in relevant thread | Drive first traffic |
undefinedFrameworks & Best Practices
框架与最佳实践
The 10:1 rule: Give 10 valuable contributions for every 1 product mention. Communities have long memories — one spammy post can get you banned and your brand damaged permanently.
Platform-specific tactics:
| Platform | Best for | Promotion approach |
|---|---|---|
| Problem validation, feedback, launch day | Answer questions in comments, share in relevant "share your project" threads. Never post direct ads. | |
| Slack | B2B relationships, warm intros | Be helpful in channels for weeks before mentioning your product. DMs only after building rapport. |
| Discord | Developer communities, gaming, crypto | Participate in discussions, share expertise, use #showcase or #self-promo channels if they exist. |
| Indie Hackers | Founder-to-founder, building in public | Share your journey with real numbers. The community rewards transparency over polish. |
| Hacker News | Developer/technical audience, launches | Show HN for launches. Don't astroturf. Substantive comments build reputation over months. |
| Facebook Groups | SMBs, local businesses, niche B2C | Join groups your customers are in. Respond to "looking for recommendations" posts. |
| LinkedIn Groups | Enterprise B2B, professional services | Low-signal, high-noise — generally not worth the effort unless very niche. |
Red flags — avoid these communities:
- More self-promo than real discussion
- Moderators are inactive or absent
- "Pay to post" or "pay for featured" requirements
- Last meaningful discussion was months ago
- Members are mostly other founders/marketers (not your actual customers)
Common mistakes:
- Joining 20 communities and being active in none (pick 3-5 and go deep)
- Leading with your product instead of being helpful first
- Copy-pasting the same message across communities
- Ignoring community rules and getting banned
- Giving up after 2 weeks because no one clicked your link
10:1 法则: 每进行一次产品提及,先提供 10 次有价值的贡献。社区记忆力很强——一条垃圾帖就可能让你被封禁,并永久损害品牌。
平台专项策略:
| 平台 | 最适合 | 推广方式 |
|---|---|---|
| 问题验证、反馈、发布日 | 在评论区回答问题,在相关的“share your project”帖子中分享。绝不直接发布广告。 | |
| Slack | B2B 关系、暖 introductions | 先在频道中提供帮助,数周后再提及产品。只有在建立信任后才能发送私信。 |
| Discord | 开发者社区、游戏、加密货币 | 参与讨论,分享专业知识;如果存在 #showcase 或 #self-promo 频道,可以在其中分享。 |
| Indie Hackers | 创始人之间、公开构建 | 分享带有真实数据的创业历程。社区更看重透明度,而不是表面包装。 |
| Hacker News | 开发者/技术受众、产品发布 | 发布时使用 Show HN。不要使用 astroturf。有深度的评论需要数月才能积累声誉。 |
| Facebook Groups | 中小企业、本地业务、垂直 B2C | 加入客户所在的群组。回复“looking for recommendations”类型的帖子。 |
| LinkedIn Groups | 企业级 B2B、专业服务 | 信号低、噪声高——除非群组非常垂直,否则通常不值得投入精力。 |
危险信号——应避开以下社区:
- 自我推广多于真实讨论
- 版主不活跃或长期缺席
- 要求“付费发帖”或“付费推荐”
- 上一次有意义的讨论已是数月之前
- 成员大多是其他创始人或营销人员(并非你的实际客户)
常见错误:
- 加入 20 个社区,却没有任何一个保持活跃(选择 3-5 个并深入参与)
- 一上来就推广产品,而不是先提供帮助
- 在不同社区复制粘贴同一条消息
- 无视社区规则,最终被封禁
- 仅仅因为两周内没人点击链接就放弃
Related Skills
相关 Skills
- — for direct outreach to individuals found through communities
cold-outreach - — for creating content to share in communities
content-strategy - — for using communities as launch distribution channels
launch-strategy - — to convert community traffic into signups
landing-page
- ——用于直接联系通过社区找到的个人
cold-outreach - ——用于创建适合在社区分享的内容
content-strategy - ——用于将社区作为产品发布的分发渠道
launch-strategy - ——用于将社区流量转化为注册用户
landing-page
Examples
示例
Prompt: "I'm building a tool for data engineers. Where should I be hanging out online?"
Good output includes: A prioritized map of communities — specific subreddits (r/dataengineering, r/apachekafka), Slack groups (dbt Slack, Data Engineering Weekly), Discord servers, relevant HN threads, and a 4-week engagement plan for the top 3.
Prompt: "We're launching our design tool next month. Which communities should I warm up in advance?"
Good output includes: Communities sorted by launch relevance (Designer Hangout Slack, r/UI_Design, Dribbble, specific Discord servers), a pre-launch engagement timeline, and specific "Show X" or "Share your project" threads to target on launch day.
提示:“我正在为数据工程师开发一款工具。我应该在线上哪些地方活动?”
优质输出应包括: 一份按优先级排序的社区地图——具体的 subreddit(r/dataengineering、r/apachekafka)、Slack 群组(dbt Slack、Data Engineering Weekly)、Discord 服务器、相关 HN 帖子,以及为优先级最高的 3 个社区制定的 4 周互动计划。
提示:“我们将在下个月发布一款设计工具。应该提前在哪些社区中预热?”
优质输出应包括: 按发布相关性排序的社区(Designer Hangout Slack、r/UI_Design、Dribbble、特定的 Discord 服务器)、发布前的互动时间线,以及在发布当天重点参与的“Show X”或“Share your project”帖子。