Waitlist

Comprehensive documentation for the KilatKoding waitlist feature, including pre-launch use cases, Supabase dependencies, and funnel verification.

The waitlist feature is most useful when you do not want to open the full application yet, but you do want to start validating demand and collecting interested users.

What this feature includes

• /waitlist
• POST /api/waitlist
• waitlist signup storage

Related routes and endpoints

Route or endpoint	Type	Purpose
/waitlist	Public page	Waitlist form for potential users
POST /api/waitlist	API mutation	Stores the waitlist signup

Who uses it

• potential users,
• founders validating demand,
• marketing teams running a pre-launch funnel.

Main dependencies

Item	Required?	Notes
NEXT_PUBLIC_ENABLE_WAITLIST=true	Yes	Enables the waitlist page and API
NEXT_PUBLIC_SUPABASE_URL	Yes	Needed to store data
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY	Yes	Needed for the relevant client access
Waitlist table migration	Yes	The table must exist and be ready

What teams usually customize

• waitlist CTA,
• demand-validation copy,
• pre-launch value proposition,
• success and duplicate-submission messages,
• the relationship between the landing page and the waitlist funnel.

When this feature is disabled

It is usually disabled when:

• the product is fully open,
• the main funnel shifts to signup or checkout,
• waitlist no longer matches the product positioning.

Verification checklist

1. /waitlist can be opened.
2. A new email can be submitted successfully.
3. A duplicate email shows a clear response.
4. Public CTA paths point to the waitlist when it is the intended funnel.
5. There are no dashboard or billing CTA paths if the product is still only in waitlist mode.

If you use waitlist as the launch strategy, continue to Launch checklists and Preset recipes by use case.