Why this person?
Direct operating experience, a body of work, data, a decision, a failure or a point of view with consequences. The guest earns the hour before outreach begins.
A podcast is strongest when the episode, the guest evidence, the YouTube package, the chapters and the native cuts are designed together. The show needs a thesis and a catalogue, not a clip quota.

The guest list is not the strategy. A strong show owns a question, knows who the listener is becoming, and creates progression inside the hour.
The desk finds the obvious questions and removes them. What remains is the contradiction, the operating detail, the source the guest has not been asked about and the moment worth staying with.
Primary sources, prior interviews, contradictions, useful facts and claims that need checking.
Opening tension, proof, consequence and the question that earns a deeper answer.
Moments worth extending, verifying, chaptering or turning into standalone ideas.
YouTube, Shorts, LinkedIn, X and Instagram receive complete native ideas.
A good recording gives the programme options: the full conversation, a YouTube package, chapters, a short-form idea, a written argument and a future guest thread. The work is deciding which outputs deserve to exist.
The episode map makes the listener feel progress. It also gives the editor clean chapter boundaries and gives distribution complete ideas instead of arbitrary timestamps.
The problem, the guest's standing and why this hour is worth spending.
The operating context that created the guest's point of view.
How the thing actually works, with examples and sources in the room.
The failure, disagreement or trade-off the category usually edits out.
What the listener should now see differently and where to go next.
A short clip should survive without the hour around it. A LinkedIn post should carry the operator's judgement. An X thread should keep the source visible. An Instagram Reel should earn context fast.
Packaging, progression, end screen, playlist and connected library.
The idea a buyer or operator can carry into the next meeting.
The sharpest live idea, the source trail and the consequence.
One moment, one proof beat, one reason to save, send or ask.
For video podcasts, the title and thumbnail make one contract. The opening repays it. Retention shows where the promise weakens. The catalogue decides whether the viewer has a reason to come back.
Thumbnail: one crossed-out growth chart, guest face absent, one operating number visible.
Example values for interface design. The supplied public case repository does not contain permissioned podcast outcome metrics.
A large following can help distribution. It cannot rescue a guest who has no inspectable experience, no tension and nothing the listener could not get from a conference bio.
Direct operating experience, a body of work, data, a decision, a failure or a point of view with consequences. The guest earns the hour before outreach begins.
The research desk finds the trade-off, contradiction or category assumption worth testing. Agreement is allowed; inevitability is boring.
Reports, product screens, filings, research, old quotes, charts, customer examples or artifacts the conversation can point at instead of merely asserting expertise.
The programme reads packaging, consumption, catalogue continuation and business context separately. That keeps the programme from celebrating a clip because it travelled while the full show stopped earning return.
Do not claim precise last-click causality where the show sits earlier in the buying path.
We map the season before filling dates. The point is not to force a rigid narrative; it is to see which questions deserve repetition, which guest archetypes create useful contrast and where a missing episode is leaving the catalogue thin.
Published work, contradictions, claims worth checking, primary sources, prior interviews, red lines and the two questions everyone else keeps asking so we can avoid them.
Thesis turn, proof moment, disagreement, source reference, clean clip boundary and unanswered question. The editor inherits a map instead of an undifferentiated hour.
Final masters, clips, transcripts, guest permissions, music and footage rights, thumbnails, chapters and distribution files stay organised for the next release and later reuse.
Physical production, travel, studio, crew and complex motion stay separately scoped · client owns RSS, raw files and final masters · month to month · 30 days' notice.
Listener, category question, show promise, guest acceptance criteria, research template, episode progression and visual package.
Record, package, chapter and distribute the first programme. Read retention, audience questions, guest fit and next-video behaviour.
Formalise recurring segments, playlists, guest arcs and the native distribution products that deserve to return.
They can be coordinated when needed, but physical production remains a visible separate scope. The programme covers the show architecture, research, packaging, distribution and agreed edit capacity.
No. We control the thesis, guest standard, research, package, edit decisions and distribution system. Audience response remains audience response.
Yes. For most commercial programmes, YouTube packaging and catalogue design are treated as first-class parts of the product rather than an afterthought to the RSS feed.
The client. RSS, channel accounts, raw footage, masters, research notes and approved source files stay in client-owned systems.
We will build the research, episode and distribution product around it.