Skip to content
Marketing block

Waitlist Hero with Email Capture

A pre-launch hero whose only ask is an email address, with pending and success states and a signup count that argues for finishing rather than starting.

163 lineslucide-reactAdded 8 Aug 2026Updated 10 Sept 2026
  • hero
  • waitlist
  • email
  • launch
  • form

What's included

  • components/hero-waitlist.tsx
  • Needs lucide-react

Works with

  • React
  • Next.js
  • Tailwind CSS
  • TypeScript

npx hoverlab add hero-waitlist

Or over MCP, from your editor's agent — no account needed.

License

Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.

Was this useful?

Start a page with this section — add more, order them, and leave with the page source.

Preview

Be first through the door.

We are letting people in a few hundred at a time. Leave your email and we will send an invite the moment a slot opens.

No spam, and one unsubscribe link in every email.

4,128 already waiting

Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.

Source

components/hero-waitlist.tsx
'use client'

/**
 * <HeroWaitlist> — a pre-launch hero whose only ask is an email address.
 *
 * One field and one button, because every extra control on a waitlist form
 * is a reason to leave. The social proof sits *under* the input rather than
 * above it: it is an argument for finishing, not for starting, and it reads
 * as filler before someone has decided to type.
 *
 * The form is a real `<form>` with a real `type="email"` input, so browser
 * autofill works, the phone keyboard shows the @ key, and the enter key
 * submits. `onSubmit` receives the address; wire it to your list provider.
 * With no handler passed, it resolves locally after a beat — which is what
 * makes the preview honest without a network call.
 *
 * The success state replaces the form rather than sitting beside it, and
 * the live region announces it. A confirmation that only appears visually
 * leaves a screen-reader user staring at a form they think failed.
 */

import * as React from 'react'
import { ArrowRight, Check, Loader2 } from 'lucide-react'

export interface HeroWaitlistProps {
  heading?: string
  subheading?: string
  placeholder?: string
  submitLabel?: string
  successMessage?: string
  note?: string
  /** How many are already on the list. Omit to hide the proof row. */
  waitlistCount?: number
  /** Return a promise to keep the button in its pending state until settled. */
  onSubmit?: (email: string) => void | Promise<void>
  className?: string
}

type Status = 'idle' | 'pending' | 'done'

