How to launch a SaaS product
The launch sequence for a web product you charge for — pricing, the first paying customers, launch week and the channels that keep working afterwards.
A SaaS launch is different from an app launch in one way that changes everything: there is no store, no review queue and no ranking algorithm deciding whether anybody sees you. Nothing happens unless you make it happen, and nothing stops you launching on a Tuesday because you feel like it.
That freedom is why most SaaS launches are badly sequenced. Here is the order that works, and the reasoning for each step.
Before anything: know who the first ten customers are, by name
Not a persona. Ten actual people or companies you could email today, who have the problem, and who you could plausibly get to try the thing.
If you cannot write that list, the launch is not the problem. Every step below assumes it exists, because a launch spreads a message through people who already care, and if nobody yet does there is nothing to spread.
Decide pricing before launch, not after
The instinct is to launch free and add pricing later. It is usually the more expensive path: free users are a different population from paying ones, they give different feedback, and converting them later is its own project.
- Free trial or free tier, not both. A trial suits a product somebody evaluates once and commits to. A free tier suits a product that gets more useful the longer it is used, and where usage grows into a reason to pay.
- Pick a number and put it on the page. "Contact us" on a small SaaS is a form nobody fills in. You can change the number later; you cannot get back the people who left because they could not tell whether it was for them.
- Charge from the first week if you can. The first payment tells you more than a hundred sign-ups.
The pages you need before launch week
A SaaS product is found and evaluated through pages, so these are the launch.
- A home page that says what it does in the first sentence. Not the category ("modern collaboration for teams") — the job ("turn your standup notes into a weekly summary your manager will actually read").
- A pricing page, even at one plan.
- Documentation, or at least a getting-started page. For anything technical this is the page that closes the sale and the page search engines actually rank.
- One comparison page, if you have obvious competitors. "X vs Y" is a search people make with their credit card already out.
- A changelog. Cheap to keep, and it is the evidence that the product is alive — which is the first thing a stranger evaluating a small SaaS is trying to determine.
Launch week
- Show HN, if there is a technical angle. Plain title, honest first comment.
- The launch boards. Product Hunt if the audience matches; otherwise see Product Hunt alternatives. For a B2B product, expect sign-ups rather than customers.
- Email your list, if you have one, and email the ten people by name individually. The individual emails will outperform everything else on this list, which is annoying and consistently true.
- Post where the problem is discussed, not where founders hang out. The subreddit for the job your customers do beats the subreddit for building startups, every time.
- Answer everything the same day. Launch traffic is a one-day window in which strangers will tell you what is wrong with your product for free.
The month after: the channels that compound
Launch traffic goes to zero. What replaces it is one or two of these, and it is worth choosing rather than doing all of them badly.
- Search. For SaaS this is usually the largest long-term channel and the slowest to start. It means pages that answer the questions your customers type before they know you exist, and it takes months, so start in month one.
- Comparison and directory listings. Being present where people are already deciding. See where to submit your startup for the list worth working through.
- Integrations. Being listed in another product's marketplace is a channel with a shape most people underuse: their users have already proved they have the problem.
- Writing about the specific thing you know. Not content marketing in general — the one operational thing you learned building this, which nobody else can write.
The mistakes that show up most
- Launching to founders instead of customers, because that audience is easier to reach and gives warmer feedback.
- Treating launch day as the goal. It is the start of the measurement, not the end of the work.
- Rebuilding after a quiet launch. A quiet launch usually means the message was wrong or the room was wrong, and rebuilding fixes neither.
- Waiting for the product to be ready. It is a web app; you can ship on Tuesday and change it on Wednesday, and that is the actual advantage you have.
Where this site fits
WhatAreYouBuilding.AI is a directory of independent builders and what they are shipping. For a SaaS product it does the compounding kind of work rather than the launch kind: a permanent page, a regular do-follow link, and a place in a catalogue organised by country, category and funding stage.
It is also queryable by agents via MCP, so a listing is visible to the assistants people increasingly ask instead of searching. If you want to check whether your own site is readable that way, the AI readability checker will tell you in a few seconds.
Submit a product, or read what a listing gets you first.