In fact, the first time I submitted a conference talk, I hovered over the submit button for nearly an hour. I was convinced someone else had more experience, a better résumé, or more impressive GitHub stars. But I submitted anyway. And to my surprise, it was accepted.

Since then, I’ve spoken at more than 20 conferences including API Conf Lagos, Indabax Nigeria, multiple DevFests, and Write the Docs Prague. Some of my talks include:

• Leveraging Open Banking APIs for Innovation at API Conf Lagos

• Optimizing Your JavaScript Code for Speed, Sailsconf AF 2024

• Creating Documentation for the African Audience at Write the Docs Prague

Table of Contents

1. Don’t Wait Until You Feel Ready

2. Where to Find Calls for Proposals (CFP)

3. Start With a Story, Not Just a Topic

4. How to Write Strong Proposals That Get Noticed

5. Tailor Your Proposal for Each Event

6. How to Get Better at Giving a Presentation

7. Keep Going After You Speak

8. Expect Rejections — and Keep Submitting

I have three more talks lined up for the second half of 2025.

Along the way, I have developed a system that works. Whether you’re preparing your first CFP or aiming for bigger events, here is how I approach it and what I’ve learned.

1. Don’t Wait Until You Feel Ready

If you want to submit conference talks, you’re going to have to overcome your hesitation and start where you are.

In 2022, I co-submitted a talk to Write the Docs Prague with my friend Benny Ifeanyi Iheagwara. The talk was titled “Creating Documentation for the African Audience.”

It focused on challenges like language diversity, cultural assumptions, and inconsistent internet access.

We weren’t sure a European audience would care. But we believed the message was important, so we submitted it.

It was accepted.

That session gave us a platform to discuss issues that affect millions of African developers and users. We delivered it virtually, and the feedback showed us how much it resonated.

What I learned was simple: you don’t need to be perfect. You just need to be useful and timely.

2. Where to Find Calls for Proposals (CFP)

This might seem obvious, but many people don’t know where to start. I find most of my CFPs through platforms like:

• Sessionize

• Papercall.io

• cfp.land

• LinkedIn posts by organizers

• Community Slack or Discord channels

Some CFPs are hidden in newsletters or tucked away on event websites. If there’s a conference you admire, follow it and check in regularly. Keep a calendar of deadlines. The earlier you plan, the better your submissions will be.

3. Start With a Story, Not Just a Topic

Craft a compelling narrative that resonates with audiences.

The organizers have requirements to meet. Figure out what they are looking for and build your story around it.

For example, here are some submission guidelines from a conference that outline what the conference organizers are expecting and looking for:

When I pitched “Leveraging Open Banking APIs for Innovation” to API Conf Lagos, I didn’t open with code. I started with the story of a Nigerian fintech startup struggling with outdated bank systems. That story gave the session weight.

The technical content mattered, but the narrative made it relatable.

Start by studying the Call for Proposals (CFP) carefully. Most CFPs will tell you the themes, skill levels, and audience types the event caters to. Look for phrasing like “we’re looking for real-world stories,” “new voices,” or “hands-on technical depth.” That language is a blueprint for what the organizers want.

Beyond that, look at previous years’ talks. What kind of speakers did they feature? Were the sessions deeply technical, more inspirational, or a mix?

Finally, don’t be afraid to reach out to the organizers directly. A quick message like, “Hey, I’m thinking of submitting something about open banking and fintech devs in West Africa – would that be a good fit?” can give you early feedback that steers your proposal in the right direction.

4. How to Write Strong Proposals That Get Noticed

Learn how to make your submission stand out.

A strong proposal does a few things well:

• It starts with a clear, relevant problem

• It explains why this topic matters now

• It outlines what the talk will cover

• It describes what attendees will gain

Here’s an example from my “Banking without Banks” talk that got accepted for a conference just this past May:

When you’re writing these proposalas, keep the 5 W questions (Who, What, Where, When, Why) plus the story in mind. It’s a clear and effective way to communicate the purpose and value of your talk.

1. Who is this talk for?

This talk is for developers, tech leads, and product managers building or exploring financial technology solutions. It is especially valuable for startups embedding financial services like payments, lending, or account insights into their applications. It’s also for anyone interested in API-driven innovation in emerging markets, with a particular focus on financial inclusion.

2. What is this talk about?

This talk explores how open banking APIs are creating new opportunities for innovation in financial services. It features practical strategies, technical demos, and real-world case studies that show how developers can build robust, secure, and user-centric applications – even in regions with infrastructure challenges.

