Verified against Bolt.new · 2026-07-24
Build a waitlist landing page with a real signup form
A Bolt.new landing-page brief that treats the signup form as the actual product: the exact Supabase table, insert logic, and duplicate-email handling are specified up front, since Bolt.new has no database or auth of its own to fall back on.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Build a single-page marketing site for Recap, an AI meeting-notes tool that writes the follow-up email for you. The goal is to collect email signups for a waitlist before launch. Page sections, in order: 1. Hero — headline, one-line subheading, and the signup form (button text: Get early access) above the fold. 2. How it works — three short steps with icons. 3. Social proof — a row of three placeholder testimonial quotes with name and role. 4. FAQ — four questions in a collapsible accordion. 5. Footer — signup form repeated, plus a contact address: hello@getrecap.com. Signup form requirements — this is the important part: - Fields: email (required), and optionally name. - Bolt.new has no database or auth of its own, so wire this form directly to Supabase: create a waitlist_signups table (columns: id, email, name, created_at, source) and insert a row on submit using the Supabase JS client. - Show inline validation for an invalid email format, and a success state (for example, "You're on the list") after a successful insert, without a full page reload. - Handle the duplicate-email case — a unique constraint on email — by showing a friendly "you're already signed up" message instead of a raw database error. - Do not build any other auth. This page only ever needs a one-way form submission, never a login. Style: dark background, one accent lime-green color, big confident type. Fully responsive, single page, no unused component libraries.
Customize the highlighted detailsoptional — the prompt above already works
Why this works
Bolt.new spins up a full StackBlitz WebContainer environment but has no managed database or auth of its own — that gap is the single most-cited limitation of the tool. A prompt that just says "add a signup form" gets a form that either fakes a success message with nowhere for the data to go, or throws a runtime error the moment it tries to reach a backend that was never wired up. Naming the exact Supabase table, its columns, and how to handle a duplicate email is what turns a good-looking landing page into a waitlist you can actually export and follow up with.
What you get back
A live Bolt.new preview URL with a dark hero, a working email field, and a Supabase waitlist_signups table that gains a real row every time the form is submitted, plus a friendly message if the same email is submitted twice.
Verified against
Bolt.new Bolt.new web app (StackBlitz WebContainers, Supabase integration panel) · 2026-07-24
Changelog
- 2026-07-24 — Initial version, written explicitly around Bolt.new's missing built-in database/auth after an earlier draft without a named backend produced a form with no persistence.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE

