Newsjacking is the practice of inserting your brand or founder into a breaking story by offering a reporter expert comment, context, or contrast before the cycle closes. Done correctly it earns tier-1 coverage without a wire fee, a launch event, or a news peg of your own. Done badly it reads as opportunistic or, worse, factually wrong, and costs you the relationship you need for the next real pitch.

I run fractional PR for Web3, AI, DePIN and cybersecurity founders, and newsjacking is one of the most misunderstood tactics in the toolkit. Founders either ignore it entirely, assuming you need a news event of your own to earn coverage, or they treat every macro story as an invitation to insert their brand regardless of fit. Neither approach works. The method that actually gets pickup is more specific: a tight relevance test, a pre-built comment bank, a list of twelve to fifteen reporters and editors you already have a thread with, and the discipline to send one paragraph and stop. Here is the full operator's breakdown.

What newsjacking actually is

David Meerman Scott coined the term around 2011 to describe the practice of riding a breaking story's momentum to earn media attention you did not manufacture. In crypto and Web3 the mechanics are the same but the cycle is faster: a Federal Reserve rate decision, an SEC enforcement action, a protocol exploit, a sovereign wealth fund announcing a BTC position, a major exchange going down, a Layer 2 mainnet launch by a competitor. Any of these can generate a demand for expert comment within minutes, and the reporter writing that story needs two or three named sources who know what they are talking about.

Your job, if you are running reactive PR well, is to be the source who shows up with a usable quote before the deadline closes. That is the whole game. You are not pitching a story about yourself. You are offering to make the journalist's existing story better, faster.

Field ruleNewsjacking is not about your brand. It is about making the journalist's story better. The moment your comment leads with what your company does, the journalist moves on to the next pitch.

The speed problem: why two hours is not an exaggeration

Most crypto journalists filing a breaking story have a deadline somewhere between thirty minutes and two hours after the story breaks publicly. They will reach out to two or three sources they already know and trust, file with whatever they get, and the piece goes live. By the time a founder has noticed the story, drafted a comment, got it approved, and sent it, the piece is already published and the window has closed.

This is the structural reason that newsjacking requires preparation, not just awareness. The founders who consistently earn reactive coverage are not faster readers. They have pre-built infrastructure: a monitoring stack that surfaces relevant stories in real time, a short list of reporters they have already built relationships with through the media relations groundwork done before any news breaks, and a standing approval process that does not require a three-person sign-off chain to get one paragraph out the door.

The monitoring stack that makes speed possible

You do not need an expensive enterprise tool. What you need is a stack you actually check. The one I recommend for most founder clients:

  • Google Alerts: Set for your three to five primary topic keywords plus your top five competitors. Free, adequate for daily volume, not fast enough alone for breaking news.
  • Crypto Twitter / X lists: A private list of twenty to thirty reporters and editors from CoinDesk, Cointelegraph, Decrypt, The Block, Blockworks and the mainstream outlets who cover crypto adjacently. Journalists often signal a breaking story on X before the piece is even filed.
  • Telegram news channels: Several beat reporters run public Telegram channels or broadcast in crypto-specific groups. CryptoBriefing, The Block's alerts feed, and select DePIN or AI-focused channels cover fast-moving vertical stories.
  • Slack communities: Crypto PR and media Slack groups often surface breaking stories and reporter requests within minutes. If you are not already in the relevant communities for your vertical, that is a gap worth fixing this week.
  • HARO and Qwoted alternatives: Platforms like Qwoted, ResponseSource and the newer AI-journalist matching tools surface structured media requests. Useful for evergreen reactive pitching, less useful for true breaking-news newsjacking.

The relevance test: when to pitch and when to stay quiet

Not every story that touches your vertical is a newsjacking opportunity. Pitching an irrelevant comment is the fastest way to teach a reporter to ignore your name. Before sending anything, run the comment through a three-question relevance test:

  1. Do you have genuine expertise on the specific thing that just happened? Not your vertical in general. The specific event: the exploit mechanism, the regulatory question, the technical architecture, the market dynamic. If your comment would apply to any story in any industry, do not send it.
  2. Does your comment add something the reporter could not get from a press release or a Wikipedia page? First-hand data, a contrarian read, a specific technical nuance, a prediction with a named rationale. If the answer is no, the comment is not useful enough to send.
  3. Is the story in a publication your target buyer actually reads? Coverage in CoinDesk or The Block matters for institutional and investor audiences. BloomingBit, TokenPost or CryptoTimes JP matters if you are running a multilingual syndication play into Korean or Japanese markets. Inc42 matters if you are building in India. Coverage in a tier-3 aggregator that nobody reads in your buyer segment is not worth the relationship capital it costs if the comment is mediocre.
