Pre-Launch Marketing: A 30-Day SaaS Plan

Quick answer

Pre-launch marketing is the work you do before public release to find a specific audience, test your message, recruit qualified early users, and prepare a measurable launch path.

For a SaaS product, use the 30 days before launch to:

• Define one ideal customer, urgent trigger, and product promise.
• Interview prospects and test whether the problem is real.
• Build a focused waitlist page with one clear next step.
• Recruit a small design-partner or beta cohort manually.
• Test one repeatable acquisition channel.
• Prepare proof, onboarding, tracking, and launch follow-up.
• Invite users in waves and measure activation, not just signups.

The purpose is not to manufacture hype. It is to reach launch day with matched prospects, a tested message, and evidence that users can receive value.

What is pre-launch marketing?

Pre-launch marketing is the process of validating and building demand before a product becomes broadly available. It connects customer research, positioning, audience building, channel testing, and launch preparation.

A useful SaaS pre-launch funnel is:

Matched prospect → conversation → waitlist or beta request → product invitation → activation → feedback

This is different from collecting as many email addresses as possible. A large generic list can produce a disappointing launch if subscribers do not have the problem, do not remember why they joined, or cannot use the product when invited.

A good pre-launch strategy should answer five questions:

• Who experiences the problem urgently?
• Which promise earns their attention?
• Where can you reach them repeatedly?
• What evidence makes the product credible?
• What must a user do to receive first value?

Your public launch then becomes the next measured cohort, not the first time the product meets a real user.

Start with a pre-launch hypothesis

Write one sentence before choosing channels or designing a waitlist:

When [specific customer] experiences [urgent trigger], they need to achieve [outcome]. Our product helps them do that without [painful alternative].

For example:

When a small performance agency adds several clients, its operations lead needs to produce consistent weekly reports without rebuilding spreadsheets and slides for every account.

This statement identifies a person, a situation, an outcome, and an alternative. You can use it to find interview candidates and reject people who do not fit.

Avoid targets such as “startups,” “marketers,” or “small businesses.” They are too broad to produce a useful message. Add role, company context, trigger, current process, and a disqualifier.

If the customer and trigger remain uncertain, use the founder-led sales playbook to structure the first conversations.

Decide what the waitlist means

A waitlist can serve several purposes. Choose one for the first campaign:

Do not call every email address a potential customer. Label each signup by source, customer fit, use case, and stated intent. A prospect who requests a beta for a current workflow is a stronger signal than someone who joins after a giveaway.

Also tell people what joining means. State what you are building, who it is for, what subscribers will receive, and approximately when they will hear from you. Do not imply that access is scarce unless it genuinely is.

Build a focused pre-launch landing page

The page has one job: help the right visitor decide whether to take the next step.

Include:

• Customer and outcome: name who the product serves and what it helps them accomplish.
• Problem context: describe the trigger or current process that makes the product relevant.
• Product explanation: show the core workflow in plain language.
• Evidence: use a screenshot, working demo, example output, or transparent progress update.
• Fit guidance: say who should and should not join.
• One call to action: request access, join the waitlist, book a beta interview, or apply for a pilot.
• Expectation setting: explain what happens after submission.

Keep the promise connected to the product's activation event. If the page promises a finished weekly report, the first useful product session should help the user create one. Account creation is not enough.

Do not fill the page with unsupported testimonials, countdown timers, or invented demand. Early credibility comes from a clear problem, a believable workflow, and honest limits.

Choose a meaningful pre-launch conversion

The conversion should demand enough commitment to separate curiosity from intent without creating unnecessary friction.

Ask only for information you will use. An email and role may be enough for a launch notification. A guided pilot may need company, workflow, current alternative, urgency, and availability.

Define the post-invitation activation event now. Examples include publishing a first project, connecting an integration and receiving a result, inviting a teammate into completed work, or creating a campaign that receives a qualified application.

Days 1–7: validate the customer and message

The first week should produce conversations, not polished campaign assets.

Recruit 10 relevant interview candidates

Find people who match the customer hypothesis and can describe a recent instance of the problem. Sources can include:

• former colleagues and warm introductions,
• people using the current manual alternative,
• niche communities where the workflow is discussed,
• public posts asking for recommendations,
• companies showing an observable trigger,
• and users of adjacent tools who have outgrown a process.

Ask about past behavior:

