Pitching TechCrunch Crime Reporters: Vertical Press Strategy
TechCrunch doesn't run a traditional police blotter. Its crime coverage lives at the intersection of cybercrime, platform abuse, fraud, and legal enforcement — and it's reported by security and consumer-tech specialists.
Pitch the crime beat here as a technology-crime story with documents attached. That framing is what gets read.
Editorial Scope: What TechCrunch Covers in Crime#
Coverage clusters into four lanes: data breaches and ransomware, fraud and scams on platforms, surveillance and spyware, and indictments or regulatory enforcement against tech actors.
Consumer harm stories qualify only when they scale beyond one victim. A single phishing complaint won't land; a pattern affecting thousands of users will.
💡 Vertical Pro Tip: TechCrunch Crime reporters rarely cover crime as a law-and-order story. Reframe every pitch as "the technology failure or exploit that enabled it" — that's the actual beat.
Identifying Active Writers on the TechCrunch Crime Reporters List#
Our TechCrunch Crime reporters list shows three-plus active bylines with distinct lanes. Match the reporter to the story, not the other way around.
Zack Whittaker owns security and cybercrime: breaches, ransomware, spyware, and court filings. Mike Butcher covers European enforcement, startup fraud, and disinformation. Ivan Mehta tracks consumer app scams, account takeovers, and platform-level abuse.
| Reporter | Lead With | Avoid |
|---|---|---|
| Zack Whittaker | Breach notices, court records, researcher findings, victim corroboration | Vague "cyberattack" alerts, vendor marketing |
| Mike Butcher | EU/UK regulatory action, startup misrepresentation, deepfakes | US-only local crime, non-European policy minutiae |
| Ivan Mehta | App store fraud, phishing flows, platform policy gaps | Enterprise security architecture, geopolitical framing |
For broader bench context, pair this with the TechCrunch Crime reporters list and cross-check recent bylines before sending.
Angles & Data Points That Resonate With TechCrunch Crime Journalists#
Specificity wins. Lead with the number, the document, or the named victim class — then the implication.
Strong angles: a leaked internal notice, a documented scam campaign, a court filing revealing a platform's liability, or original data quantifying harm.
Weak angles: "experts warn," unsourced trend predictions, and anything where the primary source is a press release.
| Factor | Recommended Strategy | What Gets Ignored |
|---|---|---|
| Subject line | Reporter name + concrete fact ("2.3M records") | "Story idea" or "Quick question" |
| Evidence | Link to primary docs, filings, or datasets | Attachments and PDFs |
| Timing | Same-day for breach notices; pre-brief for filings | Weeks-old news cycles |
| Spokesperson | Named researcher, victim, or counsel | Anonymous "industry sources" |
| Framing | Specific failure or exploit | Generic "cyber is scary" narratives |
| Follow-up | One nudge after 48 hours | Repeated same-day pinging |
TechCrunch Crime journalists consistently reward first-party evidence over commentary. If you can't hand over a document or a dataset, the story isn't ready.
Outreach Protocols & Accessing TechCrunch Crime Journalists Contacts#
Email is the primary channel — direct, no attachments, minimal formatting. Use publicly listed addresses from our directory rather than guessing patterns.
When accessing TechCrunch Crime journalists contacts in our database, verify beat and recency first. A reporter who last filed on crypto five months ago is likely the wrong desk.
State embargo and exclusivity explicitly in line one. If the story is already out, say so — it changes the calculation entirely.
Offer a named, quoted source and a corroborating second source. Wire-ready pitches get triaged faster than pitches promising "more details on request."
Expect a compressed window: security-driven stories move in hours, not days. Build a same-day response capability before you send.
Fast-Action Pitch Checklist for Crime#
- ☐ Subject line contains a verified fact, not a tease
- ☐ Primary document or dataset linked (not attached)
- ☐ Reporter matched to lane: Whittaker / Butcher / Mehta
- ☐ Scale established — why this affects many, not one
- ☐ Named source available on the record within two hours
- ☐ Embargo and exclusivity stated in the first sentence
- ☐ Every claim attributable to a source or record
- ☐ One follow-up scheduled for 48 hours out
💡 Vertical Pro Tip: Send the breach notice, the filing, or the raw data in the first email. TechCrunch's security desk routinely publishes from documents alone — withholding them to secure a call usually costs you the story.