Media Morpheus

How-To Guideby Media Morpheus Research

October 10, 2026 · Last fact-checked: October 10, 2026

How to Submit a Conference Speaking Proposal: Format, Title, Abstract, Outline and Follow-Up

To submit a conference speaking proposal, read the call for proposals in full, choose the session format that fits your material, then write a specific title, an abstract that says what attendees will learn, and a timed outline, and remove anything that reads as a product pitch. The main prerequisite is a topic you can prove you know, ideally with a past recording. This guide has eight steps. Key warning: competition is heavy. KubeCon + CloudNativeCon accepted 8% of 2,947 submissions for its 2025 London event.

SpeakingConferencesThought leadershipExecutive visibility

At a Glance

  • Selection rates at large events are low. CNCF reported an 11% acceptance rate for KubeCon North America 2024 (1,937 submissions) and 9% for Europe 2024 (2,541) (CNCF).
  • Relevance counts as much as quality. The KubeCon call says “the relevance of your presentation is crucial, and it's as significant as the content in determining acceptance” (KubeCon CFP).
  • Sales pitches are a common reason for rejection. The same call says to “Avoid sales or marketing pitches”; PyCon US lists infomercials among talks to avoid (PyCon US).
  • Some reviews are blind. PyCon US says that in its first round “we won't even see your name on the proposals!”, so the title, description and outline must not identify you.
  • Both calls we read reject proposals built on AI-generated text; PyCon US says not to submit one “solely or to a large extent written” by AI.

What Is a Conference Speaking Proposal?

A conference speaking proposal is a structured submission to an event's call for proposals (CFP), usually a title, an abstract or description, an outline, a format choice and speaker details, which a programme committee reviews to decide who speaks.

Committees read hundreds or thousands of proposals for a few hundred slots, and much of the decision rests on what the proposal itself says. A proposal is therefore closer to a short, specific contract with the audience than to a speaker bio: what you will cover, for whom, in how many minutes, and what people will be able to do afterwards. Whether a talk builds lasting visibility is a separate question; our explainer do conference talks build authority? found that the durable asset is the recording or write-up, not the appearance.

How to Submit a Speaking Proposal at a Glance

StepActionExpected result
1Shortlist events and read each CFP in fullDeadlines, tracks, caps and rules on one sheet
2Choose the session formatA format whose length suits the material
3Write a specific titleA title that says the topic and the audience
4Write the abstract or descriptionA concrete promise of what attendees will learn
5Write a timed outline and takeawaysA bulleted plan that fits the slot
6Remove pitches, identifying details and AI-written textA proposal that passes the CFP's rules
7Add speaker evidenceA past recording, slides or code linked
8Submit early and follow upA confirmation, then an acceptance plan or feedback

Time: one to two days for a first proposal, less for later ones (our estimate). Tools: a document, the event's submission system, a past recording. Cost: usually none to submit; travel is a separate question each event answers. Skill level: intermediate.

What You Need Before Starting

  • A topic you have worked on directly, with an example, data or a lesson others can use.
  • A short and a long speaker bio; see how to write an executive bio for media.
  • A recording of a previous talk, podcast or video of you speaking, if you have one.
  • Your employer's approval to speak, and to name any customer or project in the talk.
  • Calendar clearance for the event dates, since committees expect accepted speakers to attend.

Step 1: Shortlist Events and Read Each CFP in Full

Pick events whose audience needs your topic, then read every word of the call for proposals. CFPs differ on caps, formats, review method and what they reject.

Process: record the deadline, time zone, tracks, formats, submission cap and any rules on prior talks. KubeCon North America 2026 lists submissions due “May 31 at 11:59pm Mountain Time”, notifications on August 3 and the event on November 9 to 12; it allows a speaker on “a maximum of three proposals” and will not select talks already given at a Linux Foundation event within the past year (KubeCon CFP). PyCon US 2026 allowed three submissions per person and one talk per presenter (PyCon US). SXSW works differently: its site says “Final sessions are decided by the public, the SXSW Advisory Board, and SXSW staff”, after a public PanelPicker vote that ran August 5 to 23, 2026 (SXSW PanelPicker). Expected result: a sheet of events with their rules. Common mistake: sending the same proposal everywhere without checking each event's rules.

Share of proposals accepted at three KubeCon + CloudNativeCon events

Per cent of submissions accepted, as reported by CNCF

North America 2024 (1,937 submissions)
11%
Europe 2024 (2,541 submissions)
9%
Europe 2025, London (2,947 submissions)
8%

Source: CNCF, North America 2024 and Europe 2024 selection posts; London 2025 recap. Read October 10, 2026.

