Blog
After the launch, keep posting
Product Hunt is one busy day. Niche communities can send visitors all year, once each release already has a draft you can paste.
Product Hunt gives you one good day. The communities where your buyers already ask for help can give you a year, if the habit survives the second week.
Most founders follow the same arc. Weeks of prep, a busy launch day, a spike, then silence. The product keeps shipping. The changelog keeps growing. Anyone who was not already a user never hears about it.
The people who keep growing after launch usually do something plain. They show up in the same handful of rooms, month after month, with something a stranger can use. A few forums, a few subreddits, Indie Hackers, Dev.to, Hashnode, a tutorial hub, one Slack or Discord that is actually alive. Small audiences. The right ones.
A short list
Fifty communities feels like distribution. It is how the posts get sloppy. Start with 8 to 12 places your buyers already use when they are stuck.
- Ask your last 10 customers where they go online when a problem like yours comes up. Write down the exact subreddit, forum, or group.
- Search the problem in their words. Note where those threads live.
- Prefer a room with weekly posts and real replies over a large one where everything sinks.
- Read the rules before you write. Some rooms ban promotion. Some allow it on a set day, or only inside one thread. Some only want a tutorial.
The type of room decides the shape of the post.
- Discussion rooms, such as subreddits and niche forums, want a question, a lesson, or an honest account of what you tried.
- Builder rooms, such as Indie Hackers, want the decision, the cost, and the trade-off.
- Dev.to and Hashnode want the full technical post, with the canonical URL pointed back at yours.
- Tutorial hubs, such as DigitalOcean Community, want steps someone would bookmark.
- Slack and Discord want two or three sentences, in the channel that exists for them.
Lead with the problem
“We shipped bulk CSV import” is an announcement. People outside your user base skip it. The post is the hour those customers spent pasting contacts one by one, the import flow you landed on, and the two file formats that caused most of the errors.
Before a release goes anywhere, answer three questions.
- What problem did this solve, in the reader’s words?
- What did you learn while building it? A trade-off, a mistake, a piece of feedback that surprised you.
- What can someone take away even if they never open the product? If the answer is nothing, leave it on the changelog.
The rewrite is where the habit dies
The original note is easy. Six versions of it, each with different rules, is the afternoon that turns into “next week.”
productpost360.com is the step that removes that rewrite. Paste the product URL. It reads the changelog, the blog, and the public pages, then writes a draft in the shape each room expects. A new changelog entry or blog post starts another set the next day. You still read every draft and paste it from your own account. The 1-product plan is $1 for the first month, then $29 a month, if you want to run it on the release you just shipped.
Keep a one-page rules note next to that: allowed days, required flair, whether the link belongs in the post or a comment. Draft the versions in one sitting, then publish them across a few days. The same paragraph in five places on the same afternoon is how accounts get removed.
Show up between the launches
A cadence a small team can actually hold:
- Each release: the 3 to 5 rooms this update fits. Save the others for a later ship.
- Each week: 20 minutes of replies, with nothing of your own to promote.
- Each month: one longer post. A lesson, a teardown, or a tutorial.
- Each quarter: see which rooms sent people who signed up, and replace the ones that stayed quiet.
Put it on the calendar. A task that depends on remembering will lose to the week a customer is on fire.
Add a UTM parameter to every link you paste, so you can see which room sent the visit. Connect Search Console and read it from day 14, after the posts have had time to sit. Upvotes are a pleasant signal. Signups, and the clicks on your own site, are the score.
A year of small, useful posts will do more than one launch day. The channel works when you keep showing up, and the draft is there so the rewrite is no longer the reason you skip a week.