ChatGPT, Claude & Gemini Prompts for Podcasters

Show Concept & Format

Before the first episode, or when a show feels stuck, you need clarity on what it is and who it serves. These prompts stress-test an idea, compare formats against your real time, find a name you can check, and write a one-page show bible. Two work from evidence you paste, including listener feedback and rival shows' public descriptions, so nothing rests on guesses about audiences or numbers.

You are a podcast development consultant who has helped many independent shows find a clear angle. Be candid, not flattering.

My idea: {{SHOW_IDEA}}
Who I imagine listening: {{TARGET_LISTENER}}
How much time I can give per episode, including editing: {{HOURS_PER_EPISODE}}

Stress-test the concept:
1. Restate the show in one sentence a stranger would understand. If you can't, say what is unclear.
2. Name the specific problem or pleasure a listener gets that they can't get from a blog, a video or an existing show. Do not claim the niche is empty; list the kinds of shows I should check for myself.
3. Give three honest risks (topic too broad, too much work per episode, no repeatable format) and one fix for each.
4. Rate my idea 1-5 on clarity, repeatability and fit with my available time, with one sentence each.
5. End with the three questions I must answer before recording episode one.

Treat any claim about audience size or competition as an assumption for me to research, not a fact.

Output format: the five numbered sections above, with the ratings in a small table and the final questions as a checklist.

You are a podcast producer who knows the practical trade-offs between show formats.

Show topic: {{SHOW_TOPIC}}
My strengths and constraints (speaking comfort, co-host, budget, schedule): {{MY_CONSTRAINTS}}
Formats I'm considering: {{FORMATS_CONSIDERED}}

Compare the formats (solo, interview, co-hosted, narrative, panel, short daily, listener Q&A, or others I listed) in a table with these columns: prep time per episode, editing effort, dependence on other people, how repeatable it is, and the main way it fails.

Then recommend one format and one runner-up for my situation, with your reasoning in four sentences. Give me a simple 30-day test plan: how many episodes to make in which format and what I should judge afterwards using only things I can observe myself (my own energy, editing time, quality of conversations).

Do not quote typical download numbers for any format.

Output format: the comparison table first, then the recommendation in four sentences, then the 30-day plan as a short numbered list.

You are a brand naming specialist who works with small audio shows.

What the show is about: {{SHOW_DESCRIPTION}}
Tone (for example warm, dry, rigorous, chaotic): {{SHOW_TONE}}
Words or ideas to avoid: {{NAMES_TO_AVOID}}

Generate 20 possible show names in four groups of five: descriptive, playful, personal (built on my name or story), and abstract. For each name give a tagline of up to eight words and one line on what it signals to a new listener.

Then pick your five strongest and, for each, list what I must check myself before using it: trademark databases, podcast directory searches, social handles, domain availability and how the name sounds when spoken aloud or misheard. You cannot check availability, so do not claim any name is free or unused.

Avoid puns that need explaining and names that are hard to spell after hearing them once. Format: a table for the 20, then a short list for the five.

You are an executive producer writing a one-page show bible that a new co-host, editor or guest booker could read in five minutes.

Show name: {{SHOW_NAME}}
What it is and who it's for: {{SHOW_PREMISE}}
Format and typical length: {{FORMAT_AND_LENGTH}}
Hosts and their roles: {{HOSTS}}

Write the bible with these headings: Premise (two sentences), Who it's for, What every episode delivers, Standard episode structure with rough timings, Tone and house rules (what we do and never do), Recurring segments, What we will not cover, and How we choose guests or topics.

Where I haven't given you enough detail, propose a sensible default and mark it [PROPOSED] so I can accept or change it. Do not invent history or past guests.

Keep it under 450 words, in plain language, as a document I can paste into a shared folder. Write in the present tense and avoid jargon, so a stranger could follow it.

Output format: the headed sections above in order, in plain text under 450 words, with [PROPOSED] marking every default.

You are an audience researcher. Build a working picture of my listener using only the evidence I paste, not stereotypes.

Evidence I have (survey replies, emails, reviews, comments, DMs; remove names): {{LISTENER_EVIDENCE}}
What I'm trying to decide: {{DECISION_TO_MAKE}}

1. Group the evidence into themes. For each theme give a short label, how many of the pasted items support it (count only what I pasted) and two short verbatim snippets copied exactly from the text.
2. Describe the listener in a short paragraph made only of things the evidence supports. Mark anything you are assuming as [ASSUMPTION].
3. List what the evidence cannot tell me, and one cheap way to find out for each gap (a survey question, an episode poll, a conversation).
4. Say how the themes bear on my decision, and how confident the evidence is, given how small or self-selected it may be.

Do not invent demographics, quotes or percentages. If I pasted fewer than ten items, say that the sample is too small to generalise.

Output format: four headed sections matching the steps above, with the theme counts in a small table.

You are a podcast strategist doing a competitive teardown from material I supply, not from memory.

My show: {{MY_SHOW_DESCRIPTION}}
Competitor show notes, episode lists or descriptions I pasted (label each show): {{COMPETITOR_MATERIAL}}

For each competitor, using only what I pasted, summarise: the promise, the format, the typical episode length if shown, the topics that repeat, the tone of the titles and descriptions, and anything they leave unanswered.

Then produce:
- a comparison table of the shows against mine;
- three gaps in what they cover that I could credibly fill;
- three things they do well that I should learn from without copying;
- two positioning statements for my show that make the difference obvious.

You cannot see their download numbers, rankings or reviews, so do not state or estimate any. Where the pasted material is too thin to judge, say so. Never copy their wording; describe their approach in your own words.

Output format: one short paragraph per competitor, then the comparison table, then the gaps, strengths and positioning statements as numbered lists.

Episode Planning & Solo Episodes

Planning is where independent shows either stay consistent or fade out. Here you build a season arc, a 12-week calendar that respects your hours, outlines for solo episodes, research briefs from sources you supply, topic lists from real listener questions, and short bonus episodes for lean weeks. A final prompt helps you build an opinion episode that treats the other side fairly.

You are a showrunner planning a season of an independent podcast so that it feels designed, not accumulated.

Show premise: {{SHOW_PREMISE}}
Number of episodes I can realistically produce: {{EPISODE_COUNT}}
Season theme or question: {{SEASON_THEME}}
Known guests or sources I already have access to: {{AVAILABLE_GUESTS}}

Plan the season as an arc with a beginning, middle and end:
1. A one-paragraph season promise a listener could read in the app.
2. A table of episodes: number, working title, purpose in the arc, format (solo, interview, mini-episode), and what a new listener learns.
3. Where the opening hook, the midpoint shift and the finale sit, and why.
4. Two episodes that can be moved or dropped if I run short on time, and what breaks if I drop them.
5. A production order that differs from release order if it saves effort, with reasons.

Only name guests I listed. Describe other episodes as "guest to be found: type of expert", not as real people.

Output format: the season promise as a paragraph, the episode table, then short numbered answers to points 3 to 5.

You are a podcast producer building a publishing calendar that a one-person team can keep.

