Playbooks · Acquisition System

SaaS launch playbook for solo founders

Launch day is a marketing event, not a growth strategy. Here is the four-week sequence, and the number that actually tells you whether it worked.

A SaaS launch playbook has one honest premise: launch day is a marketing event, not a growth strategy. The spike arrives, lasts about seventy-two hours, and then you are back to whatever channel you built beforehand.

The sequence
  • Four weeks out — talk to twenty people who have the problem
  • Two weeks out — pricing live, payment tested, activation instrumented
  • Launch week — one primary channel, one secondary, nothing else
  • Week two onward — the actual work: converting the people who stayed

The measure of a launch is not day-one signups. It is how many of them are still active in week six.

Founders who treat launch as the finish line spend six weeks polishing a launch post and zero weeks building the channel that has to carry them afterwards.

Four weeks out — the part that decides the outcome

Launch performance is largely determined before launch week. Two things matter and neither is the landing page.

Talk to twenty people who have the problem. Not to validate — to collect language. The words they use to describe the problem become your headline, and a headline written in customer language outperforms one written in founder language by a wide margin. The customer interview guide covers how to run these without leading the witness.

Build a list of people who asked to know. Fifty people who explicitly said "tell me when it is ready" beats two thousand followers. Launching to nobody and hoping a platform sends traffic is the most common failure in this playbook.

Two weeks out — mechanics, not messaging

Four things must be working before you tell anyone. Each of them is a silent revenue leak on launch day.

Marcus · GhostCoach's AI coach
"I recommend you decide before launch week what number would mean it worked. Founders who skip that step get four hundred upvotes and two customers, and cannot tell whether that is a success or a failure."

Launch week — one channel, not five

Pick one primary channel and one secondary. Directories, communities, your list, a subreddit, a newsletter. The specific choice matters less than the constraint.

Running five channels in one week means five half-prepared posts, no capacity to answer comments properly, and no signal about which channel actually works. The comments are where the conversion happens, and they need you present for a full day.

DoDo not
Answer every comment within the hourPost and check back tomorrow
Reply to every signup personally, onceAutomate the first message on day one
Note the exact wording of every objectionArgue with the objections
Ship one fix a day for obvious breakageRebuild the onboarding mid-launch

Week two — where the real work starts

The spike ends. What remains is a cohort of signups in various states of activation, and the job changes entirely.

Measure how many reached first value. If it is under twenty percent, onboarding is your bottleneck and no amount of additional traffic will help — the onboarding framework covers the fix. If activation is healthy but nobody converts, look at trial-to-paid conversion.

Then pick the channel you will run for the next ninety days, which is a separate decision from your launch channel. Launch channels are one-shot; a repeatable acquisition system is what carries you to $1k MRR.

What to ignore during a launch

Everything on this list is legitimate work that is wrong for this specific fortnight.

Set your success number before launch week. A reasonable one for a first solo launch: ten people who reach first value and are still active thirty days later. Upvotes, traffic and signups are all easier to get and tell you far less.

If launch week goes quiet

Silence is data, not a verdict. Four things can produce it and they need different responses — the flopped launch diagnosis works through them in order.

For products built quickly with AI tools, the gap is usually between having a working product and having a business around it. What comes after vibe coding covers that specific transition.

SaaS launch playbook FAQ

What should a SaaS launch playbook include?

Four phases: customer conversations four weeks out to collect language, mechanics two weeks out (pricing live, payment tested, activation instrumented, self-service first run), one primary and one secondary channel during launch week, then conversion work from week two onward.

How many customers should I expect from a SaaS launch?

Far fewer than the traffic suggests. A reasonable success measure for a first solo launch is ten people who reach first value and are still active thirty days later. Upvotes and signups are easier to get and tell you much less.

Should I launch without pricing?

No. Launching without prices to see what happens wastes the one moment when attention is concentrated, and it gives you no information about willingness to pay. Decide the pricing method, commit to a number, and put it on the page.

How many channels should I launch on?

One primary and one secondary. Five channels in one week produces five half-prepared posts, no capacity to answer comments, and no signal about which channel works. Comments are where conversion happens and they need a full day of presence.

What should I ignore during launch week?

SEO, a second pricing tier, integrations nobody requested, redesigning the landing page based on the first ten reactions, and comparing yourself to whoever launched the same day. All legitimate work, all wrong for that specific fortnight.

Plan your launch week with Marcus

Tell Marcus your product, your list size and your launch date. You get a sequence and a success number to judge it against.

Try GhostCoach free →

14-day free trial · cancel anytime · 30-day money-back on Lifetime