Wait Blasting:
blast into a filter, not a crowd.

There is a point in filling a Room where you want more reach without giving up control.

That is the problem Wait Blasting solves. The tactic is designed for the final stretch of a curated event, especially when capacity is tight and you already have a meaningful owned list from previous Rooms.

Do not blast for volume. Blast into a filter.

The problem with a normal invite blast.

Luma makes invitations frictionless. That is usually a strength. But if accepting an invite can place someone directly into the going list, a large blast can fill a limited-capacity event before you have had a chance to review fit.

For a broad open meetup, that may be fine. For a Room built around a very specific ICP, it can destroy the exact thing that makes the event valuable.

In the recording, the example was a private founder Room designed around Series A and Series B founders with a hard capacity. The goal was not simply to get to 50 names. It was to get to the right 50 people.

1. Fill the core of the Room before you turn the filter on.

I would not use this method too early. In the training, I recommend it mainly in the final one to two weeks, once you already have the known people and obvious fits you want inside.

At that point, the objective changes from broad discovery to controlled filling.

2. Lower capacity to the number already approved.

The core move is simple: temporarily set the event capacity to the exact number currently marked as going, then make sure the over-capacity waitlist is enabled.

Now the event appears full by design. New people can still raise their hand, but they enter the waitlist rather than bypassing the qualification layer.

3. Keep the qualification questions live.

The waitlist is not useful if it only collects names. Keep the same questions that help you understand fit, stage, obstacle and intent.

That means the burst of distribution still flows into the operating system. You can see whether somebody is part of the ICP, what problem they are trying to solve and whether they raised their hand for a relevant next step.

4. Send invitations in waves.

Do not necessarily blast the entire database at once. Work from the warmest and most relevant audience outward.

This gives you control over the velocity. You can stop, review quality and then decide whether another wave is actually needed.

Position it as a waitlist opportunity.

The message in the recording was intentionally simple: a few additional spots had opened from the waitlist for qualified founders. That makes the invitation honest and gives the later fit-check call a natural reason to exist.

5. Review the waitlist like a pipeline.

The waitlist is not a pile of disappointed attendees. It is a live queue of people who raised their hand, answered qualification questions and may be a fit for this Room, another Room or a relevant follow-up.

Review it in that order:

1. Does the person match the Room's ICP?
2. What problem did they say they are dealing with?
3. Did they declare intent for any relevant next step?
4. Should they be approved, kept for another Room or called for clarification?

The live snapshot showed why the tactic is useful.

In the recording, the first invite wave went to roughly 87 people from a prior audience segment. Within minutes, the dashboard showed new opens and waitlist conversions. One early snapshot showed 14 opens and 5 acceptances, roughly a 30% acceptance rate at that moment.

That is not a benchmark or a promise. It is simply what made the operational risk obvious in real time. A strong invite blast can move fast enough that you need the filter in place before you press send.

Then hand the waitlist to Turn Calling.

Wait Blasting creates controlled demand. Turn Calling converts that demand into a personal relationship.

Once people enter the waitlist, call the best-fit guests, verify the Room is right for them, build rapport and offer any next step they already requested in the form.

One timing note: use the audience's rhythm.

In the recording, the blast went out in the late afternoon, around the end of the workday for the target audience. That is the window I personally prefer for this use case because people are transitioning out of the day and thinking about what comes next.

Treat that as a test, not a universal law. The more important rule is to understand when your own ICP is most likely to notice and act on an invitation.

The guest list should get better, not just bigger.

The deeper point is not a Luma hack. It is a philosophy of distribution. Growth is only useful if it preserves the promise of the Room.

The stronger the filter, the more valuable the Room becomes.