Find [number] journalists, newsletter writers, and podcast hosts who covered [topic] in the last [number] days. For each person, verify their name, outlet, one specific recent piece or episode, why it fits our story, and a public contact route on their own site or a linked byline. Compare against [previous outreach list] and exclude [people or outlets]. Put the findings in a table with source links and checked dates. Drop entries you cannot verify and record why. Draft a short pitch that refers to each person's actual work and uses only the approved facts I provide. Hold every pitch for my review. Send nothing without my approval.
Press and podcast list with verified relevance
Research relevant writers and hosts, verify their recent work and public contact routes, and prepare outreach drafts for review.
Copy-ready brief
Example output
Example output for illustration only: Target: A podcast host who interviewed a founder about delegated work last month. Evidence: [episode URL], checked [date]. Public contact route: [show contact page URL]. Fit: The episode asked how teams review an agent's work; our approved angle addresses that question. Draft opening: “Your conversation with [guest] raised the question of who signs off before an agent sends a message. I can share a concrete approval workflow and its limits.” Status: Draft held. Contact route will be rechecked before an approved send. Dropped: One syndicated byline and one profile without a public contact route.
Trigger and cadence
- The reader defines a story, audience, and research window.
- One research pass, then a source refresh before any approved outreach.
Inputs
- Story angle, target topics, and relevant publication window.
- Target count, exclusions, and previous contact list.
- Approved product facts, tone, and public contact criteria.
Steps
- Find writers and hosts whose recent work matches the topic.
- Verify each person, outlet, piece, and public contact route.
- Check the exclusion and previous-contact lists.
- Record the evidence and drop entries that cannot be verified.
- Draft a short, specific pitch for each eligible contact.
Approval boundary
Every pitch and recipient waits for review; research alone never authorizes outreach.
Stop conditions
- A byline is syndicated or the original author is unclear.
- No public contact route can be verified.
- A person is excluded or was contacted inside the reader's chosen interval.
Expected output
A checked list with relevant pieces, contact routes, dropped entries, and held draft pitches.
Receipt fields
- Pages visited, checked dates, and verification outcome for each person.
- Draft versions, exclusions, approval decisions, and send status.
Recovery when it fails
- Recheck a contact route and recent work before any approved send.
- Remove stale or unverifiable entries with a recorded reason.
On this page
Match the person to the story
A press and podcast list needs a specific article or episode that explains each person’s fit. Give OperatorNest the story angle, publication window and approved product facts before it searches. “Who covered how teams review delegated work?” is a usable question; “find people interested in AI” will fill a list without giving you a reason to pitch them.
For example, Sam asks for 25 contacts. Three candidates fail the check: a syndicated byline, a missing public contact route and an article outside the chosen window. Return 22 eligible entries and the three exclusions with reasons. The example output illustrates a held pitch.
Verify the record before drafting
Record the person’s name, outlet or show, recent piece and public contact route, linking the original article or episode. Confirm they still work there and compare them with the previous-contact list. A recently contacted host can fit the story and still belong on the exclusion list.
A general contact form stays a general form in the record. An address in a directory needs confirmation from the person’s own site, outlet page or byline before it belongs in the outreach queue.
Make the research shape the pitch
Refer to one concrete point in the person’s work. If the same opening fits 50 messages, rewrite it from the linked piece. Keep claims within the facts supplied with the task; leave out customer quotes or results you were not given.
The research assistant use case covers source checking. This workflow adds an outreach record, with every pitch held for review.
Approve the recipient and exact text
Before a send, recheck the contact route and current work. Show the recipient, source piece, draft and previous contact together, even for a batch approval. If the route has disappeared or the person changed outlets, stop that pitch and record why.
Run it on a schedule
Plan the timing and missed-run behavior with the recurring task planner. For documented schedule controls across assistants, read scheduled AI tasks compared.
Related tools
- AI follow-up email writer
Draft two or three follow-up emails for a proposal, meeting, unpaid invoice, or introduction, with a suggested send time and copy buttons.
- Email tone checker
Check an email draft for unclear asks, passive aggression, over-apology, and missing deadlines, then copy or download a rewrite in your chosen tone.
- AI agent approval policy
Set clear approval rules for an AI agent. Choose systems and risk limits, then copy a policy that says what waits and what can run.
Common questions
Is a large list better than a small verified one?
A shorter list with a specific piece and public contact route gives you a clearer basis for each pitch. Keep names that fail the check in the dropped log.
Can it use an address found on a third-party directory?
Prefer a contact route on the person's own site, outlet page, or recent byline. If the route cannot be confirmed there, leave it out of the outreach queue.
When do pitches go out?
Only after you review the recipient and exact text for each pitch or approved batch. A research instruction does not authorize a send.
Keep reading
- An AI research assistant that turns a question into a sourced briefIt researches a question or a standing topic and delivers a sourced brief, once or on a recurring schedule.
- Approvals before anything that mattersIt asks before it sends, pays, books, deletes or posts. You approve, edit or hold from any channel.
- A receipt for everything your operator doesEvery task keeps a receipt: what was asked, what ran, which model did it, what it cost, and every approval.
- Build a press list with an AI agent, overnightBuild a press list with an AI agent overnight: verification rules, tone memory, your own model key, and every pitch held for approval before it sends.
Hand off your first task tonight.
Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.