How to promote your side project without spamming anyone

First: the sentence. One line that tells a stranger what the project does and who it is for - 'X for Y' is fine, plain description is better ('turns your GitHub releases into social posts'). If you cannot write it, that is diagnostic: the project may do too many things, and promotion will fail no matter the channel because nobody retells a story they cannot compress. Test it on someone who does not know the project; if their follow-up question is 'but what does it do?', keep working.

Second: the proof. One honest screenshot, GIF, or 30-second demo showing the thing actually working on a real example - not a landing-page mockup, the product. Builders' channels are veterans of vaporware; visible working software is the credibility threshold, and posts with real proof consistently outperform identical posts without it. Third: somewhere to land. A page with the sentence, the proof, and one obvious action (try it, install it, star it). It does not need design polish; it needs to load fast and not ask for a credit card before showing anything.

That is the whole checklist - deliberately short. The classic mistake is inverting the effort: three weeks on a logo and a pricing page for a project with zero users, then one exhausted Reddit post. The assets above take an evening, and everything after them is distribution. If you have the working project, the sentence, the proof, and the page, you are more prepared than most of what gets posted to r/SideProject today.

Two rules govern the table. Spend high-effort channels on milestones only: a Show HN or a value-first subreddit post can each deliver thousands of qualified visitors, but each community punishes repetition and low effort, so you get a few shots a year - make them count. And run low-effort channels continuously: the X/Bluesky drumbeat and your own changelog cost minutes and compound quietly between milestones. Product Hunt sits in the middle: worth one well-prepared launch for the badge and backlink, rarely worth optimizing beyond that for a developer tool.

Weeks 1-2, foundations: the sentence, the proof, the landing page, and accounts wherever your users gather (post nothing promotional yet - on Reddit especially, participate first so your account has history when it matters). Start the shipping drumbeat immediately: your first 'shipped dark mode' post to eleven followers feels pointless and is not - you are building the habit, the archive, and the algorithmic history before the audience arrives. This is also the moment to automate the drumbeat, while the routine is forming: wire your releases to your channels once, and the habit becomes deadline-proof.

Weeks 3-6, first community moments: one value-first post in one niche subreddit where your project solves that community's specific problem - written for them, honest about limitations, link carrying the least weight. Answer every comment. A week later, r/SideProject for the friendlier launch crowd. Collect every question people ask; each one is a landing-page fix or an FAQ entry. You are looking for the moment someone you have never met uses the thing and tells you something you did not know about it - that is the signal to escalate.

Weeks 7-12, the milestone: when the feedback from weeks 3-6 is incorporated and the project is genuinely try-able in two minutes, Show HN. Morning, US weekday, title that states what it is without hype, first comment from you explaining why you built it and what you know is missing. Whatever happens - front page or twenty views - the drumbeat continues behind it, announcing what you fix and ship from the feedback. By day 90 the loop exists: ship, announce automatically, show up personally at milestones, fold feedback back in. That loop, not any single spike, is the growth engine.

The launch-spike hangover is predictable: HN traffic decays in 48 hours, the Reddit thread stops commenting, and the project feels finished as a story. It is not - the users you want mostly did not see the launch, and the ones who did will forget. The projects that grow treat the launch as the first announcement of hundreds: every real improvement after it gets its shipped-work post, every meaningful version gets its changelog entry distributed, and two or three times a year a genuinely big milestone earns another community post ('Show HN: X - now with the thing everyone asked for').

This is exactly where manual promotion collapses, and the collapse is structural, not moral. Launch week ran on adrenaline; month four runs on nothing. You are back to building, the posting takes forty minutes per update across channels, and it silently loses to the roadmap every single week - the project goes dark precisely while it is improving fastest. The fix is the one from the drumbeat playbook: make the announcements a side effect of shipping rather than a task. When a release automatically becomes channel-ready drafts you approve in a minute, month-four consistency stops requiring month-one energy.

And keep the compounding surfaces warm. The Reddit threads and Show HN post keep ranking in Google for your problem's keywords - link to them from your site and keep the landing page they point at current. The changelog archive doubles as proof of momentum for every prospect who checks whether the project is alive (they all check). Sustained visible shipping is, for a side project, the single most persuasive marketing asset that exists: it answers the only question that matters about a side project - is this thing maintained?

S2P wires your side project's GitHub to your channels: when you tag a release, merge a meaningful PR, or update the changelog, it drafts channel-native posts in your voice - the compressed X version, the contextual LinkedIn version, a value-first Reddit draft when a release warrants one - for any of LinkedIn, X, Threads, Bluesky, Mastodon, Reddit, Facebook, Instagram, YouTube, Discord, Slack, and custom webhooks. You review and approve; nothing publishes without you unless you opt a channel into autonomous mode. Rules on semver or labels keep the trivial patches quiet.

For a side project specifically, the free plan is designed to be the whole system: one repo, two social channels, one post a day, as of July 2026 - which is exactly the X-or-Bluesky drumbeat plus one more channel this playbook prescribes, at the cadence a side project ships. If the project graduates into something bigger, paid plans start at $5/mo billed yearly. And if you just want better launch-week posts today, the free changelog-to-social generator turns your release notes into six channel drafts in the browser, no signup.

What it deliberately will not do for you: the Show HN, the community participation, the replies. Those need you - and they are the parts you will actually have energy for once the weekly announcement grind is automated away.

Mistake one: promoting before the two-minute test passes. If a stranger cannot go from your link to experiencing the value in two minutes (no signup wall before the demo, no config file before hello-world), every visitor your promotion earns bounces, and high-effort channels are wasted on a leaky funnel. Mistake two: the spray - posting the identical announcement to eight subreddits in one hour. Moderators remove it, users recognize it, and the account carries the smell permanently. One community, written for that community, beats eight copy-pastes every time.

Mistake three: disappearing from your own threads. On HN and Reddit the comments are the event; an absent author converts a promising thread into an abandoned stall. Block the hours after posting. Mistake four: reading silence as verdict. Early posts reach nobody because you have no distribution yet - that is the cold-start mechanics, not the market speaking. The verdict that matters comes from the ten real users you eventually get, not from post number three's zero comments.

Mistake five - the quiet killer: treating promotion as a launch-week activity instead of a property of how you ship. The project that announces every real improvement for a year will beat the project with the better launch week, essentially always. Everything in this playbook reduces to that: prepare the assets once, spend the milestone channels carefully, and make the ongoing announcements automatic so the drumbeat survives your motivation. Ship, and be seen shipping.