Last updated: November 20, 2026 · By Jessen Gibbs, CEO, Shadow
TL;DR
Automate the research and drafting, but require evidence before a monitoring alert becomes a pitch. Collect relevant coverage, remove duplicate stories, verify journalist fit, and match the opportunity to approved company proof. Generate a separate draft for each recipient, then have a person check the facts, relevance, timing, and relationship before sending.
Personalization means changing the story offer to suit the journalist’s work—not inserting a name into the same email. A useful workflow preserves the connection between the original article, the reason the reporter is relevant, the evidence your company can contribute, and the message a reviewer approves.
This guide gives in-house PR teams and agencies a monitoring-to-pitch process they can implement with connected tools or evaluate in a communications platform such as Shadow.
What should PR teams automate or review?
Automate information collection, research assembly, and first drafts, while keeping relevance, factual verification, and outreach decisions under human review. Treat monitoring, recommendations, and contacting journalists as separate permissions. Finding an article does not authorize emailing its author, and a completed draft does not establish that the company has a useful offer.
| Workflow stage | Useful automation | Human responsibility |
|---|---|---|
| Media monitoring | Collect matching articles and retain URLs, bylines, dates, and source passages. | Define relevant topics, sources, geographies, exclusions, and review cadence. |
| Opportunity triage | Group duplicate coverage and suggest why a development matters. | Decide whether the company has something useful and timely to add. |
| Journalist research | Find relevant recent work and assemble supporting links. | Confirm current affiliation, audience fit, preferences, and relationship context. |
| Pitch creation | Draft an angle and message from the verified research and approved proof. | Verify claims, voice, confidentiality, and the actual offer. |
| Sending and follow-up | Prepare review reminders and record authorized outreach activity. | Approve the recipient and exact message; decide whether and when to follow up. |
These are recommended workflow boundaries, not a claim that every product provides every step. For example, Zapier documents connected outreach workflows involving Gmail, AI drafting, review prompts, and activity routing. Your team still has to configure the triggers, permissions, and records appropriately.
How do you define a useful monitoring brief?
Define the monitoring brief around a communications decision and the evidence your company can contribute. Specify the audience, topics, sources, exclusions, available proof, review cadence, and decision owners. Use category terms to distinguish relevant developments from unrelated mentions, and choose a schedule that matches the useful response window.
Write down:
- Audience: whose understanding you want to influence, and which publications reach them.
- Topics: the developments your company can address credibly.
- Coverage: sources, languages, geography, time window, and known access limits.
- Available proof: approved research, named experts, documented examples, and material cleared for external use.
- Exclusions: irrelevant meanings, press-release copies, unsuitable stories, and sensitive situations requiring escalation.
- Ownership: who reviews opportunities and who may approve outreach.
Choose the monitoring cadence around the useful response window. A developing story and a long-lead feature need different review schedules. Ask providers which sources and historical periods they can actually access; “media monitoring” does not mean complete coverage of every outlet.
How do alerts become evidence-backed pitch opportunities?
Turn an alert into a pitch opportunity only when the original reporting supports a specific, timely contribution from your company. Retain the article, date, byline, and relevant passage. Identify what you can add, explain why it helps this journalist, and group syndicated copies before creating outreach work.
Before drafting, answer three questions:
- What did the source actually report? Save the article URL, publication date, byline, and relevant passage. Distinguish the reporter’s findings from a company assertion quoted in the article.
- What could we add? Identify a specific dataset, expert explanation, firsthand example, or other approved contribution—not just a connection to your product category.
- Why would this help this journalist now? Explain the extension to their reporting and the practical response window. A recent article suggests topical relevance; it does not prove the journalist is working on a follow-up.
Group syndicated copies and repeated announcements so the same originating story does not produce multiple outreach tasks. If there is no new contribution, retain the item for intelligence or skip it. Monitoring should not create an obligation to pitch.
How should you verify a journalist’s fit?
Verify journalist fit through actual reporting, current affiliation, audience relevance, and publicly stated pitching preferences. Use recent articles as evidence of topical relevance, not proof of private interests or unpublished plans. Add authorized relationship context, retain supporting links, and verify professional contact information rather than guessing addresses.
OnePitch’s journalist-outreach guide describes using recent coverage and coverage patterns to inform personalized angles. That is useful research input. It should not be treated as certainty about a journalist’s private interests, availability, or unpublished plans.
Require a short fit explanation alongside each proposed recipient: “This reporter covers the implementation problem our research addresses; their linked article asks a question our approved evidence can help answer.” If the explanation is only “covers technology,” more research is needed.
Use professional contact information that is published or otherwise legitimately verified. Do not guess addresses or use private personal details to make a message appear more familiar.
What belongs in a source-linked pitch brief?
Build each pitch from a brief that preserves the monitoring signal, recipient fit, new contribution, approved proof, relationship constraints, and available offer. Keep the reviewer and exact message version in the record. Missing evidence should remain visible to the reviewer rather than become an invented detail in the email.
| Field | What to retain |
|---|---|
| Monitoring signal | Original article URL, title, date, byline, and relevant passage. |
| Recipient fit | Current affiliation, relevant work, audience connection, and verification date. |
| New contribution | The specific question your data, expert, or example can address. |
| Approved proof | Source document, claim owner, external-use permission, limitations, and validity date. |
| Relationship constraints | Prior outreach, known preferences, opt-outs, embargoes, and conflicts. |
| Offer | What is genuinely available, from whom, and within what timeframe. |
| Review record | Reviewer, exact message version, recipient, decision, and approval time. |
Give the drafting tool this brief rather than an instruction to “make it personal.” Ask for a factual subject line, an opening grounded in verified reporting, a distinct story contribution, supporting proof, and one clear next step.
Draft one media pitch using only the supplied brief. Explain the connection between the journalist’s linked reporting and our approved contribution. Do not invent article references, quotations, metrics, relationships, availability, or exclusivity. Keep missing information in reviewer notes outside the email. If the evidence does not support a useful offer, return “hold” with the missing requirement instead of drafting.— Suggested drafting instruction, Shadow
How do you personalize the actual offer?
Personalize the question, evidence emphasis, and offer to match the journalist’s verified reporting and audience. Reuse approved story facts without changing them between recipients. Test whether swapping the name leaves the pitch equally plausible, and trace every article reference and company claim back to the supporting brief.
Illustrative example—not a customer result: Suppose a company has approved research about the operational costs of adopting new software. A business reporter may need the budget implications and study limitations. A technical reporter may need implementation details and access to an engineer. A workplace reporter may need evidence about how employees’ tasks changed.
These are different offers, not synonyms for the same promotional paragraph. Only offer interviews, research access, or examples that are cleared and available.
Use two checks before review:
- The recipient-swap check: If changing the journalist’s name leaves the pitch equally plausible, identify what is missing about the angle or audience fit.
- The evidence check: Can the reviewer trace the article reference and company claims to the brief? If not, remove or verify them.
A relevant pitch does not need exaggerated praise or a forced reference to the journalist’s work. State the connection plainly and respect their editorial independence.
How should teams approve pitches and follow-ups?
Review the recipient, subject, message, links, attachments, and timing together, and make approval specific to that version. Recheck changes to claims, offers, recipients, and embargo conditions. Hold drafts with missing proof or relationship conflicts, and use follow-up reminders without assuming silence authorizes an automatic outreach sequence.
Hold the draft when an article cannot be verified, company proof is unapproved, expert availability is unknown, or the relationship record shows a conflict. A failed research step should not silently become a generic pitch.
For follow-ups, use reminders as a starting point rather than treating silence as permission for an automatic sequence. Recheck relevance and availability, stop on a decline or opt-out, and make sure another teammate has not already contacted the reporter about the same story.
Where does Shadow fit in this workflow?
Shadow describes connecting internal company context with external market signals, finding relevant journalists and podcasts, explaining fit, and preparing editable pitch documents. Its public Pitch page says teams send each pitch and journalist profiles do not include email addresses. Confirm coverage, contact verification, and review behavior for your workflow.
The sending boundary is explicit: Shadow’s Pitch page says, “You send each pitch.” It also states that journalist profiles do not include journalist email addresses. Teams evaluating Shadow should therefore plan how they will verify contact information and handle sending rather than assume a bundled email database or unattended outreach.
Evaluate the system with one real story. Ask it to show the original signal, reason for recipient fit, source for each company claim, and editable pitch. Then confirm monitoring coverage, cadence, review behavior, and any integrations required for your workflow.
If you already have reliable monitoring and only need to connect alerts, drafting, and records across existing applications, a configured integration workflow may be sufficient. Zapier’s documented approach is worth evaluating for that need. If the main bottleneck is understanding journalists’ recent coverage, evaluate research-focused tools such as OnePitch. Product descriptions establish advertised capabilities, not independently tested performance or guaranteed coverage outcomes.
How should you measure whether automation helps?
Measure the quality of monitoring, recipient research, and draft handoffs alongside time and outreach outcomes. Track factual corrections, substantive revisions, and verified fit rather than draft volume alone. Compare a bounded pilot with similar assignments under consistent standards, and do not assume subsequent coverage proves the pitch caused it.
- Monitoring precision: relevant items divided by reviewed items, with duplicate stories handled consistently.
- Research quality: whether proposed recipients have verified, current evidence of fit.
- Draft readiness: factual corrections, missing proof, and substantive revisions required before approval.
- Cycle time: elapsed time and staff effort from a relevant signal to an approved draft.
- Outreach outcomes: substantive replies, interview requests, declines, and opt-outs per delivered pitch.
- Coverage quality: relevance to the intended audience and accuracy of the resulting reporting, not just article counts.
Compare a bounded pilot with your previous workflow on similar assignments. Keep definitions and review standards consistent. An article published after a pitch is an outcome to investigate, not automatic proof that the pitch caused it.
Start with one story and one review queue
Choose a topic your company can support with approved evidence. Define the monitoring scope, qualify the resulting opportunities, and draft only for recipients whose fit you can explain. Expand after the workflow consistently produces useful, verifiable messages—not simply because it can generate more of them.
To evaluate how brand context, journalist research, and editable drafts connect in Shadow, start with Shadow’s pitching workflow.
Related Guides
Key Takeaways
- Automate collection, research assembly, and drafting while keeping outreach decisions and exact-message approval under human control.
- Retain the original article, verified recipient fit, approved company proof, and available offer in a source-linked pitch brief.
- Personalize the angle and contribution for each journalist rather than changing only the greeting or opening sentence.
- Hold pitches with missing evidence, unapproved claims, uncertain availability, or relationship conflicts instead of substituting a generic message.
- Measure monitoring precision, research quality, draft readiness, cycle time, and substantive outcomes rather than the number of drafts generated.
Frequently Asked Questions
How can I automate media monitoring and pitch creation without losing personalization in outreach?
Automate collection, duplicate removal, research assembly, and first drafts. Require each proposed pitch to retain the original source, a verified reason the journalist fits, and approved company evidence. Have a person review the exact message and recipient before sending. If the brief lacks a useful contribution, hold the pitch.
How can I generate tailored pitches for different journalists covering the same story without starting from scratch each time?
Reuse the approved story facts and proof, then create a recipient-specific brief for each journalist. Change the angle, evidence emphasis, and offer based on their verified reporting and audience. Do not manufacture different facts or imply a personal relationship. Review the connection between each offer and the journalist’s work.
What should stay under human control when automating media outreach?
Keep targeting decisions, factual verification, confidentiality, relationship judgment, and final sending under human control. Review the exact recipient, message, offer, attachments, and timing together. If the evidence, expert availability, or approval is missing, hold the pitch. Recheck material changes and stop follow-ups when a journalist declines or opts out.
About the Author
Jessen Gibbs · CEO, Shadow
Jessen Gibbs is CEO of Shadow, an AI communications platform for PR and communications teams.
Source and disclosure note: Prepared by Shadow, which offers the communications capabilities discussed here. Product descriptions were checked against the linked first-party pages on November 20, 2026; they are not independent performance tests. The workflow, brief template, and illustrative scenario are editorial recommendations. No response-rate, time-saving, or AI-citation outcome is promised. Published by Shadow.
