How to build a waiting list for a drop

Sixty units land in three weeks. You've got 900 followers, and last time you posted "available now" at nine in the evening you sold nine, then spent a month dropping the price.

A waiting list fixes the specific problem in that sentence. It turns "some people might see this" into "141 people said yes before it existed and I can reach every one of them without an algorithm's permission."

Here's the whole mechanism. You ask for one piece of contact information in exchange for one specific promise: early access, at a named hour, on a named date. You keep that promise exactly. That's it. Everything else in this article is how to make the ask worth answering and how not to blow the hour itself.

A waiting list is not your followers

Followers are people a platform might show your post to. A waiting list is people you can reach directly.

The difference shows up on drop day. If you post a story to 900 followers, a fraction see it, and the fraction is decided by something you don't control. If you send a message to 141 people who typed their number into a box last Tuesday, 141 people get it.

That's the only reason waiting lists exist. Not scarcity theatre. Reach you own.

Which also means a waiting list you can't actually message is decoration. "Comment DROP below" gets you 60 comments and a very tedious afternoon of copying names into DMs, half of which land in message requests because those people don't follow you. If you're going to run a keyword, run it knowing you have to convert those comments into something durable within a day or two.

The two things the list has to have

A way to reach them off-platform. Phone number, email, Telegram, a WhatsApp broadcast list. Something that still works if your account is suspended on a Wednesday morning.

A promise narrow enough to be checkable. "You'll hear first" is not checkable. "The link goes to this list at 7pm on Friday the 14th, and publicly at 9pm" is checkable, and that's what makes people give you their number.

Vagueness is the reason most waiting lists don't convert. People are not withholding their email because they're precious about it. They're withholding it because "join the list for updates" describes a newsletter they don't want.

Where to collect names, ranked by what it costs you

Method	Reach on drop day	What it costs you
Email	Good, and it survives everything	Slowest to build, needs a signup form
WhatsApp broadcast list	Very high open rate	Only reaches people who have your number saved
Telegram channel	High, and it's one post	People must join, not just tap
DM keyword	Fast to build	Manual, and message requests eat some
Instagram close friends list	Instant, no signup	Not a list you own, and caps out

That second row is the one that costs sellers a drop. A WhatsApp broadcast only reaches people who have your number saved in their contacts. Not people who have messaged you. Not people whose number you have. It's the single most expensive thing nobody mentions, and you find out at 7pm on drop day when 80 of your 141 messages don't arrive.

The fix is to say it in the signup message, in plain words: "save this number as [Shop name] or you won't get the drop message." Then send a test broadcast a week before, and count replies. The ones who don't reply, message individually.

If you'd rather not run into that at all, a Telegram channel or an email list has no saved-contact rule, and building an email list without a website covers collecting addresses when you have no site to put a form on.

The ask that actually gets signups

Compare these two.

Join my waiting list for the new drop, link in bio.

The 60 hoodies land on the 14th. List gets the link at 7pm Lagos time, everyone else at 9pm. Last time the two most popular sizes went in under twenty minutes. Send me the word HOODIE and I'll add you.

The second one works because it contains a number, a date, a time, a named risk of missing out that's true, and a two-second action. The first one asks you to do admin for a stranger's benefit.

Four things to put in the ask, every time:

1. What's coming, in one clause. Not a teaser silhouette. People join lists for things, not mysteries.
2. How many. Sixty is a real constraint and everyone understands it. "Limited quantities" is not.
3. The date and the hour, with a timezone. Name the timezone even if you think everyone's local. They're not.
4. What the list gets that the public doesn't. Early access is enough. It doesn't have to be a discount, and it's usually better if it isn't.

The one thing to leave out: a discount for joining. It converts signups and it wrecks the drop, because now the list is waiting for a price, not a product, and you've set the price for every drop after this one.

A 21-day run-up that doesn't require daily posting

Three weeks is enough. Two is tight. Five and people forget.

Days 21 to 15, collecting. Post the ask three times in the week, in three different formats: a story with a sticker, a feed post with the date in the caption, and one message to people who bought from you before. The last of those converts best and takes the longest, which is why almost nobody does it.

Days 14 to 8, showing the work. This is where the list warms up. Post the cutting, the misprint, the box of blanks arriving, the size run written on a piece of paper. Process posts work here because the audience is already committed and now wants to feel involved. Nobody needs a fourth polished flat-lay.

Days 7 to 2, the count. "Forty-one of the sixty are spoken for from the list." Only say that if it's true. Then post the size breakdown, because that's genuinely useful and it makes people decide before the hour rather than during it.

Day 1, the logistics message. Send the list exactly how it'll work. What time. What link. What payment methods. How long you'll hold an unpaid order. One message, boring on purpose.

