01
Episode audience
Name the specific listener who should care. “B2B marketers at companies with a small content team” gives the host more direction than “business leaders.”
Podcast guest brief template
Prepare the conversation without scripting it.
A podcast guest brief is the working agreement for an interview: who the episode is for, what it should accomplish, why the guest matters, where the conversation can go, and what production needs to verify before publishing.
What belongs in the brief
Eleven decisions before the record button.
The brief should remove production ambiguity, not remove the guest's ability to surprise the host.
02
Editorial promise
State what the listener should understand or be able to do by the end. This becomes the test for every topic and question in the brief.
03
Guest relevance
Write one sentence explaining why this guest can credibly teach the subject. Use current role, direct operating experience, or a specific body of work.
04
Editorial angle
Turn the broad topic into an argument, tension, or useful question. “Why expert interviews fail when the brief becomes a script” is an angle. “Podcasting” is not.
05
Run of show
Give the conversation a rough sequence and time budget. The host should know where the episode is going without needing to read a script.
06
Anchor questions
Prepare a small set of questions that open useful territory. They are anchors, not a checklist. Leave room for follow-ups based on what the guest actually says.
07
Boundaries
Record sensitive areas, claims that require care, embargoed topics, conflicts, and anything the guest or approver has explicitly ruled out.
08
Clip targets
Identify moments worth listening for, such as a concise framework, a surprising example, a mistake, or a clear before-and-after explanation. Do not prewrite the quote.
09
Fact checks
List the names, dates, figures, product claims, regulations, or other statements that should be verified before publication.
10
Guest prep
Send the guest the audience, premise, topic areas, practical preparation, and boundaries. Keep the host’s full follow-up map internal if you want the conversation to stay responsive.
11
Listener takeaway
Finish the brief with one sentence: after listening, the audience should be able to do what? If the answer is vague, the episode is still vague.
A five-step workflow
Build the brief in the order the decisions depend on each other.
- 01
Define the listener and outcome
Write the episode audience and the practical editorial promise before choosing questions.
- 02
Establish the guest and angle
State why the guest is credible, then turn the topic into one argument, tension, or useful question.
- 03
Map the conversation
Set a timed run of show and a small group of anchor questions, leaving room for live follow-ups.
- 04
Add production guardrails
Record boundaries, clip targets, and the claims or details that require fact checking.
- 05
Prepare the guest and approval path
Send the guest-facing prep, then confirm the final listener takeaway with anyone who must approve the episode.
Reusable working document
Copy/paste podcast guest brief template
Copy this into a doc, Notion page, production ticket, or guest workflow. Delete any line your team does not need. Keep the decisions that prevent ambiguity later.
Prefer a guided version? The free builder turns the same decisions into a timed run of show, anchor questions, clip targets, fact checks, and guest prep.
Open the Podcast Guest Brief BuilderWorking template
PODCAST GUEST BRIEF Episode / working title: Show name: Guest: Guest role / credibility: 1. Episode audience Who is this episode specifically for? 2. Editorial promise After listening, the audience should understand or be able to: 3. Guest relevance Why is this guest qualified to teach or discuss this topic? 4. Editorial angle What argument, tension, or audience question will organize the conversation? 5. Topics to cover - - - 6. Boundaries What is sensitive, off-limits, embargoed, or easy to misstate? 7. Run of show 00:00-05:00 Context and stakes 05:00-15:00 Guest experience / story 15:00-30:00 Working ideas, examples, or framework 30:00-40:00 Trade-offs, mistakes, or objections 40:00-45:00 Practical takeaway and close 8. Anchor questions - - - - 9. Follow-up cues Listen for assumptions, examples, numbers, contradictions, and unfinished stories worth probing. 10. Clip targets - A concise framework or method - A specific example with a useful lesson - A clear point of view or correction to common advice 11. Fact checks before publication - Names, roles, and company references - Dates and numerical claims - Product, legal, regulatory, or research claims 12. Guest prep to send Audience: Premise: Topics: Examples worth preparing: Boundaries: Recording logistics: 13. Listener takeaway After this episode, the listener should be able to:
Worked example
B2B SaaS founder example
This example is fictional. It shows the level of specificity that makes a brief useful without pretending the conversation has already happened.
Episode audience
Heads of marketing at B2B SaaS companies where the founder is still a primary source of product and category expertise.
Editorial promise
Give the listener a way to decide which founder ideas deserve a full interview, which belong in a short update, and which should not become content at all.
Guest relevance
A SaaS founder who still participates in customer research and has had to turn repeated sales and product conversations into a sustainable content habit.
Editorial angle
The bottleneck is often not a shortage of founder ideas. It is the lack of a repeatable way to capture context without turning every interview into a scripted performance.
Run of show
0-5: the content bottleneck. 5-15: how ideas currently get lost. 15-30: a capture and triage method. 30-40: mistakes and trade-offs. 40-45: what to try next week.
Anchor questions
Where do useful ideas disappear today? What context gets lost when a marketer writes from notes? Which conversations reliably surface language customers understand? What should never be automated?
Boundaries
No unreleased roadmap details. Avoid naming customers without permission. Flag any conversion or revenue figure for verification before publication.
Clip targets
A practical triage rule, one example of an idea that looked good but failed in production, and a clear explanation of when a live interview is better than a written prompt.
Fact checks
Current company role, any customer or market examples, dates, numerical performance claims, and names of tools or frameworks mentioned.
Guest prep
Bring one example of an idea that became useful content, one that did not, and the current workflow from conversation to approved asset. No prepared answers needed.
Listener takeaway
The listener should be able to draft a simple capture workflow that preserves founder context while giving the content team a clear editorial decision.
Common brief mistakes
A brief fails when it becomes a script or a topic list.
- Writing twenty questions but never stating who the episode is for.
- Sending the host and guest identical documents even when the host needs private follow-up cues.
- Prewriting clip quotes, which encourages performance instead of listening for a real useful moment.
- Using “thought leadership” as the objective without defining what the listener should learn or do.
- Skipping boundaries and fact checks until after the edit, when corrections are slower and more expensive.
From brief to live conversation
A useful brief should make the interview easier to listen to, not easier to rehearse.
Mato’s AI host interviews a real human guest live, listens to the conversation, and asks follow-up questions. Mato can then turn the interview into a finished podcast episode and supporting production assets.