"Our PR agency says they've got relationships with every top-tier outlet." Fine. So why is the pitch sent on your behalf something a reporter can delete in four seconds flat, without opening a single link? Relationships get an email read. They do not get a story written, because the reporter still has to stand behind whatever they publish, and a warm introduction does not verify a contract address.
That's the part the retainer invoice never mentions, and it's the reason a lot of crypto marketing teams keep paying for coverage that never lands. A pitch can be beautifully timed and still fail, because it asks a journalist to trust a claim rather than check it. There is no Coinpresso-held data on crypto pitch open rates to wave around here, so everything below leans on what journalists themselves say they want, not a benchmark we've invented. This piece is about building the thing that actually gets read: a pitch that hands a reporter everything they need to verify your story, whether you send it or your crypto PR team does.
What Journalists Need From a Crypto Pitch
A journalist opens a pitch looking for five things in roughly this order: is it relevant to what I cover, is it new, can I prove it, what does it mean, and can I reach someone who'll actually answer a question. Miss the first one and nothing else matters.
Nearly three quarters of journalists decline a pitch because it simply doesn't fit what they cover, Muck Rack's own research found. Beat research isn't a nicety. It's the entry ticket.
Crypto adds a wrinkle general PR advice doesn't account for. A SaaS pitch asks a journalist to describe a product. A crypto pitch asks them to describe a financial claim, and financial claims get checked before they get published. That's the gap in most "how to pitch journalists" advice: it was written for a beat where the worst-case failure is a boring story, not a wrong one.
The Source-utility Test
Before you send anything, run it through one question: could a reporter verify this without calling you back? If the answer is no, the pitch isn't ready, however well it reads.
Three things need to be true. There's a reportable fact: something concrete enough for a headline, not a mood. A contract address or a funding figure, not "we're excited about our momentum." There's a credible voice attached, a named person with a reason to be quoted. And there's an independent way to check the claim that doesn't run through you.
That third point is where polished pitches quietly fall apart. A panel of working journalists told Muck Rack that pitches approved by clients are often not the pitches journalists actually want. A pitch built to make the founder feel well-represented and one built to survive five minutes of fact-checking are different documents. Most agencies are quietly writing the first one.
If your pitch would collapse under one follow-up question, it isn't a pitch yet. It's a draft wearing a subject line.
Build the Evidence Shelf
A reporter should verify your core claims using material you've already published, without emailing you back. Build this before you write the pitch. The pitch is just a signpost pointing at it.
Here's what belongs on the shelf, by story type:
- Funding or partnership claims — signed terms or a dated announcement, named investors who'll confirm on request
- Protocol or product launches — the audit report with scope stated plainly, the contract address, mainnet status with a date
- Data-driven claims — methodology, date range, and where the raw numbers live so a reporter can spot-check them
- Regulatory claims — the actual filing reference, not a paraphrase of it
Regulators are already pushing issuers toward this standard, and it's worth borrowing even if your project isn't filing anything with anyone. SEC staff guidance on crypto asset disclosure calls for material information on launch history, the development team, and supply, rather than a paragraph of vague assurance. You don't need to be raising a security to learn the lesson: specific and checkable beats polished and vague.
Caveats belong on the shelf too, not buried. If the audit covered one contract out of three, say so plainly. A reporter who finds the gap themselves stops trusting everything else you sent.
Write the 150-word Brief
Keep the pitch itself to roughly 150 words, structured in five moves: the news, why it matters, the proof, who's available to talk, and why this reporter specifically. Everything else lives on the evidence shelf, linked, not pasted in.
Journalists are consistent on length even when the exact ceiling moves. Muck Rack's pitching guide recommends 200 to 400 words, while a more recent panel found 69% of journalists prefer under 200. Shorter wins either way, and anything that reads like a press release gets treated like one: skimmed, then binned.
Here's an example of the structure in practice:
> Subject: [Protocol] completes $12M raise led by [Investor], mainnet live Nov 3 > > [Reporter name] — following your coverage of [recent relevant piece], thought this might fit your beat. [Protocol] closed a $12M round led by [Investor] on [date], mainnet live the same day. Audit scope and contract address attached; founder [name] is available this week. Happy to send the term sheet or connect you with [Investor] directly.
No adjectives doing the work facts should do. Just what happened, why it matters, and how to check it.
Match the Pitch to the Beat
A markets reporter and a regulation reporter reading the same announcement want different stories. Sending them the identical pitch is the fastest way to look like you skipped the beat research you claimed to do.
The table below is the cheat sheet: what each beat checks first, and what to put in front of them before anything else.
| Beat | What they need first | What to lead with |
| Markets | Price and volume context, timing relative to broader moves | The number, and why it's happening now |
| Regulation | What changed legally, which jurisdiction, what the filing says | The primary document, quoted directly |
| DeFi | TVL impact, contract risk, what's composable with what | The audit, the contract address, the integration list |
| Infrastructure | Throughput, uptime, who's building on it already | Technical benchmarks, named integrators |
| Gaming | Player numbers, retention, what's actually playable | A working build link, not a trailer |
| Culture | Why anyone outside crypto would care | The person, the community reaction, the screenshot |
A markets reporter does not want your audit scope leading the email. A DeFi reporter does not want your price chart. Knowing which proof point leads for which beat comes from doing this across newsrooms, not from filling in a template.
Follow up Without Creating Noise
One follow-up, with something genuinely new attached, five to seven business days after the first pitch. That's the practical ceiling before persistence turns into noise a journalist starts filtering by sender.
Nearly half of journalists seldom or never respond to pitches at all, and the ones who do are fielding a high daily volume already. A second email that repeats the first reads as pressure, not persistence.
A useful follow-up carries new information: a confirmed quote, a corrected figure, a second data point. "Just circling back" is not new information, it's a reminder you want something, and journalists can tell the difference instantly. Respect whatever a reporter has stated publicly about contact preference, whether that's no DMs or email-only. Ignoring a stated preference is the fastest way onto a mental blocklist, and those lists have long memories in a beat this small.
Conclusion
A crypto pitch earns a read the way a crypto claim earns belief: by making itself easy to check. Relevance gets the email opened. Evidence is what gets it forwarded to an editor.
Here's the reusable checklist, worth running every pitch through before it leaves your outbox:
- Does it fit this specific reporter's recent coverage, not just their general beat?
- Is there one reportable fact a headline could be built around?
- Is there a named, reachable person attached to a quote?
- Can the core claim be verified independently, without calling you back?
- Is the pitch under 200 words with everything else on a linked evidence shelf?
- Have you stated the caveats rather than let the reporter find them?
A credible crypto story needs more than a polished email. Contact Coinpresso and we'll turn your evidence, your audits, your terms, your data, into a journalist-ready source package before the next pitch goes out, not after a reporter hands it back asking questions you should have answered first.
FAQs
What makes a crypto story newsworthy?
A reportable fact that didn't exist yesterday: a raise closing, a mainnet going live, a filing becoming public. Relevance to the reporter's actual beat matters as much as the news itself, since nearly three quarters of journalists reject pitches purely for not fitting their coverage area, regardless of how strong the news is. Check the reporter's last five pieces before you pitch, not just their job title.
Should the founder send the pitch directly?
Either works, provided whoever sends it can answer a follow-up question within the hour, not the week. A founder sending directly often reads as more credible on a technical or regulatory story, where the reporter wants the person who actually knows, but only if that founder is genuinely reachable and not routing every reply through an agency. See our crypto PR page for how we structure that handoff so the agency clears the path rather than standing in it.
How long should a crypto pitch be?
Under 200 words, with everything else living on a linked evidence shelf rather than stuffed into the email. Journalist surveys aren't fully consistent on the exact ceiling, Muck Rack's own guide suggests 200 to 400 words while a more recent panel put the preference closer to under 200, but every figure points the same direction: shorter beats longer. These are directional survey findings across all beats, not a guaranteed crypto-specific response rate.
What evidence should accompany a funding or partnership pitch?
Signed terms or a dated announcement, and a named investor willing to confirm the round if a reporter calls. Vague language like "strategic partnership" without a document behind it is the fastest way to get ignored by anyone who has been burned by a crypto story before. If the deal has conditions attached, state them; a reporter who discovers an undisclosed condition later won't take your next pitch as seriously.
How many follow-ups are appropriate?
One, sent five to seven business days after the first pitch, and only if it carries something new, a confirmed quote, an updated figure, not a repeat of the original ask. Nearly half of journalists say they seldom or never respond to pitches at all, so a second email that adds nothing just confirms you had nothing else to say. Our case studies page covers how we sequence outreach across a launch window without tipping into noise.
