Guides·August 8, 2026

How to Write a CFP That Gets Accepted at Tech Conferences

Most CFPs get rejected. The ones that get accepted share specific structural patterns — here's exactly how to write one.

Most CFPs — Call for Proposals — get rejected. Large conferences accept fewer than 10% of submissions. Regional events aren't much kinder. But the proposals that get accepted aren't necessarily from the most famous speakers or the most groundbreaking research. They share specific structural patterns that signal to reviewers: "this person is prepared, this talk will deliver value, and this session fits our audience." Here's exactly how to write one.

Whether you're submitting to a major tech conference or an intimate networking event, the fundamentals of a strong CFP are the same. The difference is in how you tailor your pitch to each audience.

What is a CFP and why does it matter?

A CFP (Call for Proposals) is how conferences select their speakers. Organizers put out an open call — usually a form with fields for your talk title, abstract, audience level, and speaker bio — and hundreds of people submit proposals. A small committee reviews them, selects the best fits, and sends acceptances. For popular events like KubeCon, SaaStr, or TechCrunch Disrupt, the acceptance rate can dip below 5%.

Getting accepted as a conference speaker is one of the highest-leverage personal brand moves a founder or engineer can make. It positions you as an authority, puts you in front of your target audience, and creates content you can repurpose forever. But only if you write a proposal that actually gets selected.

How do you write a CFP that stands out?

The single biggest mistake people make with CFPs is writing about what they want to talk about instead of what the audience needs to hear. Reviewers aren't evaluating your expertise — they're curating an experience for attendees. Your proposal needs to make their job easy by clearly answering three questions: What will the audience learn? Why are you the right person to teach it? How does this talk fit the conference's theme?

Here's the structural pattern that works across nearly every tech conference:

Start with a specific, actionable title

Your title is the first thing reviewers see, and it carries more weight than you think. Vague titles like "The Future of AI" or "Scaling Your Startup" blend into the hundreds of similar submissions. Specific titles like "How We Reduced LLM Inference Costs by 73% Using Speculative Decoding" or "Building a $2M ARR Sales Pipeline With Zero SDRs" stand out immediately.

The formula: Outcome + Specificity + Credibility Signal. Include a number, a concrete result, or a named technique. Avoid buzzwords without substance. "Disrupting the Paradigm" tells the reviewer nothing. "5 Patterns We Found Analyzing 10,000 Failed Pitches" tells them exactly what they'll get.

Write your abstract for a busy reviewer

Conference reviewers read hundreds of proposals. They spend an average of 2-3 minutes on each one. Your abstract needs to work at two speeds: a quick scan that conveys the core idea, and a deeper read that shows you've thought it through.

Structure your abstract in three parts:

The hook (1-2 sentences) — A surprising stat, a counterintuitive claim, or a relatable pain point. Something that makes the reviewer pause and keep reading.
The substance (3-5 sentences) — What you'll actually cover. Be specific about frameworks, case studies, or data you'll present. "I'll share three real examples" is better than "I'll discuss best practices."
The takeaway (1-2 sentences) — What the audience walks away with. A checklist, a decision framework, a new mental model. Something they can use the next day.

Choose the right audience level

Most CFP forms ask for a session level: beginner, intermediate, or advanced. This isn't just a formality — it determines which reviewers evaluate your proposal and how it's scheduled. A beginner talk submitted as "advanced" will be rejected by the advanced track reviewer who expects depth. An advanced talk submitted as "beginner" will confuse the audience.

The sweet spot for most speakers is intermediate. You can assume the audience understands the basics but hasn't implemented what you're teaching. This gives you room to go deep without losing people, and it's the level with the most attendee demand.

What are the most common CFP mistakes?

After reviewing hundreds of proposals, conference organizers consistently flag the same patterns. Avoid these and you're already in the top 30% of submissions.

Being too broad

"Everything You Need to Know About Kubernetes" is not a talk — it's a book. Narrow your scope ruthlessly. If you can't explain your talk's specific angle in one sentence, it's too broad. The best CFPs tackle one problem, one technique, or one case study in depth.

Writing a product pitch disguised as a talk

Conference reviewers can smell a vendor pitch from a mile away. If your abstract reads like a product demo, it goes straight to the reject pile. The fix: frame your talk around the problem and the approach, not the product. If your company's tool is genuinely the best way to solve the problem, it'll come up naturally in the talk — but the CFP should focus on the learning, not the logo.

Ignoring the conference's audience

A DevOps-focused proposal submitted to a design conference won't get accepted, no matter how well-written. Before submitting, look at the conference's past sessions, speaker lineup, and stated mission. If your talk doesn't fit their audience, save your energy for a better-aligned event. Check out our guide to finding speaking opportunities that match your expertise.

How far in advance should you submit a CFP?

Most major tech conferences open their CFP 4-6 months before the event. The deadline is usually 2-3 months before the conference date. Submitting early (within the first week of the CFP opening) doesn't increase your chances directly, but it does mean your proposal gets read when reviewers are freshest — not buried at the bottom of a pile on deadline day.

Track CFP deadlines for conferences you want to speak at. Tools like 47Hz's event discovery, PaperCall.io, and Sessionize list open CFPs with deadlines. Set calendar reminders so you're not scrambling at the last minute.

How do you build credibility as a first-time speaker?

You don't need to be famous to get accepted. But you do need to show that you can deliver. Here's how to build credibility without prior speaking experience:

Write about the topic first. A blog post, a Twitter thread, or a detailed README that shows you've thought deeply about the subject. Link to it in your proposal.
Start with smaller events. Local meetups in San Francisco, NYC, Chicago, Austin, and Seattle have lower acceptance bars and give you a recording you can reference.
Include a speaking reel. Even a 2-minute clip from a team lunch talk or a podcast appearance counts. It shows you can communicate clearly.
Get a co-speaker. Pairing with an experienced speaker boosts your credibility and teaches you the craft. Look for co-speakers through your founder network.

What happens after you submit?

After submitting, you'll typically wait 4-8 weeks for a response. Some conferences send accept/reject emails; others just publish their lineup. During this waiting period, keep submitting to other events — don't pin your hopes on one conference.

If you get accepted, start preparing immediately. The talk you described in your CFP is a contract with the audience — deliver exactly what you promised. If you get rejected, don't take it personally. Even experienced speakers get rejected regularly. Ask for feedback if the conference offers it, refine your proposal, and submit it elsewhere. A talk rejected by one event is often accepted by another.

Once you land the speaking slot, the real work begins. Learn how to follow up after the conference without being salesy, and check out our pitch competition guide if you want to take your public speaking to investor stages next.

Explore more from 47Hz

Whether you're submitting your first CFP or your fiftieth, these guides will help you make the most of every conference opportunity.