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.

Keep the night free, get two or three sponsors to commit for six or twelve months at a time so no single company carries the whole bill, and add one small paid option for the people who want more. Charge everyone at the door only if that still leaves a gap.

1. Write down what one night costs, including what your sponsor already pays for. The venue they donate has a price, and if they leave, that price is your bill. Add food and drinks, AV, name tags, software and anything you pay for yourself. The total is the number to cover.
2. Turn the venue sponsor into a written agreement. Agree on what they get each month, such as a short welcome, their name on the event page and in emails, and a few seats, and ask for six or twelve months at once. Then you ask once, not every month.
3. Add a second and third sponsor for separate costs, like food and drinks or recording the talks, so losing one company does not end the meetup. For a professional crowd, companies that hire your attendees or sell the tools they use are the usual fit.
4. Sell the room, not a logo. After each night, send every sponsor how many people actually checked in and what happened. That short report is what gets the renewal.
5. Add one paid option beside the free night: a workshop before doors, a small dinner after, or a supporter ticket with a perk. The free night stays free.
6. Offer your regulars a yearly supporter membership with a clear perk, such as a reserved seat or first access to the small sessions.
7. Tell the room what a night costs and what each sponsor and supporter pays for. People chip in for a cost they can see.
8. Keep the money separate from your own. Use a separate account, and ask an accountant how sponsor payments should be received and taxed before you send the first invoice.

An illustrative example: if the venue would cost $500 without your sponsor and food and drinks for 100 people cost $700, one night costs $1,200, or $14,400 a year. Two sponsors at $500 a month cover $1,000, and 20 supporter tickets at $10, with buyers covering the ticket fees, cover the other $200. Your own numbers will differ; the method is the same.

There is no market rate for a 100-person meetup, so price sponsorship from what a night costs you and what the sponsor gets, and split that cost across two or three sponsors.

Start with your cost per night. If two sponsors share it, each pays about half; a sponsor who wants more, such as a talk slot or the only table in the room, pays more. Offer a lower monthly price for a longer commitment, because six months of certainty is worth more to you than one.

Ranges you read online are guesses about other cities and other audiences. What a sponsor will pay depends on who is in your room: 100 engineering managers are worth more to a hiring company than 100 students. Ask, and adjust after the first two conversations.

You will lose some sign-ups, and on a cheap ticket fees take a large share, so keep a free option, let buyers pay the fees, and test the price on one night before you commit.

Nobody can tell you in advance how many people a price will cost you. Compare the check-in count, not the RSVP count, on the paid night with the nights before it.

A small ticket loses the most to fees, because many platforms add a fixed amount to every ticket. If you absorb the fees, this is what you keep:

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.