Inside Dexerto: How to Pitch Dexerto Journalists & Win Product Coverage
Dexerto journalists do not cover technology the way TechCrunch does. They cover technology the way culture consumes it — through streamers, patches, platform policy, and the hardware in a creator's PC.
Founded in Dublin in 2015 as an esports outlet, Dexerto has evolved into a high-velocity gaming, streaming, and entertainment news engine with a global readership and a publishing cadence measured in hours, not weeks.
That single fact should reshape your entire pitch.
Editorial Focus & The Technology News Cycle at Dexerto#
Dexerto reporters operate in a breaking-news environment. A Twitch policy change, a Kick exclusivity deal, or an anti-cheat ban wave can generate three stories before a competitor files one.
Technology enters that cycle through the side door: platform APIs, moderation tooling, game engine updates, GPU launches, peripherals, and creator-facing software.
Pure infrastructure news — a Series A for a database company — is a hard sell unless you can attach it to a named creator, a live product, or a measurable change in how games are played.
💡 Editorial Pro Tip: Dexerto's newsroom rewards the second-order angle. Don't pitch "we raised $8M." Pitch "we raised $8M and here's why 40,000 streamers are abandoning [Competitor] this month."
Story Angles: What Lands vs. What Gets Archived
| Pitch Angle | Receptivity at Dexerto | Key Requirement |
|---|---|---|
| Creator tooling (overlays, moderation AI, chat infra) | Very high | Named streamer using it, on the record |
| Platform policy & API changes (Twitch, YouTube, Kick) | Very high | Documented developer impact + a quotable dev |
| Gaming hardware / GPU / peripheral benchmarks | High | Reproducible methodology, retail-available units |
| Anti-cheat and security research | High | Responsible disclosure already completed |
| Consumer AI apps with a cultural hook | Medium | Real daily-active users, not a waitlist |
| Engine / middleware / netcode releases | Medium | Playable demo and a latency number |
| Enterprise B2B dev tooling | Low | Requires a gaming or creator wedge |
| Standalone funding news | Low–medium | Round size plus cultural relevance |
There is no formal "tech desk" at Dexerto in the traditional sense. Coverage is organised around verticals — gaming, entertainment, esports, and internet culture — and the writers inside those verticals absorb technology stories that touch their beat.
That means your pitch should go to a beat specialist, not a section head. A writer covering Call of Duty is your best entry point for an anti-cheat story; a writer covering streaming platforms is your entry point for a moderation-API launch.
Names in your Dexerto journalists list such as Connor Bennett, Sourav Banik, Keshav Bhat, Michelle Cornelia, Bee Delores, and Tom East each sit on distinct verticals. Read the last twenty bylines before you send anything.
Freelancers matter here too. A significant share of Dexerto's feature output is commissioned, so a strong freelancer relationship can convert into a 1,500-word feature that a staff writer has no bandwidth to write.
Accessing the Verified Dexerto Journalists Database for Targeted Pitches#
The most common founder error is treating a media list as a volume game. At a publication this fast-moving, a mis-targeted pitch is not just ignored — it burns a relationship permanently.
A well-maintained Dexerto journalists database should let you filter by vertical, recent output, seniority, and preferred contact channel. Build that filter before you build the pitch.
⚠️ Common Mistake: Blasting the full Dexerto reporters list with an identical email. Dexerto's writers openly compare inboxes; a spray-and-pray send is visible within a day and gets your domain flagged.
Segment the Dexerto journalists database into three tiers: primary beat writers (10–15 names), adjacent writers who occasionally cover your category (5–8), and freelance contributors (open-ended). Pitch only Tier 1 in any given cycle.
Reaching Tech Reporters: Direct Contacts and Verification Ethics#
Dexerto's editorial roots sit in Ireland and the UK, which means GDPR discipline is not optional. Scraped personal addresses are a reputational and legal liability.
Legitimate Dexerto journalists contacts come from three sources: public bylines with linked author pages, verified social profiles, and the publication's own masthead or contact page.
For Dexerto reporters contacts, prefer the channel the journalist has publicly signalled — a Bluesky or X DM, a Signal number in a bio, or a press inbox. Respect the signal.
Verification matters as much as acquisition. Before you commit a Dexerto journalists contacts record to your CRM, confirm the person still publishes there — turnover in gaming media is rapid and stale lists undercut your credibility.
On Dexerto reporters emails: keep them transactional. One pitch, one follow-up, then stop. A clean, well-targeted Dexerto journalists emails list of forty names beats a scraped Dexerto reporters emails dump of two thousand.
What Moves the Needle: Benchmarks, Demos, and Traction Metrics#
Dexerto's audience is technically literate and allergic to marketing language. They will read your benchmark chart and they will notice a missing baseline.
Provide reproducible benchmarks: an open methodology, the exact hardware, the driver versions, the raw output files, and a script the journalist can rerun themselves. Anything less is treated as marketing.
Demos outperform decks. A 90-second screen capture showing real usage — a live moderation queue, a stream with sub-40ms latency, a patch deploying in production — is worth more than a fifteen-slide narrative.
Traction metrics must survive scrutiny. "120,000 monthly active users" is credible only with a definition of active, a date range, and a growth chart that a journalist can sanity-check against third-party traffic tools.
Funding milestones matter mainly as news pegs, not stories. A Pre-seed or Seed round is a paragraph; a Series A with a named creator partnership is an article; a Series B with a market-shift thesis is a feature.
💡 Editorial Pro Tip: Attach a one-page "Benchmark Reproducibility Sheet" — hardware, OS build, driver, sample size, and a link to raw JSON. Dexerto writers cite sources; be the source they cite.
The Embargo Playbook: Timing, Exclusives, and Pitch Subject Lines#
Dexerto publishes on GMT/BST, not Pacific Time. A pitch sent at 6pm ET lands after the newsroom's day is effectively over.
Embargoes are honoured when they are precise and absurdly clear: date, hour, timezone, and a named contact who can confirm lift. Vague embargoes get broken, and rightly so.
Exclusives carry disproportionate weight at a speed-driven outlet. Offering a 12-hour head start on a benchmark dataset or an API launch to a single writer will often outperform a wide, simultaneous send.
| Pitch Window (GMT/BST) | Best Suited For | Embargo Discipline |
|---|---|---|
| Mon 07:00–09:00 | Platform policy, breaking tech news | Hard embargo, timezone explicit |
| Tue–Thu 08:00–11:00 | Funding + product launch combos | 48-hour pre-brief standard |
| Thu 14:00–16:00 | Feature-length, creator interviews | Flexible, negotiate lift |
| Friday | Avoid unless genuinely breaking | No embargo — newsroom is thin |
| Weekends | Esports events, patch drops, live shows | Tie embargo to event start |
Subject lines should read like a headline, not a request. "EMBARGO 14 May 09:00 GMT: Anti-cheat startup [X] raises $6M after banning 1.2M accounts" tells an editor everything.
⚠️ Common Mistake: Sending an embargoed pitch to five Dexerto writers simultaneously and calling it an exclusive. Editors talk. Send one, wait, then widen after the agreed window.
Field-Tested 120-Word Pitch Template for Dexerto Reporters#
Subject: EMBARGO [Date]: [Company] raises $[X]M to [Mission]
Hi [Name],
Quick context for your [beat] coverage: [Company] closed a $[X]M [Round] led by [Investor] to [one-line mission]. We built [product] because [specific pain point streamers/players/devs hit].
The proof: [metric 1 — e.g. 40ms median latency], [metric 2 — e.g. 120k MAU], plus a reproducible benchmark your team can rerun on [hardware]. Full test harness and raw JSON attached — no NDA, no cherry-picked graphs.
Demo: [link]. API docs: [link]. Founder [Name] is ex-[Company] [engineering credential] and will walk your readers through the architecture on a 15-minute call.
Embargo lifts [Date, Time, Timezone]. Happy to give you first look.
[Name], [Title] — [Signal]
Streamlining Founder PR Workflows with Pytch#
Manual list-building collapses at scale. A founder running a Seed-to-Series-B PR cadence needs a living system, not a spreadsheet that rots within a quarter.
Pytch maintains structured, verified media records so that your Dexerto journalists list stays current as bylines shift and beats rotate. Filtering, segmentation, and pitch-history tracking live in one place.
That infrastructure is what converts a media database into a repeatable pipeline — one where every send is traceable, every follow-up is timed, and every relationship is preserved across funding rounds.
The result is unglamorous but decisive: fewer emails, better targeting, and a newsroom that opens your next pitch because the last one was actually worth reading.
Dynamic Verification & The Dexerto Journalists Database
In high-growth technology journalism, beat assignments shift rapidly. Product reviewers transition to venture capital coverage, enterprise reporters move to AI safety desks, and editors launch independent industry newsletters. Static press lists experience substantial contact decay each quarter.
Utilizing an active, real-time Dexerto journalists database protects founders from pitching dormant inboxes. Our verified Dexerto reporters database monitors 23+ active journalists currently reporting at Dexerto, indexing recent product coverage, software teardowns, and beat transitions to maximize inbox deliverability.