Swipe file
Waitlist Signup Swipe File
A waitlist is a pre-revenue cohort builder. The patterns below differ in how aggressively they qualify the signup (low-friction email vs ZIP-code-style filters) and how aggressively they signal scarcity. The best ones earn a 30-60 percent open rate on launch.
Verified · editorial policy
TL;DR
As of , the short version is: A waitlist is a pre-revenue cohort builder. The patterns below differ in how aggressively they qualify the signup (low-friction email vs ZIP-code-style filters) and how aggressively they signal scarcity. The best ones earn a 30-60 percent open rate on launch.
Waitlist Signup Swipe File TL;DR
- Element
- Waitlist signups
- TL;DR
- A waitlist is a pre-revenue cohort builder. The patterns below differ in how aggressively they qualify the signup (low-friction email vs ZIP-code-style filters) and how aggressively they signal scarcity. The best ones earn a 30-60 percent open rate on launch.
- When to use
- Pre-launch (no product live yet). Mid-launch (capped cohort capacity). Post-launch (re-engagement waitlist for sold-out batches).
- When NOT to use
- When the product is already live and self-serve. Forcing a waitlist on a launchable product wastes momentum.
- Brunson lens
- Hook
- Patterns
- 12 named patterns with formula + example + structural notes
- Last verified
- May 21, 2026
When to use
Rewrite this when
Pre-launch (no product live yet). Mid-launch (capped cohort capacity). Post-launch (re-engagement waitlist for sold-out batches).
Do NOT touch when
When the product is already live and self-serve. Forcing a waitlist on a launchable product wastes momentum.
12 named patterns
Pattern 1
Single Email Field
Formula
<H1: 'Coming soon'> + <2-line description> + <single email field + submit>
Example
'Coming soon: a 90-second diagnostic for indie SaaS post-launch. Get the launch email.' + email field
Why it works
Lowest friction. Best for top-of-funnel awareness lists.
Pattern 2
Named-Cohort Waitlist
Formula
<H1: '<Named cohort> early access'> + email + cohort dropdown
Example
'Indie SaaS founder early access. We're letting in 500 founders this quarter.' + email + 'I'm a [post-launch / pre-launch / agency]' dropdown.
Why it works
Cohort dropdown segments at signup. Higher launch-day open rate.
Pattern 3
Scarcity Counter
Formula
<H1: '<N> spots remaining'> + email + counter that decrements.
Example
'247 / 500 founder spots taken. Reserve yours.' + email field + live counter.
Why it works
Real counter only. Fabricated 'spots remaining' gets noticed within 48 hours.
Pattern 4
Story Waitlist
Formula
<Founder story> + 'Want the launch email?' + email field
Example
Founder photo + 'I'm building this because my own launch flatlined for 6 weeks. Want to be on the launch email list?' + email.
Why it works
Story-led waitlist. Higher launch-day conversion; harder to scale via paid ads.
Pattern 5
Free Asset Waitlist
Formula
<H1>: 'Get the <named asset> + the launch email'.
Example
'Get the 12-pattern hero headline swipe file + the launch email for the diagnostic tool.' + email.
Why it works
Pairs the waitlist with a free asset. Higher signup rate; lower launch-day conversion (some signups just wanted the asset).
Pattern 6
Pre-Order Waitlist
Formula
<H1>: 'Pre-order at <discount price>'. + payment field.
Example
'Pre-order the playbook at $19 (launch price will be $49).' + Stripe checkout.
Why it works
Pre-order with payment. Highest signal of intent; lowest signup volume.
Pattern 7
Referral Waitlist
Formula
<H1>: 'You're #<N> on the list. Move up by referring.'
Example
'You're #247 on the list. Refer 3 friends to move to the top.'
Why it works
Referral mechanic borrowed from Robinhood / Superhuman. Build viral coefficient pre-launch.
Pattern 8
Drop Schedule Waitlist
Formula
<H1>: 'Next drop: <date>'. + email.
Example
'Next drop: June 1, 12pm ET. Get notified.' + email.
Why it works
Drop-based waitlist (cohorts, batched). Earns urgency without fabricating scarcity.
Pattern 9
Application Waitlist
Formula
<H1>: 'Apply for early access'. + 3-question form.
Example
'Apply for early access. 3 questions, 60 seconds.' + form (email, URL of live page, current state).
Why it works
Application instead of signup. Filters for high-intent. Lower signup volume; higher launch conversion.
Pattern 10
ZIP-Code-Style Filter
Formula
<H1> + email + 1-question filter ('Do you have <X>?').
Example
'For founders with a live page. Do you have a live page? [yes/no]' + email if yes.
Why it works
Single-question filter pre-signup. Disqualifies the wrong cohort honestly.
Pattern 11
Founders-Only List
Formula
<H1>: 'Founders-only list (verified)'. + email + LinkedIn / domain check.
Example
'Founders-only list. Verified via your email domain or LinkedIn.' + email.
Why it works
Identity-verified list. Smaller; higher per-signup engagement.
Pattern 12
Cohort-Sized Waitlist With Public Tracker
Formula
<H1>: 'Cohort <N> of 1000'. + public tracker page link.
Example
'Cohort: 247 / 1000 founders.' Link: 'See the public tracker / member list.'
Why it works
Public-tracker waitlist with named members (with permission). Highest trust signal pre-launch.
Common implementation mistakes
- Waitlist for a product that already exists and is live. Waste of momentum; just sell.
- Waitlist with no expectation of when the product ships. Buyers forget; launch-day opens are low.
- Counter that's static (always says '247 spots left'). Trust kill within days.
- Waitlist that requires more than 3 fields. Friction collapses signup rate without improving quality enough.
- Waitlist email sequence that's silent for 30+ days. Re-engagement at launch is much harder than expected.
Real examples from indie SaaS teardowns
Pattern names above are illustrative. These are real, named, dated funnels from the Unlock SaaS teardown set where the waitlist signup demonstrates the pattern in a shipping product. Funnel-hack the real ones.
hook lens
Beehiiv – Future-identity positioning
Beehiiv positions against Substack on creator monetization, not features. The funnel sells the upgrade path.
Future-identity positioning – the waitlist is the identity claim ('I'm a creator who scales').
From the teardown: The hero appeals to who the reader wants to BE (a creator running a real newsletter business) rather than what the platform does. The reader who lands the identity does not comparison-shop on features.
hook lens
Polar – Named-segment bundle hook
Polar bundled MoR plus creator monetization into a single sell. The funnel targets the open-source maintainer specifically.
Named-segment bundle hook drives waitlist segmentation – the segment name does the cohort filter.
From the teardown: The hero names open-source maintainers as the buyer and bundles payment, subscription, and sponsorship features at that named segment. A maintainer reading the page sees a tool built for them rather than for generic creators.
hook lens
Cal.com – Open-source as differentiator
Cal.com sells the open-source alternative to Calendly. The repo IS the trust signal.
Open-source as differentiator – waitlist for self-host capability filters for the operator cohort that wants control.
From the teardown: The hero frames the product as the open-source version of a SaaS the reader already knows. This compresses two messages into one: what we do (scheduling, like Calendly) and why we are different (open, extensible, self-hostable).
hook lens
Plausible Analytics – Named villain plus principle
Plausible sells transparency as the product. Open revenue dashboards do the conversion work.
Named villain plus principle – waitlist is the principle-claim ('I want to leave Google Analytics').
From the teardown: The hero names Google Analytics as the thing being replaced and frames the replacement on a principle (privacy) rather than a feature. This converts an undecided reader into a decided one within the first paragraph by giving them a side to be on.
Which Brunson job does this element do?
This element sits in the Hooklens. Knowing the lens tells you what the element is supposed to accomplish, not just what shape it takes – so you don’t rewrite a Story element using Hook tactics or vice versa.
People also ask
What is a waitlist signup swipe file?
A waitlist is a pre-revenue cohort builder. The patterns below differ in how aggressively they qualify the signup (low-friction email vs ZIP-code-style filters) and how aggressively they signal scarcity. The best ones earn a 30-60 percent open rate on launch.
When should I rewrite my waitlist signup?
Pre-launch (no product live yet). Mid-launch (capped cohort capacity). Post-launch (re-engagement waitlist for sold-out batches).
When is the waitlist signup not the right thing to fix?
When the product is already live and self-serve. Forcing a waitlist on a launchable product wastes momentum.
Questions founders ask about waitlist signup copy
How long should a waitlist run before launch?
30-90 days is the working range. Shorter than 30 doesn't accumulate enough volume; longer than 90 burns through the engagement window. Most successful indie launches hit 60-90 day waitlists.
Should I send weekly updates to the waitlist?
Yes. Silent waitlists open at 5-15 percent on launch day. Weekly updates with build-in-public progress keep open rates at 30-60 percent.
Should the waitlist signup ask for more than email?
Only one extra field, max. A cohort dropdown or a single qualifier question. More than that collapses signup rate without proportional quality lift.
Related Brunson terms
Apply these patterns to your live page
The free 90-second Launch Diagnostic checks whether the waitlist signup is actually the broken step on your page, or whether the bottleneck is upstream.