# Build brief — a focused alternative to GetWaitlist / LaunchList

> **Verdict:** Yes, for personal use · **Buildability:** 76/100 · **Category:** Waitlists
> **Source:** https://www.canitbevibecoded.com/getwaitlist
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from GetWaitlist / LaunchList. Verify current pricing and capabilities before acting.

## Context

**GetWaitlist / LaunchList** — Email capture with a referral counter. It currently costs $15/mo.

Email capture with a referral counter. This site's waitlist was built exactly this way — it took one prompt.

This brief describes a focused, single-operator replacement for the part of GetWaitlist / LaunchList that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

A focused, single-user version of GetWaitlist / LaunchList's main workflow.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a waitlist signup system like GetWaitlist. Requirements:

- A drop-in signup form (one HTML snippet I can paste into any landing page):
  email field + submit, posting to /api/waitlist.
- Server stores emails in SQLite with created_at, referral_code (short unique
  slug per signup), and referred_by. Dedupe by email, honeypot field for bots,
  rate-limit by IP.
- After signup, show the user their position in line and a personal referral
  link (?ref=CODE). Each signup arriving via their link moves them up 5 spots ·
  recompute position as base_position minus 5 × referrals.
- A /admin page (basic-auth from .env): count, growth chart drawn with a tiny
  inline SVG (no chart libraries), CSV export, delete button per row.
- No third-party services, no client-side JS frameworks. Node or Python, one
  process, deploy instructions for a VPS behind a reverse proxy.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Their referral-widget templates.
- Built-in email blasts to the list.
- Spam filtering you didn't tune yourself.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
- Reliability at the vendor's scale is an operations problem, not a prompt.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/getwaitlist