---
title: "Call for Speakers: How to Run a CFP for a B2B Conference"
description: "How to run a call for speakers for a B2B conference: CFP page copy, application form fields, a scoring rubric, a timeline and acceptance emails."
canonical: "https://attendir.com/blog/call-for-speakers"
lang: "en"
updated: "Oct 8, 2026"
---

# Call for Speakers: How to Run a CFP for a B2B Conference

To run a call for speakers for a B2B conference, decide the program you need first, then publish a CFP page that names the audience, the topics and what you will not accept, collect submissions through a short application form, score them against a written rubric, and give accepted speakers a promotion kit on acceptance day.

A B2B call for speakers can fail quietly. The page goes up, submissions arrive, and the committee finds a pile of thinly disguised product demos from vendors who want stage time in front of your customers. The practitioners you wanted, the customer who rebuilt their onboarding or the partner who ran a large migration, never applied, because nothing on the page said their story was the point.

This guide covers planning the call, paste-ready CFP page copy and application form fields, a scoring rubric with explicit criteria, a week-by-week timeline, acceptance and rejection emails, and the handoff that turns accepted speakers into your first promotion wave.

## Why a B2B CFP Is a Marketing Asset, Not Just an Agenda Tool

An academic call for papers fills a program with peer-reviewed work. A B2B call for speakers has two more jobs, and both belong to marketing.

