Files
skills/public/journalist-pitching.html
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

420 lines
25 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>journalist-pitching</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/journalist-pitching.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/journalist-pitching">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/journalist-pitching.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>journalist-pitching</h1><p class="lede">Building a media list, scoring journalist fit, and crafting pitches that actually get opened.</p><h1>Journalist Pitching — Proactive PR Workflow</h1>
<p>Building a media list, scoring journalist fit, and crafting pitches that actually get opened. This is a 4–8 week practice, not a one-shot.</p>
<h2>Contents</h2>
<ul><li>Building the media list</li><li>Scoring journalist fit</li><li>Pitch templates by angle</li><li>Subject lines that get opened</li><li>Voice and structure</li><li>Embargoes, exclusives, and follow-up etiquette</li><li>Pitch killers</li><li>Tooling</li></ul>
<hr>
<h2>Building the Media List</h2>
<p>The goal: a list of 20–40 journalists who actually cover your beat. Not 500 names from a database.</p>
<h3>Discovery checklist</h3>
<p>For each candidate journalist:</p>
<ul><li>[ ] Read their <strong>last 5 articles</strong> — are they covering your beat right now?</li><li>[ ] Note their <strong>publication</strong> — does it reach your ICP?</li><li>[ ] Check their <strong>bio</strong> on the outlet site — what topics do they own?</li><li>[ ] Check <strong>X/LinkedIn</strong> for what they&#x27;re posting about this week</li><li>[ ] Note their <strong>email</strong> (usually on outlet author page, Muck Rack, or company About page)</li><li>[ ] Check <strong>Muck Rack</strong> if available — it shows recent topics and pitch preferences</li></ul>
<h3>Where to find candidates</h3>
<p>| Method | How | |--------|-----| | <strong>Reverse lookup from coverage you want</strong> | Find 5 articles about competitors / your category, note bylines | | <strong>Topic search on Muck Rack</strong> | Free tier shows journalists by topic | | <strong>X / Twitter lists</strong> | &quot;[your niche] reporters&quot; lists already exist | | <strong>LinkedIn search</strong> | &quot;Journalist&quot; + &quot;[your category]&quot; — filter by recent activity | | <strong>Newsletter author pages</strong> | Beehiiv, Substack, ConvertKit creators are pitchable | | <strong>Podcast host research</strong> | Listen to 1 episode before pitching — non-negotiable |</p>
<h3>Don&#x27;t waste time on</h3>
<ul><li><strong>Mass media databases</strong> (Cision, Meltwater) for early-stage — overkill and expensive</li><li><strong>Journalists who haven&#x27;t posted in 6+ months</strong> — they may have left</li><li><strong>&quot;Editor-in-chief&quot; generic addresses</strong> — pitches there get ignored or routed to interns</li><li><strong>Journalists who explicitly state &quot;no PR pitches&quot; in bio</strong> — respect it</li></ul>
<hr>
<h2>Scoring Journalist Fit</h2>
<p>Score each journalist 1–10 across four dimensions. Sum and rank. Focus on top 20.</p>
<p>| Dimension | What it measures | Weight | |-----------|------------------|--------| | <strong>Beat match</strong> | Do they cover your category specifically? | 3x | | <strong>Reach</strong> | Outlet&#x27;s audience size + their byline traction | 2x | | <strong>Engagement</strong> | Do they respond to pitches publicly / on X? | 2x | | <strong>Recency</strong> | Have they written about a related topic in last 30d? | 1x |</p>
<p><strong>Tiering:</strong></p>
<ul><li><strong>Tier 1 (8–10):</strong> Personal pitch with original angle. Custom each time.</li><li><strong>Tier 2 (5–7):</strong> Standard pitch, lightly customized.</li><li><strong>Tier 3 (below 5):</strong> Skip or pitch only when story is exceptional.</li></ul>
<hr>
<h2>Pitch Templates by Angle</h2>
<p>Six structures that work. Pick the one that matches your story.</p>
<h3>1. Data story</h3>
<pre><code>Subject: [Specific stat] — [implication]
Hi [name],
I noticed you covered [recent article] — wanted to share data that might
be relevant.
We [analyzed N / surveyed N / tracked N] and found:
• [Stat 1 with surprise factor]
• [Stat 2]
• [Stat 3]
The most interesting pattern: [one-sentence insight].
Full data + methodology here: [link to one-pager, not your homepage]
Happy to share the raw dataset, jump on a call, or connect you with
[customer who&#x27;s relevant].
[your name + 1-line credential]</code></pre>
<h3>2. Exclusive launch / milestone</h3>
<pre><code>Subject: Exclusive: [specific milestone] at [company]
Hi [name],
I have an exclusive on [milestone] that I think fits your [beat] coverage.
The story: [one sentence]
Why it matters: [one sentence — for their readers, not for you]
What&#x27;s new: [the actual news, not the marketing line]
Embargo until [day, time, timezone] — would love to give you first
window. Press kit + assets: [link]
Free to talk [two specific time options].
[your name]</code></pre>
<h3>3. Op-ed / contributed piece</h3>
<pre><code>Subject: Op-ed pitch: [provocative thesis]
Hi [name],
I read your piece on [recent article] — sharp take on [specific point].
I&#x27;d like to pitch a 700-word op-ed: &quot;[Thesis as a headline]&quot;
Core argument:
• [Point 1]
• [Point 2]
• [Point 3 — the surprising one]
Why me: [1 sentence — credential or unique vantage]
Why now: [1 sentence — the news hook]
Can have a draft to you by [date]. Happy to adapt to your house style.
[your name]</code></pre>
<h3>4. Customer story</h3>
<pre><code>Subject: Customer story for [their beat] — [specific outcome]
Hi [name],
For your [beat] coverage, I have a [customer type] willing to talk on
the record about [specific outcome].
The hook: [customer] [did something specific] and [measurable result].
The interesting part: [the surprising or counterintuitive detail].
Customer details:
• Name: [name, title, company]
• Available: [windows]
• Willing to share: [data points / screenshots / metrics]
Happy to coordinate the intro.
[your name]</code></pre>
<h3>5. Trend piece / connector</h3>
<pre><code>Subject: Trend forming in [space] — three signals
Hi [name],
Three things in [space] this month that I think connect:
1. [Signal 1 with link]
2. [Signal 2 with link]
3. [Signal 3 — yours, briefly]
The pattern: [one sentence].
This might be early for a piece, but if you&#x27;re tracking the space I
wanted to flag it. Happy to share data we&#x27;ve collected or connect you
with others seeing the same.
[your name]</code></pre>
<h3>6. Newsjack response</h3>
<pre><code>Subject: Re: [their article headline] — quick data point
Hi [name],
Saw your piece on [story] this morning — wanted to add a relevant
data point in case you do a follow-up.
[One-sentence stat or insight].
Source: [our data / our customers / our analysis]
Methodology: [one sentence]
Quotable: &quot;[a sentence you&#x27;d be comfortable seeing in print]&quot;
If useful for a follow-up, I&#x27;m around all day at this number: [phone].
[your name]</code></pre>
<hr>
<h2>Subject Lines That Get Opened</h2>
<p>Journalists open pitches based on the subject line alone. Rules:</p>
<ul><li><strong>Under 50 characters</strong> — mobile preview cuts off</li><li><strong>Lead with the specific</strong> — &quot;73% of devs deploy to prod on Fridays&quot; beats &quot;New data on developer workflows&quot;</li><li><strong>Promise a story, not a product</strong> — &quot;Why [trend]&quot; beats &quot;[Company] launches [thing]&quot;</li><li><strong>Use prefixes that signal value</strong> — &quot;Exclusive:&quot;, &quot;Data:&quot;, &quot;Op-ed pitch:&quot;, &quot;Re: [their article]&quot;</li></ul>
<p><strong>Test against this question:</strong> would <em>you</em> open this in a 200-email inbox?</p>
<p><strong>Patterns that work:</strong></p>
<ul><li>&quot;[Specific stat] — [implication]&quot; — &quot;73% of agents fail this test&quot;</li><li>&quot;Exclusive: [milestone]&quot; — &quot;Exclusive: Anthropic launches AgentOS&quot;</li><li>&quot;Re: [their headline]&quot; — direct response to recent coverage</li><li>&quot;[Provocative thesis]&quot; — &quot;Why VC funding is bad for AI safety&quot;</li></ul>
<p><strong>Patterns that get deleted:</strong></p>
<ul><li>&quot;Press release: [boring]&quot;</li><li>&quot;[Company] announces [thing]&quot;</li><li>&quot;Story idea for you!&quot;</li><li>&quot;Following up on my previous email&quot;</li><li>Any subject line with &quot;innovative,&quot; &quot;disruptive,&quot; &quot;revolutionary&quot;</li></ul>
<hr>
<h2>Voice and Structure</h2>
<h3>Length</h3>
<p><strong>150 words max for the pitch.</strong> If you can&#x27;t say it in 150 words, you don&#x27;t know what your story is yet.</p>
<h3>Structure</h3>
<ol><li><strong>One-line context</strong> — why you&#x27;re emailing them specifically (their recent article, their beat)</li><li><strong>The story</strong> — what it is, in one sentence</li><li><strong>Why it matters to their readers</strong> — not why it matters to you</li><li><strong>Proof</strong> — data, customer, quote, link</li><li><strong>The ask</strong> — interview, embargo, quote, link</li></ol>
<h3>Voice</h3>
<ul><li>Sound like a person, not a press release</li><li>Reference their actual recent work — proves you read them</li><li>Don&#x27;t use emoji unless they do</li><li>Don&#x27;t open with &quot;I hope this finds you well&quot; — burn it</li><li>Don&#x27;t ask &quot;did you get my email?&quot; follow-ups (see <a href="#embargoes-exclusives-and-follow-up-etiquette">Follow-up</a>)</li></ul>
<h3>Banned vocabulary</h3>
<p>Revolutionary, disruptive, game-changing, paradigm shift, leverage, synergy, robust, seamless, holistic, world-class, best-in-class, next-generation, cutting-edge, AI-powered (unless that&#x27;s the actual differentiation), at-the-end-of-the-day.</p>
<hr>
<h2>Embargoes, Exclusives, and Follow-Up Etiquette</h2>
<h3>Embargoes</h3>
<p>An embargo is &quot;you can write this story, but don&#x27;t publish until [time].&quot;</p>
<ul><li><strong>Only offer embargoes to journalists you&#x27;ve worked with</strong> or have strong reputations for honoring them</li><li>State the embargo time clearly: day, time, timezone</li><li>If they break embargo, your relationship with them is over</li></ul>
<h3>Exclusives</h3>
<p>&quot;Only you get this story&quot; — powerful tool, use sparingly.</p>
<ul><li><strong>First-tier outlet only</strong> — exclusives to tier 2/3 outlets waste the lever</li><li><strong>Be honest about scope</strong> — &quot;exclusive to [outlet] in the US&quot; is fine</li><li><strong>Have a parallel plan</strong> — what you publish/pitch the next day after the exclusive runs</li></ul>
<h3>Follow-up cadence</h3>
<ul><li><strong>Day 0</strong> — initial pitch</li><li><strong>Day 3</strong> — one follow-up if you have new information (&quot;Just talked to [customer] who can join us&quot;)</li><li><strong>Day 7</strong> — final check-in with a fresh hook (&quot;This came out today, still relevant?&quot;)</li><li><strong>After day 7</strong> — let it go. Re-pitch when you have something genuinely new.</li></ul>
<p><strong>Never:</strong></p>
<ul><li>&quot;Bumping this up&quot; / &quot;Did you see my email?&quot;</li><li>Multi-day silent follow-ups with no new value</li><li>Same pitch reformatted</li></ul>
<hr>
<h2>Pitch Killers</h2>
<p>Things that instantly disqualify your pitch:</p>
<ul><li>Wrong name / wrong outlet (autoreplace fail)</li><li>Pitching topics they explicitly don&#x27;t cover</li><li>Press release attached as PDF (just paste the key bits)</li><li>Long signature with logos and disclaimers</li><li>CC&#x27;ing 5 other journalists on the same email</li><li>&quot;Per my last email&quot; energy</li><li>Asking them to sign an NDA before talking</li><li>Pitching a story you can&#x27;t actually tell (no customer willing to talk, no data ready to share)</li></ul>
<hr>
<h2>Tooling</h2>
<h3>Finding journalist contact info</h3>
<pre><code class="lang-bash"># Most journalists&#x27; emails follow patterns:
# [email protected]
# [email protected]
# [email protected]
# Use Hunter.io, RocketReach, or just guess and bounce-check</code></pre>
<h3>Researching their recent work (browser-driven)</h3>
<p>Use <code>dev-browser</code> (persistent session, no rate limits) to:</p>
<ul><li>Open the journalist&#x27;s outlet author page → scrape last 5 article headlines + dates</li><li>Open their X/Twitter profile → note recent topics</li><li>Open their LinkedIn → confirm current role</li></ul>
<p>Output what you find as:</p>
<pre><code>JOURNALIST PROFILE — [name]
Outlet: [name]
Beat: [topics from last 5 articles]
Recent angle: [pattern you noticed]
Recent X activity: [what they&#x27;re posting]
Score: [X/40 from rubric]
Best pitch angle: [from template library]
Email: [confirmed]</code></pre>
<h3>Maintaining the media list</h3>
<p>Store in <code>.agents/media-list.md</code> (or <code>.csv</code> if you prefer). Update monthly — journalists move jobs constantly.</p>
<pre><code class="lang-markdown">## Tier 1 (top 20)
| Name | Outlet | Beat | Last contact | Last coverage | Email | Score |
|------|--------|------|--------------|---------------|-------|-------|
| ... | ... | ... | 2026-05-15 | none yet | ... | 9/10 |</code></pre>
<h3>Pitch tracking</h3>
<p>Track in a simple spreadsheet:</p>
<ul><li>Date sent</li><li>Subject line</li><li>Journalist</li><li>Outlet</li><li>Response (open / reply / pass / coverage)</li><li>What they said</li></ul>
<p>After 30 pitches, you&#x27;ll see which subject patterns and which angles work for you specifically.</p>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/journalist-pitching.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>