Newsjacking is attaching your company to a story that is already moving: a breaking event, a regulatory decision, a competitor's stumble, a number everyone is suddenly arguing about. Done well, it gets a small company quoted next to large ones. Done badly, it produces the screenshot that follows a brand around for years.
The difference is almost never cleverness. It is standing, speed, and knowing which stories to leave alone.
Why it works at all
Reporters covering a developing story have a specific, temporary problem: they need someone credible to explain what it means, and they need that person before the story goes cold. For a few hours, the usual hierarchy of who gets quoted flattens. A founder who actually knows the subject and answers in twenty minutes beats a large company whose comms team needs two days of approvals.
That is the entire opportunity. You are not selling your product. You are solving a reporter's sourcing problem faster than anyone else.
The speed requirement
Assume the window is measured in hours, not days.
The first wave is the event itself, straight reporting with no outside commentary needed. That wave is not yours. The second wave, usually starting a few hours in and running through the following day, is analysis: what does this mean, who does it affect, what happens next. That is where an outside voice gets used.
By day three, the story has either been covered to exhaustion or moved into a slower explainer phase where long-lead outlets and trade publications take over. You can still enter there, but with a different offer: data, a customer example, a considered argument rather than a quick reaction.
Practically, this means the whole thing has to be pre-built. If your process requires assembling a media list after the news breaks, you have already lost. Keep a standing list of ten to twenty reporters who cover your category, which is how to build one, and keep approved spokesperson bios and a one-paragraph company description ready to paste.
The standing test
Before drafting anything, answer four questions honestly. Three yeses is the minimum.
- Do you know something about this that a general reporter does not? Not an opinion. Knowledge, drawn from your data, your customers, or your operational experience.
- Would a reader be unsurprised to see your company in this story? If your category has no obvious connection to the event, the connection you invent will read as opportunism, because it is.
- Can you say something specific? "This underscores the importance of security" is not a comment. It is throat-clearing, and no reporter has ever used it.
- Can you be wrong in public about this? Reactive commentary is made on incomplete information. If being wrong would be a serious problem, wait for the facts.
Failing the standing test is the normal outcome. Most news is not yours. The discipline of skipping is what makes the occasions you do enter credible.
What is off-limits
Some categories are not close calls.
- Deaths, injuries, disasters, and violence. No commercial angle is acceptable, including ones framed as helpful. The exception is organizations whose actual function is response, and even then the message is information, never positioning.
- Active crises where facts are unsettled. Commenting on an ongoing incident and being wrong is a lasting error.
- Anything requiring you to speculate about a named person's conduct. Legal exposure, and it reads badly regardless.
- Political flashpoints where your company has no stake. You will alienate part of your audience to gain nothing.
- A competitor's outage or breach. This one tempts everyone and almost always backfires. Reporters notice who is dancing, customers notice harder, and your own outage is coming eventually.
A useful gut check: imagine the reaction screenshot with your logo on it, posted by someone hostile. If that image is easy to picture, do not send.
A worked workflow
Say a regulator publishes new rules affecting how companies in your category handle customer data, and you build compliance tooling for exactly that.
Within the first hour. Read the primary source, not the coverage. Decide whether you clear the standing test. Pick one spokesperson and confirm they are available for the next several hours. An unreachable spokesperson kills more newsjacks than bad pitches do.
Hour one to two. Write three things: a two-sentence reaction that a reporter could quote verbatim, a short paragraph of context explaining the practical consequence, and one concrete specific, such as a number from your own operations, a customer scenario, or an implementation detail nobody outside the field would know. The specific is the reason you get used instead of someone else.
Hour two. Send to your standing list. Subject line names the story and your angle plainly. Body is short: who you are in one line, what you can speak to, the quotable sentence, and availability. No attachments. The mechanics of the pitch email matter more than usual here, because the reporter is reading it on a phone between calls.
Same day. Check the journalist source-request services, where reporters post exactly these needs during a big story. Publish your own take somewhere you control, such as a post or a note on your press page, so later-arriving reporters can find it.
Day two onward. If there is follow-through, offer the slower version: data, a walkthrough, a customer willing to speak. This is where a trade-press feature actually comes from.
The real risks
- Being wrong. Say what you know and label what you are guessing at. "Based on what has been published so far" is not weak. It is accurate, and reporters trust it.
- Over-selling. A comment that pivots to your product gets cut, and the reporter remembers. Mention the company once, in the attribution line.
- Getting quoted in a story you would rather not be in. Once you are on the record, you do not control the frame. Ask what the angle is before you answer anything sensitive.
- Crowding out your own news. Reactive work is cheap but it is not free. If it is consuming the hours your planned announcements need, the ratio is wrong.
- Habitual commenting. Companies that react to everything become background noise. A handful of well-chosen interventions a year does more than weekly reflexes.
When newsjacking is not the answer
If you have actual news of your own, do not dilute it by chasing someone else's story the same week. Run it through the newsworthiness test and give it a proper runway instead. Reactive commentary fills the space between announcements, but it does not replace having something to say.
Have news of your own worth putting on the record? [See how it works](/how-it-works).