3. Where is this knowledge coming from?

The talk is grounded in firsthand experience from working with fintech startups in Nigeria and across emerging markets. These insights are based on real projects, real companies, and real challenges – with live examples of how open banking APIs are already being used to solve meaningful problems.

4. When is this talk relevant?

Right now. In March 2023, the Central Bank of Nigeria (CBN) formally approved open banking regulations, making Nigeria the first African country with a legal framework for it. As more countries adopt similar regulations, the demand for embedded finance is growing. Developers must be prepared to navigate this rapidly evolving space.

5. Why Should People Care?

Open banking presents an unprecedented opportunity to unlock financial innovation. Also, brings technical, compliance, and design complexity. Developers must understand:

• What the framework enables and limits

• How to work with standardized APIs from banks and third parties

• How to manage security, compliance, and user experience in sensitive financial applications

5. Tailor Your Proposal for Each Event

Even if I’m presenting similar material, I never use the same exact abstract twice. DevFest Ajah and Google I/O Extended Ibadan have different audiences and energy.

I always reframe the content to fit the event.

Show that you understand the community and what they care about. Event organizers notice when you’ve taken time to customize your submission.

6. How to Get Better at Giving a Presentation

Your first talk may be terrible. But it’s ok – with practice and effort, you’ll get better.

Want to improve your delivery? Here's a method that works for me:

1. Pick a great talk from a past conference – something close to your topic or style.

2. Download the transcript and slides, if they’re available.

3. Record yourself delivering that exact talk as if it were your own.

4. Compare: Watch your version next to the original. Notice what works and what doesn’t – pacing, tone, energy, clarity.

5. Share your recordings with friends and ask for feedback.

This kind of deliberate mimicry isn’t copying – you’re not sharing it publicly. It’s training. Just like athletes study match footage, great speakers study other speakers. Over time, you’ll develop your own rhythm, voice, and presence.

Presenting is a skill. And like any skill, it improves with practice, feedback, and repetition.

7. Keep Going After You Speak

Leverage each talk to grow your influence and connections.

Speaking at a conference is only the beginning. After each session, I usually:

• Share my slides online. You can find mine on SpeakerDeck.

• Post a recap on LinkedIn or Twitter

• Thank the organizers publicly

• Connect with attendees who reach out

This helps you build momentum and expand your network. After my TensorFlow talk at Indabax, I posted a follow-up summary. That single post led to an invitation to speak at another community event.

8. Expect Rejections — and Keep Submitting

Not every submission gets accepted. I’ve had proposals sit in “in evaluation” forever and never hear back. Some were outright rejected. My talk on using SVGs to visualize election data was one I believed in deeply. Still, it never made it into any lineup.

That’s normal.

Rejection is not a judgment of your worth. It doesn’t mean your idea is weak or your voice is not needed. Conferences have limited slots, and even strong proposals get turned down.

But here’s the truth:

If your talk was rejected, accept yourself anyway. 😊

• You already have the speaker – you

• You already have the content – your proposal

• You may not have the audience yet – create one

• Set your own stage – YouTube, LinkedIn, Twitter, Dev.to

That talk you prepared? Present it.

Publish the content. Record a video. Host a Twitter Space. Turn it into a blog post or a mini-course. Accept your own talk. And then try again.

Conclusion

Sharing your ideas on stage can feel intimidating, but it’s also one of the most rewarding ways to grow. You don’t need to be the most experienced speaker to make an impact. You just need to start.

So take that first step. Hit submit. Your story might be exactly what someone in the audience needs to hear.

Conferences offer different session formats, such as lightning talks, workshops, panels, and full-length sessions. Organizers look for clear, relevant, and valuable topics for their audience. A strong proposal aligns with the event's topic and clearly demonstrates its significance to reviewers.

I have been selected to speak at conferences such as API World, API Specification Conference, PyCon Italia, and PHP Day Italy, and I co-organize API Conf Lagos. From both sides of the table, when submitting and reviewing CFPs, I have seen what works and what does not.

In this guide, I’d like to share what makes a good CFP and offer tips on creating a standout proposal. Whether you are submitting for the first time or looking to refine your approach, these insights will help you craft a compelling proposal that gets noticed.

In this article, you’ll learn the following:

• Understanding the CFP Criteria

• Key Components of a CFP Submission

• How to Choose the Right Topic

• How to Craft a Strong Title and Abstract

