Design the waitlist offer

People need a reason to join now instead of waiting for launch.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Design my waitlist offer. I will describe the product below. Produce: the core promise of joining (what waitlisters get that latecomers do not - early access, founding price, limited perk, input on the roadmap); the position mechanic (numbered spots, tiers, or simple list - recommend one); the honest scarcity logic (real capacity limits or staged rollout reasoning); and the one-line pitch for the page. No fabricated urgency.

MY PRODUCT: [describe here]

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A join-now offer with mechanic, honest scarcity, and page pitch.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

The waitlister advantage is concreteScarcity logic is realOne mechanic is chosen

Do not continue if…

! A 'join waitlist' form that stores nothing
! No reason to join before launch (why not just wait?)
! Radio silence until launch, then a cold blast
! Fake 'Join 10,000 others' counters

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

There is no reason to join early. Add a real early-joiner advantage (founding price, capacity-limited access, or roadmap influence) or the waitlist is just delayed marketing.