AddThisFeature

Waitlist

Capture demand before you're ready to open the doors.

simple Growth

What it adds

An email capture that gates access and lets you admit people in batches.

What your agent is told to do

4
  1. 1

    Add an email capture on the landing page, storing entries with a timestamp and source.

  2. 2

    Give yourself an admin way to admit people, individually or in batches.

  3. 3

    Send an email when someone is admitted, with a unique access link.

  4. 4

    Confirm clearly on signup — 'you're #482' beats a silent redirect.

Edge cases it handles

4
  • The same email joining twice must not create two entries or two emails.
  • Validate the email address; a waitlist full of typos is worthless.
  • Rate-limit the endpoint — it's public and will be abused.
  • An admitted user's access link must be single-use and expiring.

Definition of done

7
  • Emails are validated and deduplicated.
  • The endpoint is rate-limited against abuse.
  • Admins can admit people individually or in batches.
  • Admission sends a unique, expiring access link.
  • Signup gives clear confirmation.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.