How to Write a CFP Proposal That Gets Accepted

A CFP proposal gets accepted when the review committee can see, in under a minute, what the audience will learn, why it matters to this specific event, and why you are the right person to deliver it. That means a specific title, a short abstract focused on outcomes, a clear outline, and honest notes for reviewers about your experience. Most rejected proposals are not bad ideas; they are vague, generic or written for a different event.

How reviewers actually read proposals

Understanding the reviewer’s side changes how you write. A typical review committee is a small group of volunteers or organizers who read a large number of submissions in their spare time. Each reviewer scores proposals, often on a simple scale, and the organizer combines the scores with the needs of the agenda.

This means:

• Reviewers skim. The title and the first two sentences of the abstract do most of the work.
• Reviewers compare. Your proposal sits next to others on similar topics.
• Reviewers think about the agenda as a whole. A good talk can be rejected because the event already has three talks on the same subject.

Some events use anonymous review for the first round, where reviewers do not see your name. In that case, your experience must come through in the content, not in your reputation.

The parts of a strong proposal

1. Title

The title should tell the reviewer what the talk is about and hint at the payoff. Specific beats clever.

Weak	Stronger
“The Future of Payments”	“What We Learned Moving a Marketplace from Cards to Instant Payments”
“Intro to Smart Contracts”	“Three Smart Contract Bugs We Shipped and How We Caught Them”
“Community Building”	“Growing a Developer Meetup from 10 to 300 Members in a Mid-Size City”

Stay away from titles that only make sense if you already know the joke.

2. Abstract

This is what attendees will read on the agenda, so write it for them. Two short paragraphs:

1. The problem or context: who has this problem and why it matters now.
2. What attendees will take away: specific lessons, techniques or decisions.

Avoid claims you cannot support in the talk. Avoid marketing language about your company’s product; most events reject product pitches outside sponsor slots.

3. Outline

A short list of sections with approximate timing shows reviewers that the talk exists and fits the slot. For a 30-minute talk, four or five sections are enough.

4. Audience level

Say who the talk is for: beginners, intermediate practitioners or experts. Reviewers need this to build a balanced agenda.

5. Notes for reviewers

This private section is your chance to explain:

• Your direct experience with the topic.
• Whether you have given this talk before, and where; include a recording if you have one.
• Why this talk fits this particular event and audience.
• Any constraints, for example if you need to present on a specific day.

6. Bio

Short, third person, focused on what is relevant to the talk. Mention the language or languages you can present in.

A fill-in template

Copy and adapt this:

Title: [Specific action or result] + [context]

Format and length: [Talk / workshop / lightning talk], [minutes]

Level: [Beginner / intermediate / advanced]

Language: [Spanish / Portuguese / English]

Abstract: [One or two sentences on the problem and who faces it.] [One or two sentences on what attendees will learn or be able to do after the talk.]

Outline: 1. [Context: the situation and the problem] — [minutes] 2. [What we tried first and why it did not work] — [minutes] 3. [What worked, with concrete details] — [minutes] 4. [Lessons and how attendees can apply them] — [minutes] 5. [Questions] — [minutes]

Notes for reviewers: I [role/experience directly related to the topic]. I have given [this or a related talk] at [event], recording: [link]. This talk fits [event name] because [reason connected to its audience or theme].

Bio: [Name] is a [role] at [organization or independent], working on [area]. [One relevant achievement.] [Languages they present in.]

The most common reasons proposals are rejected

1. Too generic. “An introduction to X” with no angle. Reviewers have seen many.
2. Product pitch. The talk is mostly about your company’s product. Organizers usually offer sponsor slots for that.
3. Wrong event. The topic does not match the event’s theme or audience. Read the CFP description and past agendas before writing.
4. Unclear takeaway. The abstract describes the topic but not what the audience will learn.
5. Too much for the slot. An outline that tries to cover a whole field in 25 minutes.
6. Missing information. No bio, no level, no outline, broken links.
7. Duplicate topic. Someone else submitted a similar talk with stronger experience behind it.
8. Late submission. Submitted at the last minute with obvious copy-paste errors, such as another event’s name.

Only some of these are under your control, but the controllable ones are the most frequent.

Tailor each submission

Reusing a proposal is fine; sending it unchanged everywhere is not. For each event:

• Read the CFP text and look for themes, tracks or questions the organizers want covered.
• Look at last year’s agenda to understand the level and style.
• Adjust the title and the “why this event” note.
• Check the language: many Latin American events accept proposals in Spanish or Portuguese, and some prefer them. If the event audience is local, consider proposing in the local language.

Local context matters

For events in Latin America, reviewers often value talks that show how something works in the region: regulation in a specific country (with sources), the realities of local payment systems, building with limited budgets, or community growth outside the capital cities. A global talk that adds a well-researched regional angle stands out.

If you are a foreign speaker, say so in the notes and mention whether you need help with travel or an invitation letter. See visas and travel for speakers in Latin America for what to plan.

After you submit

• Note the decision date and do not chase organizers before it.
• If accepted, confirm quickly and ask about logistics.
• If rejected, ask briefly whether feedback is available, then improve and submit elsewhere.

For the bigger picture of building a speaking career, read how to become a conference speaker. If you are an organizer reading this, our guide on running a call for papers covers the other side.

On BuildAConf, events open a call for papers on their own website and you apply from there. Organizers review proposals with 1–5 scores and accept or reject them, and you receive an email when a decision is made. Create your profile at buildaconf.com/para-speakers.

Frequently asked questions

How long should a CFP abstract be?

Short enough to read in under a minute. Two compact paragraphs usually work: one on the problem, one on what attendees will learn. Follow any length limit the event sets.

Can I submit the same talk to several conferences?

Yes, that is normal. Adapt the title, abstract and reviewer notes to each event, and tell organizers if the talk has been recorded elsewhere, since some events prefer new content.

Should I mention my company in the proposal?

Mention it in your bio and, if relevant, as context for your experience. Do not make the talk about selling your product unless it is a sponsor slot.

What if the CFP asks for a video?

Record a short, simple clip on your phone explaining the talk and why it matters. Reviewers want to hear how you speak, not see a professional production.