How to Get Accepted as a Conference Speaker: A Practical Guide

Speaking at a conference is one of the most reliable ways to grow into a field faster — more contacts, sharper thinking, and a visible artefact of your work that lives on well after the event. The path from "I have something to say" to "accepted, see you on stage" usually runs through a Call for Proposals (CFP), and CFPs have a rhythm that's worth understanding before you start submitting.

Pick the right event

The fastest way to collect rejections is to submit to the biggest event you've heard of. Those CFPs are saturated: established speakers with track records and organised pitches apply, and first-time proposals have a rough time. A more realistic first target:

Regional conferences — city-level or state-level events in your field.
Community-run events — single-track or small multi-track conferences organised by practitioners rather than a company.
Specialised tracks within larger events. Sometimes a dedicated track has a much higher acceptance rate than the main track at the same event.
Meet-ups and local chapters, which rarely have formal CFPs but often book speakers by recommendation.

Browse category-specific listings in the directory to build a shortlist, and look for events that publish their selection process; those are usually more predictable to apply to. Fields like technology, healthcare, and design each have well-run regional events that serve as good starting venues.

Read the CFP carefully

The CFP page tells you what the programme committee is looking for, often directly. A useful reading pass checks for:

Talk length. A 20-minute slot and a 45-minute slot are completely different formats.
Audience level. Beginner, intermediate, advanced, or mixed. Mis-targeting the level is the single most common rejection reason.
Explicit themes or tracks. "We want talks that…" is not filler — committees score proposals against those criteria.
What the conference explicitly does not want. Usually: pure product pitches, recycled talks from previous events, thinly disguised sales decks.
Submission deadlines and any early-review dates. Some events reward early submissions.
Whether travel, hotel, or an honorarium is covered. Many events cover speakers; some don't. Know before you spend time submitting.

Write an abstract selection committees actually read

Selection committees read dozens — sometimes hundreds — of proposals in a sitting. Yours has roughly thirty seconds to earn the second read. A strong abstract usually has four parts:

A specific hook — the first sentence. Skip the setup; start with the tension or discovery that makes this talk worth sitting through.
The question or problem. What is the talk actually about? Concrete, not thematic.
What you'll cover. Two or three sentences on structure. This is where committees assess whether the talk can fit the time slot.
What the audience will take away. One concrete outcome per persona — "engineers will leave knowing…", "managers will leave with…".

An abstract pattern to work from

(1) [One-sentence hook that names the specific tension or finding.]

(2) [One to two sentences: what the talk is really about, in plain language.]

(3) [Two to three sentences: the structure of the talk — what you'll walk through.]

(4) [One sentence per audience type: what they'll take away.]

The biography and speaker credibility

Most first-time speakers write their bio wrong. The goal is not to list every job — it's to make the committee confident that you're the right person to give this specific talk. A focused bio:

Tells the committee what you do day-to-day in a sentence.
Mentions the experience that qualifies you to give this talk — not every job you've ever had.
Links to any previous talks or written work on the topic. If you have none, that's fine — a meet-up talk or a blog post counts.
Skips adjectives. "Passionate about" and "innovative" add nothing; specific verbs do.

If you've never spoken before, say so honestly in any "speaker experience" field. Many committees actively look for new voices; faking experience is far worse than admitting this would be your first talk.

Common mistakes that sink proposals

The thinly disguised vendor pitch. If the talk only makes sense when your product is on stage, committees can tell. Rewrite it as "how we solved this problem" without naming the tool.
The 101 talk to an expert audience. Giving "What is [topic]?" to a conference full of senior practitioners rarely lands. Mismatched level is a fast rejection.
The entire field in 30 minutes. Abstracts that promise to "cover everything about X" usually get rejected for scope. Narrow, narrow, narrow.
The story without a takeaway. War-stories are great, but the audience needs to leave with something they can apply. What did you learn that others can use?
Submitting the same talk everywhere. Tailor each abstract — different audiences want different framings.

After submitting

Response times vary widely — a few events respond in a week, others take months. Don't write the talk in detail until you hear back, but do keep a simple outline so you can start fast on acceptance. Plan for rejection: aim to submit five to ten proposals in a CFP season and expect a mix. Many accepted speakers started with a string of rejections.

If you get accepted

Build the talk backwards from the takeaway

Write the single sentence you want the audience to remember a week later. Every slide and example should earn its place against that sentence. Cutting is more important than adding.

Rehearse out loud, more than you think is needed

A first run-through almost always runs long. Record yourself, rewatch once, cut the weakest third. Rehearse the opening and closing until they are second-nature — those are the moments the audience remembers most.

Slides that support, not narrate

The slides aren't the talk; you are. Use big visuals or a small number of words per slide. Dense slides make the audience choose between reading and listening, and they usually choose reading — at which point your talk becomes a voice-over.

Handle Q&A as an extension of the talk

A strong Q&A session is often what attendees remember. If a question is off-topic, answer briefly and offer to continue in the hallway. If you don't know, say so; faking an answer is worse than admitting you'll follow up.

What you get out of it

Speaking amplifies what attending already gives you: better conversations because people approach you, clearer thinking because you had to structure the talk, and a piece of work — slides, a recording, a write-up — you can point to for years. Start small, submit often, and treat rejection as part of the process. If you're running an event and need speakers, the submission page is how to get the CFP itself listed in the directory.

How to Get Accepted as a Conference Speaker