BUILDSIDE — YOUR SAAS PRELAUNCH PLAN
https://www.buildside.app/solutions/grow-saas-waitlist

A four-update plan + signup-quality worksheet
Use this as a working document. Adapt it to real progress, not a fixed schedule.

BEFORE YOU SHARE
Product:
Intended user:
Problem they already experience:
What is usable now:
What is still unfinished:
What joining the waitlist means:
What happens next, and when (only if known):
Public waitlist URL:

UPDATE 1 — THE PROBLEM
The recent experience I want to understand:
The question I can ask without suggesting an answer:
Where relevant people already discuss this:
My draft:

UPDATE 2 — THE PROTOTYPE
The real progress or decision I can show:
What the example demonstrates:
What it does not demonstrate yet:
My draft:

UPDATE 3 — THE CONSTRAINT
The limitation I need to explain:
How it changes expectations for early access:
What I am investigating next:
My draft:

UPDATE 4 — THE INVITATION
Who this is for:
Why this update is relevant to them:
What joining means (do not imply immediate access unless available):
The waitlist link and next step:
My draft:

DISTRIBUTION NOTES
Community or existing conversation:
Why the problem is relevant here:
Posting rules / permission to follow up:
Useful context to contribute:
What I learned from the response:

SIGNUP-QUALITY WORKSHEET
Use one entry per person or conversation. Keep personal details private.

Person or private reference:
Audience fit: How do they currently handle this problem?
Joined: What expectation did the waitlist page establish?
Replied: What concrete experience did they describe?
Tried: What relevant task did they complete, if any?
Returned: Did they use the product again when the need arose?
Buying decision: What evidence, if any, is there of willingness to pay?
Next step / owner:
Date reviewed:

Review these commitments separately. A signup is interest, not proof of payment.
A helpful peer can give feedback without matching your customer profile.

FOLLOW-UP
Does the product description still match what is available?
What did subscribers expect to hear about?
Is a test invitation now appropriate, and what does it involve?
Who needs a clear update if timing or scope changes?
Export your Buildside signup list for your own follow-up workflow.
Respect subscriber expectations and make it easy to decline further contact.

PocketLedger, used on the landing page, is a fictional example.
Buildside — build in public.