Most first launches are planned as one big day. You post everywhere at once, get a spike of visitors, and a week later it’s quiet again. Kat Mañalac of Y Combinator puts the mistake simply: “Most people think about launching as something that you get one shot at.” Her advice in YC’s talk How to launch (again and again) is to “destroy the idea that launching is just one moment in time.”
For a first-time founder that’s good news. A quiet first launch isn’t the end of anything. It’s the first of several.
What a launch strategy is for
Your launch has three goals:
- Get your first users: people who actually have the problem your app solves.
- Learn what works: which message and which places bring sign-ups.
- Build proof for the next launch: real users, a few honest quotes and some numbers.
Upvotes, followers and visits only matter if they lead to one of those three.
A go-to-market strategy for a small SaaS
Go-to-market strategy sounds like something for companies with a sales team. For a first SaaS it comes down to three answers you can write on one page:
- Who it’s for. One kind of person with one problem, described the way they’d describe it. “People who keep killing their houseplants” works better than “plant lovers”.
- Where they already are. Two or three places where those people talk, search or read, such as a subreddit, a forum or a search they type into Google.
- What you’ll say there. One promise that makes them want to try it, in their words, not yours.
Pricing and channels follow from those answers. The 30-day plan below is how you test them.
Days 1–3: fix what makes strangers leave
Every visitor in your first month is one you worked for, so don’t spend them on a broken first impression. Before you tell anyone, check at least these basics:
- Your headline says what the app does and who it’s for. Why visitors don’t sign up shows how to fix it.
- Google can read your page, not an empty shell. See why your app isn’t showing on Google.
- Shared links show a title and an image. Paste your address into the Open Graph preview to see.
- Sign-up emails reach the inbox, not spam. See why your sign-up emails go to spam.
- Strangers can’t read your users’ data. See vibe coding security: 5 things to check.
- You can see where visitors come from, with analytics and a separate link for every place you post.
The free LaunchPal check covers most of these and goes further, with your speed, your icon, your sitemap and more, in about a minute.
Week 1: a quiet launch to people who have the problem
Before any launch site, go where your problem is already being discussed: a subreddit, a forum, a Slack or Discord group, your own network. Help first, mention the app only where it genuinely helps, and message people one by one. Ask for feedback, not for sign-ups.
Kat Mañalac’s one rule for posting in online communities: “write like you talk.” Nobody there wants an ad.
For example, Bloomly’s founder answered three plant-care questions in a houseplant community, mentioned the app once where it fitted, and messaged ten friends who keep killing their plants. That first week is about conversations, not numbers. How to get your first 10 users goes deeper.
Prompt for your first community post
Write a short post for a community where people discuss the problem my app solves. Start with the problem in their own words, share one thing I learned while building the app, mention the app once at the end with a link, and write like a person talking to friends, not like an ad.
Weeks 2–3: launch in public, small places first
Once a handful of people have used the app and you’ve fixed what confused them, launch in public. Start with the smaller, friendlier launch sites, such as Uneed, Microlaunch, Peerlist or Fazier, and with communities that welcome new projects. If you built a developer tool, Show HN is worth it. Where to launch your app compares them.
Save Product Hunt for later, when you have users and some proof. Its own launch guide says new accounts have to wait a week before they can post, and recommends joining “well ahead of your launch (three months or more).” You don’t need anyone to post it for you: you can launch your own product.
Give every place its own link, so you can tell which one brought sign-ups and not just visits.
Week 4: keep what worked
For each place you posted, compare three numbers: visitors, sign-ups and people who came back. Stop spending time on what brought nobody, and do more of what brought sign-ups.
Be patient with the numbers. With a few dozen visitors, small differences mean nothing. Look for the big ones: the place that brought five sign-ups while the others brought none.
After day 30: launch again
Every real change is a reason to launch again: a feature people asked for, a new group of users, a free plan or a lower price. Post an update where you got a warm welcome, write about what you learned, and plan your Product Hunt launch once you have something to show. Each launch reaches people the last one didn’t.
Your 30-day launch plan
- Days 1–3: fix the basics above.
- Days 4–7: help in two or three communities and message people who have the problem, one by one.
- Week 2: fix what your first users struggled with, then launch on one or two small launch sites.
- Week 3: post where your users are, each place with its own link.
- Week 4: compare sign-ups by place, drop what didn’t work and plan your next launch.