• How to Structure the Proposal

• Submission Best Practices

• Where to Find CFP Opportunities

Understanding the CFP Criteria

CFP requirements vary from conference to conference, so understanding the specific criteria before submitting your application is crucial to increasing your chances of selection. Most conferences provide a criteria page outlining key details. When you’re writing a CFP submission, some criteria are more crucial than others in shaping a strong proposal.

The most relevant criteria include:

• Topic – Areas of interest that the conference aims to cover.

• Session format and duration – This indicates the available sessions for the conference. It could be a session, workshop, or lightning talk, along with the time allocated.

• Audience expectations – This is used to gauge the audience's level of expertise (beginner, intermediate, advanced) and what attendees hope to gain from the event.

Keeping an eye on the core criteria, topic, audience, and format will help ensure your CFP submission aligns well with the conference expectations. And this can help increase your chances of acceptance.

While necessary for planning, other logistical aspects play a less direct role in crafting the proposal. These include:

• Speaker logistics and support – Information on travel, accommodation, and benefits for speakers, such as honorariums or reimbursements.

• Event fees and scholarships – Whether speakers receive free entry or if financial aid options are available.

• Code of conduct – The conference sets the ethical and behavioral guidelines for speakers and attendees.

• Conference duration – Whether the event lasts for one day, two days, or multiple days, which may affect scheduling and availability.

Elements of a CFP

Talk Title

First, you’ll need to decide on a clear, compelling title that makes it obvious what the talk is about in an easy-to-understand way. Clarity and simplicity always win.

You should avoid overly verbose or clickbait-style titles like: “Harnessing the Ultimate Power of Next-Gen APIs to Revolutionize Your Tech Stack”. Instead, you could say something friendlier and clearer: “How to Design Scalable APIs That Align With Your Product.”

Abstract

The abstract is a brief description of your talk. In this section, you should provide a summary that generally explains what your talk is about, how the audience would benefit from it, and why the conference organizers should value and select your talk.

It’s acceptable to discuss example scenarios you plan to cover and the tools or libraries you’ll be using, as this will help promote your idea more effectively than a simple sentence or two with no technical info.

Detailed Description/Proposal

I would like to note that not all conferences offer this section, but for those that do, it is a more in-depth and detailed explanation of your abstract, which sometimes can exceed 1000 words. This will enable you to explain the value, structure, areas of focus, and key takeaways of your talk.

In both the abstract and proposal, you should discuss the problems you’re addressing in your talk and what the audience stands to learn, which are both very important.

Speaker Bio

This is just as important as the talk title itself, as it informs the organizers about who you are, where you work, your relevant experience, and how the conference can benefit from having you at the event. Include a recent picture of yourself and, if possible, provide your social media profiles like LinkedIn, so they can connect with you.

Alright, now that you know the various parts involved in creating a CFP, let's look at each component in more detail – and how you can actually craft each part.

How to Choose the Right Topic

Most CFP pages showcase topics that interest conference organizers. As a prospective speaker, your goal is to select a topic that aligns with these subjects. You’ll also want to make sure that you have a deep enough knowledge on the topic you choose to speak and answer questions about it confidently.

For example, if a conference emphasizes specific topics such as PHP, Continuous Delivery, DevOps, Security, Testing, or APIs, proposals that align with those subjects are more likely to be accepted. Submitting a topic outside the listed themes the conference plans to cover may reduce your chances unless it provides exceptional value to the audience.

Here are some practical examples:

• If a conference is focused on DevOps, your proposal is more likely to be accepted if it covers continuous delivery pipelines, performance and monitoring, infrastructure automation, or incident response practices. Submitting a topic outside the listed subject, such as frontend design, may reduce your chances unless it offers exceptional value to the audience.

• If a conference is focused on APIs, your proposal is more likely to be accepted if it covers how to design versioned APIs, securing API endpoints with Authentication and Authorization, scaling API-first applications, compliance and governance, Api performance and observability, Api documentation, or managing third-party integrations.

• For a PHP conference, you should submit a proposal that cover performance improvements in PHP 8+, real-world security use cases in Laravel applications such as OWASP, PHP architecture patterns, scaling large PHP applications, writing extensions in PHP, highlighting important libraries you use daily, or guiding attendees on how to contribute to such PHP libraries.

When selecting your topics, ask yourself:

• What’s the value I’m bringing to attendees?

• Is the topic something I’m passionate about and knowledgeable about?

• Does it align with the needs and interests of the target audience?