Drop hour. Send the link at the promised minute. Not two hours early "as a treat" for a few people, because you'll be caught, and not late.

Day 0 plus two hours. Public post. The list already had their window and the window has to visibly close, or next time nobody joins the list.

What happens in the hour, and how it breaks

Two failure modes, and they need opposite responses.

It sells out in four minutes. Feels great. Then you discover 31 people paid, nine of them wanted the same two sizes, and you oversold M and L because you were counting manually while replying to messages. Fix before the drop: decide who wins a tie, and write it down. Payment timestamp is the fairest rule and the easiest to defend. Announce it in the day-1 message so nobody is surprised.

It doesn't sell out. Also fine, and much more common. Do not immediately discount. Wait 48 hours, then message the people on the list who didn't buy, individually, once, asking a real question: "Was it the price, the sizes, or just timing?" You'll get answers, because they signed up, which means they wanted it recently enough to remember why they didn't.

Both cases have the same follow-up job: message everyone who missed out and ask if they want to be told about the restock. That's your list for the next drop and it's already warmer than the first one.

Payment on drop night is the part that breaks

Forty people paying inside ten minutes is a different problem from forty people paying across a fortnight.

If you're on manual rails, bank transfer or cash on delivery, you're going to be reconciling payments while people are still messaging. Decide in advance how long you hold an unpaid order. Fifteen minutes is normal for a drop, an hour is generous, and whatever you pick has to be in the day-1 message. Then actually release the unpaid ones, because the people watching will notice if you don't.

Bank transfers are the slow part. You cannot see them arrive in real time, and neither can any shop tool, including Sailo. Only your bank knows, and on drop night that means you're refreshing a banking app with 30 unread WhatsApp messages. How to know a bank transfer actually arrived is worth reading before drop day rather than during it.

If you want card payments so the money confirms itself, there are two conditions worth knowing weeks ahead. Card on Sailo needs a Stripe account that Stripe has actually cleared for charges. Stripe's checks aren't instant and they sometimes come back asking for a document. Do not schedule a drop for four days after you sign up and assume cards will be live. Sort it a fortnight out, run one real test charge on a cheap product, and then you know.

Sailo takes 1–3% of the goods on card orders, after any discount, excluding delivery and tax — 3% on the free plan, falling to 1% on Business. On a $34 hoodie that's 34c to $1.02 depending on your plan, plus whatever Stripe charges you. At 60 units a drop the plan you're on matters more than the rate does.

Devon's second drop, in Atlanta

Devon screen-prints tees in Atlanta. $34 each, $6 shipping in the US, and he prints in runs of 60 because that's what his supplier's minimum and his kitchen table can handle together.

Drop one: posted "new tee available now" to about 900 followers on a Tuesday evening. Sold nine in the first week, 22 over six weeks, and dropped the last dozen to $24 in November.

Drop two, with a list:

Stage	Number
Days spent collecting	19
People on the list	141
Sold in the list-only window (7pm to 9pm)	38
Sold in the public window, same night	11
Sold over the next nine days	7
Left over	4

Fifty-six of sixty, at full price, and the four left were all XS because he guessed the size run wrong.

Three things he did differently, and only one of them was clever. He asked for a phone number instead of a comment. He told the list the exact size breakdown two days early, which meant the people who wanted M knew to be quick and the people who wanted XL knew they didn't need to be. And he sent one message to everyone who'd bought from drop one, by hand, which took 40 minutes and produced 14 of the 38.

The unglamorous detail: 23 of his 141 never got the broadcast, because they hadn't saved his number. He worked that out at 7:20pm, messaged them individually over the next half hour, and six of them bought. That's roughly $200 he'd have lost to a contact-list rule.

When you shouldn't do a drop at all

If you can make the thing to order, don't do a drop. Drops exist because a production run has a minimum and a deadline. If yours doesn't, a permanent listing sells more over a year than four artificial launches, and it's less work.

Drops also don't fix a demand problem. Sixty units of something nobody wanted at $34 becomes sixty units of something nobody wants at $34 with a countdown on it. If you haven't sold this thing before, the honest first step is testing a product before you make it, which is cheaper than a run of blanks.

And if you're still in the first stretch, before you've sold ten of anything, a waiting list is premature. Getting your first ten orders is a list of forty names in a notes app, which is the same idea at a size where it actually works.

Start the list before you've decided what's on it

You don't need the product finalised to start collecting. You need a date and a category. "Something in fleece, mid-March, list gets it first" is enough to collect names for two weeks while you're still arguing with the supplier.

So today: pick the drop date and the hour, write it down with the timezone, and post the ask once. Then message the last ten people who bought from you and ask them individually if they want to be on it. Those ten replies are the seed, and the drop with ten committed buyers before it starts is a completely different night from the one without.