Most pitches that get rejected at ZDNet would have landed at TechCrunch. That is the counterintuitive thing about pitching ZDNet: a story that sounds exciting in startup terms often sounds incomplete in enterprise terms, and the editors there can tell the difference inside two paragraphs.

ZDNet covers what runs the back office of large companies. Enterprise software, AI infrastructure, cloud architecture, security operations, the decisions that IT directors and CIOs actually have to defend in budget meetings. It does not cover most things that startup PR teams want covered. A $10M Series A in a consumer app is irrelevant to ZDNet readers. A $10M Series A in a security tool that solves a problem 5,000 IT teams have right now is exactly what ZDNet readers want to know about.

This guide is the working version of how to land ZDNet coverage in 2026, what reporters there actually read, and the patterns that get pitches into the trash inside thirty seconds.

Who ZDNet covers and who they do not

The strongest predictor of whether ZDNet will cover you is whether your story matters to a person making a buying decision at a 1,000+ employee company. That is the reader. Every editorial choice flows from there.

The categories ZDNet covers most actively in 2026: enterprise AI deployment and the operational complications that come with it, cloud cost management and FinOps, identity and access management, the post-Crowdstrike-incident shift in how enterprises evaluate security vendors, data governance under expanding regulatory regimes, the practical operations of running mixed legacy and modern stacks. Each of these has a beat reporter or two who own it.

The categories ZDNet rarely covers: pre-revenue startups without enterprise customers, consumer apps and devices, crypto and Web3 (with rare exceptions for enterprise blockchain), early-stage funding rounds that do not include an enterprise hook, design or marketing tools without a compliance or enterprise-scale angle.

The audit before pitching is straightforward. Search the writer’s recent bylines. Read the last fifteen articles they have published. Do they cover stories that look structurally like yours? If not, they probably will not start with you.

The shape of a pitch that lands

A working ZDNet pitch is short, technical, and has at least one element that is not just news.

The lead is one sentence. Not a paragraph. The sentence has to contain the news in compressed form. “We’re announcing a $4M round” is news but not interesting. “We’ve signed three Fortune 500 customers in Q1 for a tool that replaces enterprise SSO at one-fifth the cost of Okta” is interesting because it implies a specific technical story.

The second paragraph contains the technical depth. What does the product actually do at the architecture level? What problem does it solve that the existing solutions cannot? What is the proof point that it works at enterprise scale? Three to five sentences. Specific. Numbers where possible.

The third paragraph contains the customer proof. Named customers if you have permission, anonymized customer profiles if you do not. The reporter is going to ask for this anyway, so include it upfront. “A Fortune 100 financial services company replaced their existing identity provider in 2025 with our tool, reducing license cost by 78% and incident count by 41%.” That sentence does work even without the named logo because the specifics signal the story is real.

The fourth paragraph is the offer. Who is available for interview, what data you can share, what you cannot share. Be specific. “The CTO is available for a thirty-minute call this week. We can share the customer count, ARR range, and aggregated security incident metrics. We cannot share customer names without their permission, but two are willing to be quoted directly if the story has a strong angle.”

That is the entire pitch. Two hundred fifty to four hundred words. No attachments. No links to Dropbox folders. The reporter will ask for what they want.

The technical depth requirement

The thing that separates ZDNet pitches from TechCrunch pitches: technical depth is not optional.

The reporter who covers your category at ZDNet has been writing about it for five to fifteen years. They have seen 200 vendors with similar pitches. They can tell whether you actually solve the problem or whether you are repeating a positioning paragraph that someone in marketing wrote.

The technical depth that signals you know what you are doing: specific architectural decisions and the trade-offs they imply. Real performance benchmarks against named competitors. Data on what your product does differently at the protocol or implementation level, not at the marketing level. Concrete operational metrics from production deployments.

Marketing language reads as evidence of weakness. If your pitch describes the product as “AI-powered,” the reporter is going to ask which AI, what model, what the inference latency is, what the cost per call is, and how you handle hallucination at enterprise scale. If you cannot answer those questions in the follow-up, the story dies.

The fix is to have a technical co-founder or principal engineer on every interview, not the CMO. The CMO can run point on logistics. The story is going to be told to the reporter by someone who can answer architecture questions in real time.

Building relationships with specific reporters