CNCF says its 2024 counts of accepted talks exclude the 90 slots held for special interest groups at each event. Rates at smaller or regional events can be very different; few events publish them.

Step 2: Choose the Session Format

Pick the format whose length fits what you can teach well. A strong 30-minute talk is easier to accept than a padded 75-minute one.

KubeCon lists a 30-minute session for one or two speakers, a 30-minute panel of three to five, a five-minute lightning talk, a 75-minute hands-on tutorial and a poster session. PyCon US offers 30 and 45 minutes and warns that 45-minute slots “are in very limited supply”; it asks you to explain how you would shorten the talk if only 30 minutes are offered. Panels carry extra rules: KubeCon will not accept panels of three or more speakers who all identify as men, and panelists must represent more than one company. Expected result: one chosen format with a fallback. Common mistake: proposing a panel of colleagues from one employer.

Session lengths offered in two 2026 calls for proposals

Minutes per session, as published

KubeCon tutorial
75 min
PyCon US talk, long slot
45 min
PyCon US talk
30 min
KubeCon session presentation
30 min
KubeCon panel discussion
30 min
KubeCon lightning talk
5 min

Source: KubeCon + CloudNativeCon North America 2026 CFP; PyCon US 2026 talks page. Read October 10, 2026.

KubeCon poster sessions have no stated length and are omitted. Formats change by event and year.

Step 3: Write a Specific Title

Write a title that names the problem and the audience. Reviewers and, later, attendees scan titles first.

Process: state the topic and the payoff in plain words, for example “Cutting Build Times in a 400-Service Monorepo: What Worked and What Didn't” over “The Future of Builds”. Follow house style; KubeCon asks you to “use title case”. For blind review, keep your company and product names out of the title. Expected result: a title a stranger could summarise correctly. Common mistake: a clever title that hides the subject.

Step 4: Write the Abstract or Description

Say who the talk is for, what problem it addresses, what you will show, and what attendees will be able to do afterwards. This is the part reviewers weigh most.

The KubeCon call says “a well-crafted, engaging abstract will improve your chances of acceptance” and asks for a description that is focused, detailed and concise, plus a separate statement of benefits to the ecosystem. PyCon US asks what attendees will know when they leave and lets you set an audience level. Process: write four short paragraphs or fewer: context, what you did, what you learned, who benefits. Use one concrete figure if you have it. Keep to any character limit in the submission form; the calls we read did not publish one, so check the form itself. Expected result: an abstract that could appear in the printed programme unchanged. Common mistake: describing the speaker instead of the talk.

Step 5: Write a Timed Outline and Takeaways

Show how the minutes will be spent. An outline proves the talk exists and fits the slot.

PyCon US says: “Your outline should be an enumeration of what you intend to say, along with time estimates”, and that “a two-level bulleted list format works best” (PyCon US). Process: list five to eight sections with minutes against each, leave time for questions, and end with two or three takeaways written as things the attendee can do. If a talk is a case study, KubeCon asks you to say so. Expected result: minutes that add up to the slot. Common mistake: an outline with no times, or one that only lists slide titles.

Step 6: Remove Pitches, Identifying Details and AI-Written Text

Read the draft as a reviewer who has been asked to reject vendor talks. Strip anything that sells, identifies you in a blind round, or reads as machine-written.

KubeCon tells submitters to “Avoid sales or marketing pitches” and says it checks for “low-effort, AI-generated” content. PyCon US lists infomercials and generic “state of our project” talks among those to avoid, and says not to submit a proposal “solely or to a large extent written” by AI. For blind review, refer to “a payments company” rather than your employer. If you need help with an executive's delivery and message discipline, see how to run a media training session for executives. Expected result: a proposal a competitor could attend and learn from. Common mistake: a roadmap of your product presented as industry trends.

Step 7: Add Speaker Evidence

Give reviewers a way to judge whether you can deliver. A short recording is the strongest evidence.

KubeCon invites a recording of a previous talk or a short video of you speaking, and asks you to explain how a talk differs if you gave it in the past year. PyCon US asks for links to source code, articles, videos and prior slides or recordings. If you have never spoken at a conference, a podcast interview can serve; see how to pitch yourself as a podcast guest and how to write a podcast guest one-sheet. Expected result: one or two public links that open without a login. Common mistake: a link to a sales webinar.

Step 8: Submit Early and Follow Up

Submit before the deadline, save the confirmation, and plan for both outcomes.

PyCon US says it encourages speakers “to submit their proposals as early as possible”. If accepted, publish the slides and recording on a stable page you control, with a transcript, so the talk outlives the event; see how to add video structured data and how to add Person schema for executives. If rejected, ask for feedback: CNCF says “Many Committee members are more than willing to chat with you to provide feedback on your submission.” Expected result: an acceptance plan or a revision list for the next CFP. Common mistake: treating a rejection as a verdict on the topic; at an 8% to 11% acceptance rate, most good proposals are declined.

