
Sign Up Stream
A pre-launch waitlist that keeps intent warm
A drop-in waitlist page that captures email, project name and consent in one pill, posts straight to a Make.com webhook, and keeps the lead warm with on-brand confirmation.
01 — The business problem
Most pre-launch waitlists leak intent. You collect an email and then ghost the lead for weeks before launch. By the time you have something to show, the warm signal has gone cold and the attention you paid for is wasted.
02 — The workflow
- Single email input in a rounded pill, with an optional marketing-consent checkbox on the same surface. No second screen.
- Submission POSTs to a Make.com (or Zapier / n8n) webhook with email, project_name, marketing_consent and timestamp, routable into a CRM, Notion table, Loops or ConvertKit downstream.
- The success state confirms the exact email used and switches the page to a calm 'you're on the list' confirmation, with project branding intact.
- The error state auto-resets after 3 seconds so a transient webhook failure does not strand the user on a dead form.
03 — What I built
- Single-page build, dark surface, single neon-green accent. Deliberately minimal so it adapts to any sub-brand.
- Configurable PROJECT_CONFIG block (project name and webhook URL). The same component drops into any new venture in minutes.
- Framer Motion micro-interactions on submit, success and error states.
- Mobile-first by construction. The pill, consent line and footer stack cleanly without a separate layout.
04 — Tools used
Make.com webhook (Zapier / n8n compatible) · Framer Motion · React + Vite
05 — Commercial use case
A drop-in waitlist surface for pre-launch ventures, agency client projects and internal R&D bets. It is the kind of micro-build a customer engineer ships in an afternoon to unblock a launch, and the pattern scales to every subsequent venture without rework.
06 — ROI and adoption
Hours from 'idea has a name' to 'leads in a CRM', instead of days.
Illustrative assumptions
- Baseline: a custom waitlist page typically takes 1 to 2 days of design, frontend and integration work per venture.
- This pattern compresses that to under an hour. Change two config values and ship.
- Assumes the venture already has a marketing automation tool (Make, Zapier or n8n) and a downstream destination (CRM, Loops, ConvertKit).