Key takeaways
- Start with the story and evidence, then identify the people whose current work shows genuine fit.
- Store source, beat, geography, preference, relationship owner, last contact, suppression, and review date.
- Write a short pitch that makes verification easier rather than manufacturing urgency.
- Limit follow-up and honor corrections, opt-outs, role changes, and explicit preferences across tools.
01
A database match is not evidence that somebody wants this story
A broad technology beat can include policy, enterprise software, consumer devices, labor, science, and local startups. Sending the same announcement to all of them saves research time by spending the recipient’s attention. Fit comes from recent work, stated interests, geography, format, and whether the evidence offers something their audience can use.
Write the story brief first: what changed, why now, who is affected, what can be verified, what is genuinely new, and which source can answer difficult questions. Then build the list. A weak story does not become relevant because the spreadsheet has five thousand rows.
Swipe to compare every column
| List field | Why it matters | Review trigger |
|---|---|---|
| Current beat and geography | Tests actual relevance | New role or recent work changes |
| Source and review date | Shows where the detail came from | Field exceeds its review window |
| Preference and channel | Respects stated working style | Recipient corrects or opts out |
| Owner and history | Prevents overlapping pitches | Team or agency changes |
02
Give the recipient a way to judge the claim quickly
Use a specific subject, one-sentence relevance, concise finding or event, source link, methodology or supporting material, available expert, timing, and honest limitations. Avoid false exclusivity, hidden embargoes, invented familiarity, and “just bumping this” without new information.
Provide accessible assets and a person who can answer follow-up questions. If the story depends on a customer, expert, or dataset, confirm availability and permissions before the pitch. A journalist should not discover that the named source cannot speak after starting the reporting.
03
Treat the contact record as governed operational data
Record only what the work needs, limit access, review stale fields, and propagate suppression across the CRM, outreach tool, agency, and personal lists. The FTC’s CAN-SPAM guidance and the ICO’s direct-marketing guidance are not interchangeable global rules; map applicable requirements with counsel for the sender, recipient, channel, and market.
Beyond minimum law, professional ethics still matters. PRSA’s code emphasizes honest and accurate information, independence, fairness, and avoiding deceptive practices. A technically deliverable email can still be irrelevant, misleading, or disrespectful.
04
Measure relationship quality, not sender activity
Track relevant replies, requests for evidence, interviews, accurate coverage, corrections, opt-outs, complaints, bounces, duplicate outreach, and follow-up frequency. Open tracking can be unreliable and privacy-sensitive; do not use an invisible pixel as the main proof of interest.
Read the replies. They reveal weak framing, missing evidence, bad timing, and beat mismatch faster than an aggregate open rate. The goal is not to automate more pitching. It is to make every message easier to understand, verify, decline, or pursue.
Primary sources and further reading
Use the source material to validate details against your own context and current platform configuration.
- PRSA Code of Ethics
- FTC: CAN-SPAM Act compliance guide
- ICO: Respect people’s direct marketing preferences
This field note follows the XenGrowth editorial policy: primary sources where available, visible limitations, material review dates, and no invented first-hand experience.
Stay with the problem