To improve your chances, tailor your proposal to fit the conference’s focus. Pay close attention to the wording of your topic and ensure it directly connects with the event’s goals.

How to Craft a Strong Title and Abstract

Once you've chosen a relevant topic, you’ll need to create your talk title and abstract. For instance, you might focus on addressing security concerns using a particular programming language or tackle modern security challenges within a niche area.

It’s important to remember that while tools like AI models (for example, ChatGPT) can be helpful, relying too heavily on them to craft your title and abstract can work against you. The key is to use clear, simple language that speaks directly to your audience. Avoid overly technical jargon or convoluted phrasing, as this may hinder understanding.

Here are some key things to keep in mind when choosing a title and writing your abstract:

Select a Friendly Title

Your title is the first thing conference organizers see, and keeping it simple, engaging, and clear should be the goal.

Examples of strong titles might include:

• Moving Beyond CRUD: Designing More Scalable APIs with TDD

• How to Keep Your Application Secure with the Zero Trust Principle

• Why You Should Care About the Risk and Rewards of Feature Flags

• How to Orchestrate Effective Releases with CI/CD with Practical Tips for Teams

You may be wondering why these are examples of strong titles. Well, it’s because:

• They are clear and accessible, and at a glance, you already know what the topic is about. The topics are also approachable even if you’re not an expert.

• The topics also highlight values or possible outcomes: either the audience will learn about risk and rewards with feature flags, or they will equip themselves with knowledge of securing their applications using the Zero Trust principle, or learn how to design scalable APIs in a test-driven manner.

• The topic targets those directly involved in the software delivery lifecycle, including developers, DevOps engineers, engineering teams, and managers.

Writing a Compelling Abstract

When writing your abstract, it’s essential to provide a thorough overview of what your talk will cover. A one or two-sentence summary likely won’t be enough to give conference organizers the deeper insight they need into what your session offers.

Your abstract expands on the talk title, providing a more detailed description of the topic. This includes what your talk will cover (if it’s a workshop, mention the language or tools used, along with any expected outcomes or builds), the attendees who would benefit most from the talk, and possible learning outcomes.

Spending most of your time crafting your abstract is crucial to your talk getting accepted. From experience, here’s what a good abstract should include:

• Start with a sentence or two introducing the subject. So if you’re talking about the Zero-trust principle, explain what it means and discuss why it matters. Then talk about the problem it helps stakeholders involved in software delivery solve.

• Describe what the talk will cover. Mention tools, frameworks, or case studies you’ll use here to deliver the talk if selected. For example, “We’ll cover core concepts like 'Never trust, always verify,' least privilege, and continuous monitoring, along with practical steps such as using OAuth2, MFA, RBAC, JWTs, and encryption”.

• Explain who the target audience is. Are they beginners, intermediates, or experts? This will help organizers place your talk on the right track for the identified audience.

• End your abstract with 2-3 clear learning outcomes. What will attendees be able to do, understand, or think differently about after your session? For example, attendees will learn about Zero Trust architecture, enforcing strong authentication and authorization, as well as tools for continuous monitoring and auditing to detect threats.

Don’t rush through the process of writing your abstract. Allow yourself time to develop it gradually as ideas come to mind. It’s perfectly fine to keep your proposal open and pinned, updating and refining it over time. This approach will give you the bandwidth to ensure your abstract is clear, comprehensive, and engaging, ultimately leading to a stronger proposal.

Remember, your abstract should be written in simple, clear language and be free from grammatical errors. Keep in mind that some conferences have word limits for abstracts, so ensure your description fits these constraints.

How to Structure the Proposal

Once you’ve identified a topic and written the abstract, it’s crucial to structure your proposal in a way that is easy to read and provides clarity regarding your target audience and the learning outcomes. A well-structured proposal makes it easier for conference organizers to understand the value of your session and decide whether it’s a good fit.

To illustrate this, we’ll look at two proposal examples: one that can be improved and one with a strong structure that’s likely to be accepted.

❌ Weaker Proposal

Topic: Security in Software Development

Abstract:
Security in software development is important. This session will cover security practices and techniques in code.

Why this proposal is weak:

• The title is too vague and doesn’t specify the talk's focus.

• The abstract lacks depth and does not clearly describe what the attendees will learn.

• The audience is unclear, and no specific learning outcomes are mentioned.

✅ Strong Proposal

Topic: Building Secure Web Applications with Modern [Programming Language 1] Frameworks

