Skip to contentFIRST1000
First 1000 blog

First 1000 field note · Updated September 21, 2026

Robinhood Made the Queue a Product

A waitlist is easy to ignore when the only thing it gives back is a confirmation email.

The queue had a reward attached

This was a guest post by George Vasiliadis, published in the February 19, 2021 First 1000 issue. The source reports that Robinhood collected nearly one million people on its waitlist during the year before launch.

The important mechanic was not the size of the number. Robinhood offered invitation-only early access to a private beta. Joining the list meant waiting for something specific, and a better position meant earlier access.

That turns the queue into a product surface. A person can understand what they are waiting for, why their position matters, and what they can do next. It is more useful than a page that accepts an email and disappears.

Make the first step almost boring

The source describes a landing page with one required action: enter an email address. The hook was equally direct: $0 commission stock trading, compared with fees of up to $10 per trade in the historical copy.

There was no long survey before the opt-in. No explanation of every future feature. The page made the promise legible and left the user one small action away from the queue.

That is different from making a signup page empty. The page can have a sharp promise and a real reward while keeping the first step narrow.

The thank-you page did the distribution work

After signup, Robinhood showed the person’s queue position. Under that position was a referral invitation: share the offer, move higher in line, and get access sooner.

The referral was not a detached “tell your friends” request. It changed the same status the person already cared about. The queue position made progress visible; the referral gave progress a lever.

This is the part I would study before adding a waitlist leaderboard. Does the action change access to the product? Can the person see the effect? Would someone still share if the queue position did not move? A game layer is only useful when it is attached to a real product decision.

Use the queue as a measurement surface

Keep email signup, referral, queue movement, invitation acceptance, beta activation, and first useful action as separate events. A million signups is not a million active traders, and the source does not publish a clean conversion denominator for the loop.

The useful question is narrower: which part of the queue makes someone take the next step? If referrals move people but beta activation does not, you built reach. If queue movement predicts activation, you may have found a useful prelaunch signal.

A queue should tell users what happens next and tell the founder what the next step is worth. Otherwise it is just an inbox with a nicer number.

The queue checklist

If I were designing a prelaunch queue, I would ask:

  1. What exactly is the reward for joining?
  2. Does the visible position map to a real access decision?
  3. Does the next action change the same status the user cares about?
  4. Are referrals, beta access, activation, and later use tracked separately?

The takeaway

Robinhood’s useful prelaunch move was to make the wait visible and changeable. The queue itself gave users a reason to return, and the referral loop was tied to the access reward instead of being a generic share request.

Sources and original research

Adapted from Robinhood, published February 19, 2021. The issue identifies the post as a guest contribution by George Vasiliadis; the historical waitlist, single-field signup, $0/up-to-$10 fee framing, queue position, and referral mechanics are source-reported. No current Robinhood metrics or conversion result is claimed.

Updated September 21, 2026. Based on original First 1000 reporting and the sources listed above.