Skip to content

Recipe R04

The Launch

A pre-launch page for a SaaS product: a waitlist that prints your ticket, the product working, launch pricing and answers.

Teams launching a developer tool or SaaS product who want the waitlist itself to feel like part of the product.

ScenarioA pre-launch page for a deploy-preview platform in private beta: join the waitlist and see your place in line, see what works today, lock in launch pricing, ask questions, and know when the next wave opens.

The page, section by section

  1. 01

    A gradient ring that floods the button on hover: the waitlist action, always in view at the top.

  2. 02

    Join with your email and a ticket prints with your place in line, the estimated wait and a link that moves you up.

  3. 03

    What works today

    Bento Grid

    Tiles of working interface (live traffic, a command palette, presence, settings, regions) instead of feature icons.

  4. 04

    Launch pricing

    Credit Tier Pricing

    Three plans in black glass with a month/year switch and the cost per 100 credits, so the value is comparable.

  5. 05

    An FAQ you ask: each answer suggests the next question, and a person is one tap away.

  6. 06

    The closing call with the next wave's date, seats per wave and the queue running round its border.

Change first

The first things to replace to make this page yours.

  1. Connect the waitlist to your real list, with your real queue size and how many you let in each week.
  2. Rebuild the bento tiles from features that genuinely work in your beta, using your own product screens.
  3. Set the three plans, credit units and launch-pricing promise to what you will honour.
  4. Rewrite the chat FAQ from questions people have actually asked you about the beta.

The build brief

Copy this text

Automatic copying is unavailable. Copy the selected text using your device’s copy command.

Paste it into Claude, Cursor or ChatGPT with the component files, and ask for your own version: your name, your work, your product. It names each component and where to copy it from.

# Build brief: The Launch

A pre-launch page for a SaaS product: a waitlist that prints your ticket, the product working, launch pricing and answers.
For: Teams launching a developer tool or SaaS product who want the waitlist itself to feel like part of the product.

Scenario: A pre-launch page for a deploy-preview platform in private beta: join the waitlist and see your place in line, see what works today, lock in launch pricing, ask questions, and know when the next wave opens.

## Direction
- Cool night (#07080b) with blue as the only accent (#4f8cff, lighter #8fb4ff for text). The pricing section's dome is the only bright moment below the fold.
- Bricolage Grotesque for every heading, tight and confident; Geist for reading; Geist Mono for small labels.
- Honest about being early: everything in the bento works today, the pricing says it's kept for waitlist teams, and the closing call names the date of the next wave.
- Ring Flood buttons for the main action at the top; the waitlist button inside the hero is the primary one.
- Six components share one palette through their tokens; content inside components is checked so nothing names another product.


## Page map
1. Bar action: Ring Flood Button. A gradient ring that floods the button on hover: the waitlist action, always in view at the top.
2. Hero: Waitlist Hero. Join with your email and a ticket prints with your place in line, the estimated wait and a link that moves you up.
3. What works today: Bento Grid. Tiles of working interface (live traffic, a command palette, presence, settings, regions) instead of feature icons.
4. Launch pricing: Credit Tier Pricing. Three plans in black glass with a month/year switch and the cost per 100 credits, so the value is comparable.
5. Questions: Chat Thread FAQ. An FAQ you ask: each answer suggests the next question, and a person is one tap away.
6. The ask: Ticker Ring CTA. The closing call with the next wave's date, seats per wave and the queue running round its border.

## Change first
- Connect the waitlist to your real list, with your real queue size and how many you let in each week.
- Rebuild the bento tiles from features that genuinely work in your beta, using your own product screens.
- Set the three plans, credit units and launch-pricing promise to what you will honour.
- Rewrite the chat FAQ from questions people have actually asked you about the beta.

## Components
Copy each component's files from its page (Code tab) into your project before you start, and use them as given: change props and content, not internals.
- Ring Flood Button: https://tryvitrine.dev/components/ring-flood-button (A gradient loops slowly around the border; on hover the dark face draws in from every side and the gradient floods the whole button.)
- Waitlist Hero: https://tryvitrine.dev/components/waitlist-hero (A launch hero whose sign-up works like a ticket dispenser: join, and a stub feeds out of the form with your place in line rolling into view and an honest estimate of the wait.)
- Bento Grid: https://tryvitrine.dev/components/bento-grid (A product bento where every tile holds a small piece of working interface — a live traffic chart, a command palette typing itself, presence, real settings switches, an install snippet with package-manager tabs and a turning dotted globe — under one soft light that follows the pointer across the whole grid.)
- Credit Tier Pricing: https://tryvitrine.dev/components/credit-tier-pricing (A three-plan pricing section in black glass: a rating pill, a heavy two-line headline, a Month/Year switch with a sliding thumb, cards lit by dot-matrix glows with a colour-drenched middle plan, and a glowing dome of dots rising underneath.)
- Chat Thread FAQ: https://tryvitrine.dev/components/chat-thread-faq (An FAQ you ask rather than scan.)
- Ticker Ring CTA: https://tryvitrine.dev/components/ticker-ring-cta (A closing banner with its small print — dates, seats left, where — running continuously round its border like a ticker; point at the button and the ticker slows so you can read it.)

## Build
- Next.js (App Router), TypeScript, Tailwind CSS. No extra UI libraries.
- Write real content for this site: real names, dates, numbers and sentences. No lorem ipsum, no "Feature one".
- Compose the sections in the order of the page map. Keep each component's own spacing; add page rhythm with consistent section padding.
- Mobile first: every section must work at 375px wide without horizontal scrolling.
- Respect prefers-reduced-motion everywhere; every Vitrine component already does.

## Before you ship
- Run `/landing-page-art-director` (https://tryvitrine.dev/workshop/skills/landing-page-art-director): One hero idea (your place in line) and a proof sequence, instead of a stack of blocks.
- Run `/conversion-ux-review` (https://tryvitrine.dev/workshop/skills/conversion-ux-review): The page has one job, joining the waitlist; every section should lead back to it.
- Run `/template-tells` (https://tryvitrine.dev/workshop/skills/template-tells): SaaS launch pages are where generic patterns gather; this finds them.
- Run `/responsive-audit` (https://tryvitrine.dev/workshop/skills/responsive-audit): The ticket, the bento and the pricing cards each recompose at 375px.
- Run `/accessibility-pass` (https://tryvitrine.dev/workshop/skills/accessibility-pass): The waitlist form, the period switch and the chat FAQ must work by keyboard and announce results.

Direction

  • Cool night (#07080b) with blue as the only accent (#4f8cff, lighter #8fb4ff for text). The pricing section's dome is the only bright moment below the fold.
  • Bricolage Grotesque for every heading, tight and confident; Geist for reading; Geist Mono for small labels.
  • Honest about being early: everything in the bento works today, the pricing says it's kept for waitlist teams, and the closing call names the date of the next wave.
  • Ring Flood buttons for the main action at the top; the waitlist button inside the hero is the primary one.
  • Six components share one palette through their tokens; content inside components is checked so nothing names another product.