“I can tell in the first line whether you’ve read a word I’ve written.” A reporter who covers enterprise software told me that, and it is the entire problem with how most people pitch tech press, compressed into one sentence. Tech reporters at the outlets people actually want, the TechCrunches and The Verges and the serious trade desks, get hundreds of pitches a week and open a small fraction of them. The deciding factor is rarely the quality of your product. It is whether the first line proves you know who you are writing to and have an actual story for them. Get that wrong and you are noise. Get it right and you are one of the few emails they open.
I have spent years building and working a network that now runs past 1,200 journalist relationships, and the tech beat is its own animal. Tech reporters are pattern-matchers under deadline. They have seen every “world-changing platform” pitch and they delete them on reflex, because a product existing is not news. What gets opened, read, and replied to follows a recognizable shape. Here are the five things that put your pitch in the small opened pile instead of the large ignored one.
Pitch a story, not a company
The fatal flaw in nine out of ten tech pitches is that they pitch the company. “We’re excited to announce our platform.” A reporter does not write about your company. They write about a trend, a conflict, a surprising number, a shift their readers need to understand, and they need your company to be the vehicle for one of those. Before you write a word, decide what story you are actually offering. Are you evidence of a trend. Do you have data nobody else has. Are you taking a contrarian position in a fight readers care about. The pitch is built around that story, and your product appears as the proof or the example, not the headline.
We once helped a small developer-tools company that kept getting ignored pitching “the easiest API for X.” We threw that out and pitched instead a data story: they had aggregated anonymized usage showing a measurable shift in how developers were adopting a certain pattern, with numbers. That reframe, from “our product” to “here is a trend, with data, that your readers are living through,” got a reporter at a major tech outlet to reply within the day. Same company, same product. The difference was that the second version contained a story a journalist could actually write.
Research the specific reporter, then prove it in line one
Every tech reporter has a beat, and most have an obsession inside that beat. Read their last several pieces. Notice not just the topics but the angles, what they keep coming back to, what they clearly find interesting. Then open your pitch with one specific line that could only have been written to them, referencing their actual work and connecting it to what you are offering. This is the line that the reporter quoted above was talking about. It is the difference between “Hi, I wanted to tell you about” and “Your piece last month on X argued Y, and I have data that complicates it.” The first gets deleted. The second gets read, because it proves you are not blasting a list.
Get the subject line and first two sentences right
Most pitches are judged before they are opened, on the subject line, and then again in the preview pane on the first sentence or two. So the subject line has to promise a specific, relevant story in a handful of words, not a vague company update. Then the first two sentences have to deliver the news and the relevance, fast, because a tech reporter scanning an inbox gives you seconds. Lead with the most newsworthy element, the number, the trend, the conflict, and make the relevance to their beat obvious immediately. Everything you would normally put in a warm-up paragraph should be cut. The reporter decides whether to keep reading inside the first two sentences, so put the strongest thing there.
Keep it short, concrete, and free of hype
Tech reporters have a finely tuned hype detector and the buzzwords trip it instantly. A pitch full of inflated language reads as a pitch with nothing real inside it, because the people with real news tend to state it plainly. Write the whole pitch in three short paragraphs: the story and why it matters now, the concrete proof (data, names, specifics), and a clear offer of what you can provide (an interview, the data, early access, assets). Strip every adjective that is not carrying information. Concrete and brief signals that you respect the reporter’s time and that your news can stand without inflation, which is exactly the impression that gets a reply.
Make the reporter’s job easy and follow up once
End the pitch by reducing the reporter’s work to almost nothing. Offer exactly what they would need to write the story: a quick interview window, the underlying data, high-resolution assets, a named source they can quote, early access if relevant. The easier you make it for them to say yes and get to work, the more likely they are to. Then, if you hear nothing, send a single brief follow-up after a few business days that adds a new element, a fresh data point or a timely peg, rather than just “checking in.” One good follow-up is professional. A string of them is why some senders end up filtered. After the second message goes unanswered, move to the next reporter whose beat fits.
Pitching tech reporters in 2026 is not about volume or cleverness. It is about respecting that the person on the other end is a busy expert who has seen everything, and giving them a real story, addressed specifically to them, that they can write with minimal effort. Do that consistently and you stop being one of the hundreds of pitches they ignore and start being one of the few senders whose name in the inbox means there might actually be a story worth opening.