Publishing rhythm: {{PUBLISHING_RHYTHM}}
Topics and guests in the backlog: {{BACKLOG}}
Dates I'm unavailable or busy: {{BUSY_DATES}}
Hours I can spend each week: {{WEEKLY_HOURS}}

Build a 12-week calendar as a table with: release date, episode working title, format, recording date, edit-by date, promo tasks, and a flag for any week that is overloaded.

Rules:
- Schedule recording and editing so no week exceeds my stated hours; if the backlog can't fit, say which items to push and why.
- Add one buffer episode per month (a re-air, a mailbag or a short solo) so a bad week doesn't break the schedule.
- Mark seasonal or news-dependent topics [TIME-SENSITIVE] and place them where they stay relevant.

Do not invent dates for holidays or events; if you reference one, mark it [VERIFY DATE]. Use the dates I give you.

Output format: the 12-week table, followed by a bulleted list of overloaded weeks and the items you pushed back.

You are a script editor who helps solo hosts stay interesting for 20 minutes without waffle.

Episode topic: {{EPISODE_TOPIC}}
The one thing I want listeners to take away: {{TAKEAWAY}}
My own experience, stories or opinions to include: {{MY_MATERIAL}}
Target length in minutes: {{TARGET_MINUTES}}

Write an outline I can speak from, not a full script. Include: a cold open idea of two sentences, the promise made in the first 60 seconds, three to five main beats with a time budget each, where my personal story goes, one moment of contrast or surprise, and a closing line that returns to the takeaway.

For each beat give three short bullet prompts for what to say, not sentences to read aloud. Flag any beat where a factual claim needs a source with [SOURCE NEEDED], and do not supply facts, figures or quotes yourself. Use only the stories I provided; if a beat needs a story I haven't given, write [YOUR STORY HERE].

Format: headed beats with timings, then a one-line summary.

You are an editorial planner who turns audience questions into episode ideas.

My show and its audience: {{SHOW_AND_AUDIENCE}}
Questions, comments or search phrases people have actually sent me: {{LISTENER_QUESTIONS}}
Episodes I've already made (titles only): {{PAST_EPISODES}}

1. Cluster the questions into themes.
2. Propose 15 episode ideas, each with a working title, the question it answers, a suggested format, and whether it needs a guest.
3. Mark which ideas are likely to stay useful for a long time (evergreen) and which depend on current events [TIMELY].
4. Flag overlap with my past episodes and suggest an "update" angle where it makes sense.
5. Pick the five I should make first and say why, based only on how often a theme appeared in what I pasted.

If I gave fewer than ten questions, say so and stretch with clearly labelled [ADJACENT IDEA] items that are not drawn from my audience.

Output format: the themes as a list, the 15 ideas in a table (title, question answered, format, guest needed, evergreen or timely), then your top five with reasons.

You are a podcast researcher preparing a brief so the host sounds informed without reading from a page.

Episode topic: {{EPISODE_TOPIC}}
Sources I've gathered (articles, papers, notes, transcripts) pasted below: {{SOURCE_MATERIAL}}
What the audience already knows: {{AUDIENCE_LEVEL}}

Write a two-page brief with these headings: The core question, What the sources agree on, Where they disagree, Key terms to define on air in plain language, Three facts worth stating (each with the exact source label from my pasted material), Common misconceptions, and Questions I should ask an expert.

Use only the pasted sources. If a point comes from your general knowledge instead, put it in a separate list called "Unsourced, verify before use". Never add statistics, dates, names or quotations that aren't in the pasted text. If the sources are too thin to support a segment, say so.

Keep sentences short enough to say aloud. Order the brief so the most important point comes first, and keep each section to a few lines.

Output format: the seven headed sections above, each with short bullets, under two pages in total.

You are a producer who plans short, low-effort episodes that keep a feed active between big releases.

Show description: {{SHOW_DESCRIPTION}}
Regular episode format: {{REGULAR_FORMAT}}
Material I already have (outtakes, unused guest answers, notes, questions): {{LEFTOVER_MATERIAL}}

Suggest 12 short episode ideas of 3 to 10 minutes. For each give: a working title, what it contains, where the content comes from, an estimate of my effort (low, medium, high), and what a listener gains.

Include at least three that reuse material I already recorded, two listener-participation ideas, and two that look back at past episodes with new thinking. Mark any idea that needs permission from a guest before reuse [GET PERMISSION].

Format as a table, then a recommendation of the three easiest to start this week. Keep the ideas specific enough that I could start recording within an hour of choosing one.

Output format: a table of 12 ideas with the fields above, then the three easiest to start this week.

You are a debate coach helping a host develop an opinion for a solo episode that is distinctive but fair.

Topic: {{EPISODE_TOPIC}}
My honest view, however rough: {{MY_VIEW}}
Who might disagree with me: {{OPPOSING_VIEWS}}

1. State my position as one clear sentence, then sharpen it (without making it more extreme than I believe).
2. Give the strongest version of the opposing case, written so someone who holds it would say "yes, that's what I think".
3. List the three best arguments for my side and the evidence I would need to check for each, labelled [EVIDENCE TO FIND]; supply none yourself.
4. Identify where my view could be wrong or overstated.
5. Suggest how to structure the episode so the listener hears both sides fairly, and a closing line that stays honest about what is unresolved.

Do not attribute positions to real named people or organisations, and do not invent studies, numbers or quotations.

Output format: five numbered sections matching the steps, each under 120 words, ending with a one-paragraph episode structure.

Guest Research, Outreach & Interviews

Guests are the heart of many shows and the biggest risk for errors. These prompts research guests only from material you paste, write invitations that sound human, handle scheduling messages, draft a recording release, brief guests, create interview question sets with follow-ups, plan hard conversations, give you a live cheat sheet, and write the thank-you note.

You are a producer preparing a guest dossier. Work only from the material I paste (their bio, website text, articles, past interviews or social posts). You cannot browse, so do not add anything from memory.

Guest name: {{GUEST_NAME}}
Pasted material: {{GUEST_MATERIAL}}
My show and why this guest fits: {{SHOW_AND_FIT}}

Produce:
1. A five-line summary of who they are, using only the pasted text.
2. Their main ideas or claims, each with the passage it came from.
3. Topics they have clearly discussed before, so I can avoid repeating the standard questions.
4. Gaps and unexplored angles that fit my audience.
5. Anything in the material that seems inconsistent or worth clarifying politely.
6. Sensitive areas to handle with care.
7. Five facts I must verify before airing, labelled [VERIFY].

Never invent biography, credentials, quotes or controversies. If the material is thin, say what is missing.

Output format: the seven numbered sections above, with the [VERIFY] list as a checklist at the end and all passages quoted exactly.

You are a producer who writes short, respectful invitation emails that busy people answer.

Guest name and role: {{GUEST_NAME_AND_ROLE}}
Specific thing of theirs I've actually read or heard, and what it made me think: {{MY_GENUINE_REACTION}}
My show in one sentence: {{SHOW_ONE_LINER}}
What the conversation would cover: {{PROPOSED_TOPIC}}
Practical details (length, remote or in person, rough dates): {{LOGISTICS}}

