Pitch the audience's problem, not your résumé. Name one specific talk, say what changes for the room afterward, add one line of proof, and link to a simple speaker kit. Then send that pitch on a steady schedule instead of once and hoping.
That is the whole idea. The rest of this post is how to do it when you have little or no stage record.
What organizers actually want
Organizers are not looking for your life story. They are looking for what their audience will walk away with, as one speaker-coaching guide puts it. That changes how you write everything, from the subject line to the bio.
Before you write a word, answer three questions about the talk:
- Who is it for?
- What problem does it solve?
- What is different for them after the session?
The Speakeria's guide to pitching for major conferences is a good place to read more on framing a pitch around outcomes instead of background.
If you cannot answer those three in plain words, you are not ready to pitch yet. A vague talk ("lessons in leadership") gets a vague reply, which is usually none.
Two different routes: keynote pitch or call for speakers
People mix these up, and it costs them months.
| Route | How it works | Fits a first-timer? |
|---|---|---|
| Pitching for a keynote | You contact an organizer directly and propose yourself for a headline slot | Rarely, with no record |
| Answering a call for speakers | The event asks for talk proposals and you submit one | Yes, usually the better start |
Many of the guides that show up for this search are really about the second route. This guide on conference speaker pitches is written for a technical conference, and the proposal advice in it (who the talk helps, why you are the right person, a topic the community cares about) carries over to other fields.
If you have never spoken, start with panels, local events and smaller stages. Aim for a keynote after you have a few recordings to show.
Pick one narrow topic
Do not pitch "AI" or "leadership." Pitch one problem for one kind of audience. According to a guide on getting invited to speak, a specific, narrow talk idea with a contrarian angle works better when you have no experience yet.
Make it timely too. Look at what the event's audience is stuck on right now. One guide suggests looking at current conference themes and industry pain points before you choose.
A good test: can you say the talk in one sentence that names the audience and the change? "Operators who still copy data between tabs by hand, and how to spot the three tasks worth automating first." That is a sentence an organizer can picture on a schedule. (That is a made-up example of a talk topic, not a talk I have given.)
Build a small speaker kit
You do not need a big production. You need a few things in one place:
- A one-line promise: what the audience gets.
- A short bio, written for the audience, not for yourself.
- One to three talk titles, each with a one or two sentence description and the takeaway.
- A link to a clip or recording, even a rough one.
- A contact email.
A speaker one-sheet is a single page, usually a PDF, that sums up who you are, the talks you give and the proof that you deliver. Most guides, such as this one-sheet template from SpeakerHub, list client logos and testimonials as proof. If you have none, say so to yourself and use what you do have: a recorded talk at a meetup, a podcast episode, an article you wrote on the topic.
Do not make up testimonials or logos to fill the space. Thin and honest beats padded and false, and organizers check.
Whether to print a fee on the sheet is your call. Some guides lean toward including rates. A first-time speaker can reasonably write "fee on request" and settle it in the conversation.
Your bio and profile also get read. When an organizer looks you up, your profile should say clearly who you help and with what, even without big numbers. This post on writing a LinkedIn About section when you have no big metrics covers that part.
The pitch email, in five sentences
The shape most guides agree on is short. Show you know the event, name the talk, state the outcome, give one line of proof, and link your kit. This email template for pitching as a guest speaker or panelist follows that pattern: acknowledge the event, give a clear topic tailored to their audience, add a one-line outcome, and link to your speaker kit.
Here is a made-up example. The names, event and talk are invented, so do not copy the details:
Subject: A 30-minute talk on cutting busywork for small ops teams
Hi Dana, I read the program for the Example Ops Summit and liked that you put a full track on small teams. I would like to propose "Three Tasks Worth Automating First," a talk for operators who lose hours to copy and paste. People leave with a short list they can act on the next day. I have given this as a talk to a small group and can send the recording. Here is my speaker kit: [link]. If useful, I can record a short sample for your team.
Keep the subject line specific. Keep the body short enough to read on a phone. Put the ask last, in one sentence.
Two cautions. First, only write the proof line if it is true. If you have never spoken, your one line of proof can be something you wrote or built, and you can offer to record a sample. Second, send each organizer a different email. A pitch that could go to any event reads like it did.
Follow up once, politely
Silence is normal. Guides on following up with pitches commonly suggest waiting a few days to about a week. That advice is written for media pitches rather than speaker pitches, so treat it as a rough guide and not a rule.
Keep the follow-up to two or three sentences. Restate the talk title, link the kit once, and ask if they would like anything else from you. One nudge is enough. After that, move on to the next organizer.
Run it as a weekly routine
Consistency in outreach is what wins, according to one guide: reach out on a plan and a schedule, to friends, colleagues and event organizers. Treat it like any other pipeline.
A simple weekly routine:
- Pick a few events or organizers you could realistically speak at.
- Read their past programs so the pitch can name something real.
- Send tailored pitches.
- Log who you contacted and when, and send the one follow-up.
- Record every talk you give, even small ones, and add the best clip to your kit.
That last step matters most. Each small talk becomes proof for the next pitch.
Where people go wrong
- Leading with credentials instead of the audience's problem.
- Pitching a broad theme that fits every event and none in particular.
- Sending one generic email to fifty organizers.
- Faking proof. A made-up testimonial is worse than an empty slot.
- Quitting after one pitch.
One more thing, if you build things for a living
If you are a founder or builder, your best talk topic is probably the thing you do all day. A problem you have already solved is easier to explain than a theory. And if what you are tired of is repetitive manual work in your own business, that is a problem worth sending me directly. I build AI tools and run an AI automation agency, Riot Digital, and I work as one person, so you talk to the one doing the work. Email me the task and we will talk it through.