It's 11pm the night before launch. You have one tab open on a "500 places to launch your startup" spreadsheet, another on a half-written Reddit post you're not sure will survive the moderators, and a plan to submit to all of it tomorrow and see what sticks.
I've done that. It feels productive and mostly isn't.
The real question isn't where to launch a SaaS product. It's what this launch needs to produce right now - users, feedback, links or proof - and which places actually give you that. Sort places by what they give back and the plan almost writes itself.
This is the map I'd hand a friend launching this month. It's opinionated, and you definitely shouldn't hit every group on the same day.
Key takeaways
- Sort launch places by what they give you (traffic, feedback, backlinks, AI-search mentions), not by how famous they are.
- Your own site and docs come first - every other channel sends people there.
- Launch boards give you a burst plus a page that lasts; developer communities give honest feedback if you follow their rules.
- Directories and "alternatives" sites are slow and dull, and they keep paying for months.
- Space your launches over four to six weeks so each wave sees a better product than the last.
Decide what this launch needs before you pick places
Before you open a single submission form, write down what this launch needs to produce. For an early SaaS product it's usually one of four things:
- Traffic and signups - people who try it this week.
- Feedback - people telling you what's confusing or broken.
- Backlinks - links from other sites that help search engines trust your domain.
- AI-search mentions - your product showing up on the kind of pages AI answer tools read when someone asks "what's a good tool for X?"
Most places give you one or two of these well. None gives you all four. A Show HN post can bring sharp feedback, then sinks within a day. A niche directory listing brings almost nothing on day one, then a trickle for years.
Say you're launching Ledgerly, an invoicing app for freelancers. In week one Ledgerly needs feedback: does the first invoice go out without help? By week four it needs steady signups and a few dozen pages that mention "Ledgerly" next to "invoicing for freelancers". Different jobs, different places.
The map: six groups of places, by what they give you
Roughly in the order I'd use them.
Your own site and docs: where every launch points
The boring answer and the most important one. Every other channel sends people here. If your homepage can't say what the product does in one sentence, you'll waste every launch that follows.
Before any public launch I'd want:
- A headline that names the user and the outcome. "Smart finance for modern teams" says nothing. "Send an invoice in 60 seconds and get paid by card" tells a freelancer exactly what Ledgerly does.
- A pricing page, even if it just says "free during beta".
- A short docs or FAQ page answering the questions you keep getting by email.
- A changelog, so you have something to post about later.
- Analytics that read UTM tags and referrers, so you know which launch sent which signups.
Effort: medium, once. When: before everything else. The long version is in my launch checklist for indie makers.
Launch boards: a burst of attention and a page that stays
You submit, people browse new products, vote and comment. Boards come in two shapes.
One-day boards. Product Hunt is the best known. A launch there lasts one day, on a 24-hour cycle in Pacific Time. You spend the day rallying people, and tomorrow you're off the front page. That works if you already have an audience to bring. If you don't, a single day is unforgiving.
Weekly boards. On QikLaunch, a launch gets a full week on the board (Monday to Sunday, closing Sunday 23:59 UTC), ranked by votes from signed-in accounts, and keeps a permanent product page afterwards. A week lets you share it with your email list on Monday and LinkedIn on Thursday without missing the window.
There are plenty of others - BetaList, Uneed, DevHunt and more. Read how each one works before you submit; they aren't interchangeable. Our alternatives pages put a few side by side.
What you realistically get: a spike of visits, comments from other makers (who skew toward builders rather than buyers), usually a backlink, and an indexed page search engines and AI tools can read.
Effort: low to submit, medium to do well. Good screenshots, a clear tagline and replying to every comment make the difference.
When: once your onboarding works. A launch board is a terrible place to discover your signup form is broken. And don't stack two boards on the same day - you'll do both badly.
Developer communities: honest feedback, strict rules
Show HN and the right subreddits give you the most honest feedback of your life.
Show HN is for things people can actually try. Write a plain title ("Show HN: Ledgerly - invoicing for freelancers with card payments") and a first comment explaining why you built it and what you'd like feedback on. Don't ask for upvotes. Stay around to answer for hours, not minutes.
Subreddits each have their own self-promotion rules, and they vary a lot. Some only allow promotion in a weekly thread; some don't allow it at all. Read the rules first, and ideally have a history of real comments there. For Ledgerly, a freelancing subreddit beats a general startup one - you want users, not other founders.
What you get: feedback, sometimes a big spike, sometimes nothing. Don't expect much SEO value; community sites often mark user links nofollow or ugc, which Google treats as hints. You're not here for links.
Effort: medium to high. The post is easy. The replies are the work.
When: a week or so after your main launch, once the obvious bugs are gone. Never paste the same post into five subreddits on one day.
Niche directories and "alternatives" sites: slow, dull, compounding
Most founders skip this group because it's tedious. It's also the one that keeps paying.
Category directories ("tools for freelancers") and "alternatives to X" pages are where people go when they're already shopping. Someone looking to replace the invoicing tool they're fed up with is far closer to signing up than someone scrolling a launch board.
What you get: small, steady, high-intent traffic. Backlinks, some dofollow and many not (here's why both still matter). And mentions on exactly the kind of category pages AI answer tools can draw on - more on that in getting found in AI search.
Effort: low per listing, high in total. Write a long description, a short one, a tagline and a set of screenshots once, then adapt them per site instead of pasting identical text.
When: across weeks two to four, a handful a day. If you'd rather not build the list yourself, QikLaunch's Boost plan includes a checked list of 300+ launch directories.
Newsletters: borrowed trust, small but warm
A newsletter covering tools in your space sends visitors who already trust the editor's taste. Think small and focused - a freelancer tools roundup, a newsletter for one profession.
What you get: a modest burst of good visitors, with little lasting SEO value since most issues live in inboxes.
Effort: medium. Find 10 to 20 that fit, read a couple of issues, then send a short personal pitch: what it does, who it's for, why their readers would care, one link.
When: once you have something to point at, like a launch page with real comments or a changelog with recent fixes.
Your own audience on X and LinkedIn
If you've been posting about the build, your followers are the warmest people you'll reach.
What you get: early votes and comments during launch week, first signups, and shares into networks you can't reach.
Effort: low on launch day, high in the months before.
When: every phase, with each post pointing at one thing. "We're live this week." Then "Here's what 40 people told us about onboarding." Then "We shipped the fixes you asked for." That's a story people follow, not a string of "please upvote" posts.
A phased plan from week -2 to week +4
Here's the order I'd run for Ledgerly. Stretch the weeks if you need to, but keep the sequence.
| Week | Focus | Where | What you're after |
|---|---|---|---|
| -2 | Foundation | Own site, pricing, docs/FAQ, changelog, UTM-ready analytics | A clear pitch and measurable traffic |
| -1 | Warm-up | Build posts on X/LinkedIn, email list, shortlist newsletters | People ready to show up |
| 0 | Main launch | One launch board, plus your own audience | A burst of visits and first feedback |
| +1 | Hard feedback | Show HN or one or two relevant subreddits | Honest criticism and a fix list |
| +2 | Fix and tell | Ship fixes, post the changelog, start directories (5-10 a day) | A better product and first links |
| +3 | Borrowed audiences | Newsletter pitches, more directories, "alternatives" sites | Warm traffic and category mentions |
| +4 | Second wave | A second launch board, a recap post, remaining directories | Fresh attention for an improved product |
Why spacing launches out beats launching everywhere at once
"Launch everywhere on day one" has three problems.
You can't reply properly. A launch board, a Show HN thread and three subreddits on the same day means rushed replies everywhere, and replies are where people decide whether to trust you.
You can't learn. If day one shows the signup flow confuses people, you want the next wave to see the fixed version. Launch everywhere at once and everyone sees the broken one.
You get one spike and then silence. Spaced launches give you several smaller spikes, each a fresh batch of people to turn into your first 100 users, and each hands you something new to say. "We fixed what you told us about" beats "we're still live".
If you have a hard date, compress the plan, but still keep developer communities a few days behind the main launch.
Common mistakes I keep seeing
- Launching before onboarding works. Your first wave is your best audience. Don't spend it on a bug.
- Posting identical text everywhere. Hacker News wants the technical story. A freelancer subreddit wants the problem it solves.
- No tracking. Without UTM tags or ?ref= links you'll never know which place was worth the hours.
- Asking for upvotes instead of opinions. People can tell. Ask what they think and the votes tend to follow.
Your launch-places checklist
- Homepage headline names the user and the outcome
- Pricing, docs/FAQ and changelog pages are live
- Analytics records UTM tags and referrers
- Short description, long description, tagline and screenshots ready
- Main launch board picked and the week booked
- Rules read for every subreddit and community on the list
- Show HN title and first comment drafted
- 10-20 relevant newsletters listed with editor contacts
- Directory list ready, at 5-10 submissions a day
- Recap post scheduled for week +4
FAQ
Where should I launch a SaaS product first?
Start with your own site, then one launch board backed by whatever audience you have on X, LinkedIn or email. That gives you a focused burst and a solid place to send people. Add communities and directories once you've seen the first feedback.
Is Product Hunt still worth it for a SaaS launch?
It can be, especially if you already have an audience to rally, because a launch there lasts one day. Without that audience, a single 24-hour window is hard to win. Many makers start on a weekly board and save a one-day launch for a bigger release.
Can I post my SaaS on Reddit?
Sometimes. Every subreddit has its own self-promotion rules, and some only allow it in specific threads or not at all. Read the rules, take part first, and post where your users are rather than where other founders are.
Do launch backlinks actually help SEO?
They help, just not overnight. Dofollow links pass more signal, while nofollow and ugc links are treated by Google as hints. A spread of relevant links over several weeks is worth more than a pile from one day.
Pick one place and start this week
You don't need the perfect list. You need one launch done properly, then the next one a week later.
If a weekly board fits your plan, you can submit your product for free and get a full week on the board plus a permanent page.
Stay Up