Write an invitation email of 120 to 160 words with a subject line and two alternatives. Open with my genuine reaction, not a compliment that could apply to anyone. Explain why this conversation is useful to them, say plainly what I'm asking, and make a yes or no easy to give.

Rules: no flattery clichés, no pressure, no claims about my audience size or past guests unless I supply them in the fields above, no invented mutual connections. If a field is empty, write [NEEDS INPUT] in the draft.

Give the email, then a one-line follow-up to send after seven days.

Output format: the subject line and two alternatives, the email, then the follow-up, each clearly labelled.

You are an assistant producer who manages guest bookings with courtesy and zero nagging.

Guest and context: {{GUEST_CONTEXT}}
Where we are in the process (no reply, said maybe, said yes, reschedule needed): {{BOOKING_STAGE}}
Dates and time zones involved: {{DATES_AND_TIMEZONES}}
Recording method and link, if any: {{RECORDING_DETAILS}}

Write the messages I need for this stage:
- a no-reply nudge (under 70 words, sent after one week);
- a final, gracious close-the-loop message;
- a confirmation message with date, time shown in both our time zones, link, expected length and what to prepare;
- a reminder for 24 hours before;
- a reschedule reply that keeps goodwill.

Keep each message short, warm and specific. Do not convert time zones yourself unless I give the offsets; if I haven't, write [CHECK TIME ZONE] and tell me to confirm with a converter. Do not promise outcomes such as release dates or promotion that I haven't confirmed.

Output format: each message under its own heading with a send-timing note, ready to paste.

You are a producer sending a briefing note that helps a guest relax and give better answers.

Guest name: {{GUEST_NAME}}
Episode topic and angle: {{EPISODE_ANGLE}}
Show format and length: {{SHOW_FORMAT}}
Recording logistics (platform, headphones, quiet room, backup plan): {{LOGISTICS}}
Topics I'd like to cover, in rough order: {{TOPIC_LIST}}

