For Speakers · 8 min read
How to write a winning CFP submission
Every conference organizer we work with says the same thing: they reject hundreds of talks not because the ideas are weak, but because the proposals are. A great CFP submission is a craft. Here is the structure, language and polish that consistently gets talks accepted at top tech conferences.
1. Start with the audience takeaway, not your journey
Reviewers scan the first three lines of a CFP abstract before deciding to read on. That real estate is for the audience — not your autobiography. State what attendees will walk away knowing, building, or rethinking, in one sentence. Everything else follows.
2. Make the problem visceral
The strongest submissions start with a concrete pain the audience recognises in the first paragraph. Numbers help: "we had 47 incidents last quarter" lands harder than "we had reliability problems." If it doesn't feel like a real problem worth 45 minutes of a stranger's life, it probably isn't.
3. Sketch the arc of the talk
Reviewers want to know you've actually thought about the talk, not just the idea. A proposal with a three-act arc (problem → insight → how-to) beats one with bullet points every time. Programme committees are buying the journey, not the slide count.
4. Prove you can deliver it
Link to past talks, blog posts, OSS work, or relevant experience. On submitcfp, your speaker profile auto-imports talks you've given and slidedecks you've published — so reviewers don't have to trust your word. If you're new, record a 3-minute sample and link it. Evidence over ego.
5. Match the event's voice
Read five accepted abstracts from previous editions. Notice the register: academic, practitioner, storytelling, playful? Adjust your tone. A wry submission to a buttoned-up banking conference reads wrong; a dry submission to a creative-coding conference reads dead. submitcfp keeps past editions browsable for exactly this reason.
6. Respect every field
Organizers add custom questions for a reason. "How will you make this interactive?" asked in field 4 is not a formality; leaving it blank signals you don't actually know. Answer every question specifically, briefly, and with opinions.
7. Ship, then iterate
Use submitcfp's Talk Library to keep every version of every abstract. When the next CFP opens, you clone the closest fit, adapt the arc to the event, and move on with your week. Getting accepted is a volume game and a craft. Both matter.