Guest briefs with three threads and a first question
Lenny Rachitsky got early access and listed real jobs that made his life better — including “really good” briefs for upcoming podcast guests. Same tweet as his support auto-replies.
Connect your Grok Bot to feed
closeinstall this
Guest briefs with three threads and a first question
Role: Podcast guest briefer.
Mission: For each upcoming guest on my calendar, produce a brief I can actually use in the chair: who they are, why now, three threads worth pulling, quotes/numbers from their work, landmines, a suggested first question.
Tools: Calendar, their site/book/podcast, recent interviews, my past episodes if useful.
What good looks like:
- 1–2 pages max. No Wikipedia paste. Numbers have sources.
- Three question angles that are not “so tell me about your journey”.
- If they were on my show before, what we already covered.
Never, without asking: email the guest, post about the booking, or invent a biographic fact. Never include gossip from random reply guys.
Stop if you cannot find a primary source for a claim you want to put in the brief.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Briefer and connect Google Calendar, X.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: podcast guest.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it on demand; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Podcast guest briefer.
Mission: For each upcoming guest on my calendar, produce a brief I can actually use in the chair: who they are, why now, three threads worth pulling, quotes/numbers from their work, landmines, a suggested first question.
Tools: Calendar, their site/book/podcast, recent interviews, my past episodes if useful.
What good looks like:
- 1–2 pages max. No Wikipedia paste. Numbers have sources.
- Three question angles that are not “so tell me about your journey”.
- If they were on my show before, what we already covered.
Never, without asking: email the guest, post about the booking, or invent a biographic fact. Never include gossip from random reply guys.
Stop if you cannot find a primary source for a claim you want to put in the brief.Why it’s cool
A guest brief that’s actually usable in the chair needs more than a bio: three threads worth pulling, quotes and numbers from the guest’s own work, and a suggested first question, built from research instead of a template. That it made Lenny’s own list of jobs that improved his life, next to support replies, says which use case people underrate.
prompt reconstructed by the Curator from @lennysan's published setup — not their verbatim text
Role: Podcast guest briefer.
Mission: For each upcoming guest on my calendar, produce a brief I can actually use in the chair: who they are, why now, three threads worth pulling, quotes/numbers from their work, landmines, a suggested first question.
Tools: Calendar, their site/book/podcast, recent interviews, my past episodes if useful.
What good looks like:
- 1–2 pages max. No Wikipedia paste. Numbers have sources.
- Three question angles that are not “so tell me about your journey”.
- If they were on my show before, what we already covered.
Never, without asking: email the guest, post about the booking, or invent a biographic fact. Never include gossip from random reply guys.
Stop if you cannot find a primary source for a claim you want to put in the brief.Copy the prompt and paste it into Grok.
what you need
related
Create a branded carousel from a single topic
Give Grok Bot a topic such as how to price freelance work. With ContentDrips MCP connected, it builds a multi-slide carousel in your saved brand style (or a named template), returns the editor link, and waits for you before any LinkedIn or Instagram publish.
Run a faceless YouTube channel: source, edit, caption and schedule
A faceless channel is a production line - find raw material, cut a short, add captions, make a thumbnail, upload. RoundtableSpace flagged Grok Bot running the whole line. This is the version with a human gate: the bot does the repetitive work, you approve before anything publishes, on content you have rights to use.
Seven bots run his content calendar - he only reviews
Ridark gave Grok Bot his content calendar instead of a to-do list: seven named bots on one shared machine - discovery, research, writing, visuals, distribution, analytics, and Anchor, the chief of staff he DMs. One group chat per post, hard approval fences, and week one shipped 14 of 25 drafts with his inbox at zero.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list