Abstract:

It’s important to think security first when trying to build applications for the web, regardless of what programming language or framework you’re using. In today’s world, securing your application will protect you from data breaches, prevent fraudulent transactions, and help you avoid common vulnerabilities, ultimately improving the performance of your system.

In this talk, we will discuss the key security practices that developers should follow when building web applications with modern JavaScript frameworks, such as [Framework 1] and [Framework 2]. We’ll cover concepts such as input validation, securing APIs, handling authentication, and best practices to prevent common security vulnerabilities, including cross-site scripting (XSS) and SQL injection.

At the end of this session, developers will gain actionable insights on implementing security measures, explore common vulnerabilities, and build a demo app using [Framework 1] or [Framework 2] to address the security concept listed above, along with secure coding practices and tools to safeguard their apps.

This talk is designed for intermediate and advanced JavaScript developers who want to enhance the security of their web applications.

Why this proposal is strong:

• The title is clear and specific, highlighting the session's main focus.

• The abstract provides an introduction, a detailed description of the content that will be covered, ensuring organizers know exactly what to expect.

• The target audience is defined as "intermediate and advanced JavaScript developers."

• Learning outcomes are clearly outlined, including actionable takeaways and specific skills attendees will gain.

Here are two samples of my proposals that have been accepted in the past.

• PHPDAY ITALY ‘25: Securing PHP Applications with Zero Trust Principles

• API SPECIFICATION CONFERENCE ‘21: ABC of GRAPHQL

Submission Best Practices

Once you've completed your proposal, it's essential to take a step back and reflect on your topic and abstract. Review your submission carefully for any areas that need refining, check for typos, and ensure the message is clear and well-structured.

Sometimes, sharing your proposal with colleagues or peers for feedback can be invaluable. They might catch things you overlooked or offer suggestions to improve clarity or focus.

This reflection and review process acts as a safety net, ensuring you haven’t missed anything important before submitting. Keep in mind that conference organizers receive hundreds of CFPs, so taking the extra time to polish your submission can significantly improve your chances of standing out in a competitive pool.

The submission process typically looks like this:

1. Call for Paper (CFP) Announcement

The conference announces its call for papers (CFP) information, including details such as the deadline, topics, venue, session types, and submission guidelines.

2. Submission Platform

Conferences use tools like Typeform, Sessionize, Papercall, and even Google Docs, based on preference, and you’ll be asked to provide information about your talk proposal. This information includes:

• Talk title

• Abstract

• Talk format (Workshop, Session, Keynote)

• Target audience

• Speaker bio

• [Optional] Past speaking experience, like YouTube links to previous talks, and so on

Review Phase

After the CFP closes, panels begin reviewing submissions and deciding who will speak at the conference. They select speakers based on their own checklist and determine the lineup of speakers.

Notification and Follow-up

Successful speakers will receive congratulatory emails notifying them to confirm their participation in the conference and may need to submit additional information, such as a slide deck or session outline.

Speakers who don’t make the cut will typically get a rejection email, and often some organizers extend free or discounted event tickets to those speakers who have invested their time in submitting a proposal.

Conference schedule

Once selected, speakers will have their bio, talk title, and abstract published on the conference website. The schedule will also include the date, time, and room where each session will take place, helping attendees plan which talks to attend.

Where to Find CFP Opportunities

If you're looking for conferences to submit your proposal to, several platforms and resources regularly list open calls for papers (CFPs). Instead of waiting to stumble upon a CFP announcement, you can actively search for speaking opportunities that align with your expertise.

Popular CFP Platforms:

• Sessionize – A widely used platform where conferences post CFPs, allowing speakers to submit proposals easily.

• PaperCall.io – A hub for discovering CFPs across different industries, including tech and open-source events.

Other Ways to Discover CFPs:

• Conference websites: Many conferences post their CFPs directly under a "Call for Papers" or "Call for Speakers" section.

• Tech communities and newsletters: Platforms like Dev.to, Hashnode, and newsletters often share open CFPs.

• Social media: Following conference organizers and speakers on LinkedIn and Twitter can help you stay updated about new CFP openings.

• Local and virtual meetups: Many meetup groups are seeking speakers, and these smaller events can be a great way to gain experience before applying to larger conferences.

Conclusion

In this article, you learned what makes a good conference talk proposal, how to structure your proposal with examples, and submission best practices.

Keep improving your proposal, and good luck with your submissions!

You can find me on LinkedIn and Twitter.