**It is a customer-story intake.** Every customer submission is a documented use case with a named owner who wants to talk about it publicly. Declined ones are still leads for case studies, webinars and reference calls, so agree with your [customer advocacy program](https://attendir.com/blog/customer-advocacy-marketing) owner, before the CFP opens, who follows up on what.

**It is the first promotion wave.** Accepted speakers announce their sessions to networks full of their peers, which for a user conference means people who look like your customers, with a credibility no brand post has. Design for that and you collect what promotion needs (LinkedIn URL, headshot, a one-line hook) at submission time instead of chasing it later.

## Before You Open the Call

Settle four things with your program committee first.

1. **The program shape.** How many sessions does the open call fill? Keynotes, sponsor sessions and roadmap talks are filled by invitation or contract, so the CFP might cover, say, 12 of 30 sessions.
2. **The tracks and the audience.** Name the tracks and describe the attendee in each. "Ops leaders at companies with 200 to 2,000 employees" is a brief a submitter can write to. "Innovation" is not.
3. **The vendor and sponsor policy.** A rule we recommend: partners and vendors may submit only with a customer co-presenter, and paid sponsor sessions run in their own clearly labeled slots outside the CFP.
4. **The review committee.** Three to five reviewers, at least one of whom is a customer or community member rather than an employee. Everyone scores independently against the same rubric before any discussion.

## The CFP Page: Copy Template

Replace the bracketed placeholders. Keep the "What we will not accept" section: it is the clearest signal to vendors that a pitch will not get through.

> **Call for Speakers: [Event Name] [Year]**
>
> [Event Name] brings together [number] [audience description, e.g. "operations and RevOps leaders"] in [city / virtual] on [date]. We are looking for practitioners who have done the work and can show the room how.
>
> **Who should apply.** Customers, partners and practitioners who have run a project, changed a process or solved a problem our attendees are facing. You do not need to be an experienced speaker. We pair every first-time speaker with a coach.
>
> **Topics we want this year.**
> - [Track 1]: [two or three example questions a session would answer]
> - [Track 2]: [examples]
> - [Track 3]: [examples]
>
> **Session formats.** [30-minute talk / 45-minute panel / 20-minute lightning talk / hands-on workshop].
>
> **What we will not accept.** Product demos or sales pitches. Talks whose main takeaway is "buy our product." Vendor and partner submissions without a customer co-presenter. Sessions already delivered at another event in the last [12] months, unless substantially updated.
>
> **What speakers get.** A full conference pass, [travel support / hotel nights, if offered], a speaker coach, professional recording of your session, and a personalized promotion kit to share your session with your network.
>
> **Key dates.** Submissions close [date]. Decisions by [date]. Slides due [date].
>
> **How we review.** Every submission is scored by [number] reviewers, including at least one customer, against published criteria: practitioner evidence, audience fit, specificity of the takeaway, originality and format fit.
>
> [Submit your session]

Publishing the criteria tells a practitioner that specificity wins and a vendor that a pitch will be scored down.

## The Speaker Application Form: Field List

Every field below feeds either the review or promotion; cut anything that does neither.

| Field | Required | Used for |
|---|---|---|
| Full name, job title, company | Yes | Review, agenda listing |
| Work email | Yes | Communication |
| Relationship to us (customer, partner, community member, employee, other) | Yes | Vendor policy, track balancing |
| Session title (under 80 characters) | Yes | Review, agenda |
| Session abstract (150 to 250 words) | Yes | Review, agenda |
| "What will attendees be able to do after your session?" (up to 3 bullets) | Yes | Rubric: specificity |
| "What did you actually do, and what changed?" (100 words) | Yes | Rubric: practitioner evidence |
| Track and format preference | Yes | Program building |
| Co-presenter name and company | Required for vendors and partners | Vendor policy |
| Has this talk been given before? Where? | Yes | Rubric: originality |
| LinkedIn profile URL | Yes | Promotion handoff |
| Headshot upload | Optional at submission, required on acceptance | Agenda, share assets |
| One-line hook: "Why should someone come to your session?" (under 25 words) | Yes | Promotion copy |
| Permission to name your company publicly | Yes | Agenda, promotion |
| Willing to share your session with your network if accepted? | Yes | Tiebreaker, promotion planning |
| Approval needed from your employer to speak? | Yes | Risk of late dropouts |

"What did you actually do, and what changed?" separates practitioners from people with opinions. The one-line hook becomes the first draft of every promotional post, in the speaker's own voice. And ask about employer approval explicitly: a customer speaker who needs legal or comms sign-off to name their company is a late-withdrawal risk, and you want to know that before you build the agenda around them.

Dedicated CFP tools such as Sessionize exist for intake and review; a form builder plus a shared spreadsheet also works for a few dozen submissions.

## The Scoring Rubric

Each reviewer scores every submission 1 to 5 per criterion before the committee meets; the weighted total ranks the pool.

| Criterion | Weight | 5 looks like | 1 looks like |
|---|---|---|---|
| **Practitioner evidence** | 30% | Submitter led the work; describes a concrete before and after | Opinion or trend commentary with no first-hand project |
| **Audience fit** | 25% | Solves a problem the named track audience has this year | Interesting, but for a different audience |
| **Specific takeaway** | 20% | Attendees leave with a method, template or decision they can reuse | "Lessons learned" or "the future of X" |
| **Originality** | 15% | Not available elsewhere; new data, new approach, or an unusual context | Talk already on YouTube from another event |
| **Pitch risk (reverse scored)** | 10% | No product the speaker sells is central to the story | The session is a product walkthrough |

Then apply three rules the scores miss:

- **Hard disqualifiers.** A vendor submission without a customer co-presenter, or a talk whose takeaway is a purchase, is out regardless of score.
- **Program balance.** After ranking, adjust for track coverage, company size, industry and speaker diversity, and record the reason for every adjustment.
- **Promotion willingness as a tiebreaker only.** When two submissions score within a point, the speaker who agreed to share the session can take the slot. Never score follower count; a practitioner with a small, relevant network can matter more than a well-known commentator.

Route good submissions that miss the cut instead of just declining them: a strong customer story that fits no track is a case study, webinar or panel candidate. Agree the routing with customer marketing before decisions go out, so the rejection email can offer something real.

## The CFP Timeline (Weeks Before the Event)

Recommended windows for an in-person B2B conference with a four-to-six-month runway; compress for smaller events.

| Week (before event) | Milestone |
|---|---|
| T-26 to T-24 | Committee agrees program shape, tracks, vendor policy, rubric |
| T-24 | CFP page live; announce to customers, partners, community and past speakers |
| T-22 to T-17 | Personal outreach: CS and account teams invite customers with strong stories to submit; one reminder push |
| T-16 | Submissions close |
| T-16 to T-14 | Independent scoring, then one committee meeting |
| T-13 | Acceptance emails (with a confirm-by date); waitlist held |
| T-12 | Rejection emails with routing offers; agenda published |
| T-12 to T-10 | Speaker promotion kit delivered; speakers announce their sessions |
| T-6 | Draft slides and first coaching session |
| T-3 | Final slides due; tech check scheduled |
| T-0 | Event; on-site speaker photos and session recordings captured |

Two rows matter more than they look. The personal outreach window is where you recruit the customers who would not have applied on their own: a practitioner often does not see their own project as conference material until someone who knows it says so. And acceptances go out before the agenda is public, so every speaker is confirmed and ready to share when sessions are announced.

## Acceptance Email Template

**Subject:** You're speaking at [Event Name]: please confirm by [date]

> Hi [First name],
>
> Congratulations: the committee has accepted "[Session title]" for the [Track] track at [Event Name] on [date] in [city].
>
> Reviewers singled out [one specific thing from their submission, e.g. "the before-and-after numbers from your onboarding rebuild"]. That is exactly what our attendees came for.
>
> **Please confirm by [date]** by replying to this email. If you need employer approval to speak or to name [Company] publicly, let us know now and we will help with whatever your team needs.
>
> What happens next:
> - [Date]: we publish the agenda and send your speaker promotion kit, including a personalized share card and suggested posts.
> - [Date]: first coaching session and draft slides.
> - [Date]: final slides due.
>
> [Name], [Event Name] program team

## Rejection Email Template

**Subject:** Your [Event Name] submission

> Hi [First name],
>
> Thank you for submitting "[Session title]" to [Event Name]. We received [number] submissions for [number] open slots, and yours was not selected for this year's agenda.
>
> [Choose one routing line:]
> - We would love to feature your story in a different format: [a customer webinar / a case study / our customer panel]. Could we set up 20 minutes to talk about it?
> - We have placed your session on our waitlist. If a slot opens before [date], we will contact you first.
> - The committee's main feedback was [one specific, constructive sentence]. We hope you will submit again next year.
>
> Either way, we hope to see you there. [Here is a speaker-applicant discount code / Registration is open here]: [link].
>
> [Name], [Event Name] program team

Never send rejections before acceptances are confirmed, or you lose the waitlist you may need.

## The Handoff: From Accepted Speaker to Promoter

A speaker who has just confirmed is ready to talk about the session, so the promotion kit should arrive with the agenda, not a month later. It needs the session title and time, the speaker's hook turned into two or three suggested posts, a personalized share image, and a link that shows whose post drove which visits. The [speaker-led event promotion](https://attendir.com/blog/speaker-led-event-promotion) guide covers the post copy and the reminder sequence in detail.

This is the step Attendir does. You create a campaign under the event from the Speaker Promotion template, which sets the Audience label to "Speakers" and the Landing Page Label to "Speaking at," then paste the accepted speakers' emails to invite them in bulk. On the campaign's share page, each speaker signs in with LinkedIn, gets a card with their LinkedIn photo composited onto your event artwork, can publish the post and image to LinkedIn in one click, and gets their own tracked link; the campaign shows shares, views and clicks through to the event page per speaker. Registrations themselves are counted in your registration platform, so tag the event URL with UTMs if you want to see them by source there.

Without a tool, the same handoff works with per-speaker images in a shared folder, a copy-paste post kit and a UTM-tagged link per speaker tracked in a spreadsheet. It takes longer to assemble; the principle is the same.

For how the speaker wave fits the rest of a customer conference's promotion and measurement, see the [user conference playbook](https://attendir.com/blog/user-conference-playbook).

## Frequently Asked Questions

### What is the difference between a call for speakers and a call for papers?

A call for papers usually means an academic or research conference asking for written papers that are peer reviewed. A call for speakers, common at B2B and industry conferences, asks for session proposals that a program committee reviews for audience fit and practical value. Some tech events use the terms interchangeably, so state exactly what you want submitted.

### How long should a call for speakers stay open?

For a conference with a four-to-six-month runway, we recommend about eight weeks, from week 24 to week 16 before the event in the timeline above. That leaves room for personal outreach to customers mid-window, which is how you reach practitioners who were not planning to apply, and for scoring before the agenda is published.

### How do you stop vendors from pitching in a call for speakers?

Say it on the page, enforce it in the form and score it in the rubric: a "What we will not accept" section ruling out demos and pitches, a required customer co-presenter for vendor and partner submissions, and a reverse-scored pitch-risk criterion. Keep paid sponsor sessions in their own labeled slots outside the CFP, so vendors have a legitimate route to the stage.

### Should you pay speakers who answer a call for speakers?

A speaking fee for practitioner speakers is not required, but we recommend covering the cost of being there: a full conference pass, plus travel and hotel for non-local speakers where the budget allows. State whatever you offer on the CFP page before anyone applies. Invited keynote fees are a separate negotiation outside the open call.

## Run the Call So the Promotion Starts on Acceptance Day

A call for speakers written for practitioners, scored against published criteria and built to collect promotion details at submission gives you an agenda customers want to attend and credible speakers ready to tell their networks about it. If you are running that speaker wave for a B2B conference, see how [Attendir supports B2B conferences](https://attendir.com/use-cases/b2b-conferences) with per-speaker share pages and tracked links.