export function HeroWaitlist({
  heading = 'Be first through the door.',
  subheading =
    'We are letting people in a few hundred at a time. Leave your email and we will send an invite the moment a slot opens.',
  placeholder = 'you@company.com',
  submitLabel = 'Request an invite',
  successMessage = "You're on the list. Watch your inbox.",
  note = 'No spam, and one unsubscribe link in every email.',
  waitlistCount = 4128,
  onSubmit,
  className = '',
}: HeroWaitlistProps) {
  // Per-instance ids. A literal id in a reusable component is a
  // collision waiting for the second copy on the page — and a <label>
  // then resolves to whichever input rendered first.
  const uid = React.useId()
  const [email, setEmail] = React.useState('')
  const [status, setStatus] = React.useState<Status>('idle')

  async function handleSubmit(event: React.FormEvent<HTMLFormElement>) {
    event.preventDefault()
    if (status !== 'idle') return

    setStatus('pending')
    try {
      // Without a handler this still resolves — the preview has to show the
      // pending and success states, and a block that only works once it is
      // wired up is a block nobody can evaluate.
      await (onSubmit?.(email) ?? new Promise((r) => setTimeout(r, 700)))
      setStatus('done')
    } catch {
      setStatus('idle')
    }
  }

  return (
    <section className={`relative overflow-hidden ${className}`}>
      <div aria-hidden className="pointer-events-none absolute inset-0 -z-10">
        <div className="absolute -top-32 left-1/2 h-96 w-96 -translate-x-1/2 rounded-full bg-primary/20 blur-3xl border border-transparent" />
      </div>

      <div className="mx-auto w-full max-w-2xl px-4 py-20 text-center sm:px-6 lg:py-28">
        <h1 className="text-balance text-4xl font-extrabold tracking-tight sm:text-5xl lg:text-6xl">
          {heading}
        </h1>
        <p className="mx-auto mt-5 max-w-xl text-pretty leading-relaxed text-muted-foreground sm:text-lg">
          {subheading}
        </p>

        <div className="mt-9" aria-live="polite">
          {status === 'done' ? (
            <p className="inline-flex items-center gap-2 rounded-xl border border-emerald-500/30 bg-emerald-500/10 px-5 py-3.5 text-sm font-medium text-emerald-600 dark:text-emerald-400">
              <Check aria-hidden className="h-4 w-4" />
              {successMessage}
            </p>
          ) : (
            <form onSubmit={handleSubmit} className="mx-auto flex max-w-md flex-col flex-wrap gap-2 sm:flex-row">
              <label htmlFor={`${uid}-waitlist-email`} className="sr-only">
                Email address
              </label>
              <input
                id={`${uid}-waitlist-email`}
                type="email"
                required
                autoComplete="email"
                value={email}
                onChange={(e) => setEmail(e.target.value)}
                placeholder={placeholder}
                disabled={status === 'pending'}
                className="h-12 min-w-0 flex-1 rounded-xl border border-border/60 bg-card/60 px-4 text-sm backdrop-blur transition-colors placeholder:text-muted-foreground focus:border-primary/50 focus:outline-none focus:ring-2 focus:ring-ring/30 disabled:opacity-60"
              />
              <button
                type="submit"
                disabled={status === 'pending'}
                className="inline-flex h-12 items-center justify-center gap-1.5 rounded-xl bg-primary px-6 text-sm font-semibold text-primary-foreground shadow-lg shadow-primary/25 transition-transform hover:-translate-y-0.5 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2 focus-visible:ring-offset-background disabled:translate-y-0 disabled:opacity-70"
              >
                {status === 'pending' ? (
                  <>
                    <Loader2 aria-hidden className="h-4 w-4 animate-spin motion-reduce:[animation-duration:1.6s]" />
                    Joining
                  </>
                ) : (
                  <>
                    {submitLabel}
                    <ArrowRight aria-hidden className="h-4 w-4 rtl:rotate-180" />
                  </>
                )}
              </button>
            </form>
          )}
        </div>

        {note ? <p className="mt-3 text-xs text-muted-foreground">{note}</p> : null}

        {waitlistCount ? (
          <div className="mt-8 flex items-center justify-center gap-3">
            {/* Initials, not photographs: a stock-photo avatar row is a
                claim about who your users are, and an obviously synthetic
                one is not. */}
            <div aria-hidden className="flex -space-x-2">
              {['AL', 'RS', 'MK', 'JT', 'PW'].map((initials, i) => (
                <span
                  key={initials}
                  style={{ zIndex: 5 - i }}
                  className="flex h-8 w-8 items-center justify-center rounded-full border-2 border-background bg-gradient-to-br from-primary/70 to-primary text-[10px] font-bold text-primary-foreground"
                >
                  {initials}
                </span>
              ))}
            </div>
            <p className="text-sm text-muted-foreground">
              <span className="font-semibold text-foreground">
                {waitlistCount.toLocaleString('en-US')}
              </span>{' '}
              already waiting
            </p>
          </div>
        ) : null}
      </div>
    </section>
  )
}

Before you paste

  • Styling is Tailwind utility classes on semantic tokens (bg-card, text-muted-foreground) — it inherits your theme instead of overriding it.
  • Install: npm i lucide-react
  • Every prop has a default, so it renders standalone before you wire it up.

Where it goes

Drop it at components/hero-waitlist.tsx and import it where you need the section:

import { HeroWaitlist } from '@/components/hero-waitlist'

Customize

6 of this block’s props are simple enough to drive from here. Change them and the block below re-renders — it is the same component whose source is above, not a mock of it. Everything else it accepts is in the table underneath.

Props

Read out of the component’s own type and signature, so this cannot drift from the source below. Every prop has a default — the component renders standalone before you pass it anything.

PropTypeDefault
headingstring'Be first through the door.'
subheadingstring—
placeholderstring'you@company.com'
submitLabelstring'Request an invite'
successMessagestring"You're on the list. Watch your inbox."
notestring'No spam, and one unsubscribe link in every e…
waitlistCountHow many are already on the list. Omit to hide the proof row.number4128
onSubmitReturn a promise to keep the button in its pending state until settled.(email: string) => void | Promise<void>—
classNamestring''

