Podcast Show Notes Writer: Timestamps, SEO Blurb, and Guest Bio

Prompt

Act as a podcast producer writing show notes a listener will actually use, and a searcher will find. You are not a recap bot. You are a table of contents with a reason to click.

Inputs:
- Show name and positioning: [Show]
- Episode title working: [Title]
- Runtime: [Runtime]
- Hosts: [Hosts]
- Guest: [Guest]
- Outline or transcript crumbs: [Notes]
- Timestamp sources: [Timestamps or "estimate from outline"]
- Links and sponsors: [Links]
- Audience: [Audience]
- SEO phrases they would search: [Keywords]
- Claims I can stand behind: [Proof]
- Tone: [Tone]

Generate:
1. Title stack:
   - Episode title (under 70 characters, specific, no "INSANE").
   - YouTube/podcast app subtitle (under 100 characters).
   - Filename-safe slug.
2. SEO blurb (80-120 words): What the episode is, who it is for, 2-3 Keywords used as sentences, no spoiler dump of every joke. One sentence on the guest's relevant proof from Inputs only.
3. Full show notes:
   - 1-paragraph hook.
   - Bullet takeaways (5-7), each a complete thought a skimmer can steal.
   - Timestamped outline. If Timestamps were not given, label them as estimated from the outline and use mm:ss. Do not fake precision.
   - Pull quotes (3) that appear in Notes. If a quote is not in Notes, skip it. Do not invent dialogue.
   - Guest bio (60-90 words) from Guest only. No padded resume.
   - Chapters list matching timestamps.
4. Resource list: Links from Inputs, labeled. If a sponsor is present, a 2-sentence read that does not sound like the host sold a kidney. If no link, say so.
5. Platform cuts:
   - Apple/Spotify description (first 400 characters must work alone).
   - YouTube description (timestamps on their own lines, links at top after the blurb).
   - Newsletter blurb (80 words) plus a 5-word subject line.
6. Social clip list: 3 moments to cut, with estimated timestamp, why it works as a clip, on-screen title under 6 words.
7. Accuracy pass: List any claim in your notes that is not in Proof or Notes. Cut or hedge it.

Constraints:
- Do not invent quotes, timestamps you present as exact, sponsors, or guest credits.
- If Notes are thin, write a shorter outline and list 5 questions the producer should timestamp on the next pass.
- No "in this episode we sit down with." Ban "thought leader," "journey," "humbled."
- Keywords appear where a human would say them, not as a tag cloud.
- Honor Tone.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Examples

Example Input

Show name and positioning: Batch Notes, a 30-40 min show for ops leads at 20-200 person companies who hate tool sprawl
Episode title working: We cut 4 tools and kept Slack, with Maya Chen
Runtime: 34:20
Hosts: Priya (ops, host)
Guest: Maya Chen, Director of Ops at Northline (58-person B2B services), previously ran tooling at a 120-person shop
Outline or transcript crumbs: 00:00 cold open: Maya's team had 11 tools for work chat, docs, tasks, time, and "AI notes." 01:10 intros. 04:00 the 11-tool list (Slack, Notion, Asana, Harvest, Loom, Otter, Drive, a wiki nobody opened, two AI summarizers, email, a custom intake form). 09:30 the cut rule: if two tools store the same source of truth, one dies. 14:10 they kept Slack + Notion + Harvest. Cut Asana (tasks moved into Notion DBs), Otter and one AI summarizer (people did not read the summaries), the wiki. 19:40 migration: 3 weeks, office hours not a memo. 24:00 what broke: Harvest-Notion time entries got messy for 10 days. 28:20 what they will not cut next: Slack, because clients live there. 32:00 listener question they pre-answered: "what about Jira" - they are not a software org. 33:30 outro.
Timestamp sources: from the outline above, treat as real
Links and sponsors: none this week; archive is batchnotes.example/listen
Audience: ops leads, chiefs of staff
SEO phrases they would search: cut SaaS tools, ops stack, replace Asana with Notion, tool sprawl
Claims I can stand behind: 11 tools down to Slack, Notion, Harvest plus email and Drive still in use; 3-week migration; 58-person company; 10 days of messy time entries. Do not invent cost savings.
Tone: dry, specific, no hustle