Quick filterIf you cannot complete this sentence in one specific clause, do not pitch: "I have direct experience with this because [specific, credible reason] and my read on this story is [non-obvious, defensible position]." Vague expertise claims get ignored. Named credibility gets callbacks.

The reactive comment pitch: format and mechanics

A reactive pitch to a journalist on deadline is different in every structural way from a standard pitch. It is not a press release. It is not a pitch email with three paragraphs of context. It is one thing: a usable quote, a one-line credential, and a signal that you know what story they are working on. That is it.

ElementWhat to includeWhat to skip
Subject lineQuote / [Specific story or headline keyword] / [Your name + title]Anything longer than 10 words
Opening lineReference the specific story by name, show you read it"I hope this finds you well"
The quote2-4 sentences, attributable, opinionated, one specific pointA paragraph of hedged PR language
CredentialOne sentence: who you are and why you are qualified on thisA full company bio
Offer"Happy to jump on a 10-minute call if useful""Please let me know if you have any questions"
Total lengthUnder 120 wordsAnything that requires scrolling

The mechanics for the specific outlets that matter in Web3 are covered in detail in the Cointelegraph pitch guide and the broader crypto media relations guide. The reactive pitch follows the same relationship rules, just compressed to a single paragraph sent in real time.

The comment bank: pre-building your reactive capability

The founders who land reactive coverage consistently have done one thing the rest have not: they have pre-written quotes on the ten to fifteen scenarios most likely to generate a breaking story in their vertical. This is the comment bank, and building it takes about two hours on a quiet afternoon.

For a DePIN protocol, the relevant scenarios might include: a major competitor's mainnet launch, a regulatory action on decentralised infrastructure, an energy or bandwidth pricing story, a large telecom announcing a competing product. For a cybersecurity or AI safety founder, the scenarios include: a major breach of a named institution, a new vulnerability class disclosure, an AI regulatory announcement from the EU or SEC, a nation-state attribution story.

For each scenario, draft two things: a two-to-three sentence attributable quote that takes a specific, defensible position, and one sentence of credential context. Review and refresh the bank quarterly. When a story breaks that matches a scenario, you pull the relevant quote, adjust two or three words to make it specific to the actual event, and send within the hour. The quality of a quote drafted calmly before a news cycle is almost always higher than one drafted in a panic while the story is live.

Build your comment bank nowOpen a shared doc. List your ten most likely breaking-news scenarios. Draft a two-to-three sentence attributable quote for each. Include one credential sentence. Share it with whoever approves quotes at your company and agree: these are pre-approved for same-day reactive use. That agreement is worth more than any media monitoring tool.

Where newsjacking goes wrong: the reputational risks

Newsjacking has a short list of failure modes, and each one is worth naming clearly because the downside is not just a missed pitch, it is a damaged relationship with a reporter you need.

Inserting on a tragedy or crisis

A protocol exploit that wiped user funds, a founder arrested, a rug pull affecting retail investors: these are not newsjacking opportunities for an outsider. Commenting on an industry crisis to earn coverage for your brand is read by journalists and readers as exactly what it is, and the reputational cost is not recoverable in the short term. If you have genuine expertise in crisis communications and can add something that actually helps affected users or the industry's response, the bar for that is very high. Most of the time, the right call is silence.

When the crisis is about your own protocol or your own team, that is a different and much more demanding situation entirely. The mechanics of that are in the crypto crisis communications guide.

Getting the facts wrong

A quote that mischaracterises what happened in a breaking story can run in a tier-1 publication under your name before you have a chance to correct it. The speed that makes reactive PR valuable also makes it risky. The solution is a firm rule: if you are not certain of the facts as reported, do not send a quote that assumes them. Send a more general position that holds regardless of the specific facts, or wait for the second news cycle when the picture is clearer.

Over-pitching the same story

Sending reactive comments to ten different journalists for the same story is not efficient, it is visible. Journalists talk to each other, especially in a small beat like crypto. If the same boilerplate quote appears in three competing pitches in one hour, you will be known for it. Pick two or three reporters whose readers most need your angle, and send a slightly different version to each, tailored to that publication's frame on the story.

Field ruleSpray-and-pray reactive pitching is indistinguishable from spam. Two targeted pitches to reporters you have a real relationship with will always outperform a ten-person blast, because the first two get read and the ten-person blast gets filtered.

Building the relationships that make newsjacking possible

