Community Organic

community-organic

The rule that governs everything: you are a guest.

Every community can tell the difference between a member and a marketer. A bad launch can cost the account, the channel, and the product's reputation. Treat each community as a place with its own owners, history, language, and permission rules. If a tactic works only because people misunderstand your role, do not use it.

1. Earn the right to post

Read the rules, pinned posts, FAQ, and recent moderation decisions before you post. Check whether it allows self-promotion, product links, launch posts, or requires account age, karma, membership, or moderator approval. Participate before you promote. Answer questions in your area. Explain a fix. Share useful sources. Ask good questions. Give feedback on other people's work. Do this from the account you will use for the launch. The practical estimate is two to four weeks of regular participation before a first launch. Some communities need longer. A new account with no useful history has no trust signal, even when the product is good. Hacker News currently tells unfamiliar users to learn the community and become good contributors before an occasional Show HN. See the Show HN update. Do not manufacture history. Ten shallow comments do not equal membership. A moderator can see the pattern, and readers can see the sudden change from helpful comments to links. Post only when you know the rule that permits it, have useful local history, can explain the problem without your product, and can answer criticism after posting. Otherwise, keep participating or ask a moderator first.

2. Hacker News

Hacker News rewards curiosity and discussion. It does not provide a free launch list. Do not use HN primarily for promotion or solicit upvotes, comments, or submissions. See the HN Guidelines.

Show HN has a narrow purpose

Use a Show HN for something people can try. The project must be something you built and can discuss. Make the demo easy to test. Avoid a signup or email gate when possible. Explain what you made and why it interests you.

The title must begin with Show HN. A landing page, fundraiser, newsletter, or article does not fit the Show HN format. A routine feature release usually does not fit either. See the Show HN guidelines. The common failure is a sales page disguised as a technical post. Readers flag it because the post asks for traffic while offering nothing to inspect. Show a working artifact, a clear problem, and the maker in the comments. Never ask friends, customers, or a private group to upvote or comment. HN explicitly rejects this. The request makes ordinary engagement look coordinated. It can lead to penalties or bans for the submission, account, or site. Stay in the thread. Answer hard questions and state limits. Do not argue with people who find the product uninteresting. Useful criticism is part of the launch.

3. Reddit

Reddit is a collection of communities, not one promotion channel. The subreddit rules control the decision. Read them before you post, even when another subreddit allowed the same content. Reddit says promotional content is not automatically spam. Some communities ban it, while others use a 10% self-promotion rule. Reddiquette gives a 9:1 rule of thumb. Treat both as signals, not universal laws. See Reddit spam guidance and Reddiquette. Do not calculate a ratio to justify weak participation. Comments must help people. Use the history that readers and moderators can inspect. A subreddit ban is easy to miss. You can still view the community and remain a member, but you cannot post or comment there. Reddit sends a moderator message, while the community itself remains visible. See Reddit's ban guidance.

Do not evade a subreddit ban with another account. Reddit treats that as ban evasion and can apply wider action. Appeal once if the ban is mistaken. When a subreddit permits product posts, use its flair and format. Put the problem and useful context in the post. Ask for specific feedback. Disclose that you built it.

4. Discord and Slack communities

Discord and Slack communities are more local than Reddit. Owners can set stricter rules. Read the welcome message, rules channel, channel topic, and recent moderator replies. On Discord, do not send unsolicited bulk messages. Do not use self-bots. Do not inflate membership or engagement. Discord lists these actions in its Community Guidelines. An invite link in the wrong channel can look like spam even when the product is relevant. Ask where product sharing belongs. If no channel exists, ask a moderator first. Use one relevant message. Do not copy it across servers or mass-DM members from a member list. Slack communities often use channels for support, jobs, events, or introductions. Keep promotion out unless the local rule allows it. Slack's official Community Code of Conduct applies to the Slack Community workspace. Other workspaces can add their own rules. Slack also maintains an Acceptable Use Policy. The common failure is treating a live conversation like a mailing list. Answer first. Share a link only when it adds value and the channel permits it.

5. Niche forums

