Twenty's waitlist intent maps well to landing-page kits with waitlist search. Read setup instructions for storage and email provider choices before you buy.
What a serious waitlist stores
- Email, createdAt, and optional referral source.
- Consent timestamp if you market in regulated regions.
- Status flags for confirmed vs pending if you use double opt-in.
- Notes field for manual qualification later.
Validation loop
- Ship a clear promise on the landing page.
- Capture emails with consent language.
- Message a small cohort with a survey or early access offer.
- Track reply rate and payment intent - not only signup count.
- Only then buy a full boilerplate if signals look real.
After validation, jump to the indie hackers or MVP use cases and browse full SaaS boilerplates.
Spam and quality
Public forms attract bots. Kits should document rate limits, honeypots, or CAPTCHA. Without that, your "demand" is noise and your ESP reputation suffers.
From waitlist to first revenue
- Segment by signup date and source.
- Offer a founding-member price to the first N confirmed emails.
- Interview ten users before you build rare edge features.
- Keep the waitlist page live even after launch for overflow demand.
Legal and trust basics
- Link privacy policy near the form.
- Say what you will email and how often.
- Provide unsubscribe when you start campaigns.
- Do not buy email lists to "seed" the waitlist - it destroys signal.
If you already have Twenty's waitlist kit direction in-repo, compare marketplace listings against the same bar: SETUP docs, env vars, and export path.