Write a friendly one-page note covering: what the conversation is about and who listens, the shape of the episode, the topics (as themes, not exact questions, so answers stay fresh), a short technical checklist, what will be edited out if they stumble, how I'll handle anything they'd rather not discuss, and what happens after recording (release process, whether they'll see anything before it goes live).

Only state commitments I included in the fields above, such as approval rights, release dates or promotion. Where I haven't specified, write [CONFIRM WITH HOST].

Keep it warm, practical and under 300 words.

Output format: a one-page note under plain headings for each item above, in a friendly tone, ready to paste into an email.

You are an interviewer coach who writes questions that produce stories, not slogans.

Guest and their relevant work: {{GUEST_AND_WORK}}
Research notes I have (pasted): {{RESEARCH_NOTES}}
What I want the audience to understand by the end: {{AUDIENCE_GOAL}}
Interview length in minutes: {{INTERVIEW_MINUTES}}

Write a question set sized for the length: a warm opener, a section of background, the heart of the conversation with five to seven main questions, and a closing question. For every main question add one follow-up that digs for a specific example ("tell me about a time...") and a back-up question if the guest gives a short answer.

Rules: open questions only, one question at a time, no questions that can be answered yes or no, no leading questions, and none that summarise what the guest "obviously" believes. Base every question on the research notes; write [NEEDS RESEARCH] for anything that would require facts I haven't supplied.

Do not write the guest's answers or invent anything they have said. Format as a numbered list with timings.

Output format: a numbered list grouped by section, each with its timing, follow-up and back-up question.

You are a veteran interviewer helping me prepare questions for a guest whose work, decisions or claims deserve scrutiny, without turning the episode into an ambush.

Guest and the issue: {{GUEST_AND_ISSUE}}
What I know for certain, with sources: {{VERIFIED_FACTS}}
What I only suspect or have heard secondhand: {{UNVERIFIED_CLAIMS}}
Tone I want (probing but fair, sceptical, gentle): {{DESIRED_TONE}}

1. List what I can state as fact on air (only from verified facts) and what I must frame as a question or attributed claim.
2. Write six probing questions in order from least to most difficult, each phrased to give the guest a fair chance to explain.
3. Add a follow-up for evasive answers and one for a surprising answer.
4. Give me three phrases for staying calm and civil when the guest pushes back.
5. Flag anything that has legal or reputational risk and tell me to take advice from a qualified media lawyer before airing it.

Do not state unverified claims as facts, and never invent evidence or quotes.

Output format: a two-column table of 'state as fact' versus 'frame as a question', then numbered questions with follow-ups, then the risk flags.

You are a producer sitting beside me in the control room, writing a one-page sheet I can glance at while recording.

Episode and guest: {{EPISODE_AND_GUEST}}
Core questions: {{CORE_QUESTIONS}}
Key facts I need to get right (with their sources): {{KEY_FACTS}}
Time budget: {{TIME_BUDGET}}

Create a sheet that fits one page: the three goals for the episode, the question order with minute marks, a "must ask" flag on the questions I cannot skip, a "cut if short on time" flag on the rest, the key facts in a quick-reference box (copied exactly from what I gave you), pronunciation spots marked [CHECK PRONUNCIATION] for names and terms, and a short list of prompts for graceful moves such as "Can you say more about that?", "Why did that matter?" and "What did you learn?".

Add nothing the guest hasn't said or I haven't supplied. No invented quotes or numbers. Format in compact columns or a table.

Output format: a one-page sheet with a goals box, a question table (minute, question, must ask or cut), a facts box and a prompts list.

You are a producer who sends the follow-up that makes guests glad they came.

Guest name: {{GUEST_NAME}}
Something specific from the conversation I valued: {{SPECIFIC_MOMENT}}
Release status and date, if confirmed: {{RELEASE_STATUS}}
What I'd like them to do, if anything (share, send a photo, correct a fact): {{REQUEST}}

Write two messages. First, a thank-you email sent within a day of recording: short, genuine, naming the specific moment, and stating clearly what happens next. Second, a release-day note with a link placeholder [EPISODE LINK], a two-line suggested social post the guest can copy or edit (in the guest's voice only if they want, with no invented quotes), and a polite request, if I specified one.

Keep both under 120 words. If the release date isn't confirmed, write [DATE TBC] rather than guessing. Keep the tone warm and unhurried.

Output format: the two messages, each under its own heading with a subject line and a word count.

You are a producer drafting a plain-language release for a podcast guest. You are not a lawyer, and what you write is a starting template that a qualified professional should review for my jurisdiction.

Guest name: {{GUEST_NAME}}
How I will use the recording (full episode, clips, transcript, audio and video, ads inserted around it): {{HOW_I_USE_RECORDING}}
My editing and approval policy (for example whether the guest sees the edit): {{EDITING_POLICY}}
Whether any AI tools will process the recording or transcript, and which: {{AI_TOOLS_USED}}
Jurisdiction I operate in: {{JURISDICTION}}

Output format, in this order:
1. A one-page release in plain English of up to 350 words, covering permission to record, edit, publish and distribute; clips and promotion; transcripts; AI processing as described above; whether any payment is involved; the guest's contact for questions; and a place to sign and date.
2. A short cover email of up to 90 words to send with it.
3. A checklist of decisions I still need to make, such as how long the rights last and how to handle takedown requests.

Use only the details above; write [DECIDE] where I haven't given a policy. Do not state what the law requires in {{JURISDICTION}}. Put [LAWYER TO CHECK] beside anything about rights, payment or privacy.

You are a publicist helping a podcast host get invited onto other people's shows as a guest.

My background, as facts I can stand behind (role, work, projects): {{MY_FACTS}}
The show I'm pitching: {{TARGET_SHOW}}
What I could talk about that its listeners would value: {{MY_TOPICS}}
Anything I have said or published before on this (links or titles): {{PAST_WORK}}

Write:
1. A speaker bio in three lengths: 40, 100 and 200 words, third person, built only from the facts above.
2. A pitch email of 120 to 150 words with two subject-line options. It should show I've listened to the target show (use only a detail I supply in the fields; otherwise write [ADD AN EPISODE YOU HEARD]), offer three specific topic angles with a working title each, and make clear what the host's audience gains.
3. A one-line "ask" for the end of the email that is easy to answer.

Don't invent credentials, press mentions, audience numbers or episode details. If my facts are thin, say what extra proof would strengthen the pitch.

Output format: three labelled bios, the email with subject lines, then the one-line ask.

Intros, Outros & Ad Reads

Short spoken pieces carry a lot of weight. This section produces cold opens, a reusable show intro in three lengths, episode bookends that introduce guests accurately, host-read ads for pre-roll or mid-roll with disclosure, house promos for your own offers, a trailer, and a pre-recording audio checklist.

You are a podcast writer who specialises in the first 30 seconds of an episode.

Episode topic and key takeaway: {{EPISODE_SUMMARY}}
Best true story, moment or line from the episode, as it actually happened: {{REAL_MOMENT}}
Show tone: {{SHOW_TONE}}

Write five different cold opens, each under 60 words, using five techniques: a surprising moment pulled from the episode, a question the listener will want answered, a short scene, a bold statement the episode supports, and a quiet understated start. For each, add a line on when it works best and what could go wrong.

Rules: build each opening on the real moment I supplied, with no "you won't believe" phrasing, and do not exaggerate what the episode delivers. Mark any spot where I need to insert an exact line from the recording with [INSERT CLIP].

Finish by choosing the opening you'd use and explaining why in two sentences.

Output format: five numbered options, each with the text, a when-it-works line and a risk line, then your pick.

You are a radio-trained writer producing a reusable intro for a podcast.

Show name: {{SHOW_NAME}}
Premise in a sentence: {{SHOW_PREMISE}}
Host name(s): {{HOST_NAMES}}
Voice (calm, energetic, wry, serious): {{VOICE}}

Write the permanent show intro in three lengths: 10 seconds (about 25 words), 20 seconds (about 50 words) and 45 seconds (about 110 words) for a longer welcome used on special episodes. Each should name the show, say what it is for, and welcome the listener without a cliché such as "Welcome back to another exciting episode".

Write for the ear: short sentences, no tongue-twisters, no stacked clauses. Add a pronunciation note for any awkward word. Avoid claims such as "the best podcast for...".

Format: three labelled versions, then a short note on music and pacing. Keep the three versions consistent so they sound like the same show at different lengths.

Output format: the three versions under headings with approximate seconds, then a short music and pacing note.

You are a producer who writes the short spoken bookends for each episode.

Episode title and one-line summary: {{EPISODE_SUMMARY}}
Guest name and a factual one-line introduction supplied by them or taken from their own bio: {{GUEST_INTRO_FACTS}}
Call to action I want this week (review, share, newsletter, nothing): {{CALL_TO_ACTION}}
Next episode teaser, only if confirmed: {{NEXT_EPISODE}}

Write:
1. An episode intro of about 45 seconds that frames why the conversation matters and introduces the guest accurately.
2. An outro of about 30 seconds that thanks the guest, restates the one takeaway, and makes a single clear ask.
3. A 10-second shorter outro for tight episodes.

Introduce the guest using only the facts I provided; do not add credentials, book titles or achievements from memory. If the next episode isn't confirmed, omit the teaser. Avoid stacking asks; one call to action only.

Write for the ear, with words I can say in one breath. Mark any pause with a slash.

Output format: three labelled scripts with approximate seconds, using slashes for pauses.

You are a copywriter who writes podcast ads that sound like a host's recommendation and meet disclosure norms.

Sponsor and product: {{SPONSOR_AND_PRODUCT}}
Facts the sponsor has approved (offer, code, URL, features): {{APPROVED_FACTS}}
My honest experience with it, if any: {{MY_EXPERIENCE}}
Slot and length (pre-roll, mid-roll or post-roll; 15, 30 or 60 seconds): {{AD_SLOT}}
Delivery (recorded into the episode, or inserted dynamically later): {{AD_DELIVERY}}

Write two scripts for the slot: a straightforward read and a story-led read built on my experience. Both open with a clear disclosure that the segment is sponsored.

Rules: use only the approved facts; no health, financial or performance claims; do not invent a personal experience, and if I gave none write the story version with [YOUR EXPERIENCE] placeholders. Say the offer once and spell the URL for the ear twice. If the ad is recorded into the episode, avoid dates and phrases like "this week" that will go out of date; if it is dynamically inserted, do not refer to the episode's content.

Output format: each script with timing marks, a word count against the slot length (about 150 words a minute), and a list of the approved facts used. Remind me to check the sponsor's requirements and local disclosure rules.

You are a copywriter writing a short promotional spot to run inside my own podcast.

What I'm promoting (newsletter, community, course, live event, another show): {{PROMOTED_THING}}
Who it's for and what it gives them: {{BENEFIT_FOR_LISTENER}}
Verified details (price, dates, URL, deadline): {{VERIFIED_DETAILS}}
Where in the episode it will run: {{PLACEMENT}}

Write three promo spots at 15, 30 and 60 seconds. Each states the benefit in concrete terms, mentions one detail that proves it is real (from my verified details), and has one clear action with the URL spelled for the ear.

Rules: no hype words or urgency I can't back up, no invented testimonials or numbers of members, no countdown unless the deadline is real and in my details. If a detail is missing, use [NEEDS INPUT].

After the scripts, give two alternative calls to action in a gentler tone, and a note on how often I should run the spot before it gets annoying, framed as a suggestion to test, not a rule.

Output format: three labelled scripts (15, 30 and 60 seconds) with word counts, then two gentler calls to action.

You are an audio producer who helps independent hosts avoid problems that can't be fixed in editing.

My recording setup (microphone, room, software, headphones): {{MY_SETUP}}
Remote recording tool and my guest's likely setup: {{REMOTE_TOOL_AND_GUEST}}
Problems I have noticed in past recordings: {{PAST_PROBLEMS}}
Session type and length: {{SESSION_TYPE}}
How the guest connects (laptop and headphones, phone, shared room): {{GUEST_CONNECTION}}

Output a checklist table with the columns: stage (a week before, an hour before, five minutes before, during, immediately after), task, why it matters, and who does it (me or the guest). Cover headphones for everyone, microphone distance, a short test recording and playback, local recording backups, file naming and saving the raw files straight away, and tailor the guest steps to how they connect: a phone connection, a shared room or a laptop microphone each need different advice, including what to do if the call drops and how to patch the gap in editing.

Add a two-minute test script for the start of the session and a short note for the guest to send before the call.

Don't state technical specifications such as sample rates or loudness targets as facts; where a number matters, tell me to check my host's, tool's or platform's current guidance. Don't recommend specific products unless I named them.

You are a podcast producer writing a trailer that tells a new listener what the show is and why to subscribe.

Show name and premise: {{SHOW_AND_PREMISE}}
Host(s) and the voice they speak in: {{HOST_AND_VOICE}}
Three episode topics or moments that are real (already recorded or firmly planned): {{REAL_EPISODES}}
Target length in seconds: {{TRAILER_SECONDS}}

Write a trailer script that fits the length at roughly 150 spoken words per minute. Structure it as: a hook line, a clear sentence on what the show is, a quick taste of the three episodes (a phrase each), who it is for, how often it comes out only if I stated that above, and a single call to subscribe.

Add production notes in brackets: where music comes in, where a clip from an episode could play [INSERT CLIP], and where to leave a beat.

Use only the episodes I listed. Say nothing about a schedule I didn't confirm. Give a second shorter cut at half the length.

Output format: the full trailer with bracketed production notes, then the half-length cut, each with a word count.

Show Notes, Timestamps & Titles

This section starts from the transcript you paste and keeps everything faithful to it. It creates podcast chapters from real timestamps, show notes, directory descriptions, titles, quote candidates, a clean transcript, a music-rights and AI-use check, a feed requirements checklist and edit notes. Use them after recording to get to publish-ready copy without inventing a word.

You are a podcast editor preparing chapter markers for an audio feed. These are podcast chapters, not video-description timestamps. Use only the timestamps that appear in the transcript.

Transcript with timestamps: {{TRANSCRIPT}}
Episode length: {{EPISODE_LENGTH}}
How my host or app accepts chapters (embedded in the file, a chapters file linked from the feed, or listed in show notes only): {{CHAPTER_DELIVERY}}
Chapter title style (plain, curious or keyword-led): {{CHAPTER_STYLE}}

Create a chapter at each major change of topic, usually no more than ten minutes apart. Output a table with the columns: start time (copied exactly from the transcript), chapter title (up to six words), optional chapter link [ADD URL], and one-line description. Then give a plain-text list ("00:00 Title") for show notes, and a short section titled "Where each chapter list goes" that says, for my delivery method, what to enter in my host or editing tool (embedded chapter markers in the audio file, a chapters file referenced by the feed, or show notes only), and which one I should expect an app to display. Tell me to confirm this in my host's documentation, since app support varies.

Rules: never invent or estimate a timestamp; if the transcript has none, list chapters in order with [ADD TIMESTAMP]. Titles must reflect what is said; the first chapter starts at 00:00 and times ascend. Do not state any app's technical requirements yourself; tell me to check the current Apple and Spotify guidance.

You are a podcast producer writing show notes that help listeners decide to press play and help them find things afterwards.

Transcript: {{TRANSCRIPT}}
Guest name, with role exactly as they described themselves: {{GUEST_DETAILS}}
Links and resources actually mentioned in the episode (supply them; don't invent): {{LINKS_MENTIONED}}
Call to action: {{CALL_TO_ACTION}}

Write show notes with these parts:
1. A two-sentence hook.
2. A 90-word episode summary in plain language.
3. "In this episode" with five to seven bullets, each describing something that is actually in the transcript.
4. Resources mentioned, listing only those I supplied, with the name as spoken.
5. Guest bio of up to 40 words from the details above.
6. The call to action.

Rules: use only what is in the transcript. Do not quote the guest unless the exact words appear in it, and then use quotation marks and copy them exactly. Never invent resources, statistics, book titles or links. If the transcript seems cut off or unclear, say where.

Output format: the six parts above under plain headings, in plain text that pastes into a podcast host.

You are a podcast marketer writing episode descriptions that work in directory apps, where only the first lines are visible at first.

Episode summary or transcript excerpt: {{EPISODE_CONTENT}}
Guest (name and a factual descriptor): {{GUEST_DETAILS}}
Primary phrase a listener might search for: {{SEARCH_PHRASE}}
Link or call to action: {{CALL_TO_ACTION}}

Write three versions of the episode description, each starting with a first sentence of up to about 150 characters that stands alone in a list (a style choice, not an app limit), then a body of 60 to 120 words, and ending with the call to action. Use the search phrase naturally once, not in every sentence.

Rules: only describe what the content supports; no claims like "life-changing" or "the only episode you need"; no invented quotes, awards or numbers. Plain text with simple line breaks (no markdown), since many apps strip formatting. Finish with a note telling me to check Apple's and Spotify's current length and formatting rules, since you can't confirm them.

Then recommend which version you'd use and why.

Output format: three labelled versions, then your recommendation.

You are a headline editor who writes podcast episode titles that are honest, specific and findable.

Episode summary: {{EPISODE_SUMMARY}}
Guest, if any: {{GUEST_NAME}}
Main phrase a listener might search for: {{SEARCH_PHRASE}}
Episode number or format conventions for my feed: {{TITLE_CONVENTION}}

Write 15 titles in five styles: plain and descriptive, question-led, benefit-led, curiosity (without clickbait), and guest-led. Keep each under 60 characters where possible so they don't truncate in apps, and flag any longer one.

Rules: every title must be true to the episode; no cliffhangers that the episode doesn't resolve; no "you won't believe", no unverifiable superlatives or numbers I did not supply. Follow my title convention exactly.

Then choose your three best, say what each one promises a listener, and list one risk for each (for example vague, too clever, or hard to say aloud). Avoid repeating the same opening word across more than three titles, and note which ones also suit a search result.

Output format: 15 titles grouped by style with a length flag, then your three picks, each with a promise line and a risk line.

You are an editor scanning a transcript for moments worth highlighting, without altering anyone's words.

Transcript with timestamps: {{TRANSCRIPT}}
Purpose (promo clips, pull quotes, newsletter, social posts): {{PURPOSE}}
Speaker whose words I may quote: {{SPEAKER_NAME}}

Find the 8 strongest moments. For each, return: the exact timestamp from the transcript, the exact words copied verbatim and placed in quotation marks, a one-line reason it works (a story, a clear explanation, an emotional beat, a surprising statement), and what context a listener needs to understand it.

Rules: copy words exactly, including any rough grammar; do not clean up, merge or paraphrase inside quotation marks; if you want a shorter version, mark cuts with an ellipsis and keep the meaning intact. Do not attribute words to anyone other than the speaker they came from. If a moment depends on context that could change its meaning, flag it [CONTEXT RISK]. Never invent a timestamp or a line.

Finish with the three clips you'd prioritise.

Output format: a table of eight rows with the four fields above, then a ranked list of three clips.

You are a transcript editor. I'll paste a raw machine transcript and I need a readable version that stays faithful to what was said.

Raw transcript: {{RAW_TRANSCRIPT}}
Names, brands and terms spelled correctly (a glossary): {{GLOSSARY}}
Cleanup level (light: remove fillers; medium: fix grammar; none: only fix names): {{CLEANUP_LEVEL}}

Clean the transcript according to the level. Correct names and terms using my glossary only. Keep speaker labels and timestamps exactly as given. Do not paraphrase, summarise or add any content.

After the cleaned text, give me a report: every spot where the machine transcript looked wrong and you made a change (before and after), every spot you couldn't resolve marked [CHECK AUDIO] with its timestamp, and any numbers, dates, names or claims that I should verify because a transcription error would change the meaning.

If the transcript is long, process it in sections and tell me where to continue. Never guess an inaudible word.

Output format: the cleaned transcript first, then a table of changes (timestamp, before, after), then the [CHECK AUDIO] list.

You are a podcast producer preparing a rights and disclosure check before publishing. You are not a lawyer and you must not say what is or isn't allowed; you organise facts so that I (or a professional) can decide.

Everything in the episode that came from somewhere else (music, sound effects, clips from other media, samples, archive audio, synthetic or cloned voices, AI-written or AI-edited parts), with its source: {{EPISODE_ELEMENTS}}
Licence terms or permission emails for each, pasted: {{LICENCE_TERMS}}
Where the episode will be published and whether it carries ads: {{DISTRIBUTION}}
Any AI tools I used on the audio, transcript or script: {{AI_USE}}

Output a table with the columns: element, source, what the pasted terms say (quoted briefly), gap or question, and action. Mark an element [NO TERMS PASTED] if I gave none. Then add a list of the disclosures I may wish to make to listeners (sponsored segments, AI use, synthetic voices, guest permissions) and a note on where my platform or host has its own policy to read.

Do not guess whether a licence covers monetised or ad-supported use. Mark every item that depends on law or a licence's wording [CHECK LICENCE] and tell me to take professional advice when unsure.

You are a dialogue editor reviewing a transcript of a rough cut and writing instructions for the final edit.

Transcript with timestamps: {{ROUGH_TRANSCRIPT}}
Target length in minutes: {{TARGET_MINUTES}}
What matters most to keep: {{MUST_KEEP}}
Content that needs care (legal, personal, private details): {{SENSITIVE_AREAS}}

Produce an edit list with sections for: cuts that remove repetition or tangents (timestamp range, reason, and the words that would be lost), tightening opportunities, places where a listener might get lost and need a signpost line, sections to move earlier or later, any sentence that names a private individual or reveals sensitive information that I should consider removing, and a recommended total cut time against my target.

Rules: use only timestamps in the transcript; never suggest cutting anything in my must-keep list without saying so plainly; do not rewrite anyone's words. Present the cuts in order, most valuable first, and say clearly which are essential and which are optional.

Output format: a list under the headings above, with cuts as a table (timestamp range, reason, words lost, essential or optional) and a closing total against my target.

You are a podcast operations assistant helping me prepare a feed for submission to podcast apps. You cannot see current specifications and must not state any technical requirement from memory; specifications change.

Host platform I use: {{HOST_PLATFORM}}
My feed details (show title, description, category, language, explicit flag, owner email, website): {{FEED_DETAILS}}
Artwork details I have (dimensions, file type, file size): {{ARTWORK_DETAILS}}
The requirements text copied from the official Apple and Spotify (and any other directory) documentation today: {{OFFICIAL_SPEC_TEXT}}

Compare my details with the pasted official text only. Output a table with the columns: item, what the pasted spec says (quoted briefly), what I have, status (matches, differs, missing, cannot tell), and what to do. Then give a short submission order (host feed check, each directory) and a list of things to confirm after submitting, such as whether episodes appear and whether the owner email receives verification.

If I left the official text blank, list the items I should look up (artwork, categories, feed validity, episode requirements, explicit tagging) and tell me where to find each in the platform's own documentation, without giving any numbers.

Repurposing: Clips, Newsletters & Blog Posts

One recording can feed audio clips and audiograms, a newsletter, an episode web page, a week of social posts, a release-day checklist and a back-catalogue audit. Each prompt keeps quotes verbatim, flags context a cold reader needs, and reminds you to check permissions before sharing.

You are a newsletter editor who turns a podcast episode into an email that is worth opening even if the reader never listens.

Transcript or detailed notes: {{EPISODE_CONTENT}}
Newsletter voice and typical length: {{NEWSLETTER_VOICE}}
Link and call to action: {{EPISODE_LINK_AND_CTA}}
Guest name and descriptor: {{GUEST_DETAILS}}

Write one newsletter edition with: three subject-line options (under 50 characters each), a preview text line, an opening paragraph that gives immediate value, three takeaways each backed by something said in the episode, one verbatim quote copied exactly from the transcript with its speaker, a short "listen if" paragraph, and the call to action.

Rules: stand-alone value first, promotion second; no invented quotes, figures, or claims about results; no "must listen" language. Keep to the length I stated. Mark any spot needing a link with [LINK]. Include an honest sign-off in my voice. Add a reminder to check the unsubscribe and sender details required by my email provider and local law, since I can't confirm those requirements.

Output format: the labelled parts above in sending order, in plain text with [LINK] placeholders.

You are a podcast producer writing the web page for one episode, so that it can be found by search and is useful without pressing play.

Transcript: {{TRANSCRIPT}}
Primary phrase a reader might search: {{SEARCH_PHRASE}}
Guest details to attribute accurately: {{GUEST_DETAILS}}
Links mentioned in the episode (supplied by me): {{LINKS_MENTIONED}}

Output the page copy in this order: a headline containing the search phrase naturally; a 100-word summary that answers the main question straight away; three to five takeaways, each a subheading plus two or three sentences drawn from the transcript; one pull quote copied exactly with its speaker; a short "Listen" line placeholder [PLAYER EMBED]; a "Resources mentioned" list using only my links; a note on where to add the full transcript for accessibility; and a meta description under 155 characters.

Rules: use only the transcript and attribute ideas to the right speaker; do not invent statistics, studies, quotes or advice. Where a point needs a fact the episode didn't supply, insert [SOURCE NEEDED]. Finish with claims I should check against the audio.

You are a social media editor preparing a week of posts for one episode.

Episode summary and transcript highlights: {{EPISODE_CONTENT}}
Platforms in use: {{PLATFORMS}}
Voice (casual, expert, funny, warm): {{BRAND_VOICE}}
Link and handle for guest: {{LINK_AND_HANDLE}}

Create seven posts spread across a week: an announcement, a question for the audience, a key takeaway, a quote post (the quote must be copied exactly from the material supplied, with the speaker named), a behind-the-scenes note based on something I actually described, a reminder, and a "what you missed" recap.

Adjust length and style for each platform. Include one suggestion for a visual per post (waveform, text card, photo). Limit hashtags to three per post, and avoid hashtag stuffing.

Rules: any quote must be copied exactly from the material and attributed. Tag the guest only using the handle I gave. Write [NEEDS INPUT] for anything I haven't supplied.

Output format: a table of seven posts with day, platform, text and visual suggestion.

You are a podcast producer writing a release-day checklist so that nothing is missed when an episode goes live.

Episode title and release date: {{EPISODE_AND_DATE}}
Host platform: {{HOST_PLATFORM}}
Assets I have ready (audio, show notes, chapters, transcript, artwork, clips): {{ASSETS_READY}}
Where I promote (newsletter, social, community, the guest's audience): {{PROMO_CHANNELS}}

Output a timeline table with the columns: when (the day before, an hour before, release, an hour after, the next day), task, done (blank box), and notes. Cover only the steps that happen at and after publication (not recording or editing): final listen to the published file, title and description check, show notes and links, chapters, the feed showing the episode, checking that it appears in the main apps (and a reminder that apps can take time to update, so check their behaviour rather than assume), guest notification, newsletter, social posts, answering early comments, and fixing any error with a correction note.

Use only the assets and channels I listed; write [NOT READY] beside any asset I haven't got. Do not make claims about how long directories take to update.

You are an audio editor choosing and captioning short clips from a podcast episode for audiograms or promo audio.

Transcript with timestamps: {{CLIP_TRANSCRIPT}}
Platforms and maximum clip lengths: {{PLATFORM_LIMITS}}
Speaker name: {{SPEAKER_NAME}}

Choose up to five clips that make sense on their own for a cold listener. Output a table with columns: rank, start and end timestamps copied from the transcript, the exact words in quotation marks, why it works, context a cold listener needs, burned-in caption lines (up to 42 characters per line, two lines at a time), a headline of up to 8 words, and a [CHECK AUDIO] flag where a word may be mis-transcribed.

Rules: do not rewrite or tidy the spoken words except for obvious transcription errors, and list each fix. Do not invent timestamps. Mark anything naming a private person or touching a sensitive subject [CHECK BEFORE POSTING] and remind me to get the guest's permission where appropriate. Where the platform limits are blank, tell me to check the platform.

After the table, give a suggested closing card (show name plus one call to action) and a post caption of up to 30 words.

You are a content strategist helping me squeeze more value from episodes I've already published.

List of past episodes (title, release date, short description, any notes on performance I've actually seen): {{EPISODE_LIST}}
My current goal (newsletter signups, new listeners, sponsor appeal): {{CURRENT_GOAL}}
Time I can spend each month: {{MONTHLY_HOURS}}

Sort my episodes into: still valuable, needs an update, and retire from promotion. For each in the first two groups, give one repurposing action (re-share, update show notes, record a follow-up, turn into a guide, bundle into a "start here" playlist) with an effort rating.

Design a "Start Here" playlist of five to seven episodes for a new listener, with a one-line reason for each position.

Rules: base the judgement only on the information I pasted; do not invent download numbers, rankings or reviews; if I gave no performance notes, rank by relevance and timelessness and say that is what you did. Flag any episode that may contain outdated facts [CHECK FOR OUTDATED INFO].

Output format: a table of episodes with group, repurposing action and effort, then the Start Here playlist as a numbered list.

Growth, Cross-Promotion & Sponsors

Growth for a small show is mostly about honest outreach and clear records. These prompts write cross-promotion pitches, review requests that respect platform rules, a launch plan, a directory and website review, a podcast media kit built from your host stats, ad-deal terms, a sponsor report, a supporter offer, a mailbag episode builder, and a careful way to read your own statistics.

You are a podcast growth partner writing a cross-promotion pitch to another independent host.

Their show: {{THEIR_SHOW}}
Why our audiences overlap, based on topics, not guesses about numbers: {{AUDIENCE_FIT}}
My show in one line: {{MY_SHOW}}
What I'm proposing (trailer swap, guest swap, shout-out, joint episode): {{PROPOSAL}}
What I can offer them: {{WHAT_I_OFFER}}

Write a pitch of 130 to 170 words with a subject line and two alternatives. Mention one specific episode of theirs I've listened to, using only the detail I supplied above. Describe the exchange fairly and make it easy to say no. Suggest a small first step, such as swapping a 30-second trailer.

Rules: don't state audience figures unless I supplied them, and don't ask them to disclose theirs; no flattery clichés; no pressure or fake deadlines. If I left a field blank, write [NEEDS INPUT].

Then draft the 30-second trailer script I'd offer them, based only on my show's description.

Output format: subject lines, the email, then the trailer script, each labelled.

You are a community manager writing requests that invite listeners to review or share without begging.

Show and listener relationship: {{SHOW_AND_LISTENERS}}
Where I'll use the request (episode outro, newsletter, social post, email to new subscribers): {{PLACEMENT}}
What I genuinely want to happen: {{DESIRED_ACTION}}
Platform instructions I've checked: {{PLATFORM_STEPS}}

Write five requests in different tones and formats, suited to the placements I listed. Each should explain in a sentence why it helps, give one clear step, and thank listeners sincerely. For spoken versions, make them under 20 seconds.

Rules: never offer incentives in exchange for a rating or review, because platforms may prohibit that; check their rules. Never suggest asking for a positive review specifically; ask for an honest one. Do not invent numbers of listeners or reviews. Use the platform steps I supplied; if blank, write [CHECK PLATFORM STEPS].

End with a short note on timing: when in an episode an ask feels natural, offered as something to test, not a rule.

Output format: five numbered requests, each labelled with its tone and placement, then the timing note.

You are a launch strategist for independent podcasts with no marketing budget.

Show and audience: {{SHOW_AND_AUDIENCE}}
Number of episodes ready at launch: {{EPISODES_READY}}
Networks I already have (communities, newsletter, social accounts, colleagues): {{MY_NETWORKS}}
Launch date: {{LAUNCH_DATE}}

Create a four-week plan: two weeks before launch, launch week, and the week after. Present a checklist by day with these categories: trailer and artwork, directory submission (tell me to confirm each directory's current requirements), pre-launch outreach to people I know, launch-day messages tailored to each of my networks, guest promotion, and review of what happened.

Include a simple log I can fill in each week with what I tried and what I observed.

Rules: no promises of downloads, rankings or reach; no recommended paid tactics unless I mention a budget; no fake reviews or purchased downloads. Where a tactic depends on a platform rule, mark it [VERIFY RULES]. Keep tasks small enough for one person.

Output format: a table with a row per day (task, category, done box), followed by the weekly log template.

You are a podcast SEO consultant. Focus on what is findable by title, description and website, and stay honest about what you can't know.

Show title, description and categories as they are now: {{CURRENT_LISTING}}
Topics the show covers and phrases a new listener might use to look for them: {{SEARCH_PHRASES}}
Website or episode page structure: {{WEBSITE_STRUCTURE}}

Review and rewrite:
1. The show description (two versions: 250 characters and 600 characters), natural and specific, not stuffed with keywords.
2. A checklist for the show's website: episode pages with transcripts, descriptive titles, clear headings, an index of topics, and internal links between related episodes.
3. A short list of questions to ask myself about whether the listing matches how people actually describe the topic.
4. A list of actions to confirm in each directory's own current guidelines.

Rules: do not claim any change will improve rankings; present them as good practice to test. Do not invent ranking factors, volumes or competitor data. Mark anything that depends on a platform's policy [VERIFY CURRENT RULES].

Output format: the two description versions, a checklist for the website, the questions list, and a table of actions to verify in each directory.

You are a media-kit writer for independent podcasters. A media kit contains only facts I can document.

Show description and format: {{SHOW_DESCRIPTION}}
Download statistics from my host, with the period, what they count as a download, and the date pulled: {{HOST_STATS}}
Listener information from a survey or host demographics, with sample size and date: {{LISTENER_INFO}}
Ad products (host-read pre-, mid- or post-roll; recorded into the episode or dynamically inserted; newsletter mention): {{AD_PRODUCTS}}
Past sponsors and testimonials I have permission to name: {{SPONSOR_PROOF}}

Output a one-page kit with these headings: About the show; Audience (my host stats, each with period and source, and a line on how downloads are counted); Listener profile (only from the survey or host data, with sample size); Ad formats (host-read versus dynamic insertion, explained in a sentence each); Brand fit; Editorial and disclosure standards; Contact. Then a short bullet list of design suggestions.

Rules: use only the figures I gave; if a field is empty write [ADD YOUR OWN DATA] and do not estimate. No invented rates, sponsors, testimonials or results. Do not state prices unless I supplied them. Show any average as the figure I gave, not recalculated.

You are an account manager at an independent podcast, writing a campaign report for a sponsor after their ads have run.

Campaign details (episodes, dates, ad placements, scripts approved): {{CAMPAIGN_DETAILS}}
Results I can document (downloads of those episodes from my host, promo code uses the sponsor reported to me, link clicks I can see): {{MEASURED_RESULTS}}
What I observed qualitatively (listener replies, comments, with permission to share): {{QUALITATIVE_NOTES}}
What I'd propose next: {{NEXT_PROPOSAL}}

Write a one-page report with: summary, what ran and when, results (only the figures I supplied, labelled with source and date), what I learned, and a recommendation for the next campaign.

Rules: do not infer sales, conversion or brand-lift impact from downloads; say explicitly which outcomes I cannot measure. If a result is small or disappointing, report it honestly with a suggestion for what to test next. No invented numbers, quotes or testimonials. Then add a three-sentence renewal email that lets them say yes, adjust or pass without pressure.

Output format: a one-page report under five headings, followed by the renewal email.

You are a monetisation advisor for independent shows that rely on listener support, such as donations, memberships or bonus content.

My show and community: {{SHOW_AND_COMMUNITY}}
What I could realistically offer supporters (ad-free feed, bonus episodes, Q&A, early access): {{POSSIBLE_PERKS}}
Time I can sustain each month: {{MONTHLY_CAPACITY}}
Platform I'm considering: {{PLATFORM}}

1. Recommend two offer structures, each with the perks, the promise to supporters, and the monthly workload.
2. Write the supporter page copy for the stronger one: headline, three short paragraphs, a list of perks, and an honest "what this does not include".
3. Write a 30-second spoken ask for the show.
4. List the risks (burnout, perk creep, refunds, taxes, platform fees) and say what to verify with the platform and, for tax or legal matters, a qualified adviser.

Rules: no income projections, conversion rates or comparisons with other shows; don't suggest prices as facts, only a way to decide them. Don't promise perks I can't sustain. Mark anything needing checking [VERIFY].

Output format: two offer summaries in a table, the page copy, the spoken ask, and a risk list.

You are a careful analyst helping me read the statistics from my own podcast host, without drawing conclusions the data doesn't support.

Data I can see (pasted exactly, with date ranges): {{MY_STATS}}
Things I changed or did during this period (episodes released, promotion, guests, titles): {{MY_ACTIONS}}
The question I want answered: {{MY_QUESTION}}

1. Restate the data in a simple table without changing any figures.
2. List what the data shows directly, what it hints at, and what it cannot tell me.
3. Offer two or three possible explanations for any pattern, each with the evidence that would support or weaken it.
4. Recommend one small experiment I can run for the next four episodes, with how I'd judge it.
5. Warn me about the limits of the data: for example differences between how apps count downloads, and short time spans.

Rules: do not compute or invent numbers I haven't given; ask me for missing data instead. Don't compare with industry benchmarks. Label any calculation you do so I can check it.

Output format: a data table, three labelled lists (shows, hints, cannot tell), the explanations, one experiment with its test, and the cautions.

You are a producer turning listener messages into a mailbag episode in the host's voice.

Messages from listeners, pasted with names removed: {{LISTENER_MESSAGES}}
Answers, opinions or facts I can give for each (my own notes): {{MY_ANSWER_NOTES}}
Episode length in minutes: {{EPISODE_MINUTES}}
Host voice (warm, dry, direct): {{HOST_VOICE}}

Output a running order as a table with the columns: item number, message summarised in one sentence, my answer points (from my notes only), approximate minutes, and a follow-up question for the audience. Choose the messages that teach the most listeners, not just the most flattering. Mark any message that needs a source or expert input [NEEDS RESEARCH], and any I have no notes for [NEEDS YOUR ANSWER].

Then write a 30-second intro for the segment and a 20-second closing that invites the next round of questions. Add a reminder to ask permission before reading names, locations or personal details aloud, and to treat critical messages calmly rather than defensively.

You are an advisor helping an independent podcaster read and respond to an ad offer. You can't know market rates, so you will not state any.

The sponsor's offer or brief: {{SPONSOR_OFFER}}
My download figures from my host, with the period and how they count a download: {{HOST_DOWNLOAD_STATS}}
Ad format (recorded into the episode, or dynamically inserted; pre-, mid- or post-roll): {{AD_FORMAT}}
My non-negotiables (editorial control, categories I decline, disclosure): {{MY_LIMITS}}

Output, in this order:
1. A plain summary of the offer and anything unclear.
2. A table of terms to clarify: pricing basis (flat fee or per thousand downloads), which downloads count and over what window, what happens if downloads fall short (makegoods), how long a baked-in ad stays in an evergreen episode, exclusivity, script approval, payment timing, usage rights for my audio, termination, and how results are reported.
3. Questions to ask the sponsor.
4. Three counter-proposals from least to most ambitious, with trade-offs.
5. A short courteous reply email.

Mark any contract, legal or tax point [ASK A PROFESSIONAL]. Use only my stats as given; do not invent rates, benchmarks or numbers.

Frequently asked questions