Skip to main content

Speaker Bio Template

Four speaker writing templates: the 50-word version, the 100-word version, the 200-word version, and the host introduction script. Save all four in one document.

50-word version (printed program)

[NAME] is [ONE-LINE IDENTITY]. [CREDIBILITY: ONE OR TWO SPECIFIC FACTS, NAMED ENTITIES.] [DIFFERENTIATOR: ONE LINE ABOUT THEIR ANGLE OR WHAT THEY'RE KNOWN FOR.]

Example:

Jane Doe is a product designer focused on onboarding flows for B2B SaaS companies. She has worked with forty-plus product teams — including HelloSign and Pendo — to reduce churn and lift activation. She writes about clarity over polish at examplestudio.com.

100-word version (session page)

[NAME] is [IDENTITY AND CURRENT WORK]. Over the [TIME PERIOD] [she/he/they] [SPECIFIC VERB] with [NUMBER]+ [TYPE OF ORGANIZATIONS] — including [TWO TO THREE NAMED EXAMPLES] — to [SPECIFIC OUTCOME], with [SPECIFIC METRIC RANGE]. [NAME]'s talks focus on [TALK SUBJECT AND ANGLE]. [She/He/They] [has/have] spoken at [TWO NAMED EVENTS] and [PUBLISHED IN / WRITES AT] [PUBLICATION OR PERSONAL SITE]. [NAME] lives in [CITY].

Example:

Jane Doe is the founder of Example Studio, a design partner for B2B SaaS companies. Over the last decade she has worked with forty-plus product teams — including HelloSign, Pendo, and Hex — to reduce churn and lift activation, with documented improvements between 8% and 34%. Jane's talks focus on the place where onboarding, copywriting, and product strategy meet — and why most "design problems" are actually writing problems. She has spoken at SaaStr and Lenny's Live, and writes occasional notes for founders at examplestudio.com. Jane lives in Austin, Texas.

200-word version (speaker microsite)

Use the 100-word version as the spine. Add a paragraph break and 100 more words of context — prior talks, a deeper take on the topic, or what they're currently working on.

Host introduction script (spoken word)

Our next speaker has spent [TIME PERIOD] working on [SPECIFIC PROBLEM]. [She/He/They] [RUNS / WORKS AT / LEADS] [COMPANY OR ROLE], where [SPECIFIC TRACTION]. [She/He/They] has [SPECIFIC CREDIBILITY: TWO NAMED EVENTS OR PUBLICATIONS]. And [she/he/they] has a [STRONG / UNPOPULAR / CONTRARIAN] opinion that [SPECIFIC POINT OF VIEW]. [She/He/They] is going to make that case in the next [TALK LENGTH]. Please welcome [NAME].

Example:

Our next speaker has spent the last ten years working on a single problem: why well-built features fail to convert. She runs Example Studio in Austin, a design partner for B2B SaaS teams. She's worked with forty-plus product teams — including HelloSign and Pendo — and she has a strong, unpopular opinion that most onboarding problems are writing problems, not design problems. She's going to make that case in the next twenty minutes. Please welcome Jane Doe.

Common mistakes

  1. One bio for every venue. Different lengths exist for a reason. Send the right one.
  2. Listing every conference. Two named events is enough. A long list looks like a CV.
  3. Forgetting the host script. Hosts will write something. Make sure it's what you want.
  4. Reading the bio onstage. Host introductions should be written for spoken word — short sentences, no semicolons, a clear ending.

Or auto-fill them

Biography.co's Speaker Bio Generator writes all four versions at once from your topic areas, credentials, past talks, and media features.

Want it auto-filled?

The matching generator turns your notes into a draft using this exact structure.

Open the generator