How to Verify It Worked

  • Submitted: the proposal shows in the event system with a confirmation email.
  • Compliant: the format, speaker count, submission cap and blind-review rules are all met.
  • After the event: the recording or slides are on a public page that you control and that is indexed; see how to check if a page is indexed by Google.

How to Choose Where to Submit

SituationRecommended approachWhy
First-time speakerLightning talks, local meetups, regional eventsShort formats and smaller pools; builds a recording
Deep technical case studyPractitioner events with blind reviewContent is judged on its merits
Executive with a business messageIndustry or trade events with keynote or panel formatsAudience and format fit; check vendor-pitch rules
Community-voted event such as SXSWStrong title and video, and a plan to share the voting linkThe public vote is one input, alongside the advisory board and staff
Paid speaking slot offered by an organiserTreat as sponsorship and disclose itIt is paid placement, not a selected talk

Common Problems and Fixes

ProblemLikely causeFix
Repeated rejectionsGeneric topic or vague abstractNarrow to one problem and one audience; ask for feedback
Accepted for 30 minutes, planned 45Long slots are scarcePrepare the shorter version in the outline from the start
Proposal flagged as a pitchProduct names and claims in the abstractDescribe the problem and lessons; leave the product out
Panel rejectedSpeakers from one company or a homogeneous lineupFollow the CFP's panel rules
Talk forgotten after the eventNo recording or pagePublish slides, video and transcript on your site

What Not to Do

  • Do not exceed the submission cap. Consequence: proposals removed or a forced choice. Correction: submit your best three or fewer.
  • Do not resubmit a talk you gave last year unchanged. Consequence: KubeCon will not select it. Correction: explain what is new.
  • Do not let AI write the proposal. Consequence: rejection under both calls we read. Correction: write it yourself, from your own notes.
  • Do not identify yourself in blind-review fields. Consequence: you break the event's rules. Correction: keep names in the speaker fields only.
  • Do not pitch the product. Consequence: rejection, or a poorly received session. Correction: teach what you learned.

Frequently Asked Questions

How long should a conference talk abstract be?

As long as the submission form allows and long enough to say who the talk is for, what it covers and what attendees will learn. The KubeCon and PyCon US calls we read did not publish a word limit on the page, so check the form itself.

What are the chances of a proposal being accepted?

At large events, low. CNCF reported acceptance rates of 11% for KubeCon North America 2024, 9% for Europe 2024 and 8% for London 2025. Most events do not publish rates.

Can I submit more than one proposal?

Usually, up to a cap. KubeCon allows a speaker on a maximum of three proposals, and PyCon US allowed three submissions per person but only one talk per presenter.

Can a company executive submit a talk about their product?

They can submit, but product pitches are a common reason for rejection. KubeCon tells submitters to avoid sales or marketing pitches, and PyCon US lists infomercials among talks to avoid. Teach a lesson instead.

Is it acceptable to use AI to write a proposal?

Not at the events we checked. PyCon US says not to submit proposals largely written by AI, and KubeCon says it checks for low-effort, AI-generated content.

What should I do if my proposal is rejected?

Ask for feedback where offered, revise and submit elsewhere. CNCF says many committee members are willing to discuss submissions. At single-digit acceptance rates, rejection often reflects competition, not quality.

Sources and Methodology

This guide is built from the calls for proposals and selection reports listed below, read on October 10, 2026. We did not submit a proposal, review proposals for any committee, or test how scoring works. Acceptance rates are those the organiser published for named events and do not describe other conferences. The SXSW figures are limited to what its public PanelPicker page states; the weighting of votes is not given there, so we do not repeat it. Time estimates are ours.

  1. organiser Linux Foundation and CNCF, KubeCon + CloudNativeCon North America 2026: Call for Proposals. Read October 10, 2026.
  2. organiser CNCF, Inside the numbers: the KubeCon + CloudNativeCon selection process for North America 2024, August 19, 2024. Read October 10, 2026.
  3. organiser CNCF, Inside the numbers: the KubeCon + CloudNativeCon selection process for Europe 2024, January 30, 2024. Read October 10, 2026.
  4. organiser CNCF, KubeCon + CloudNativeCon London recap, May 9, 2025. Read October 10, 2026.
  5. organiser Python Software Foundation, PyCon US 2026: Talks, proposal guidance. Read October 10, 2026.
  6. organiser SXSW, PanelPicker. Read October 10, 2026.
  7. own data Media Morpheus Research, Do Conference Talks Build Authority?