• When did the problem last happen?
• What triggered it?
• How did you handle it?
• What did the process cost in time, money, delay, or risk?
• Who else was involved?
• What have you tried?
• What would need to be true to test another approach?

Avoid asking, “Would you use this?” A polite yes requires little commitment. A prospect sharing data, scheduling a follow-up, introducing a colleague, or agreeing to test a workflow is stronger evidence.

Test three message variations

Keep the audience constant and vary one part of the message:

• the problem,
• the promised outcome,
• or the next step.

For example, compare “reduce reporting work,” “publish client-ready reports consistently,” and “replace the weekly spreadsheet-to-slide process.” Record which wording leads to specific questions and follow-up commitments.

At the end of week one, choose one audience, trigger, promise, and activation event. If no clear pattern appears, narrow the audience before increasing outreach.

Days 8–14: launch the waitlist and private beta

Turn the strongest message into a simple page and invite a small matched cohort.

Create one pre-launch offer

A pre-launch offer should reduce uncertainty for the prospect and create learning for the founder. Useful offers include:

• a guided beta using the prospect's real workflow,
• a limited design-partner program,
• early access to one complete use case,
• a workflow assessment followed by product setup,
• or a paid pilot with a specific success condition.

“Get updates” is acceptable when the product is not ready to test, but it is a weak validation event. Whenever possible, give qualified prospects a concrete way to experience or shape the product.

Invite people personally

Start with interview participants and prospects who showed a recent trigger. Explain why the beta may fit, what they will need to do, and what is still incomplete.

A direct invitation can follow this structure:

You mentioned that [specific workflow] breaks after [trigger]. We now have a test version that helps [customer] achieve [outcome]. I am inviting a small group to run one real workflow and tell us where it fails. Would you like access next week?

Do not automate the first invitations. Personal replies will reveal missing information, trust concerns, and timing problems that a campaign dashboard cannot explain.

Days 15–21: test one acquisition channel

Choose one channel based on where the customer already demonstrates intent.

Choose the channel because it matches buyer behavior, not because another startup succeeded there.

Use consistent campaign tagging. Google's guide to collecting campaign data with custom URLs explains the roles of `utm_source`, `utm_medium`, and `utm_campaign`. Preserve the original source through signup and activation.

Product Hunt's official launch preparation guide is useful if that community matches your audience. Prepare the product explanation, tagline, visuals, maker story, and responses before launch day. Do not make Product Hunt the default channel for a product whose buyers do not spend time there.

Days 22–30: prepare proof and launch in waves

The final pre-launch week turns private learning into a controlled release system.

Build an honest proof pack

Use the strongest evidence you actually have:

• a short product walkthrough,
• annotated screenshots,
• an example input and output,
• a before-and-after workflow,
• a beta user's specific result with permission,
• answers to repeated objections,
• known limitations,
• and a clear activation checklist.

Do not convert casual praise into a performance claim. If evidence is limited, make the claim narrower.

Segment the waitlist

Useful segments include:

• strong-fit beta participants,
• qualified prospects who have not tested,
• general launch subscribers,
• founders or buyers,
• practitioners or end users,
• and potential distribution partners.

Each segment should receive a next step that matches its context. A design partner may need a personal activation session. A general subscriber may need a concise launch email. A potential partner needs a product brief, customer definition, approved claims, tracking, and compensation rules.

Invite in waves

A simple sequence is:

• Wave 1: five to ten strong-fit users who can receive hands-on support.
• Wave 2: the next qualified waitlist segment after the largest activation issue is fixed.
• Wave 3: the broader list and primary public channel after the product path works reliably.
• Wave 4: partners and referrals after the message, tracking, and customer quality are understood.

Y Combinator's guide to launching again and again recommends treating launches as repeated opportunities to test the pitch, audience, and product response. A wave launch applies that principle while limiting the cost of a broken onboarding step.

Use a pre-launch scorecard

Review the same funnel every week:

Break the results down by audience and source. A blended signup rate can hide one small channel that produces activated users behind a larger channel that produces curiosity.

Do not use a universal waitlist conversion benchmark as your main decision rule. Compare segments inside your own campaign and look for evidence that the right users accept invitations, activate, and return.

Pre-launch campaign ideas that produce evidence

Choose activities that test a business assumption rather than only generating impressions.

Publish a problem teardown

Explain why the current workflow fails, show a better process, and invite people with that exact problem into a beta. Measure qualified replies and activation after invitation.