None of this works without the underlying relationship layer. A cold reactive pitch to a journalist who does not know you will almost never land on deadline, because they have no reason to trust that your quote is accurate and attributable. The journalists who include you in their rapid-fire source calls are the ones you have already helped with a story, introduced to a contact, or given an exclusive that held up factually.

This is why reactive PR and proactive media relations are not separate programmes. They are the same programme at different speeds. The work you do building a genuine relationship with twelve to fifteen beat reporters, through the web3 PR campaigns that land them real stories over time, is what makes the reactive window accessible when it matters. A reporter who knows your name and trusts your quotes will reply to a reactive pitch in twenty minutes. A stranger will not reply at all.

For the specific mechanics of building those reporter relationships, the crypto media relations guide covers the full approach: which beats to prioritise, how to introduce yourself before you need something, and how to be a useful source even when you have no news of your own to share. Newsjacking is the fastest possible return on that relationship investment.

The verdict on speed, relevance and risk

Newsjacking is not a shortcut. It is a capability that takes preparation to access. The brands that earn consistent reactive coverage in CoinDesk, Decrypt, Blockworks, Forbes and The Block are not just lucky. They have monitoring in place, a comment bank built, a short list of trusted reporter relationships, and an approval process that fits inside a two-hour window. They also know when not to pitch, which is at least as important as knowing when to.

The economics make the investment worth it. A well-placed reactive comment in a tier-1 breaking story reaches an audience your own press release rarely touches, carries the editorial credibility of the publication, and costs nothing beyond the relationship capital you have already built. For a fractional operator running at $5K to $12K per month, reactive PR is one of the highest-ROI activities in the programme, because the output scales with preparation rather than with budget. Build the bank, keep the relationships warm, and when the next story breaks in your vertical, you will be the source who shows up in the first draft instead of the one reading the published piece and wishing you had moved faster.

SJ
Shilika Jain

Fractional PR and media relations for Web3, AI, DePIN and cybersecurity founders. 50+ protocols placed across Forbes, CoinDesk, Cointelegraph, Decrypt, The Block, Blockworks and AI Magazine, with reactive coverage in breaking-news cycles across crypto, AI regulation and DeFi. View full profile → · Book a 30-min teardown →

Frequently asked questions

How do you get media coverage in Web3 without a launch?
Newsjacking is the most reliable method: monitor breaking stories in your vertical, offer a named journalist a usable expert comment within two hours of the story breaking, and keep the pitch under 120 words. You are not pitching yourself, you are helping the journalist make their existing story better with a credible source. The prerequisite is a real prior relationship with the reporter, built through the media relations work done before any news cycle starts.
How fast do you need to move for a reactive crypto pitch?
Under two hours from the story breaking publicly, ideally under sixty minutes. Crypto journalists on a breaking story have short deadlines and will file with whatever named sources they can reach fast. If your pitch arrives after the piece is published, the window is closed. The way to move that fast is preparation: a comment bank of pre-approved quotes and a monitoring stack that surfaces relevant stories in real time, not a morning email digest.
What should a reactive comment pitch look like?
One specific reference to the story you saw, a two-to-four sentence attributable quote with a clear position, one sentence of credential, and an offer to call if useful. Total length under 120 words. No company bios, no background sections, no bullet points. Journalists on deadline need one usable quote from a credible source, and the pitch that gives them that clearly and fast will almost always win over a longer, more polished pitch that arrives late.
When should you not newsjack a crypto story?
Skip it when the story involves user harm, a rug pull, a founder arrest, or any crisis where inserting your brand for coverage reads as opportunistic. Also skip it when you are not certain of the facts as reported, when your comment would be generic enough to apply to any industry, or when you do not have a prior relationship with any reporter covering the story. Over-pitching a single breaking story to ten journalists simultaneously is also a mistake: it is visible in a small beat and will cost you credibility with all of them.
How is newsjacking different from a press release?
A press release announces something your company did. A reactive pitch offers expertise on something that already happened elsewhere. The press release requires a news peg of your own; the reactive pitch requires a news peg in the market. Reactive pitching also requires an existing reporter relationship to work on deadline, while a release can be sent cold via wire and still earn pickup through aggregators. Both have a place in a full web3 PR campaign, but newsjacking is faster, lower-cost, and often lands in publications a standard release would never reach.

Ready to build a reactive PR capability? Start with web3 PR campaigns for the full media relations programme, then read how to pitch Cointelegraph for the outlet-specific mechanics. The full playbook library covers pricing, crisis comms and the AI-search layer.