Most SaaS companies think their PR problem is reach. It usually isn't. The problem is that tens of thousands of companies sell software to businesses, most describe themselves in the same six words, and a very small number of reporters are paid to sort through them.
This guide covers what makes SaaS PR different from consumer or enterprise-hardware PR, who actually writes about software, which announcements clear the bar, and where founders get themselves into trouble.
What makes SaaS PR different
Three structural things.
Your audience is small and specific. If you sell revenue-ops software to mid-market CFOs, a trade newsletter with 18,000 subscribers is worth more than a general tech site with two million monthly readers. Impressions are the wrong metric. The right question is: did the people who sign the check see it, and did it make your next sales call easier?
Your product ships continuously. Software teams release weekly. Journalists cover news, and a feature is almost never news. The gap between "we shipped something" and "someone should write about this" is the single most common source of frustration on SaaS marketing teams.
Your competitors say the same thing you do. Category language collapses fast in software. If you can swap your competitor's name into your positioning paragraph and it still reads fine, you don't have a pitch. You have a description.
The outlets and beats that matter
Think in four layers rather than a single wish list topped by TechCrunch.
Tech and business press. TechCrunch, VentureBeat, Business Insider, Axios, Forbes, Fortune, and The Information cover funding, acquisitions, leadership changes, and occasionally a product with a genuinely new shape. These are the names your board recognizes. They are also the hardest to reach and the least likely to drive pipeline on their own.
Vertical trades, usually your best return. Who you sell to determines your outlet list:
- Selling to marketers: Adweek, Digiday, MarTech, Marketing Brew
- Selling to developers and IT: The New Stack, InfoWorld, The Register, SD Times
- Selling to HR and people teams: HR Brew, HR Dive, Human Resource Executive
- Selling to healthcare: Fierce Healthcare, Healthcare Dive, MedCity News
- Selling to finance and banking: American Banker, CFO Dive, Payments Dive
Newsletters and analysts. SaaStr, Lenny's Newsletter, category-specific Substacks, and boutique analyst shops shape how buyers talk about categories. They rarely take a press release, but they do take a good conversation and a real data set.
Community surfaces. Hacker News, relevant subreddits, and Product Hunt are not press, but they produce the traffic spikes founders often mistake for coverage. Useful, fine to pursue, not a substitute for a media strategy.
Pitch the person, not the masthead. A reporter who has written about procurement software three times this quarter is a live target. The outlet's general news desk is not. If you don't have that list yet, start with building a media list and work outward from bylines you can actually cite.
Announcement types that land
Ranked roughly by how often they produce a story:
- Funding, with real specifics. Amount, lead investor, and what changes because of it. Vague "strategic investment" language gets ignored. Use a funding announcement template so the facts a reporter needs sit in the first paragraph.
- Acquisitions, in either direction, including small acqui-hires with a named team.
- Named customer wins, if the customer is recognizable and has approved being named in writing.
- Pricing-model changes. Moving from seat-based to usage-based pricing, or publishing prices in a category that hides them, is a legitimate story about how a market works.
- Original data from your own product. Aggregated, anonymized benchmarks from your user base are the most reliably coverable thing a SaaS company owns, because no one else has the data.
- Senior hires from companies your readers know.
What almost never lands: feature releases, integrations, minor partnerships, award wins, rebrands, anniversaries, and reports that summarize a survey of 150 of your own customers and conclude your category is important. If you're unsure which side of the line you're on, run it through the newsworthiness test before you spend money.
A product launch can land, but only when the product does something that didn't exist, serves a new buyer, or changes the price of something. Structure it properly with a product launch template and lead with the change, not the feature list.
Credibility traps specific to SaaS
Customer names. Never put a customer in a release without written approval from someone authorized to give it. Enterprise legal teams take this seriously, and "our champion said it was fine on a call" has ended partnerships.
Metrics you can't substantiate. If you cite ARR, growth rate, or user counts, assume a reporter will ask how it's calculated. Percentage growth off a tiny base is a known tell, and business reporters have seen it thousands of times. Describing the shape of growth honestly beats a number you have to walk back.
Security and compliance language. "SOC 2 compliant" and "SOC 2 Type II audited with a report available" are different claims. So are "HIPAA compliant" and "supports HIPAA-covered workflows under a BAA." Misstating certification status is a real legal exposure, not a copywriting nit. Have counsel or your compliance lead sign off on that paragraph.
Analyst and review-site mentions. Gartner, Forrester, and G2 all have rules about how their marks, rankings, and quotes may be used in public materials. Check the licensing terms before a logo or a quoted ranking goes into a release.
Competitive claims. Naming a competitor and asserting you're faster or cheaper moves you into comparative-advertising territory, where substantiation standards apply. Get legal review.
AI claims. If your product uses a third-party model, saying you "built an AI engine" is the kind of overstatement that gets a founder quietly blacklisted by a skeptical reporter.
A cadence you can actually sustain
For a seed-to-Series-B SaaS company, a realistic year looks like four to eight genuine announcements, not one a month. Fill the gaps with things that don't require a news peg.
- Quarterly: one substantive announcement, such as funding, an acquisition, a major customer, or a data release.
- Monthly: one owned asset with outward pull, like a benchmark post, a teardown, or a founder essay with a real argument.
- Weekly: reactive commentary. Respond to source requests, comment on category news, be genuinely available to two or three reporters who cover your space.
That rhythm matters more than any single hit. Reporters cover companies they recognize, and recognition comes from showing up usefully between announcements. What you should expect from all of it is covered honestly in PR for startups by stage. The short version is that early coverage is thinner and slower than founders plan for.
One caution worth repeating: distributing a release puts your news on the record and makes it findable. It does not make anyone write about you. Those are two separate jobs, and the second one is done by pitching humans.
See what a distributed SaaS announcement actually involves. [Here's how it works](/how-it-works).