What makes SaaS different
A consumer launch converts attention directly into use. A SaaS launch converts attention into a signup, a signup into activation, activation into a habit, and only then into revenue. Each step leaks, and a launch amplifies whatever leak already exists.
This produces the characteristic SaaS launch failure: a genuinely successful distribution day that yields nothing. Two thousand people land on the page, four hundred start a signup, ninety finish it, eleven reach the moment where the product becomes useful, and two are still there in a week.
The team concludes the launch failed. The launch worked perfectly, it just poured traffic into a funnel nobody had measured.
Instrument before you launch
Before any distribution work, you need to be able to answer four questions on launch day:
- How many people landed, and from which carrier? Per-source, broken out by carrier.
- Where in signup do people stop? Field-level, beyond "started" and "finished".
- What is the activation moment, the specific action after which retention changes, and how many reach it?
- Who is a qualified lead, and where does that alert go?
If you cannot answer these before launch day, delay the launch. Instrumenting takes two days; a non-repeatable traffic spike is worth more than that.
Lead with the wedge
SaaS positioning fails in a predictable way: teams describe the platform rather than the wedge. "A collaboration platform for modern engineering teams" describes a category. "Turns a failing CI run into a diagnosis in one click" describes a wedge.
The wedge wins for a mechanical reason. It is checkable. A reader can immediately decide whether they believe it, which produces the replies and arguments that drive distribution.
Category descriptions produce agreement, and agreement produces nothing.
Show the wedge working. A raw screen recording of the product doing the specific thing outperforms a produced film for nearly every technical SaaS product, polish reads as marketing, raw reads as real.
Where the traffic comes from
The uncomfortable arithmetic: your buyer is a VP of Engineering, a Head of Data, or a technical founder. They pay for ad-free feeds specifically to avoid marketing.
They are not reading trade press with any regularity. Paid acquisition reaches them badly and expensively.
What remains is the accounts they already chose to follow. That means the launch is a relationship problem before it is a publishing problem, you need people whose audiences overlap your buyer, briefed in advance, posting inside a concentrated window so that early engagement velocity triggers wider distribution. The mechanics are here, and the full sequencing is here.
One structural advantage SaaS has: your product is demonstrable in fifteen seconds. Use it. Most B2B categories cannot show the thing working, and you can.
The pricing question
Should pricing be public on launch day? For self-serve SaaS, yes, and it is not close.
A launch drives a spike of people evaluating quickly. "Contact sales" converts that spike into a form, and a form converts it into nothing, because the person evaluating you at 9:40am has four other tabs open. Public pricing lets them self-qualify in ten seconds.
The counter-argument, that public pricing constrains enterprise deals, is real but solvable with a published self-serve tier and a genuine enterprise tier that says "talk to us". What kills launches is hiding every number.
What to measure
- Signup-to-activation rate, per traffic source. The single most diagnostic number.
- Time to activation. If it takes a new user more than one session to reach value, the launch will underperform regardless of distribution.
- Qualified inbound attributed to carrier. Which specific accounts drove people who converted.
- Day-7 retention of the launch cohort against your normal cohort. Launch traffic is usually curious rather than in-market, so expect it to be worse. The question is how much.
- Reposts from credible accounts, which predict enterprise pipeline better than raw impressions do.
Questions we get asked
Should we launch on Product Hunt?
Sometimes, but understand what it does and does not do. The honest version is here.
How many signups should a SaaS launch produce?
There is no useful benchmark, because it depends entirely on price point, category, and funnel quality. The more useful target is a signup-to-activation rate that matches or beats your normal traffic.
Should we launch before the product is finished?
Launch when a cold user can reach the activation moment without help. Not before, a launch is non-repeatable and spending it on a product that cannot retain is the most expensive mistake available.