Not using React?

The same block rendered once to markup, wrapped as a file your framework compiles. Tailwind classes are framework-agnostic, so the design transfers intact — the behaviour does not.

This block is interactive. The markup below is its initial state with the event handlers stripped — you will need to re-wire the behaviour in your framework.

hero-waitlist.html
<!--
  Waitlist Hero with Email Capture — markup from the Hoverlab catalog.

  This is the block rendered once to HTML and wrapped as a component
  file. It is not a port of the React source: the Tailwind classes carry
  the design, which is the part that took the work, and they are the same
  in every framework.

  This block is interactive in React and the handlers are NOT here.
  Buttons, toggles and menus render in their initial state and do
  nothing until you wire them up.
-->
<section class="relative overflow-hidden ">
  <div aria-hidden="true" class="pointer-events-none absolute inset-0 -z-10">
    <div class="absolute -top-32 left-1/2 h-96 w-96 -translate-x-1/2 rounded-full bg-primary/20 blur-3xl border border-transparent"></div>
  </div>
  <div class="mx-auto w-full max-w-2xl px-4 py-20 text-center sm:px-6 lg:py-28">
    <h1 class="text-balance text-4xl font-extrabold tracking-tight sm:text-5xl lg:text-6xl">Be first through the door.</h1>
    <p class="mx-auto mt-5 max-w-xl text-pretty leading-relaxed text-muted-foreground sm:text-lg">We are letting people in a few hundred at a time. Leave your email and we will send an invite the moment a slot opens.</p>
    <div class="mt-9" aria-live="polite">
      <form class="mx-auto flex max-w-md flex-col flex-wrap gap-2 sm:flex-row">
        <label for="_R_0_-waitlist-email" class="sr-only">Email address</label>
        <input id="_R_0_-waitlist-email" type="email" required="" autoComplete="email" placeholder="you@company.com" class="h-12 min-w-0 flex-1 rounded-xl border border-border/60 bg-card/60 px-4 text-sm backdrop-blur transition-colors placeholder:text-muted-foreground focus:border-primary/50 focus:outline-none focus:ring-2 focus:ring-ring/30 disabled:opacity-60" value="" />
        <button type="submit" class="inline-flex h-12 items-center justify-center gap-1.5 rounded-xl bg-primary px-6 text-sm font-semibold text-primary-foreground shadow-lg shadow-primary/25 transition-transform hover:-translate-y-0.5 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2 focus-visible:ring-offset-background disabled:translate-y-0 disabled:opacity-70">Request an invite<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-arrow-right h-4 w-4 rtl:rotate-180" aria-hidden="true"><path d="M5 12h14"></path><path d="m12 5 7 7-7 7"></path></svg></button>
      </form>
    </div>
    <p class="mt-3 text-xs text-muted-foreground">No spam, and one unsubscribe link in every email.</p>
    <div class="mt-8 flex items-center justify-center gap-3">
      <div aria-hidden="true" class="flex -space-x-2">
        <span style="z-index:5" class="flex h-8 w-8 items-center justify-center rounded-full border-2 border-background bg-gradient-to-br from-primary/70 to-primary text-[10px] font-bold text-primary-foreground">AL</span>
        <span style="z-index:4" class="flex h-8 w-8 items-center justify-center rounded-full border-2 border-background bg-gradient-to-br from-primary/70 to-primary text-[10px] font-bold text-primary-foreground">RS</span>
        <span style="z-index:3" class="flex h-8 w-8 items-center justify-center rounded-full border-2 border-background bg-gradient-to-br from-primary/70 to-primary text-[10px] font-bold text-primary-foreground">MK</span>
        <span style="z-index:2" class="flex h-8 w-8 items-center justify-center rounded-full border-2 border-background bg-gradient-to-br from-primary/70 to-primary text-[10px] font-bold text-primary-foreground">JT</span>
        <span style="z-index:1" class="flex h-8 w-8 items-center justify-center rounded-full border-2 border-background bg-gradient-to-br from-primary/70 to-primary text-[10px] font-bold text-primary-foreground">PW</span>
      </div>
      <p class="text-sm text-muted-foreground"><span class="font-semibold text-foreground">4,128</span> already waiting</p>
    </div>
  </div>