Run a small workflow clinic

Invite five target users to bring a real example. Help them diagnose the process manually, then identify which parts the product should handle. This can produce customer language, objections, and beta candidates.

Create an example output

Show the report, dashboard, plan, integration result, or campaign brief the product creates. Ask prospects whether it fits a current job and what information they would need to produce their own.

Recruit a design-partner cohort

Offer close access and support in exchange for regular use and direct feedback. Define the time commitment, product scope, confidentiality, commercial terms, and exit conditions before starting.

Test one specialist distribution partner

After the audience, promise, and conversion path are clear, give one relevant marketer, consultant, or creator a structured campaign brief. Track referred prospects through activation, not only clicks.

Cobalia is being built to connect SaaS founders with performance marketers around defined audiences, campaign briefs, compensation, and visible performance rules. If your pre-launch test has a clear customer and measurable next step, join the Cobalia waitlist as a founder or marketer.

Common pre-launch marketing mistakes

Optimizing for waitlist size

A large list is not useful when subscribers cannot use the product or do not remember why they joined. Track customer fit, stated use case, invitation acceptance, and activation.

Manufacturing urgency

Fake counters, arbitrary deadlines, and unsupported claims may increase short-term conversion while reducing trust. Use genuine capacity limits and honest timelines.

Building an audience without talking to users

Content and social posts can create reach, but they do not replace direct customer evidence. Keep interviews and guided product use in the pre-launch plan.

Testing several channels at once

A small team cannot distinguish targeting, message, channel, and product problems when everything changes together. Choose one audience and one primary channel for each test.

Waiting for launch day to test onboarding

The public launch should not be the first complete journey through signup, activation, email, support, and follow-up. Run the path with a private cohort first.

Going silent after signup

Tell subscribers what happens next and send useful progress only when there is something relevant to share. Before launch, confirm that they still want access and remind them of the original problem and promise.

Recruiting partners before the offer works

External marketers can extend a clear offer. They should not be expected to discover the customer, invent the positioning, repair onboarding, and define attribution simultaneously.

Pre-launch marketing checklist

Before opening the launch to a wider audience, confirm:

• One ideal customer and urgent trigger are documented.
• The current alternative is understood.
• The product promise is specific and supportable.
• One activation event represents first value.
• The waitlist has a clear purpose and expectation.
• Signup fields collect only information you will use.
• At least one matched user has completed the core workflow.
• The largest onboarding blocker has been addressed.
• Campaign sources are tracked through activation.
• The launch audience is segmented by fit and intent.
• Proof assets use real product evidence.
• Follow-up messages are ready before invitations go out.
• Invitations will be sent in manageable waves.
• The team has a continue, revise, or stop rule for the channel.

For the public release that follows, use the 30-day SaaS product launch strategy. For the wider path from early conversations to repeatable acquisition, read the startup customer acquisition plan.

FAQ

What is pre-launch marketing?

Pre-launch marketing is the work done before a public product release to validate the customer and problem, test positioning, recruit early users, build a qualified launch audience, prepare proof, and confirm that users can reach product value.

How early should SaaS pre-launch marketing begin?

Begin as soon as you can discuss the problem with target customers. A focused 30-day plan can test the audience, message, waitlist, and beta path, but complex B2B products may need a longer period for procurement, integrations, or guided pilots.

How do you market a product before it is ready?

Market the problem, intended outcome, and testable workflow honestly. Use interviews, example outputs, prototypes, design-partner programs, and limited beta access. State what exists today, what remains incomplete, and what participation requires.

What should a pre-launch landing page include?

Include the target customer, problem, product outcome, short workflow explanation, honest evidence, fit guidance, one call to action, and a clear explanation of what happens after signup.

How many people should be on a pre-launch waitlist?

There is no universal target. The useful number depends on the product, market, price, onboarding capacity, and expected activation rate. A small group of matched prospects who accept invitations and activate can be more valuable than a large generic list.

Which pre-launch marketing metrics matter most?

Track matched prospects reached, qualified replies or visits, beta or waitlist commitments, invitation acceptance, activation, time to first value, return usage, and repeated objections. Review the metrics by audience and acquisition source.

When should a SaaS founder recruit performance marketers?

Recruit performance marketers after the founder can define the customer, product promise, proof, conversion event, attribution method, channel rules, and sustainable compensation. Start with a small test and judge performance by qualified activation and retained value rather than traffic alone.