TechCrunch’s own contributor guidance has long pointed startups at its tips inbox, and editors there have described receiving hundreds of pitches a day. Run the arithmetic on a desk of a dozen writers and the conclusion writes itself: your email gets a skim measured in seconds, and the skim decides everything. Getting featured in tech blogs is not a volume game against those odds. It is a pattern-matching game, and the patterns that survive the skim are learnable.
This piece gives you the target map, the five pitch patterns that keep working, and the mechanics that keep a good story from dying in the subject line.
What tech editors delete on sight
Start with the negative space, because most pitches die from self-inflicted wounds. Editors delete anything that opens with the company’s founding story instead of the news. They delete superlatives without evidence, the first, the fastest, the leading, because every inbox contains forty of those a day. They delete pitches addressed to the wrong beat, which signals the sender never read the outlet. And they delete anything that reads like it went to five hundred recipients, because it did, and reverse-engineering a mass email takes one glance.
The deeper pattern behind all four: editors buy stories, not companies. A pitch that describes what your startup is gives the editor homework. A pitch that hands them a story, with tension, numbers, and a reason it matters this week, does their job for them. Every pattern that works in the next sections is a variation on doing the editor’s job for them.
A useful exercise before you write a single email: read the last ten pieces the target writer published and reverse-engineer the pitch that produced each one. Was it a funding announcement dressed in a trend? A data study? A founder essay? Most writers have two or three story shapes they return to, visible in a 15-minute scan of their archive. Pitching a writer their own favorite shape, loaded with your facts, is the highest-percentage move in media outreach, and almost nobody does the scan. The few who do stop sounding like supplicants and start sounding like colleagues with a tip.
One more deletion trigger that deserves its own paragraph: the embargo abuse. Founders who mark routine news “embargoed” to manufacture importance, or who break their own embargo by posting on LinkedIn before the agreed time, end up on informal blacklists that outlive the company. Embargoes are a tool for coordinating genuine news across desks. Used for a feature release nobody else would cover anyway, they read as either naivety or manipulation, and both get the same silence.
The three-tier pitch ladder
Map your targets into three tiers before sending anything. Tier one is the national tech press, TechCrunch, The Verge, Ars Technica, Wired, where coverage moves credibility but competition is brutal and news pegs are mandatory. Tier two is the trade and vertical layer: outlets covering your specific industry, developer publications, and the regional tech press like GeekWire or the business journals, where editors actively need stories from their niche. Tier three is the long tail with outsized conversion: niche blogs, substantial newsletters, and community publications your actual buyers read.
We call working these in sequence the three-tier pitch ladder, and the order is the strategy. Tier three says yes fastest and builds your clip file. Tier two coverage is what tier one writers find when they search you before replying. By the time you pitch tier one with a real news moment, the search results validate you instead of embarrassing you. Founders who invert the ladder, months chasing TechCrunch with nothing to show, get neither the feature nor the fallback coverage they could have banked.
The ladder also changes what you count as a win. A mention in a developer newsletter with 9,000 subscribers who match your exact buyer can produce more signups than a tier-one feature that delivers a traffic spike of tourists. Track conversions per placement, not domain authority per placement, and the long tail starts earning the respect your vanity metrics were denying it. The tier-one feature still matters, for credibility, for hiring, for the citation layer AI engines read, but it is the roof of the house, not the foundation.
Build the target list with the same discipline. For each tier, name the specific writers, their beats, their last three relevant pieces, and the story shape they favor. Twenty well-researched names beat two hundred scraped emails in every measurable way, including the one that compounds: writers talk to each other, and a reputation for relevant, honest pitches travels between desks the same way the spam reputation does.
The 5 pitch patterns that work
Pattern one is exclusive data. Pull a finding from your product’s aggregate usage or run an original survey, and offer it to one outlet first. Data pitches work because they give the writer a chartable fact no competitor has. The bar for the finding is surprise, not size: a sample of 400 companies showing a counterintuitive split beats a sample of 40,000 confirming what everyone assumed. State the methodology in two sentences and disclose the sample honestly, because the first commenter will check and the writer knows it. Pattern two is the contrarian founder take, a defensible argument against something the industry assumes, offered as commentary or a guest post. Pattern three is the news hijack: when a giant ships, breaks, or gets regulated, the writer covering it needs informed reaction quotes within hours, and the founder who shows up fast with a sharp take gets featured in tech blogs all year on this pattern alone.
Pattern four is the customer story with numbers, a named customer, a measurable before-and-after, and a trend it illustrates. The trend wrapper matters more than founders expect: one customer cutting onboarding time in half is an anecdote, but the same customer as the lead example of a shift every writer in the beat has been hearing about becomes the piece that names the shift. Pattern five is the build-in-public teardown: an honest account of something that failed, cost numbers included, which works because it is the rarest thing in an inbox full of victory laps.
Notice that a product launch is absent. Launches earn coverage when wrapped in one of the five, the data behind the launch, the contrarian thesis that produced it, the customer already using it. Naked launch announcements are tier-three material at best.
Each pattern has a preparation cost worth budgeting honestly. Exclusive data needs a defensible methodology and a chart someone else could rebuild from your description. The contrarian take needs to survive the strongest counterargument, stated fairly, inside the piece itself. The news hijack needs a response system, alerts on your five storylines and a founder reachable within the hour. The customer story needs the customer’s written approval before the pitch goes out, not after the writer says yes; chasing approvals post-commitment is how startups burn their first tier-one relationship. The teardown needs real numbers and a thicker skin than most founders budget for, because the comments will be part of the deal.
The patterns also stack across a year. The data study from January becomes the credibility that lands the contrarian guest post in March, which becomes the reason a reporter calls you for reaction quotes in June, which becomes the relationship that takes your customer story in October. Treat the five patterns as a rotation, not a menu you order from once, and the press function starts compounding the way content does.
Mechanics: subject lines, timing, follow-up
Subject lines should state the story, not the request: “Data: 40% of solo devs ship with AI-written tests” beats “Pitch: exciting startup in the dev tools space” every day of the week. Keep the body under 150 words: the story in two sentences, the evidence in two more, what you are offering (exclusive, embargo, interview access), and one link to a press page with screenshots, logos, and founder bios. Attachments get your domain flagged; links do not.
Send Tuesday through Thursday, mid-morning in the writer’s time zone, and never on the day a major industry event is consuming every desk. Follow up exactly once after three or four business days with one added fact. Track everything in a simple sheet: writer, outlet, pattern used, response. After twenty sends, the sheet tells you which patterns your stories actually support, and that feedback loop, not any single placement, is what turns press from a slot machine into a channel.
Prepare for the yes as carefully as the pitch. When a writer replies with questions, answer the same day, in quotable sentences, with numbers they can publish. Offer a 15-minute call but never require one; plenty of pieces get written entirely over email, and forcing a call adds friction to a person juggling six deadlines. Have the press page live before the first send: product screenshots at publishable resolution, founder headshots, a one-paragraph boilerplate, and your funding and customer numbers stated without hedging. Every hour a writer spends hunting for an asset is an hour the story drifts toward the kill file.
One last calibration: getting featured in tech blogs is a lagging indicator of having something worth covering, and no mechanics compensate for an empty cupboard. If twenty disciplined sends across two tiers produce nothing, the market is returning data about the story, not about your subject lines. Go build the data study, sign the referenceable customer, or sharpen the thesis, then come back. The inbox will still be there, and so will the patterns.
You now have the ladder, the patterns, and the mechanics. The honest question left is the one only you can answer: which of the five stories does your company have the receipts to tell this month?