---
title: "How to Introduce a Speaker: B2B Conference Scripts"
description: "How to introduce a speaker at a B2B conference: a four-beat structure, six scripts by speaker type, a worksheet for speakers, timing and the handoff."
canonical: "https://attendir.com/blog/how-to-introduce-a-speaker"
lang: "en"
updated: "Nov 6, 2026"
author: "Attendir Team"
category: "Templates"
---

# How to Introduce a Speaker: B2B Conference Scripts

To introduce a speaker, tell the room why the topic matters to them, give one specific reason this person is the one to hear on it, say what attendees will leave with, then say the speaker's name last and hand over the stage. Keep it short, confirm pronunciation and the current title beforehand, and never preview the talk.

Much of the introduction advice online is written for a lecture hall or a club meeting. A B2B conference adds problems those guides skip: a customer speaker whose employer approved one exact title, a sponsor slot that needs disclosing without sounding like an ad, an analyst whose independence matters more than their resume, and a speaker who changed jobs the week before.

This guide covers a four-beat structure, six paste-ready scripts by speaker type, who writes the intro, a worksheet to send speakers, timing, the handoff, late changes and a mistakes-to-fix table. For the written bio the intro is built from, see our [speaker bio examples](https://attendir.com/blog/speaker-bio-examples).

## The Four-Beat Introduction: Problem, Proof, Promise, Pass

An introduction is not a shorter bio: a bio is read by someone deciding whether to attend, an introduction is heard once by people already in their seats.

| Beat | What it does | What it sounds like | Leave out |
|---|---|---|---|
| **1. Problem** | Names a problem the room already has | "If you have ever forecast renewals from a spreadsheet..." | The session title read verbatim |
| **2. Proof** | One specific reason this speaker has earned the stage | "She rebuilt that process at a bank, with regulators watching." | Degrees, awards, years of experience |
| **3. Promise** | What attendees will leave with | "She will show you the checks she runs every Monday." | A summary of the talk's conclusions |
| **4. Pass** | Title, company, name, in that order, then hand over | "She is the COO of Woodgrove Bank. Please welcome Ingrid Solano." | Anything after the name |

Two rules make it work. One proof point, not three: a single concrete thing the speaker did is easier to hear than a career summary. And the name comes last, because it is the cue for applause, for AV to switch to the speaker's slides and for the speaker to start walking. Anything you say after it talks over all three.

## Six Speaker Introduction Scripts for B2B Events

Every person, company and event below is invented; the company names come from Microsoft's fictional sample set. Swap in your speaker's details and keep only claims the speaker has approved. Pronunciation goes in brackets for the emcee, who does not read it aloud.

### 1. Opening keynote (executive)

> Every team in this room has been told to do more with the same budget this year. Our opening keynote speaker was told to do it while moving a bank's entire operations team onto new systems, with regulators watching every step. This morning she will tell you the three decisions that made it work, and the one she would make differently. She is the Chief Operating Officer of Woodgrove Bank. Please welcome Ingrid Solano [so-LAH-no].

### 2. Customer speaker at a vendor's user conference

> If you have ever had to explain to your CFO why a migration is three months late, you will want to hear this one. Our next speaker's team moved Litware's reporting onto a new platform in two phases, and he is here to walk you through each phase and what they would change. He leads the data platform team at Litware. Please welcome Rafael Lindqvist [LIND-kvist].

At your own user conference, your product is not the hero of a customer's intro. Describe the speaker's work, not "how they use our platform"; the room already assumes the connection, and leaning on it makes the session sound like a sales case study. Use the title and company wording the customer's employer approved, word for word.

### 3. Industry analyst

> Choosing procurement software usually means reading a dozen vendor claims that all sound the same. Our next speaker reads them for a living, and writes the buyer's guides for this category. She will tell you which evaluation criteria buying committees are adding this year, and which ones they are quietly dropping. She is a principal analyst at Trey Research. Please welcome Noor Achterberg [AHK-ter-berg].

For an analyst, the proof beat is coverage and independence. Do not call them "a friend of the company" or mention vendors they have advised; the room may hear a conflict of interest.

### 4. Sponsor speaker (with disclosure)

> This session comes to us from Relecloud, one of this year's gold sponsors, so you know where our next speaker works. What you may not know is that he spends his days helping finance teams get their forecasts out of spreadsheets, and today he is co-presenting with one of those teams. They will show you the data model they built together, with the customer telling you what worked. He is a solutions architect at Relecloud. Please welcome Callum Ferreira.

Disclose the sponsorship once, plainly, in the first sentence, then move to substance. A disclosure up front tends to read as honest; one buried or skipped can read as if the organizer is hiding something. Leave out taglines and product names, and check any intro the sponsor's team sends for product claims.

### 5. Panel (moderator introducing panelists)

> Our panel is answering one question: what actually changed after each of these teams consolidated their tool stack? I will introduce them in the order they will answer first.
> Hana Petrov runs marketing operations at Fabrikam, where she cut the stack down to the tools her team uses every week.
> Theo Marchetti [mar-KET-ee] leads IT procurement at Contoso, and he is the person who says no to new tools.
> And Yusra Bellamy heads revenue operations at Northwind, where she has done the consolidation twice.
> Hana, let's start with you.

One line per panelist (name, role, angle), in speaking order, ending on the first question addressed by name so the panel starts without a pause. The opening round and run sheet are in our guide on [how to moderate a panel discussion](https://attendir.com/blog/how-to-moderate-a-panel-discussion).

### 6. Host-company executive or internal speaker

> Many of you have told us, in support tickets and at the booth yesterday, that setting up approvals takes too long. Our next speaker is the person who read those tickets. He will show you what his team changed because of them, and what is coming next. He leads product for Proseware's workflow team. Please welcome Mateo Grünwald [GROON-vald].

When the speaker works for the host, take the proof beat from the audience's side, not the org chart. "The person who read those tickets" earns more attention than a title the room has seen on the agenda all morning.

## Who Writes the Introduction: Organizer or Speaker?

The organizer writes it, from facts the speaker supplies, and the speaker approves it. Speakers who send their own intro often send their bio, which sounds like a resume read aloud; keep it as source material and rewrite it into the four beats.

The emcee owns delivery, not content. Give them the approved script on a card in large type, pronunciation in brackets, with the full bio as background. A personal ad-lib ("I first met Ingrid at...") is fine before the pass, never after the name.

Customer and sponsor speakers need a second approver: the customer's comms or legal contact for the company name, title and any result, and your sponsor manager for the disclosure wording. Ask for these alongside the bio, not three days before the event.

## The Speaker Introduction Worksheet

Send this with each speaker's confirmation. It asks for what an intro needs and a bio form usually misses.

> **Subject: Your introduction at [Event name]: five minutes, reply by [date]**
>
> Hi [first name],
>
> Our emcee will introduce you before your session. Could you answer these by [date]? We will send the script back for your approval.
>
> 1. **Your name as you want it said on stage, and how to pronounce it.** A short voice memo of you saying your full name is ideal.
> 2. **Your title and company exactly as your employer has approved them.** If either might change before the event, please tell us.
> 3. **The one problem your session helps attendees with**, in a sentence.
> 4. **One specific thing you have done that relates to it**, something you built, fixed, ran or measured. Can we say it on stage? (Yes / No / Needs approval from: ___)
> 5. **What attendees will walk away with**: a framework, a checklist, a decision rule?
> 6. **Anything we should not say**: former employers, clients, results that are not public.
> 7. **Who else needs to approve this?** (Comms or legal, a co-presenter, a sponsor manager.)
> 8. **Your walk-on**: front row or side-stage? Handheld or lavalier mic? Title slide up as you walk on?
> 9. **A mobile number for event day**, in case anything changes.
>
> Thank you. We will send the final script by [date].

Questions 1, 2 and 6 prevent the worst on-stage mistakes; 3 to 5 fill the four beats; 8 and 9 belong in your [event run of show](https://attendir.com/blog/event-run-of-show-template), next to the session's AV cues.

## How Long Should a Speaker Introduction Be?

Shorter than you think. Working guidelines, not rules:

- **Breakout session:** around 30 seconds, one sentence per beat. Attendees picked this session from the agenda.
- **Keynote:** up to about a minute, rarely more. Spend the extra time on the problem beat, not on credentials.
- **Panel:** one line per panelist, plus one sentence for the panel's question.
- **Sponsor session:** as short as a breakout intro. A long one can sound like a paid placement.
- **Webinar:** short, with the name said clearly before the speaker unmutes.

Each single-speaker script above is under 100 words. Time yours by reading it aloud at stage pace with a timer, and if it runs long, cut from the proof beat first.

## The Handoff: What to Do After You Say the Name

1. **Say the name, then stop.** Start the applause yourself if the room is slow.
2. **Look at the speaker**, which points the room's attention where they are coming from.
3. **Wait at the lectern until they arrive.** Hand over the clicker or mic, then step away to the side you came from so you do not cross paths.
4. **Cue the slide on the name.** Agree the title-slide cue with AV in the run of show.
5. **Do not preview or joke about the talk.** It can take the speaker's opening line.

If the speaker is not in the room when you finish, do not stall by reading the bio. Say "We will be ready in one moment," and wait for the stage manager before introducing them again.

## When the Speaker's Title or Company Changed Last Week

The printed program may already be wrong; the introduction does not have to be.

- **Reconfirm at check-in.** Whoever greets speakers reads the title and company aloud and asks, "Is this still right?"
- **If they changed jobs, ask how they want to be introduced.** Some cannot name the new employer yet. "She led this project at Litware" is safe either way.
- **If a customer's company was acquired,** check that the approval to speak still stands with the right comms contact.
- **If it is a last-minute replacement,** say so warmly without apologizing ("we are lucky the person who ran the project could step in"), then use the four beats as normal.
- **Update everywhere the name appears**: emcee card, name slide, recording title, follow-up email.

If speakers promote their sessions through Attendir, a title change does not mean remaking anyone's card. A campaign from the Speaker Promotion template ("Speaking at") gives each speaker a branded LinkedIn card with their LinkedIn photo and name composited onto your event artwork, and nothing else on the card is per person, so the new title goes in the post copy, which the speaker can edit before posting. Our [speaker-led event promotion](https://attendir.com/blog/speaker-led-event-promotion) guide covers that wave.

## Speaker Introduction Mistakes and How to Fix Them

| Mistake | Why it hurts | Fix |
|---|---|---|
| Reading the full written bio | Sounds like a resume; the room tunes out before the name | Rewrite into the four beats; keep the bio as background |
| Mispronouncing the name | The first thing the speaker hears from the stage is an error | Voice memo in the worksheet; phonetic guide on the card |
| Name first, then more talking | Applause starts and stops; the speaker does not know when to walk | Name last, nothing after it |
| Previewing the talk | Takes the speaker's opening and any surprise in it | Promise what attendees leave with, not what the speaker says |
| Unapproved title or result | Can put a customer speaker in a difficult position with their employer | Approved wording only; reconfirm at check-in |
| Burying a sponsorship | The room finds out anyway and trusts the session less | Disclose once, in the first sentence |
| Ad-libbing about the speaker's employer | Risks saying something nobody approved | Ad-lib about the topic or the room, never the company |

## Frequently Asked Questions

### What do you say when introducing a speaker?

Name the problem the audience has, give one specific reason the speaker is the right person to address it, say what attendees will leave with, then give the speaker's title, company and name, in that order, and hand over the stage. Do not summarize the talk or add anything after the name.

### How long should a speaker introduction be?

As a working guideline, aim for around 30 seconds for a breakout and no more than about a minute for a keynote, with one line per panelist on a panel. Read the script aloud with a timer and cut credentials first if it runs long.

### How do you introduce a sponsor speaker without it sounding like an ad?

Say plainly in the first sentence that the session comes from a sponsor, then spend the rest of the introduction on the speaker's expertise and what attendees will learn. Leave out taglines and product names, and check any intro the sponsor's team supplies for product claims.

### What if a speaker's title changed right before the event?

Reconfirm every speaker's title and company at check-in, ask anyone who changed jobs how they want to be introduced, and use neutral phrasing such as "she led this project at" when they cannot name a new employer yet. For customer speakers, confirm their employer's approval still stands.

## Introduce the Speaker, Then Get Out of the Way

A good introduction is short, specific and approved: the room's problem, one piece of proof, a promise, and the name last. Collect the facts with the worksheet, script it in four beats, and the emcee only has to deliver it. If your speakers also help fill the room, see how [Attendir supports B2B conferences](https://attendir.com/use-cases/b2b-conferences).

## Related Articles

- [Event Cancellation Email: B2B Templates for Every Audience](https://attendir.com/blog/event-cancellation-email)
- [Conference Planning Checklist: A 12-Month Timeline for B2B Teams](https://attendir.com/blog/conference-planning-checklist)
- [Know Before You Go Email: B2B Templates and Send Timing](https://attendir.com/blog/know-before-you-go-email)