Wired journalists do not cover products. They cover the consequences of products — on economies, on power, on culture, on the way people live. That single distinction separates the pitches that get answered from the hundreds that die in the inbox every week.

Pitching Wired reporters requires engineering literacy, evidentiary discipline, and a story that survives contact with a skeptical senior editor. This guide breaks down exactly how to build that pitch.

Wired was founded in 1993 by Louis Rossetto and Jane Metcalfe, and it has been owned by Condé Nast since 1998. Its founding thesis — that technology is culture, not a vertical — still governs every commissioning decision today.

The publication runs two clocks simultaneously. The digital newsdesk moves in hours; the magazine and long-form features move in weeks and months. Your pitch must be timed for one clock, never both.

Per our publication intelligence, Wired's active beats span Technology, Business, United Kingdom, Finance, Arts, and Entertainment. In practice, the most contested inboxes are the security desk, the AI desk, and the business/venture desk.

Wired's UK operation is editorially distinct, London-based, and structurally closer to European regulatory and startup stories than the New York desk. Route UK-relevant founders through London, not New York.

Wired operates a hybrid model: department editors commission, staff writers execute, and contributing editors parachute into long-form. Writers at Wired carry significant autonomy over their own story pipelines.

Matt Burgess covers security and privacy from London. Andrew Couts works the security desk editorially. Natasha Bernal covers business and startups out of Wired UK. These are specialists, not general assignment reporters.

Pitching a section editor with a story that already belongs to a beat writer is a common way to get silently ignored. Pitch the specialist first; copy the editor only after interest is confirmed.

A verified Wired journalists database is not a mailing list. It is a beat map. The value lies entirely in the metadata: who covers what, from which city, with what recent output.

Filter your Wired reporters database by three fields before you write a single word — beat, geography, and last thirty days of published work. A writer who published on model evaluation benchmarks last week is a warm target for a benchmark claim this week.

Segment the Wired journalists list into primary, secondary, and watchlist tiers. Primary gets a bespoke pitch. Secondary gets a shorter, angle-specific note. Watchlist gets nothing until you have news.

The Wired reporters list you maintain should be refreshed quarterly. Beat assignments at Condé Nast titles shift with reorganisations, and stale contacts are worse than no contacts.

Wired staff email follows a predictable convention — typically first initial and surname at wired.com — but convention is not verification. Confirm Wired journalists contacts through published bylines, staff pages, or prior correspondence before sending.

For Wired reporters contacts, treat secure channels as a signal of seriousness. Security-desk writers publish Signal numbers and PGP keys because their sources need them. Using Signal for a routine funding pitch misreads the desk.

Wired journalists emails should never be harvested from scraped datasets. Reporters detect spray-and-pray instantly, and a burnt address is permanent. Build Wired reporters emails only through opt-in relationships, conference contacts, or direct replies.

Ethical verification matters here. Never use a personal address when a work address exists. Never imply a relationship you do not have. Never forward an embargoed document to a second writer to "create competition."

Wired's technical reporters will read your methodology section before they read your funding announcement. Reproducibility is the whole game.

Attach a benchmark harness, fixed random seeds, hardware specification, dataset version hash, and cost-per-inference figure. A claim without a reproduction path is treated as marketing.

Demos must be live. Give the reporter an API key, a sandbox environment, and a documented rate limit. Screenshots under NDA are not a demo — they are a press release with extra steps.

Traction metrics need a developer lens. GitHub stars are decorative. Weekly active developers, merged third-party pull requests, API call volume, and net revenue retention are evidence.

Funding milestones matter to Wired only as inflection points. Pre-seed is rarely a story. Series A is a story when it funds a capability nobody else has. Series B is a story when it signals market structure shifting — often with a regulatory or labour implication attached.

Wired respects embargoes precisely because it expects the same in return. Break one and you lose the desk permanently — not the writer, the desk.

Offer a true exclusive with a fourteen-day runway for features, and five to ten business days for news. Same-day exclusives are not exclusives; they are scheduling conflicts.

Subject lines should carry the news, the number, and the embargo flag — in that order. Never write "Quick question" or "Following up." Neither survives a busy Tuesday.

That template is 118 words. Every line is load-bearing. Cut none of it, and resist the urge to add a company boilerplate paragraph — Wired reporters will read it as filler and stop at line two.

Pytch turns this guide into an operating system rather than a document you read once. The workflow: import the verified Wired journalists contacts into a beat-segmented workspace, attach your benchmark artefacts to each pitch record, and enforce embargo logic at the template level.

Version control matters more than most founders admit. When a benchmark changes two days before lift, every drafted pitch must reflect it. A CRM that ties claims to artefacts prevents the single most damaging error in technical PR — shipping a number you can no longer defend.

Finally, log every outcome. A passed pitch with a stated reason is worth more than a published one with no explanation, because the reason is your next angle.