Meetup OS · Speakers
Getting speakers who fill the room
Who to ask, how to ask, and what to do with them once they said yes. From 80 speakers across 40+ ELC meetups and the conference.
Who fills a room
People who have done the thing, at a company the audience recognizes. Your audience is engineering managers, directors and CTOs, and they detect a consultant who advises on the thing in about 30 seconds. A case study with a named company and a number in the title beats a framework every time we have tried it. "Path to 80% AI-generated code: what one company did" fills a room. "AI strategy for leaders" does not.
Before you ask anyone, write the thesis of the night. A topic invites discussion. A thesis invites disagreement, and disagreement fills rooms. Then find the two people who can argue it with receipts. The Meetup OS timeline puts this at D-30: title, abstract and speakers are locked before the registration page exists.
Where ELC finds them
- The person who asked the sharpest question at the last meetup. Ask them on the night.
- A post in your own member Slack: who has shipped X, moved a team from Y to Z, fired someone over W. The answer is usually two hops away.
- The engineering org of the company hosting the venue. Their leaders, on what they learned, not on their product.
- A public call for papers on your site, with the past speakers listed. People apply to a stage they can see.
- Speaker alumni. Someone who spoke two years ago has a new story now, and already trusts the format.
The ask, and the four weeks after it
Senior people say yes to one clear email with a link to the public event page. They stop answering when the thread grows to eleven messages about logistics. So the ELC runner does the whole speaker side in four touches.
| Day | Touch | What it does |
|---|---|---|
| D-28 | One joint intro email | To all speakers together, from the founder, the assistant in copy to find one shared slot. Asks for one intro call at least two weeks out, two or three good photos of themselves, and links the deck template so they can start. Mentions the 48-hour slide lock and the coaching rules below. |
| D-28 | Speaker edits their own description | Each speaker is added to the registration page as a visible host with edit access, edits the paragraph about their own talk, and replies OK. Edit access ends at the OK. No speaker reads the description of their talk for the first time in a newsletter. |
| D-14 | Speaker card + personal post | A "I'm speaking at" card with their face, title and company logo, a draft post, and a tagged link. The ask is a personal post from their profile, not a reshare of yours, plus one line in their company Slack. |
| D-2 | Slides locked, takeaway asset in | The designer polishes the deck the night before. Late slides do not speak. |
| D+2 | Speaker pack | Their photos, a speaker badge for their LinkedIn profile, the alumni welcome, a post kit, and one choice: a podcast episode or a co-written blog post on their topic. |
| D+14 | Video | Their full talk on the event page and a 60-second clip for their own profile. Two touches after the event, not five. |
Ten rules every ELC speaker gets in writing
Sent the moment they confirm, sent again a week before.
01
Open with a story, not a slide.
The first 60 seconds are a scene: a failure, a decision, a moment. Name names, name numbers. Slide one of the talk is black.
02
Structure the talk as a story.
What happened, the trade-offs, the consequences. A list of bullet points is a document, not a talk.
03
Stop two or three times and ask: what would you do?
A live poll with three real options. The audience votes, the speaker reveals what they did. People remember the moment they voted differently.
04
Show the receipts.
Real screenshots, real Slack threads, real dashboards, real org charts. A stock photo tells the room the speaker has not done the thing.
05
One memorable takeaway.
The line the audience will say to a colleague on Monday. If the speaker cannot predict it, the talk is not ready.
06
A role-based call to action at the end.
"If you are an IC, do X. If you are an EM, do Y. If you are a Director, do Z." "Thanks, any questions?" is not an ending.
07
Build a takeaway asset.
The closing slide is a QR to a real artifact: a template, a checklist, a doc. Due 48 hours before. No artifact, no takeaway slide.
08
Tell the audience to take notes.
Out loud. People who write remember, and people who remember tell other people.
09
No bio paragraph on the slides.
The host introduces the speaker in 15 seconds with one line about why this person, this topic, tonight.
10
Slides locked 48 hours before.
The designer polishes the night before. Late speakers do not speak.
In a new city, speakers are your distribution
In your home city you have a member list, a newsletter and a Slack. In a new city you have none of that, and your speakers have more local reach than your whole community. So in a new city the ask is bigger and non-negotiable: post a personal invite, drop the event in your company's channels, and forward it to five engineering leaders you know in the city. One speaker's company alone can fill 20 to 30 seats. If the speakers will not promote, the room will not fill, whatever the promo plan says on paper.
Set the first-event target at 40 to 50 and book a room for that. A full room of 50 feels better than a half-empty room of 80. The readiness check scores the speaker network first, because it is the gap that decides the launch.
Get the printable Meetup OS checklist.
The full D-30 to D+90 checklist, speaker touches included, plus the ELC meetup lessons as they land, in the Leaders' Brief. One email a month.
One email a month. Unsubscribe is a reply.
You're on the list.
A welcome email is on its way. The checklist is at engineeringleaders.io/meetup-os/checklist/, open it now.
For companies
Want ELC to run the whole night at your office?
Your venue, your speaker. The ELC team brings the topic, the audience of 3,300+ engineering leaders, the games, the host and the photos. A median of 125 confirmed registrations across the last 13 public meetups.
See what ELC runs for companiesQuestions organizers ask
How do I find speakers for a tech meetup?
Start from the audience's problem this quarter, then find the person who solved it at a company your audience recognizes. Ask in your own community Slack who has done the thing; the answer is usually two hops away. Past attendees who asked the sharpest question at the last meetup are the next pool. At ELC, 80 people have spoken across 40+ meetups and the annual conference, and most of them were in the audience first.
Do meetup speakers get paid?
At ELC, no. Speakers get a photographer's photos of their talk, a badge for their LinkedIn profile, their video and a 60-second clip two weeks later, a place in the speaker alumni group with its own annual gathering, and the choice of a podcast episode or a co-written blog post on their topic. Senior people speak for reach and for the room, not for a fee. What they do expect is respect for their time: one joint email, one call, a locked deadline.
How many speakers should a meetup have?
Two deep talks of about 20 to 25 minutes, or three to four lightning talks of 12 minutes. Not both. Audience attention drops around minute 70, and the content block at ELC is capped at 75 minutes because the networking after it is half the product.
How do I ask someone to speak at my meetup?
One short email: the thesis of the night, the date and city, why them, what the audience is, the two dates you need from them. Link the public event page, never an internal document. Then one joint intro call with all speakers together, so the night has one narrative and not three separate talks.
Should a vendor or a partner company speak at my meetup?
A practitioner from that company, yes, on what their engineering org learned. A product pitch, no. The audience detects a pitch in 30 seconds and discounts everything after it. At ELC a partner's moment on stage is 60 seconds, scripted, delivered by the host, and their speaker talks about their org, not their product.