The press release has been declared dead roughly once a year for two decades, which is a good sign that the question is being asked badly. The release is not a strategy and never was. It is a document format with a narrow set of jobs, and most of the frustration in the category comes from firms buying it to do jobs it was never built for.
The useful question is not whether press releases still work. It is which specific things a release does that nothing else does, and whether you need any of those things right now. For most companies most of the time, the answer is no. For a small set of situations, the answer is unambiguously yes, and skipping the release would be a mistake.
What a wire actually buys
A distribution wire takes your text and pushes it to a network of subscribing outlets, databases, and aggregators. Understanding what that means in practice removes most of the confusion.
It buys a timestamped public record. The release exists at a fixed moment, in a form you wrote, on services that archive it. For anything with a legal or fiduciary dimension, that record is the product.
It buys database presence. Wire content flows into financial data terminals, company databases, and research tools that reporters, analysts, and diligence teams query. Someone looking you up later finds it.
It buys syndication. The release gets republished, usually verbatim, across affiliate sites and low-traffic portals. This is the part that generates impressive-looking reports and almost no value, and we have written about how that inflation works in how to choose a PR firm.
It does not buy journalism. No reporter is obligated to read a wire release, and most do not. The notion that distribution creates coverage is the single most expensive misunderstanding in the category.
When a release is the correct instrument
There are situations where a release is not optional, and situations where it is genuinely the most efficient tool. They share a common shape: the goal is the record, not the readership.
Material corporate news at a public company. Disclosure obligations are the original reason wires exist. Earnings, guidance changes, executive transitions, and anything that moves the position of a public security has a compliance dimension, and counsel will tell you the release is required. This is not a marketing decision.
Funding rounds and M&A. A funding announcement has a defined audience that will actively look for it: competitors, recruits, prospective customers, and the next round’s investors. The release establishes the canonical facts, the correct spelling of everyone’s name, the exact amount, and the participating firms. Reporters covering the round will want that document even if they never quote it. It also feeds the funding databases that become the permanent record.
Legal notices and regulatory filings. Class action notices, recalls, settlement announcements, and required public disclosures use the wire because the wire is the accepted channel for demonstrating that notice was given.
Crisis and correction. When something has gone wrong and the facts are contested, a release puts your version on the record at a specific time, in language your counsel approved. Whether or not anyone quotes it, the document exists and its timestamp matters.
Awards, certifications, and contract wins in regulated or procurement-heavy sectors. In defense, healthcare systems, and government contracting, a public record of a contract award is often the thing partners and procurement officers expect to find.
The pattern across all five: you are creating a document of record with a specific downstream consumer. That is a real job, and the wire does it well.
When a release is wasted money
The failure cases are equally consistent. A release is wasted when the goal is coverage and the news is not, by any reasonable standard, news.
A new website. A rebrand. A new hire below the C-suite. A partnership with no disclosed terms. A minor product update. A milestone that is only meaningful internally, like a customer count crossing a round number. An executive’s opinion about an industry trend. A report your marketing team produced with no novel data.
None of these are stories, and putting them on a wire does not make them stories. What it produces is a set of syndicated URLs on domains nobody reads, a report showing a large impressions figure, and the persistent belief that PR is not working.
The tell is simple. If you cannot name the specific reporter who would want this and explain why their editor would run it, a release will not fix that. The problem is upstream of distribution.
Wires versus editorial pitching
These are not competing options. They do different things, and the confusion between them is where budgets go to die.
A wire is broadcast. One text, no targeting, no relationship, no editorial judgement applied. Its output is a record and a database entry. Its cost is modest and predictable.
An editorial pitch is targeted. A specific angle to a specific reporter on a specific beat, timed to their cycle, with a named source available to speak. Its output, when it works, is a piece of journalism written by someone else, which carries credibility a release structurally cannot. Its cost is labor, and its outcome is never certain, because the publication decides.
The practical relationship between them: for genuinely newsworthy events like a funding round, you generally want both. The release establishes the record, and the pitch, which should go out under embargo to selected reporters ahead of the release, is what actually produces coverage. Firms that send only the release and wait get syndication. Firms that pitch first and release at the same moment get articles.
For everything that is not a defined news event, skip the release entirely and put the budget into building a story worth pitching. That is the work behind our digital and print PR engagements, and it looks nothing like distribution volume.
What changed, and what did not
Two things genuinely changed over the last several years.
Newsroom headcount contracted, which means fewer reporters are processing more inbound. The share of releases that get read has fallen accordingly, and the tolerance for non-news is lower than it was.
Machine consumption grew. Language models and answer engines ingest published text, and wire content is published text on many domains. This has produced a theory that wire distribution is now valuable for AI visibility. It mostly is not, for a reason worth understanding: syndicated copies are the same text repeated, not independent sources agreeing. Systems weight corroboration between sources that do not share an author, and a wire network fails that test by construction. We laid out the mechanics in press coverage and AI search visibility.
What did not change is the underlying exchange. Reporters need stories. A release is not a story. It is a set of facts, formatted for the record, which a story can be built from if a story exists.
If you are sending one, send a good one
Most releases are badly built, and the failures are consistent enough to be worth listing. A release exists to be the authoritative record, which means its job is accuracy and retrievability, not persuasion.
Put the news in the headline, in plain language, with no wordplay. The headline will be read by people scanning a database index years from now. “Company raises $40 million Series B led by named investor” is correct. A clever construction that omits the amount is not.
Put every fact someone will need in the first two paragraphs. Amount, date, parties, what changes, who is affected. A reporter building a story from your release should be able to get the spine of it without reading further, and a database indexing it should be able to extract the entities without inference.
Quote people saying something. Executive quotes in most releases are interchangeable filler that no reporter has ever used. A quote earns its place if it explains a decision, states a position, or provides context a fact cannot. If it could appear in any company’s release, cut it.
State what is not being disclosed. Terms undisclosed, valuation undisclosed. Saying so explicitly stops reporters from chasing it and stops readers from assuming an omission is evasion.
Include a boilerplate that is accurate and current. It is the paragraph most likely to be copied verbatim into a database and the one most companies have not updated in three years.
Include a real contact who will answer. A press contact address that routes nowhere is the most common own goal in the format.
A working rule
Before commissioning a release, answer three questions in writing.
Who specifically is going to look for this document, and when? If the answer is a diligence team, a regulator, a database, or an investor six months from now, the release is doing its job.
Is there a legal, fiduciary, or contractual reason this needs a public timestamp? If yes, the decision is made and it is not a marketing decision.
If neither, what is the story, and which reporter wants it? If you can answer that, pitch it. If you cannot, the release will not rescue it, and the money is better spent finding out whether a story exists at all.
The honest summary
Press releases still work at the thing they were designed for, which is creating a public record with a timestamp for an audience that will come looking for it. They have never worked as a mechanism for generating coverage, and the wire industry’s reporting conventions have obscured that for a long time.
Use a release for funding, M&A, disclosure, legal notice, and crisis. Use editorial pitching for everything you actually want written about you. Sending a release and calling it PR is how most of the disappointment in this category gets manufactured.
The PR Summit Editorial writes for founders, partners, and principals on the editorial work behind tier-1 coverage.