Live demo: https://ai.i258.cn/launchshelf/

Optional waitlist: https://tally.so/r/2jj45e

Not because the idea needed React Server Components. Because I wanted a page that looked “real” — hero, pricing, FAQ, a place for an email — and Next was the hammer I already knew.

Then I’d burn two evenings on layout, fonts, a half-wired form, and a deploy that still felt like a mini product. By the time the landing was “good enough,” the urge to launch had cooled. The waitlist stayed empty. The Gumroad link never went live.

If that sounds familiar, this is the note I wish I’d written to myself a year ago.

The actual job of a launch page

For a micro-launch — a waitlist, a $19–$49 digital kit, a course teaser — the page has one job:

Get someone from “curious” to “email or payment” without making you rebuild a frontend repo.

That’s it. It does not need auth. It does not need a CMS. It does not need a design system with 40 tokens.

Heavy boilerplates (the $150–$300 “Ship your SaaS” class) are excellent when you already know you’re building a multi-tenant app. They are overkill when you only need a front door while the real product is still a weekend away.

Static HTML + Tailwind is boring on purpose. One folder. Edit copy. Host anywhere. Ship the same afternoon.

Why static HTML + Tailwind wins for waitlist / Gumroad launches

1. Time-to-first-visitor drops from days to hours

You clone or unzip, replace headlines and prices, drop in a Gumroad embed or a Tally/Formspree action, push to any static host. No npm run rabbit hole unless you want it.

2. The cost model matches the product

If you’re selling a one-time ZIP for $39, your acquisition page should not cost a week of engineering. Static hosting is free or near-free. No serverless form tax unless you choose a paid form tool later.

3. You can change the offer without touching an app

Swap “Join waitlist” for “Buy · $39.” Add an AI-tool vertical without forking a monorepo. Indie launches iterate on positioning more than on architecture in week one.

4. Buyers of digital kits understand “download and edit”

Your customer is often another maker. They don’t need a dashboard. They need a clean page they can restyle and redeploy. HTML is the universal export format.

I’m not saying never use Next. I’m saying: don’t start the Next project until the static page has proven anyone cares.

The structure of a page that converts (enough)

You don’t need twelve sections. You need a clear path:

1. Hero — who it’s for + the outcome in one breath. One primary CTA.
2. Benefits — three to five outcomes, not feature laundry lists.
3. How it works — three short steps. Edit → host → collect emails or take payment.
4. Social proof / honesty — if you don’t have testimonials yet, don’t invent them.
5. Pricing — one clear price. “$39 one-time.”
6. FAQ — Is this a SaaS boilerplate? Can I use my own form? Where do I host?
7. Final CTA — Buy, or waitlist. Not both equally loud.

Deploy options that don’t eat the weekend

GitHub Pages / Cloudflare Pages / Netlify / Vercel static, or a cheap VPS + nginx. Wire forms to Tally/Formspree and buy buttons to Gumroad.

What I built after getting tired of rebuilding

I packaged the pattern into LaunchShelf: static HTML + Tailwind landing kit.

Live demos:

• https://ai.i258.cn/launchshelf/
• https://ai.i258.cn/launchshelf-ai/

$39 one-time on Gumroad: https://zhengchh.gumroad.com/l/launchshelf

Waitlist for vertical packs: https://tally.so/r/2jj45e

No fake “10k makers trust us” line. Solo maker. Early views, zero sales as of writing — shipping the page and asking for signal.

When you should not buy a kit

• You already have a design system and marketing site in production.
• You’re launching multi-tenant SaaS next week and need auth/billing day one.
• You enjoy building the landing as much as the product.

When static is enough

• Validating a micro-tool, course, or digital download this month.
• Your “site” is still a Notion doc.
• You need emails or one payment before another layout.tsx.

Stop rebuilding the front door. Put something live, collect the signal, then earn the right to a heavier stack.

If you roast the demos in the comments — what’s unclear, what’s missing, which vertical you’d pay for — that’s more useful than a silent scroll. Thanks for reading.