Niche forums often have deeper trust and stricter history checks. A forum may expect build logs, technical details, vendor disclosure, or a specific launch category. Read the forum's rules and recent posts. Search for prior launches. Use the native format. Do not cross-post the same copy, because it signals distribution intent.

6. Launch honestly

A good community launch gives readers enough value without the click. State the maker's role, problem, product, price, and limits. Use this shape:

1. State the problem in the community's language.
2. Say, "I built this," before the product link.
3. Show the working product, demo, or concrete result.
4. State the price, free limits, trial terms, or paid-only status.
5. Name what does not work yet.
6. Ask for specific feedback.
7. Stay present and answer questions.

Example opening:

I built [product] after [specific problem]. It [plain result]. The free plan includes [limit], and paid plans start at [price]. I am looking for feedback on [specific issue].

Do not call a card-required trial free. Do not hide limits. Do not claim unsupported results. Do not imply community approval that did not happen.

A launch is not a campaign to dominate a feed. Post once, reply carefully, and remove it if a moderator asks.

7. Answer recommendation threads without shilling

Answer the person's decision problem, not your acquisition target. Start with the constraints that change the choice. Compare alternatives fairly.

Use this order:

1. Restate the use case and important constraints.
2. Give the best answer, even when it is not your product.
3. Name the tradeoff or a better alternative.
4. Disclose your connection before sharing your link.
5. Share one relevant link only when the rules allow it.

Use plain disclosure: "I built [product], so I am not neutral. It fits when [condition]. Use [alternative] when [different condition]."

Do not write a fake user story or say "I have been using it" when you built it. Disclose your connection even when the question does not ask.

If the thread bans self-promotion, answer without the link or do not answer. Do not move the conversation to a private message to bypass the rule.

8. Run your own community only when it has a reason to exist

An empty Discord is worse than no Discord. It shows no activity and adds another support surface. Early members then feel responsible for creating the community.

Start a community when users need a shared place. Have a repeatable topic, a moderator, weekly topics, and an owner for support questions.

Use this honest test:

• A few real users ask for a shared space.
• You can name the first discussions without inventing them.
• One person owns moderation, replies, and the next decision.
• You can keep the space useful for several months.

If the test fails, use a support inbox, small user group, or existing community. Do not create a server to display a member count or seed it with fake accounts.

9. What never to do

Never use sock puppets, fake testimonials, or fake happy users. Never pay for upvotes, comments, reviews, or engagement. Never coordinate votes or ask a private group to manufacture public interest.

These actions are dishonest even when a platform does not catch them. HN prohibits vote and comment solicitation. Reddit can treat repeated unwanted promotion as spam. Discord prohibits fake profiles, ban evasion, and artificial engagement. See the cited rules.

Do not use AI-generated replies as a volume tactic. HN asks users not to post generated or AI-edited comments. Write in your own voice and check every claim. See the HN Guidelines.

If a technique needs deception, leave it out. A smaller honest audience is safer than a large audience that learns it was manipulated.

Checklist

• Confirm the target is another person's community, not an owned channel.
• Read the current rules, pinned posts, FAQ, and recent moderation decisions.
• Confirm that self-promotion and product links are allowed.
• Participate helpfully before posting; allow two to four weeks as a working estimate.
• Use the same account for participation and the launch.
• Prepare a useful answer that does not depend on the product link.
• Use Show HN only for a working, personally built artifact that people can try.
• Never ask for HN upvotes, comments, or coordinated engagement.
• Follow each subreddit's rules, flair, format, and promotion limits.
• Remember that a Reddit community ban can leave the community visible to you.
• Ask Discord or Slack moderators where sharing belongs; avoid unsolicited DMs, copied posts, self-bots, and inflated engagement.
• Use the local format for niche forums and disclose commercial interest.
• State that you built the product, its price, its limits, and its current gaps.
• Disclose your connection and name alternatives in recommendation threads.
• Start your own community only with users, topics, and an owner ready to sustain it.
• Reject sock puppets, fake testimonials, paid votes, vote manipulation, and deception.

Related

• content-engine — the owned-channel counterpart.
• founder-led-sales — the one-to-one version of the same conversation.
• grow-a-product — where this sits in the loop.