How to run a tech meetup that scales.The talks are the excuse. The hallway is the product.

The shape that holds at every size:

• Doors + food, 30–40 minutes. Long enough that late arrivals miss nothing and early arrivals start conversations. This is not padding — it’s the first hallway block.
• Two short talks, not three long ones. 15–20 minutes each, practitioner-grade (“what I learned shipping X”), with a hard stop. Two talks give the night a spine; a third steals the hallway.
• The protected hallway block. After the talks, nothing else is scheduled — no announcements, no panel, no wrap-up speech. The room talks until close. Guard this with your life; it’s why people come back.

Same time, same shape, every month. Cadence is the growth lever — a meetup people can build a habit around outgrows a clever one they have to re-decide on every time.

Speaker sourcing is where most organizers burn out — weeks of cold outreach for a 15-minute slot. The self-renewing alternative: your speakers are already attending. The person who asked the sharpest question, the one holding court by the drinks about their migration war story — ask them, that night, while they’re warm: “would you tell that story from the front next month?”

Practitioner talks from the room beat polished decks from outside: the speaker’s friends attend, their company often sponsors food, and the talk is calibrated to exactly your audience’s level. Keep a bench of 4–6 committed speakers, book at most two editions ahead, and give every speaker the same simple brief: one real problem, what you tried, what you’d do differently.

Growth breaks meetups through logistics, not content. The thresholds most organizers hit:

• ~50 people: name tags, a visible schedule on the wall, one helper at check-in. Registration needs to be self-serve by now — a door list on paper stops working here.
• ~100 people: a one-page run-of-show, an hour of AV check, and one person who owns the door completely so you can be the host, not the bouncer.
• ~200 people: capacity management becomes the job — waitlists that backfill cancellations automatically, check-in that scans instead of searches, and a sponsor or small ticket funding real production.

Notice what’s not on the list: more talks, longer nights, panels. The format stays; the machinery grows.

A tech meetup compounds through one loop: attendees become regulars → regulars become speakers → speakers bring their networks → the network brings the next attendees. Every part of the playbook feeds it — the hallway creates regulars, the from-the-room speaker bench turns regulars into stakeholders, and the audience that carries between editions makes sure nobody falls out of the loop between months.

The organizer’s real job is protecting that loop’s energy — which means ruthlessly automating everything that isn’t the room: reminders, registration, waitlists, recaps. If the machinery costs you more energy than the room gives back, the meetup dies at edition three — not from failure, from exhaustion.