Gamiflow / Use Cases / Product Launches
🚀Product Launches

A waitlist that moves people up when they bring a friend, not just a static sign-up form.

🛠️ Coming soon

This use case is on our roadmap and not yet available to build in Gamiflow today. The implementation below shows how it's designed to work once it ships.

Referrals turn a waitlist into its own distribution channel. The queue-jump mechanic gives people an actual reason to share, instead of just registering interest and forgetting about it.

Start Building a Campaign
📍Where this fits

Weeks before launch day is when this pays off.

The list you build in the six weeks before launch determines how strong day one looks. This use case is entirely about the awareness-to-consideration window, before there's even a product to buy yet.

Stage 1Pre-launch awareness
Stage 2Waitlist & referral
Stage 3Launch day purchase
Stage 4Retention
🧪Real-world implementation

How a DTC headphone brand built 14,000 waitlist signups before launch.

🎧 Nova Audio, DTC headphone brand, new model launch

Nova Audio has a new headphone model six weeks out and no existing list for it. Instead of a plain "notify me" form, they build a referral-powered waitlist where your position depends on who you bring with you.

The setup

  1. Signing up with an email puts you on the waitlist at your current position. Referring a friend who also signs up moves you up the queue, a visible, gamified incentive to share.
  2. A short preference survey asks about color and use case (commute, gym, studio), data Nova's product team actually uses to plan initial inventory splits.
  3. A handful of early-access unboxing units go to influencers in week one, seeding the initial wave of referral traffic into the waitlist.
  4. On launch day, the top 500 referrers get a same-day priority access code, everyone else gets access and a smaller discount code on a staggered schedule over the following week.
  5. SMS opt-in at signup means launch-day notifications land as texts, not emails that get buried.

Why it beat a plain waitlist

A static "notify me" form has no reason to be shared. A queue people can move up does, and that's the entire difference between a list that grows on its own and one that only grows from paid traffic.

📇First-party data captured

Useful for both marketing and inventory planning.

Email required Phone number for launch-day SMS Referral count & queue position auto-tracked Color preference survey field Primary use case survey field Referral source auto-tagged Marketing consent required
🔌How it connects to your existing stack

The waitlist feeds the exact automation launch day depends on.

01Waitlist signups sync to Klaviyo in real time, tagged with referral count so segments like "top 500 referrers" can be built before launch day, not scrambled together at the last minute.
02A pre-built launch day flow in the ESP fires based on queue tier, priority access code to the top segment, staggered codes to everyone else.
03Color and use-case survey data exports to the product team ahead of the initial inventory buy, well before a single unit ships.
📊What the launch recap looks like

Waitlist traffic converts differently than cold traffic.

app.gamiflow.com/conversion/nova-launch-recap
Segment List size Launch day conversion Revenue
Top 500 referrers 500 61% $45,750
Rest of waitlist 13,500 14% $283,500
Cold ad traffic n/a 2.1% $61,000

Illustrative numbers. The gap between the top-referrer conversion rate and cold traffic is the entire case for building the list before launch day rather than after.

Have an audience ready before the product is.

Start Building a CampaignSee Audience Growth →