如何撰写能吸引合适人才的演讲者征集

Senior speakers are pattern-matchers. They scan a call for speakers in under thirty seconds and decide whether to skip, save for later, or write a pitch. Three signals do most of the work: how specific the audience description is, whether the format and time slot are explicit, and whether compensation is stated.

Vague briefs scare off senior people because the opportunity cost is too high to gamble on. They also attract junior applicants who pitch anything that fits a keyword. The result is a tall stack of mediocre applications and the few standout pitches you wanted buried inside it.

The organizers who consistently book strong lineups treat the call for speakers like a job description. They are specific about who the audience is, what the talk should change in that audience, and what the speaker gets in return. Specificity is not a deterrent — it is a magnet for people who actually fit.

Every effective call for speakers covers the same eight things in roughly this order. Anything missing is a question your future review panel will have to answer for the applicant.

1. Event context — name, dates, venue (or platform), edition number, one sentence on positioning. Applicants need to know if this is the second edition of a regional meetup or the fifteenth edition of a flagship industry event.

2. Audience — who is in the room, how many of them, what their seniority and roles look like. "300 product managers from Series B+ SaaS companies" beats "tech professionals" every time.

3. Themes and tracks — three to six concrete topic areas with one-line descriptions. List what you already have committed and what you are explicitly looking for, so applicants do not pitch into a saturated track.

4. Talk formats and lengths — twenty-minute lightning talk, forty-minute keynote, sixty-minute workshop, panel slot. Be specific. Format mismatch is the most common reason a good speaker pitches the wrong shape.

5. Timeline — submission deadline, notification date, content deadlines (slides, bio, headshot), event date. Senior speakers will not submit without knowing the notification date.

6. Compensation and reimbursement — honorarium amount or "unpaid", travel and accommodation policy, per diems. Even "we cover economy travel within the EU and offer no honorarium" is better than silence.

7. Application process — what to submit (title, abstract, learning outcomes, bio, video links), where to submit it, who reviews, how many reviewers per application, and what the rubric looks like.

8. Evaluation criteria — the three to five things you actually score on. Publishing these self-selects for applicants who can clear the bar.

Writing a strong call is only half the work. The other half is putting it where the right speakers will see it within the first ten days of the window opening. Concentrate effort there — applications drop off sharply after the first two weeks and crater after week four until the deadline week scramble.

The distribution channels that consistently produce signal:

• Your past speaker alumni. They are pre-vetted and have already cleared your bar once. A direct email asking for both submissions and referrals usually produces the highest-quality pitches.

• Topic-specific communities. Slack workspaces, Discord servers, mailing lists, and subreddits where your target speakers already gather. Post the call, but also answer questions in the thread for a week — engagement signals legitimacy.

• Speaker platforms. List the call on platforms that connect organizers with verified speakers and route inbound matches by topic, region, and seniority — this is where SpeakUp fits.

• Partner amplification. Sponsor newsletters, co-organizer networks, university programs, and adjacent conferences with non-overlapping audiences.

• Social, in this order of usefulness: LinkedIn (best for B2B, senior), X/Twitter (still strong for tech), and topic-specific newsletters. Avoid spraying it on every channel at once — fewer, better-targeted posts outperform broad reach.

A short follow-up two weeks before the deadline is standard practice and is not pestering. State what is still open by track and what you would especially like more pitches for.

A workable timeline counts backwards from the event date. The shape that works for most conferences is six to nine months out for a major event, three to four months for a regional one, and six to eight weeks for a small or single-track event. Compressing below these numbers means you lose access to senior speakers, who book their calendars early.

Inside the window, allow at minimum:

• Four to six weeks for the open submission window. Shorter than that excludes anyone on PTO or in a heavy travel quarter. Longer than six weeks rarely adds quality — it just adds drift.

• Two to three weeks for review. This includes the time for at least two reviewers per application, a calibration discussion, and a final selection meeting.

• Two weeks of buffer between notification and the first content deadline (bio, headshot). Bios and headshots take longer to collect than first-time organizers expect.

Publish the full timeline in the call. Senior speakers will not submit blind, and "we will notify you by [date]" is a stronger commitment signal than "rolling notifications".

Here is a typical weak opening line:

"We are looking for inspiring speakers to share their expertise at our annual tech conference. All topics welcome."

It fails on every dimension. No audience, no theme, no format, no compensation, no timeline. The implicit message is "we do not know what we want yet, so pitch us anything", which is what the applicants will do.

Here is the same opening rewritten:

"DevConf 2026 is the seventh edition of our annual conference for senior backend engineers at Series B and later SaaS companies. Three tracks: distributed systems, platform engineering, and developer experience. We are programming sixteen talks (30 minutes each) and two workshops (90 minutes). Honorarium of €1,500 per talk, €3,000 per workshop, plus economy travel and three nights of accommodation. Submissions open through 30 June 2026; notifications by 28 July; event 18–19 October."

The second version reads almost like a contract. It tells a senior platform engineer at a Series C company "this is for you", and it tells a junior frontend developer "this is not for you" — both correct outcomes. Application volume will be lower with this version. Application quality will be much higher.

The mistakes that quietly kill conversion are mostly about what is missing rather than what is wrong.

• Hiding compensation. "Compensation discussed with selected speakers" is a strong negative signal. State it plainly, even if it is zero. Speakers who would not have applied for free are not the speakers you wanted to disappoint at the offer stage.

• Demanding too much at submission. A 1,000-word abstract, three reference videos, and a full deck before review is a screening mechanism — but it screens out the busy senior speakers you want, not the ones you want to filter out. Ask for the minimum needed to make a yes/no decision.

• Vague evaluation criteria. "Quality of talk" is not a criterion. "Relevance to track, depth of expertise, novelty of perspective, and clarity of takeaways" is.

• No accessibility info. Whether the venue is wheelchair-accessible, whether sign-language interpretation is provided, whether captioning is available, whether dietary requirements are catered. The absence of this section reads as carelessness.

• No mention of recording rights, slide reuse rights, or anonymization in the public schedule. Senior speakers will ask before they apply; if the answer is not in the call, many will simply not bother.