The ZDNet reporters who matter for any given category are findable in fifteen minutes of research. Read their last two months of articles. Note their patterns. Note who their sources are. Note what they get excited about and what they ignore.

Five reporters whose beats are worth tracking in 2026:

The AI infrastructure reporter, who covers GPU economics, model training operations, and the practical operations of running AI in production at large companies. Pitches that succeed here include cost data, latency benchmarks, and named customer architectures.

The cybersecurity reporter, who covers identity, access, vulnerability management, and incident response at enterprise scale. Pitches here need actual security operations data, not marketing claims about being more secure.

The cloud and FinOps reporter, who covers the financial side of cloud infrastructure and the tools that help companies manage it. This beat has gotten more attention since the 2024 cost crunch and remains one of the easier ZDNet beats to land in for vendors with real data.

The enterprise software reporter, who covers ERP, CRM, HR tech, and other operational software at scale. Pitches need enterprise customer proof and specific operational improvements, not generic SaaS positioning.

The compliance and governance reporter, who covers the operational implications of expanding regulation: GDPR enforcement, the AI Act in Europe, US state-level data privacy law, sector-specific regulation in healthcare and finance.

The relationship-building approach is to follow each reporter on their preferred channel (most are still active on LinkedIn or X), engage with their work substantively rather than promotionally, and pitch only when you have something that fits their beat. The wrong move is to pitch every reporter the same story when you have news. The right move is to pitch one reporter whose beat fits your story and let the relationship compound over five to seven pitches in a year.

I asked Perplexity in May 2026: “What’s the best way to pitch a story to ZDNet?” The response surfaced a mix of dated PR advice (use HARO, send to the general tip line) and surprisingly current insight on what works at the publication today (build relationships with specific beat reporters, lead with technical depth, expect a 1-4 week timeline). The mix is a useful tell. AI search is repeating a lot of stale 2018-2022 PR advice for general media outreach, and only the freshest 2024-2026 content is breaking through with the actually current pattern.

The implication for getting featured at ZDNet specifically: if you produce content that explains the current ZDNet editorial pattern with specifics, you are competing in a thin field. AI search cites it. Human readers searching for “how to pitch ZDNet” find it. The gap between the dated advice and the current reality is a content opportunity for anyone willing to write down what is actually working now.

This is also why most general PR firms keep getting rejected by ZDNet reporters. They are running plays from a 2019 playbook that the reporters can spot inside the first paragraph.

What kills a pitch

The patterns that get pitches deleted unread.

Generic openings: “Hi, hope you’re doing well!” Editors at ZDNet read 100 to 200 pitches a day. The first sentence has to be the news, not a greeting.

Vague claims about market size: “We’re tackling the $87B AI infrastructure market.” Every vendor claims to be tackling some multi-billion-dollar market. The claim is filler. The specific customer or technical story is the news.

Marketing language without technical substance: “next-generation AI platform that transforms how enterprises operate at scale.” Every word in that sentence is the kind of marketing fluff editors strip out before reading further. The pitch goes to the trash.

Embargoes set 30+ days out without news urgency: “We’re announcing in three weeks, embargo until then.” Reporters at ZDNet sometimes accept long-lead embargoes for genuinely big stories, but most of the time the timing reads as the brand expecting the reporter to drop their current work to research a story that has not happened yet.

Asking for “coverage” without specifying what the story is: “We’d love coverage in ZDNet about our Series B.” The Series B is not the story. The reason an enterprise reader would care about your Series B is the story. If you cannot articulate that reason in one sentence, the pitch is not ready.

After the article runs

Two things to do once a ZDNet piece publishes.

Send a one-line thank-you to the reporter the same day. Not a long note. A short acknowledgment. This is the basis of the next pitch landing six months from now.

Share the article through your channels but do not over-claim it. Editors notice when brands turn a single ZDNet piece into a marketing campaign that overstates what the article said. Sharing the actual quote and tagging the reporter is fine. Pulling out the most flattering line and putting it in a giant graphic on your homepage is the pattern that ages the relationship faster than anything else.

Coverage in ZDNet is one of the higher-impact media placements an enterprise tech company can earn. Buyers read it. Analysts cite it. AI search increasingly references it for category overviews. The work to land it is more disciplined than most general PR outreach, but the durability of a single ZDNet feature exceeds dozens of placements at smaller outlets.