---
name: get-featured-on-podcasts
description: "Share your useful work with people who listen to the right shows."
category: Personal Branding
stage: —
definitive_article: /personal-brand
status: needs-work
---

# Get featured on podcasts

Share your useful work with people who listen to the right shows. This guide helps you plan a guest pitch and follow the episode through release. Start with one show and a topic its listeners need.

**The path:** Audience fit → Specific pitch → Agreed recording → Released episode and reuse

**Start when:** The person has real expertise and a suitable show may benefit from a guest conversation.

## Inputs

- A verified show list, actual recent episodes and audience fit.
- Approved bio, real headshot, home site, topics from [Topic Wheel, the map of your offer, topics and real stories](https://blitzmetrics.com/topic-wheel/) and proof the person can discuss them.
- Outreach authority, guest availability, recording/use consent and the show’s actual submission route.

## Steps

1. Read or inspect a real recent episode and the show’s guest process. Prioritize audience fit and useful subject matter, not just a promise of backlinks. Record the host, source, topic opportunity and any published submission requirements.
2. Prepare a compact pitch kit with current bio, photo, a few relevant talk ideas and verified source links. Explain what listeners will learn. Avoid unsupported performance numbers, borrowed credentials or an assumption that a famous previous guest endorses the new one.
3. Draft a personal pitch tied to the actual show and one clear topic. Send only with the existing authority and retain the exact thread. Track drafted, sent, replied, accepted and booked states separately; no-reply remains no-reply.
4. Once accepted, agree time, format, useful talking points and recording/reuse rights. Confirm which host controls the recording and release. Prepare the person to answer directly with true examples, and give the host the correct name and home URL.
5. Record the actual appearance under consent. Save the date, participants and available source file. An appointment is not a recorded episode, and the guest’s file is not proof the host has published. Keep private or embargoed material out of the public queue.
6. When the episode airs, verify the normal episode URL, identity, title and any show-note credit. Request a factual correction through the actual host if necessary; an editorial decision not to link the site stays recorded rather than overwritten as a completed link.
7. Prepare permitted clips, a site proof entry and a specific thank-you using their respective tasks. A neutral interview proves participation; only actual praise becomes a positive mention. Retain pending host release and downstream reuse as distinct handoffs.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the actual result against its agreed requirements. Follow the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] The pitch and guest topic fit a verified show and use real evidence.
- [ ] Booking, recording, publication and reuse have their own actual receipts.
- [ ] The final inventory accurately records participation, link status, rights and next actions.
- [ ] The exact output, source revision, reviewer evidence and remaining owner action are saved.
- [ ] For any reader-facing output, the short grade-five opening states the reader’s useful outcome and supporting method or proof. The body delivers that promise; a useful authentic visual appears in the first screen. Retain exact text and quoted reviewer evidence.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional caterer pitches a local show on planning food for outdoor events. The host accepts and records the talk, but release is set for next month. The team saves the approved bio and recorded-session evidence. It prepares clip ideas while keeping the episode and clips unpublished until the agreed release and rights allow them.

## Handoff and Content Factory context

[Prepare social clips](https://local-service-spotlight.github.io/task-library/?task=create-social-content-from-video-clips#task-create-social-content-from-video-clips) receives permitted source files; [Collect and classify positive mentions](https://local-service-spotlight.github.io/task-library/?task=positive-mentions-harvester#task-positive-mentions-harvester) receives the verified episode record; the existing relationship owner retains host follow-through.

This task supports the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). Identity, proof, access or coordination can support several stages. Use the real inputs and receiving owner above; this task does not create unrelated transcripts, clips or ads merely because the diagram has four stages.

## Start with an agent

Give the [AI worker](https://blitzmetrics.com/build-agents/) this recipe, the real inputs, desired result and actions already authorized. Ask for the saved output, sources, checks and next owner. A [skill is a written recipe](https://localservicespotlight.com/plugin/); loading one does not prove account access or perform the task. Use the [installation guide](https://localservicespotlight.com/install/) if reusable setup is needed. A ZIP is a source snapshot, not an access grant or automatic update.

Use the app’s actual supported tools and verified file/account access. Keep a missing human verification step with its real owner. Recurring work needs its own configured job, trigger, timezone and observed result; this guide creates no schedule. Before any media playback, mute the player and set its volume to zero. If silence cannot be verified first, use captions, frames, metadata or another silent check.

## Record the real execution

Open the run record when work begins. Keep one execution ID, starting recipe revision, real inputs and current state. Write the [meta article, the record of this execution](https://blitzmetrics.com/meta-article-prompt/) with actual steps, results, checks, failures and next owner. Writing is required; public release follows existing authority. Link it to this recipe and the [Task Library](https://local-service-spotlight.github.io/task-library/).

Reuse the same execution ID for internal checks, revisions, retries and meta writing. A blocked run stays open with its dependency and owner, without an invented finish time. Dated public examples and distinct verified execution counts remain separate. Propose the smallest source-backed recipe improvement when the actual evidence reveals a defect.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- [Maintained source guide](https://blitzmetrics.com/personal-brand/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=get-featured-on-podcasts#task-get-featured-on-podcasts)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records fit together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `needs-work`. It is preserved, not promoted by this rewrite. That label alone does not prove document readiness, account access, an actual execution or a client result.

The fictional example teaches the method and does not fill a real-run evidence gap. A named semantic reviewer must check the actual opening, full method, sources and handoff. Check the useful opening visual in the normal rendered guide at the current required desktop and mobile sizes, including 1280 × 800 and 390 × 844. Source readability checks do not prove public presentation or task execution.