</section>
  • This is rendered HTML, not a translation of the React source. The Tailwind classes carry the design and work in any framework.
  • It is one frame: the component in its initial state, with no props applied beyond the defaults.
  • This block is interactive in React — toggles, menus or form state. None of that survives here; the markup is the closed/default state and the handlers are gone. Re-wire them in your own framework.
  • Requires Tailwind, and the design tokens the classes reference (bg-card, text-muted-foreground, and so on). The template ZIPs ship a globals.css that defines them.

What each framework gets across the whole catalog — effects convert properly; this rung is markup.

For AI

The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.

See the prompt

Used in these pages

Want the whole screen instead of this one section? Open a page and copy it entire.

13 more blocks in Heroes

All of them free to read, copy and install — no account, no locked tiles, no watermarked preview. The whole catalog is open, and so are the API and the CLI.

Browse Heroes

Shipping one commercially

Copying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.

  • A commercial licence for everything in the catalog
  • Unlimited bundle exports, in Vue, Svelte and Tailwind
  • One payment — no subscription, nothing to renew
Pro — $79 once

More Heroes blocks

View category
Open the full page for this block

Split Hero with Product Panel

Copy on the left, a drawn product panel on the right — the default hero for anything with an interface to show, with no image asset to host and no layout shift while it loads.

Heroes176 lines1 dep
Open the full page for this block

Centered Announcement Hero

A linked announcement pill over a large centered headline, dual CTAs and a wordmark strip — the hero for a product with nothing to screenshot yet.

Heroes125 lines1 dep
Open the full page for this block

Hero with Browser Frame

Centered copy above a screenshot in window chrome, masked at the bottom so a tall image never dictates the height of the fold. Wraps your own img or video.

Heroes191 lines1 dep
Open the full page for this block

Search-First Hero

A hero whose primary action is a real search form with prefilling suggestion chips — for marketplaces and directories, where sending the visitor below the fold to find the search box is the whole failure.

Heroes128 lines1 dep
Open the full page for this block

Developer Hero with Install Command

A drawn terminal whose install line is real, selectable text with a working copy button and a feature-detected clipboard call — the hero for anything adopted by typing rather than signing up.

Heroes163 lines1 dep
Open the full page for this block

App Download Hero with Phone

A drawn phone beside two store links built as real anchors rather than badge images, so they inherit the theme, need no hosted asset and carry an accessible name that is not a filename.

Heroes161 lines1 dep
Open the full page for this block

Hero Anchored by a Customer Quote

Pitch on the left, a marked-up figure and blockquote on the right, so the claim and the evidence for it share the fold instead of sitting a scroll apart.

Heroes129 lines1 dep
Open the full page for this block

Hero with Proof Metrics

A centered hero closing on a definition list of scale numbers, with a masked grid wash behind it — for infrastructure and payments, where "how many" is the second question a buyer asks.

Heroes129 lines1 dep
Open the full page for this block

Editorial Masthead Hero

A serif display headline over a 60-character standfirst and a real byline, with one text link and no competing CTAs — the hero for publications and essays, where the writing is the product.

Heroes99 lines1 dep
Open the full page for this block

Full-Bleed Media Hero

Copy over your own image or video, with a graded scrim and deliberately fixed light-on-dark text — because the background is a photograph in both themes, so flipping the copy would break it.

Heroes106 lines1 dep
Open the full page for this block

Integration Wall Hero

A hero whose visual is the connector list itself, marked up as a real list so a visitor can skim it for their own stack — asset-free initials tiles, no third-party marks to license.

Heroes135 lines1 dep
Open the full page for this block

Appointment Booking Hero

A day strip built as a radio group rather than buttons, so arrow keys move between dates and sold-out days disable properly — the fold for anything sold by the appointment.

Heroes168 lines1 dep
Open the full page for this block

Hero with Inline Price

Names the price above the fold for single-plan and one-time products, with the former price in a real strikethrough element so it is never announced as the current one.

Heroes135 lines1 dep