+ SUBMIT

Where to share what you’re building

You shipped something — or you’re halfway there — and you want eyes and honest feedback. The good news: there are a dozen places that want to see indie work. The catch: each one has its own crowd, etiquette, and payoff. Match the venue to your goal — feedback, traffic, or your first users — and post to two or three, not ten. Here’s an honest rundown of where to share and what to expect.

1.Pick the venue by what you actually want

Before you post anywhere, name the goal. “Get feedback on the flow” sends you somewhere very different from “get a spike of signups.” Use this as a quick map, then read the sections below.

VenueBest forEffort
X (build-in-public)ongoing audience, momentumlow, but compounding
Reddit (niche subs)blunt feedback, early userslow–medium
Indie Hackerspeer advice, accountabilitymedium
Hacker News (Show HN)technical eyes, big spikehigh, one shot
Product Huntlaunch buzz, backlinkshigh, coordinated
BetaListearly-adopter signupslow, slow queue
Maker Discords / Slackswarm feedback, relationshipsmedium, ongoing
What Are You Buildinglightweight showcase, voteslow

2.Build in public on X

X is where the indie-hacker scene mostly lives. Posting progress — a screenshot, a metric, a problem you just solved — builds an audience over time that you can launch to later. The payoff compounds, but it doesn’t arrive on day one.

Pros: low friction, real-time replies, and the people who care about indie products are already here. Cons: from a standing start it’s mostly shouting into the void — reach follows consistency and a network you have to build first. Reply to other builders, share specifics, and don’t just broadcast links.

3.Post to the right Reddit communities

Reddit gives you blunt, unfiltered feedback and early users — if you respect each subreddit’s rules. The most useful for makers:

  • r/SideProject — the friendliest room for in-progress and just-shipped work.
  • r/indiehackers — fellow founders; good for the story behind the build.
  • r/SaaS — sharper, more business-minded; great for B2B tools and pricing talk.

Pros: honest reactions, niche subs for almost any audience, durable (posts get found via search later). Cons: mods are strict, low-effort self-promo gets removed or downvoted fast, and you need a real account with history. Lead with a screenshot or a specific question, not a bare link.

4.Use Indie Hackers and maker communities for peers

Indie Hackers is a forum of people doing exactly what you’re doing. Posting a milestone, a numbers breakdown, or a “here’s what I’d do differently” gets thoughtful replies from peers rather than random traffic. The same goes for maker Discords and Slacks (WIP, indie-focused servers, and the communities around tools you use).

Pros: high-quality advice, accountability, and relationships that pay off across multiple projects.Cons: smaller reach than the big public sites, and you have to show up regularly — these reward being a participant, not a poster who drops in only to promote.

5.Save Hacker News and Product Hunt for real launches

These are your big-spike venues — high effort, high variance, and best used once the product can survive a crowd.

Show HN on Hacker News puts you in front of a sharp, technical audience. A front-page hit sends serious traffic and pointed feedback. Cons: the crowd is critical, timing and title matter a lot, and a flat launch sinks without trace. Submit something genuinely interesting, write a plain title, and be in the comments to answer.

Product Hunt is a coordinated launch day: a polished gallery, a tagline, and ideally a rally of people ready to support you. A strong day brings buzz, backlinks, and signups. Cons: it’s effort-heavy, it favors makers with an existing following, and the traffic bump is often a spike, not a sustained channel. Prep assets in advance and don’t launch into a vacuum.

6.Seed early adopters with BetaList and directories

BetaList and similar startup directories put pre-launch and just-launched products in front of people who specifically like trying new things. Good for collecting early signups while you’re still building.

Pros: targeted early-adopter audience, low effort to submit, and a backlink. Cons: queues can be slow, the bump is modest and one-time, and some directories charge to skip the line. Treat it as one seed among several, not a growth engine.

7.Use a lightweight showcase like this one

What Are You Building — that’s us — is a taste-forward, black-and-white showcase where builders post what they’re shipping and the community upvotes and comments. It’s deliberately lighter than a Product Hunt launch: no coordinated day, no rally required, just drop the thing and get seen. Posting also gets you a free GEO report that shows whether AI engines mention your product.

Pros: low effort, in-progress work is welcome, upvotes and comments for feedback, and that GEO report. Cons: it’s a newer, smaller room than the giants above, so reach is more modest. Think of it as one good option among several — best paired with X or Reddit, not a replacement for a real launch.

FAQ

Where should I share a product that isn’t finished yet?
Go where in-progress is welcome: build-in-public on X, r/SideProject, an Indie Hackers post, a maker Discord, or a lighter showcase like this one. Save Product Hunt and Show HN for when the product can take a wave of traffic.
How many places should I post to at once?
Two or three that fit your goal, not ten. One high-effort venue plus one or two low-effort ones is plenty — spreading thin across every site gets you ignored everywhere.
How do I share without being spammy?
Lead with the work, not the link. Show a screenshot or a concrete result, ask a real question, follow each community’s rules, and be a regular before you ask for attention.

Ready to put it somewhere?

Post your product, collect upvotes and comments, and get a free GEO report.

+ POST YOUR PRODUCT