Skip to content
WaitForge
Open navigation
WaitForge

Collect the waitlist, verify interest, and launch from evidence.

Sign in Request beta access

Launch playbooks

Choose the right launch path for your audience.

WaitForge helps authors, SaaS teams, creators, product makers, communities, and studios collect real audience intent before launch. Choose the playbook that matches your goal.

Find your launch playbook See how WaitForge works

All 7 playbooks use the same audience record.

Different launches, one audience record

The playbook changes what you ask first. It never changes where the answer lands.

One record
Launch paths you can start from
7 playbooks
Consent and answers on the same person
Always
The next move the playbook recommends
Per path
A second list to reconcile later
Never
What every playbook has in common.
Playbooks live
7 launch paths
Same loop
Capture → launch
Start surface
Hosted, embed, or API
Handoff
Export or invite

Choose by pressure

What is actually hard about this launch?

Use cases here are not industries. They are constraints. Match the pressure you feel to the signal you need, then open the playbook that runs that signal.

Start with the row that describes your current risk. The industry label can come later.

Open the matching playbook

Open only the playbook that matches your pressure.

The board routes every live pressure to a signal. Open a row for the operating flow, the capabilities, and the outcome.

7 live paths on one audience record

Decision board

Route the uncertainty

7 live paths

Readers are curious, not committed

Intent by preferred edition

Independent book release

Every email looks equal

Cohorts with problem context

SaaS private beta

Public reactions do not show commitment

Topics ranked by interest

Course or newsletter launch

Demand is still a guess

Demand by preferred variant

Small product launch

Client launches fragment

One view across client launches

Launch studio

Interest does not show implementation readiness

Readiness by implementation context

Developer API launch

The community needs one focused next step

Fit by goal and timing

Community or cohort launch
Start with the risk. Keep one audience lifecycle. Pressure → signal → action
Reader launch list

Independent book release

 Signal to watch Intent by preferred edition

Launch pressure

Readers ask about formats, signed editions, and release timing before the manuscript is ready.

Book campaign Edition questions Launch updates

Operating approach

Publish a branded book campaign, ask which edition each reader wants, share publication updates, and export a clean launch list.

  1. 01 Offer a preview
  2. 02 Qualify readers
  3. 03 Announce the release

Know who wants the book and what they want before opening sales on your own storefront.

Qualified access

SaaS private beta

 Signal to watch Cohorts with problem context

Launch pressure

A long email list says little about which users have the urgent problem the product solves.

Custom questions Consent record Audience tags

Operating approach

Ask one or two qualification questions, verify each signup, and tag the first cohorts by use case.

  1. 01 Capture the problem
  2. 02 Verify interest
  3. 03 Invite a cohort

Invite the right early users instead of treating every email as equal.

Audience validation

Course or newsletter launch

 Signal to watch Topics ranked by interest

Launch pressure

Followers may like an idea publicly without committing to a specific topic, format, or launch date.

Hosted page Interest questions Public updates

Operating approach

Create a focused campaign, ask what people want to learn, and publish useful progress updates before release.

  1. 01 Frame the promise
  2. 02 Collect preferences
  3. 03 Prepare launch

Choose the first offer from explicit audience intent rather than reactions and guesses.

Demand forecast

Small product launch

 Signal to watch Demand by preferred variant

Launch pressure

Ordering inventory before knowing likely demand creates avoidable cash and storage risk.

Product story Variant questions Source analytics

Operating approach

Show the upcoming product, collect variant preferences, and measure registrations by traffic source.

  1. 01 Show the product
  2. 02 Capture preference
  3. 03 Plan the drop

Use launch intent to shape the first production run before adding a full store.

Client operations

Launch studio

 Signal to watch One view across client launches

Launch pressure

Multiple client launches produce scattered forms, sheets, exports, and inconsistent reporting.

Multiple campaigns Team roles Branded pages

Operating approach

Operate branded campaigns from one workspace with repeatable setup, team roles, and consistent audience exports.

  1. 01 Standardize setup
  2. 02 Apply each brand
  3. 03 Report outcomes

Give each client a clear launch workflow without assembling a new stack every time.

Technical beta

Developer API launch

 Signal to watch Readiness by implementation context

Launch pressure

Docs and demos attract interest, but they do not tell you which teams have a real implementation path.

API access Use-case questions Invite waves

Operating approach

Capture the use case, team context, and expected timeline before inviting builders into the private beta.

  1. 01 Publish the contract
  2. 02 Capture the use case
  3. 03 Invite builders

Prioritize teams that can give actionable feedback and reach a successful first request sooner.

Cohort enrollment

Community or cohort launch

 Signal to watch Fit by goal and timing

Launch pressure

A community can be active and still make it hard to see who is ready for a specific program, event, or new track.

Cohort questions Consent record Invite waves

Operating approach

Collect the member goal, preferred timing, and consent for updates, then create a focused invite wave.

  1. 01 Frame the cohort
  2. 02 Collect intent
  3. 03 Open enrollment

Turn broad community energy into a launch-ready cohort with a clear reason to act.

A book campaign's qualifying answers

The question an author needs answered before a single copy is printed.

Qualified
Which edition do you want?
Hardback · Paperback · Ebook
Would you buy a signed copy?
Yes · No
Where should it ship?
Region
Payment taken here
Never
Audience qualified
Reader preferences become a launch-ready audience.

An author can validate a release before building a bookstore.

Publish a book campaign, ask readers which format or edition they prefer, share sample and publication updates, and export the final launch audience. When sales open, send readers to the author’s own checkout—WaitForge keeps the pre-launch workflow focused.

Campaign
Book release
Qualification
Format + edition
Communication
Launch updates
Handoff
Export audience

Own the amount of surface that matters.

Start with the fastest path today. Move toward deeper control later without replacing the signup lifecycle underneath it.

The audience record stays the same whether you start hosted, embed the form, or connect your own interface.

Hosted page

Choose it when
Speed matters most
Time to signal
Minutes
System underneath
Theme, audience state, and analytics

Embedded form

Choose it when
Your site owns the story
Time to signal
One script
System underneath
The same signup and queue lifecycle

Public API

Choose it when
Your UI must be fully custom
Time to signal
A few endpoints
System underneath
Validation, consent, and queue state
See the lifecycle Compare integrations

Start with one email campaign. Build toward launch day.

Choose the simplest signup surface now. Qualify the audience, track where demand comes from, and prepare a clean launch handoff without building a temporary commerce stack.

Request beta access