The queue model: scheduling classes without a calendar

The hardest part of running live classes as a solo instructor isn't the content - it's the scheduling risk. You pick a date, you announce the class, and then you find out whether anyone actually wants it. Too often, not enough people do.

I wanted to invert that. Instead of announcing a date and hoping for demand, I wanted demand to trigger the date. That's what the Bench queue model does.

How it works

Every class on Bench has an interest list. Joining is free and requires no commitment. You're just saying: I'd take this class if it runs.

When the interest list hits a threshold - currently 20 students - the class gets scheduled. I set a date and time, everyone in the queue is notified, and a billing window opens. Students have 72 hours to complete payment. After that, the class runs.

If more than 30 people sign up for a given session, the overflow automatically rolls into a fresh queue for the next session. No one gets shut out permanently.

Why this works for a solo instructor

I'm not running a school. I'm one person with good technical content and limited time. A fixed calendar means committing to sessions that might not fill. The queue model means I only run sessions that have confirmed interest.

It also means I don't have to market aggressively to fill a specific date. I market to grow the interest list, and the scheduling takes care of itself once the threshold is reached.

The milestone notifications

As a queue fills, students get milestone notifications at 25%, 50%, and 75% capacity. This isn't a dark pattern - it's genuine information. If you're in a queue that's 75% full, that's useful to know. It creates organic urgency without manufactured scarcity.

What this looks like in practice

Right now, there's one class on Bench: How to Docker. It's $10. The queue is open. When it hits 20 students, I'll set a date and run it.

If you're interested, join the list. If enough other people are too, we'll make it happen.