Somewhere in the first year of most companies, a founder says "maybe we should hold a press conference." It is almost always the wrong instinct, and the reason is worth understanding. The right instinct, a briefing, is sitting right next to it and costs a tenth as much.
The formats, distinguished
A press conference is an open, announced event where you make a statement and take questions from any journalist who shows up. It is a broadcast format. Its defining features are that attendance is uncontrolled, questions are public, and every reporter in the room hears every other reporter's question and your answer.
A press briefing is a smaller, invitation-based session, often one-to-one or one-to-few, where you walk reporters through something in depth ahead of or alongside an announcement. Questions are private to that conversation. It is closer to a structured interview than to an event.
An analyst briefing is the same format aimed at industry analysts and researchers rather than journalists. Different audience, different goal: you're not chasing a story, you're trying to be correctly represented in the reports your buyers read.
A media roundtable sits between them: a handful of reporters, a topic, a couple of executives, and a real discussion. Useful occasionally, hard to do well.
The critical structural difference: a press conference makes your news compete for its own coverage in a room where the least friendly question sets the tone for everyone. A briefing gives each reporter something they can use that the others don't have in quite the same shape.
Why most companies shouldn't hold a press conference
The format exists to solve one specific problem: a large number of journalists urgently need the same information at the same moment, and there is no way to serve them individually. Regulators, public agencies, sports teams, and companies in the middle of a crisis have that problem. A Series A software company announcing a product does not.
What actually goes wrong when a company holds one anyway:
- Nobody comes. The realistic attendance for a non-crisis announcement from a company most reporters haven't heard of is somewhere between zero and three, and two of the three are freelancers hoping for lunch. An empty room is not a neutral outcome. It is a story your team tells itself about how nobody cares.
- You lose the exclusivity that makes reporters invest. Everyone in the room gets the same thing simultaneously, so no one has a reason to write more than a short item. You've deliberately given up the advantage you'd have had by offering depth to one outlet.
- The Q&A is uncontrolled and public. One reporter with an unrelated grievance about a layoff, a lawsuit, or a customer complaint reframes the entire event for everyone present. In a one-to-one briefing that question gets asked too, but it doesn't contaminate five other conversations.
- The cost is absurd relative to the return. Venue, AV, staffing, travel, rehearsal, and a week of your executives' attention, to produce coverage that a set of briefings plus a distributed release would have produced for a fraction of it.
The blunt test: if you cannot name, right now, six specific reporters who cover your beat closely enough to clear a morning for you, you do not have a press conference. You have an announcement, and distribution plus targeted pitching is the correct shape for it.
Legitimate exceptions exist. Crisis response where a single authoritative statement needs to reach everyone at once. A genuinely major, widely anticipated event, such as a large public-company milestone, a regulatory decision, or a merger with real market consequence. An announcement at a conference where the press corps is already assembled and you're borrowing their attention rather than asking for a trip. That last one is by far the most common good reason.
Running a briefing that's actually worth attending
A briefing works because the reporter leaves with material they couldn't have gotten from your press release. If yours is a slide walkthrough of the release, you've wasted an hour of a working journalist's day and they will remember.
Before:
- Invite selectively. Six to twelve reporters who genuinely cover the specific topic, chosen from a real list, not a scraped one. If you're guessing at who covers what, fix the list first. A briefing invitation to the wrong beat is more annoying than a bad pitch, because it asks for more.
- Say what it is in the invite. Topic, date, duration, who'll be on it, whether it's under embargo, and what they'll get. "30 minutes with our CTO and the head of data at a customer, walking through eighteen months of before-and-after numbers, embargoed until Tuesday 9am ET" is an invitation. "Briefing about our exciting new platform" is not.
- Offer one-to-one as the default. Most reporters prefer it, and the group version should be reserved for cases where a shared discussion genuinely adds something.
- Send materials in advance, not during. Reporters read faster than you talk. Give them the deck, the data, and the fact sheet beforehand so the time is spent on questions.
During:
- Ten minutes of presentation, twenty of questions. If you flip that ratio, you've held a webinar.
- Bring someone who isn't an executive. The engineer who built it, the customer who uses it, the clinician who changed their workflow. Operators give better quotes than founders, every time.
- Have the specifics on hand. Pricing, headcount, timelines, the methodology behind any number you cite. "I'll follow up on that" is acceptable once, not five times.
- Answer the unflattering question directly. The churn number, the failed pilot, the competitor who's ahead on one dimension. Evading in a briefing is worse than in a press conference, because it's a conversation and evasion is obvious at conversational range.
- State the ground rules at the top, clearly. Whether it's on the record, whether anything is embargoed and until when, and who can be quoted by name. Set that before anyone starts talking, not after something slips out.
After: send the follow-ups you promised within hours, not days, and then leave them alone. One check-in before the embargo lifts is plenty.
Analyst briefings are a different job
Industry analysts are not journalists and the goals don't overlap. Analysts are writing reference material that your buyers, and sometimes your buyers' procurement teams, will read for the next year or two. They want architecture, roadmap, pricing model, customer counts, and where you genuinely don't compete, and they are largely immune to narrative.
Two practical notes. Being accurately described in an analyst's category map is often worth more to enterprise pipeline than a press hit, and it is far more achievable for an unknown company. And a briefing is not a sales call: analysts have seen every pitch deck ever built, and the fastest way to be dismissed is to treat them as a prospect.
Virtual, and why it's usually better
For briefings, video is the default and that's a gift. It removes travel from both sides, which is the single biggest reason reporters decline, and it lets you run eight thirty-minute one-to-ones across two days instead of asking twelve people to fly somewhere.
Keep it simple: a calendar link with generous options, a recognizable video platform rather than something proprietary, no registration form, no marketing automation, and camera-on as an invitation rather than a requirement. Record only with explicit permission, and never record a briefing you've described as on background.
If you were considering a press conference and land on ten virtual briefings instead, you have almost certainly made the right trade: more coverage, better coverage, a fraction of the cost, and no empty room. Pair them with a release on the wire so the news is on the record for everyone you didn't brief, and our templates cover the release itself.
Need the announcement on the record behind your briefings? [See how RepuPR works](/how-it-works).