The Launch Pack gives you a ranked directory of communities where your product belongs, generates a tailored post for each one on demand, and tracks what you posted, what you skipped, and what you still have to hit. One set of inputs. Every platform handled differently.
When you are shipping a product — or re-launching one — the challenge is rarely the product itself. It is the distribution. You know you should post on Reddit and Hacker News and IndieHackers and LinkedIn and in a dozen Slack and Discord communities. You also know that the same post does not work everywhere. A Show HN post needs a specific title format and a terse technical framing. A Reddit post needs to lead with value, not announcement language. A LinkedIn post needs short paragraphs and no links in the body. An IndieHackers post wants a story with a hook.
Writing all of that from scratch, for every community, is several hours of work — and most founders skip it, or post the same thing everywhere and wonder why it underperforms.
The Launch Pack solves the execution layer. You fill in your product details once. The system shows you a ranked list of communities that fit your product category, audience, and promotion rules. For each community you want to post in, you click Generate and get a draft written to that community's specific format, tone, and rules — not a generic AI announcement. You edit if needed, copy, open the link, post. Then mark it as posted. Done.
Every state persists. Communities you have posted to move to a Posted tab. Communities you are skipping go to a Skipped tab. Everything you have not touched yet stays on Active. You can come back the next day, or the day after launch, and continue without losing your place.
The Launch Pack maintains a curated directory of communities across platforms. Each entry describes where the community lives, how large it is, what categories of product it accepts, how strict its rules are about self-promotion, what format posts should take, and what the audience actually wants to read. That context is not publicly visible — it is what gets injected into the post generation to make the output sound like it belongs in that community rather than like a press release dropped into a forum.
Platforms covered include:
You can filter the directory by platform, by product-fit category, by how strict a community's promotion rules are, and by whether self-promotion is allowed at all, limited, or not permitted. If you are building a developer tool, filtering to communities where that is the expected category saves you from spending time generating posts for communities that will remove them on sight.
Each community card shows the platform, the community name, a member count, a rules-strictness rating from 1 to 5, and whether promotion is allowed, limited, or off. Clicking a card opens a side drawer with the full community context and the generation flow.
Before you generate anything, you fill in a plan. The plan is the input that makes the generated posts specific to your product rather than generic. It includes:
When you click Generate on a community, that plan data is passed to the generation system along with the community's full context: its rules, its audience descriptor, its tone descriptor, its posting culture, and any topics that are off-limits there. The output is written for that specific destination, not adapted from a single template. A post for a Slack community of B2B marketers sounds nothing like a Show HN post for a developer audience, even when both are about the same product.
Generates a title under 100 characters and a body of 150-300 words. Output is structured as TITLE: then a separator then the body, ready to split into the Reddit title and body fields.
Generates a Show HN title that names the product and states the technical novelty, plus 1-2 paragraphs of body totaling 80-180 words. Format is TITLE: then separator then body.
800-1200 characters, short paragraphs separated by blank lines, no markdown, no links in the body text. Conversational but professional.
A thread of 4-7 tweets, each under 280 characters, numbered with a slash format. Each tweet stands alone but flows into the next.
A forum post of 200-400 words with a clear hook line, a story section, and a call to action or question at the end. Written in founder voice.
Short. Discord gets 1-3 casual sentences. Slack gets 3-5 short paragraphs around 150 words. Nothing that reads like a press release.
After generation, the draft is checked against a list of forbidden phrases — common AI-tell patterns like "excited to announce," "game-changer," "unleash," "stoked to share," and rocket emoji. Posts that trip the filter are flagged with a quality warning, and the system retries up to two times before returning the best available draft. You are always shown which phrases were detected so you can edit them out before posting.
You can regenerate a post as many times as you want. The system tracks a regeneration count per community so you can see how many attempts it took to get something usable. You can also edit the draft inline before copying — the edit state is preserved until you mark the post as posted or skip it.
The Launch Pack computes a daily posting recommendation based on your launch date and comfort level. If you set your launch date to a specific day, the system knows how many days remain and recommends which communities to hit first. The "Today's plan" view shows you exactly which communities to focus on that day, filtered to your enabled platforms, ordered by community size and fit.
This matters because launching is not a single-day event. The first day is the Product Hunt or HN submission. The second day is the Reddit communities. The third day is the LinkedIn and Facebook groups. The fourth day is the smaller Slack and Discord channels where your ideal customers actually spend time. Spreading it out correctly means you are not spamming every channel at once, which looks bad, and you are not front-loading all your effort on launch day when you are already overwhelmed.
Comfort levels:
The Launch Pack maintains four states for every community in your list:
This state persists across sessions. If you close the browser and come back three days into your launch, you see exactly where you are. Posted communities show when you posted and what copy you used. You can look back and see which communities produced the most engagement, so you know where to focus on the next launch.
Closing a community drawer does not mark it as posted or skipped. Only the explicit buttons — Posted, Skip, Hide — change state. This means you cannot accidentally lose your place by clicking around.
Every generated post can include a viral attribution tag. When attribution is enabled, posts include a short tracking parameter — a unique token tied to your account — so you can see how much traffic your community posts actually drove. The attribution tag is off by default and can be turned on per post or set as a default in your plan settings.
This is useful for understanding which communities convert, not just which ones generate comments. A community might produce 200 upvotes and 5 clicks. Another might produce 12 upvotes and 80 clicks. Attribution data surfaces that difference so you can spend your time on the communities that actually move people toward signing up rather than the ones that generate applause from people who will never try the product.
Click the plan icon at the top of the page. Enter your product one-liner, two to four differentiators, a proof point, and an optional launch offer. Set your launch date, pick your comfort level, and select the platforms you want to reach.
Use the filters to narrow the list to communities that fit your product. Check the promotion rules badge for each community — communities where self-promotion is off-limits are shown with a "No promo" badge so you do not waste time generating posts for them.
The drawer shows the community context: where it lives, what its audience expects, and the destination link. Click Generate draft to produce a tailored post.
Read the generated post. If it tripped a forbidden-phrase check, the flagged phrases are shown at the top. Edit the draft inline if needed. If you want a different angle entirely, click Regenerate.
Click Copy to put the post text on your clipboard. Click the community link to open the destination in a new tab. Paste and post. When done, come back and click Posted.
Work through the Today's plan recommendations each day until your launch window closes. The Posted tab shows your completed list. The Active tab shows what remains.
The Launch Pack does not post on your behalf. Every post requires you to open the destination, paste the draft, and click post yourself. This is by design. Automated posting violates the terms of service of most communities and gets accounts banned. The Launch Pack handles the writing and the tracking. The human handles the posting.
The Launch Pack does not guarantee any specific outcome. The quality of a launch post depends on how much real information is in your plan. A one-liner like "a better CRM" produces generic posts. A one-liner like "CRM for solo consultants who bill by the hour — tracks time, sends invoices, follows up automatically" produces posts that actually say something.
The Launch Pack does not replace community relationships. The best-performing posts in most communities are from people who are already known there. If you have never posted in a subreddit before, your launch post is more likely to be removed. The Launch Pack surfaces which communities allow self-promotion from new accounts and which are strict about established history — that context is in the promotion rules badges.
Yes. Each plan is tied to the product details you enter. If you are launching a second product, update the plan fields before generating posts. The per-community state (Posted, Skipped, etc.) is per-user, so if you are relaunching the same product with an update, the Posted history shows you which communities you already hit.
Mark it as skipped and note it in your own records. The Launch Pack does not monitor community responses — it handles pre-post generation and post-post tracking. Checking whether a post was approved or removed requires visiting the community directly.
The community directory is curated and updated periodically. It includes communities across major platforms with documented posting norms, an active member base, and categories relevant to software and tech products. If a community you want is missing, use the support channel to request it.
Yes. Attribution is controlled per post via a toggle in the drawer, and you can set a default in your plan settings. If you prefer posts without any tracking parameters, turn off the default and leave it off for each post.
The system takes your launch date and comfort level, counts the days remaining, and recommends how many communities to hit each day to complete your list by launch day. The "Today's plan" view shows the top-ranked communities for today, filtered to your enabled platforms. You are not locked to the plan — it is a recommendation, not a schedule you must follow.
Post generation costs credits. See pricing for the credit costs associated with your plan. The community directory itself is browsable at no cost — credits are only consumed when you click Generate on a specific community.
Fill in your product details and start working through the community list.
Go to Launch Pack →123 pages shipped, grouped by type. Expand a group to browse.
Add the RSS feed at /launch/feed.xml to your reader.
Sign up free →