The Form That Sells a Strain Drop Before the Email Even Goes Out.

Sales are underway for the first CBD drug approved by the U.S. Food and Drug Administration. The drug, Epidiolex, treats two rare types of epilepsy and is made from marijuana plants grown in the United Kingdom. The maker of the …

A sold-out drop with no waitlist is not really a win. It is a list of buyers you let walk out the door twice: once when they wanted to be told, and again when you told everyone except them.

A waitlist beats a broadcast

The general email blast is a blunt instrument. It goes to everyone, most of whom were not waiting for this particular strain, and it competes with every other email in the inbox that morning. A drop waitlist is the opposite. It is small, it is warm, and every name on it asked, by name, for this exact thing. When you can message the people who already want the drop before you message anyone else, the drop sells itself and the broadcast becomes a bonus round.

There is a quieter benefit too. A waitlist tells you how much demand exists before you commit inventory. Two hundred people on the notify list for a strain is a planning signal, not just a marketing one.

The form nobody seems to build

Here is the strange part. Almost every cannabis site I look at has a contact page and maybe a newsletter box, and almost none of them have the one form that would actually move product: a "notify me when this is back" field on the sold-out or coming-soon page. The moment of peak intent, someone staring at a strain they cannot buy yet, is the moment most sites offer nothing but a dead button.

It does not need to be fancy. One email field and a hidden note recording which strain or drop it belongs to. That is the whole thing. The reason it rarely exists is not difficulty, it is that the contact form and the newsletter were set up once and never revisited, and nobody owns the question of where intent actually peaks.

Wiring it up

We built ours as a plain form pointed at Formblade, with a hidden field carrying the strain name so every signup is tagged with what it was waiting for. Submissions land in a Google Sheet and ping a Slack channel, so the team can see a waitlist filling up in real time and time the restock around it. Because a single Formblade endpoint can take more than one form, every drop page on the site posts to the same place and sorts itself out by that hidden field, instead of needing a new integration per product.

When stock lands, the list is right there, already segmented by strain, ready to export into whatever sends the actual alert. The spam filter keeps the junk out, which matters because a public "notify me" box is catnip for bots, and the free tier comfortably covers the volume a normal drop generates.

Ask for less than you think

The temptation is to turn a waitlist into a survey: email, phone, favorite category, how did you hear about us. Resist it. Every extra field is a reason to abandon, and on a phone, where most of this traffic lives, it is worse. An email address and the strain is enough to make the sale later. If your market requires age confirmation before any of this, keep that to a single clear check rather than a form of its own. You can learn everything else after the first purchase.

Time the alert, don't just blast it

Catching the waitlist is only half of it. The other half is when you tell them. Early on we treated the restock alert like the general newsletter, firing it at a round-number hour and watching half the stock go to whoever happened to be online. A waitlist deserves better than that. Because every signup is tagged with the strain it asked for, we could hold the alert until the restock was genuinely live and the page was ready, then send it to that one segment first, ahead of any public post. The people who raised their hands got a real head start, which is the entire promise of a waitlist in the first place. Routing those submissions through a backend like Formblade, straight into a sheet and a Slack channel as they arrive, is what makes that timing possible, because the team can watch demand build and plan the drop around it instead of guessing.

What it changed

The next drop we ran with a real waitlist behind it sold out faster than the first, but that is not the number that mattered. The number that mattered was that a third of the buyers came from the notify list, people we would have lost entirely under the old "back soon" page. The broadcast still went out, and it still worked, but it was no longer doing all the lifting. The drop had already found the people who were waiting for it, because this time we had bothered to catch them.