Example Output

1. Title stack
- Episode: Cut 4 tools, kept Slack: Maya Chen on a 58-person ops stack
- Subtitle: 11 tools down. Asana, Otter, a wiki, and an extra AI notes app gone.
- Slug: cut-four-tools-kept-slack-maya-chen

2. SEO blurb
Ops leads drowning in tool sprawl: Maya Chen (Director of Ops, 58-person Northline) walks through cutting four apps from an 11-tool stack. She kept Slack, Notion, and Harvest, moved tasks out of Asana, and killed a wiki nobody opened plus an extra AI summarizer. A 3-week migration, office hours instead of a memo, and 10 days of messy time entries. For chiefs of staff who want a cut rule, not a new vendor list.

3. Full show notes
Hook: Maya's company was paying for 11 ways to talk about work. She did not "optimize the stack." She wrote a rule: if two tools store the same source of truth, one dies. Four tools left. Slack stayed because clients live there.

Takeaways:
- Count tools by source of truth, not by logo.
- Asana died because tasks already had a home in Notion databases.
- AI meeting notes died because nobody read them, not because AI is bad.
- Migrate with office hours for 3 weeks, not a PDF.
- Expect a messy overlap window (their Harvest-Notion time entries: 10 days).
- Do not copy this into Jira-land; they are not a software org.
- Slack survived as the client surface, not as a religion.

Timestamps:
00:00 Cold open: 11 tools, including two AI summarizers
01:10 Intros
04:00 The 11-tool list
09:30 Cut rule: one source of truth
14:10 What stayed (Slack, Notion, Harvest) and what went
19:40 Three-week migration, office hours
24:00 What broke: time entries for 10 days
28:20 Why Slack is not on the cut list
32:00 "What about Jira?" They are not that company
33:30 Outro

Pull quotes:
- "If two tools store the same source of truth, one dies."
- Cold open frame: 11 tools for chat, docs, tasks, time, and AI notes.
- Slack stays "because clients live there."
(No invented dialogue.)

Guest bio: Maya Chen is Director of Ops at Northline, a 58-person B2B services company. She previously ran tooling at a 120-person shop. On this episode she talks through a stack cut: 11 tools down, with Slack, Notion, and Harvest kept.

Chapters: match the timestamp list above.

4. Resource list
No sponsor this week. Archive: batchnotes.example/listen. No other links in Inputs.

5. Platform cuts
Apple/Spotify (first 400 characters work alone):
Cut four tools without a new vendor. Maya Chen (ops, 58-person Northline) had 11 apps for chat, docs, tasks, time, and AI notes. Cut rule: one source of truth. Asana, Otter, a dead wiki, and an extra summarizer went. Slack, Notion, Harvest stayed. 3-week office-hours migration. 10 days of messy time entries. Not a Jira episode.

YouTube: paste the blurb, then the timestamp list on its own lines, then the archive URL.

Newsletter subject: Four tools, actually cut
Newsletter (80 words): Maya Chen cut four apps from an 11-tool ops stack at a 58-person company. The rule was boring: one source of truth. Asana lost to Notion databases. AI notes lost to "nobody read them." Slack stayed for clients. Migration was 3 weeks of office hours, plus 10 ugly days of time entries. Episode is 34 minutes. No sponsor. Link in the usual place.

6. Social clip list
- 09:30 Cut rule, on-screen: One source of truth
- 14:10 What died, on-screen: Four tools, gone
- 24:00 Messy 10 days, on-screen: The ugly overlap

7. Accuracy pass
No dollar savings (not in Proof). Email and Drive still exist; the "kept" list is Slack, Notion, Harvest as the named survivors. Jira is a listener question, not a recommendation.