Inside Future: How to Pitch Future Journalists & Win Product Coverage
Future plc is not a venture newswire. It is a Bath-headquartered, London-listed specialist publisher whose tech titles β TechRadar, Tom's Guide, T3, PC Gamer, GamesRadar+, Android Central, Windows Central, iMore β reach buying-intent audiences at enormous scale.
That single fact determines everything about how you pitch Future journalists. Funding news is context here, never the story. Product utility is the story.
This guide explains how Future reporters actually work, and how to structure a pitch that survives triage.
Editorial Focus & The Technology News Cycle at Future#
Future's editorial clock is set by the product calendar, not the funding calendar. CES, MWC, IFA, Samsung Unpacked, Apple events, GPU launches, Prime Day and Black Friday define the rhythm.
The commercial engine underneath is commerce. Reviews, buying guides and "best X for Y" pages generate affiliate revenue, so stories that help a reader decide are structurally prioritised.
Future's portfolio also carries the Dennis legacy titles β The Week, ITPro, Kiplinger β which is where enterprise, policy and business-of-tech angles genuinely land.
| Pitch Angle | Receptivity at Future | Key Requirement |
|---|---|---|
| Hands-on review unit / early hardware access | Very high | Retail-ready unit, UK pricing, full spec sheet |
| Reproducible benchmark or independent lab test | Very high | Published methodology, hardware config, raw data |
| API release with public docs and sandbox | High (TechRadar Pro, ITPro) | Live developer docs, rate limits, sample repo |
| Developer adoption metrics (SDKs, MAU, retention) | Medium-high | Verifiable third-party data, not vanity totals |
| Founder engineering credentials | Medium | Shipped systems, patents, open-source record |
| Funding round (Pre-seed β Series B) | Low as standalone | Must be attached to a product or UK-market consequence |
| Category-level data (UK pricing, energy, tariffs) | High | Original dataset, not a vendor press release |
| Enterprise deployment case study | High (ITPro) | Named customer, measurable outcome |
β οΈ Common Mistake: Pitching a "$12M Series A" headline to TechRadar. The answer is no. Pitching the same round as "the Β£X that makes a 40% cheaper 4K monitor possible in the UK, review unit attached" is a maybe.
Future is organised by brand, not by desk. Each title has an editorial leadership layer, then section specialists β phones, computing, audio, smart home, gaming hardware β then a large freelance bench.
This triage matters: a commissioning editor controls the slot, a staff writer controls the byline, a freelancer controls neither reliably. Pitch the slot-holder first.
Records in the Future journalists list β Suhas Baliga, Kaydee Barker, Matthew Bolton, Brendan Bordelon, Sam Caucci, Sharlene Gandhi β span news, features and device-review functions across Future's UK titles. Confirm current title and brand before you write a word.
Future staff move between titles frequently. A contact saved as "TechRadar computing" may now be commissioning for T3.
π‘ Editorial Pro Tip: Segment your outreach into three lanes β consumer review (TechRadar, Tom's Guide, T3), enthusiast/prosumer (PC Gamer, Digital Camera World, Creative Bloq), and B2B (TechRadar Pro, ITPro). The same release needs three different ledes.
Accessing the Verified Future Journalists Database for Targeted Pitches#
A Future journalists database is only useful if it is segmented by brand, beat and commissioning authority. A flat list of 28+ names is a starting point, not a strategy.
Build your Future reporters database around four fields: publication, beat, seniority, and date of last byline. Add a fifth β freelance or staff β because it changes your ask.
Refresh every 30 to 60 days. Future's internal mobility is high, and stale records produce misdirected pitches and bruised relationships.
Maintain a separate suppression list too: anyone who has declined twice stays out for two quarters.
Reaching Tech Reporters: Direct Contacts and Verification Ethics#
Future is a UK publisher operating under UK GDPR and PECR. That means identifiable, relevant, one-to-one contact β not scraped lists and not BCC blasts.
Future reporters contacts should be verified against a live byline, a masthead, or a public professional profile before use. Never assume a pattern is universal across a 200-brand portfolio.
Treat Future journalists contacts as relationship records, not send targets. Log the last interaction, the response, and the reason for any decline.
Where Future journalists emails are not published, use the title's editorial contact route or approach the commissioning editor through a public professional channel. Where Future reporters emails are known, keep volume to one substantive pitch and one follow-up.
Guard the Future reporters list with the same discipline as a source list. Accuracy compounds; sloppiness does too.
What Moves the Needle: Benchmarks, Demos, and Traction Metrics#
Future's testers are technical and sceptical. Benchmark claims without methodology are deleted, not challenged.
Publish your test rig, firmware version, ambient temperature, run count and raw results. A link to a reproducible repository outperforms a slide.
Demos work when they are short, self-hosted and capture the failure modes as well as the wins. A two-minute screen recording beats a scheduled call.
Funding milestones should be translated into consequence: what gets cheaper, faster, better or newly available in the UK, and when.
π‘ Editorial Pro Tip: Ship three assets in your first email β a review unit or sandbox key, a one-page spec and methodology sheet, and a 90-second demo. Reviewers reward pitches that remove work.
The Embargo Playbook: Timing, Exclusives, and Pitch Subject Lines#
Future honours embargoes consistently, but the clock is GMT/BST. A 09:00 ET lift is 14:00 in London β often too late for the UK morning cycle.
Align hardware review embargoes with your news embargo, or you will get a news brief and no review. Reviewers need lead time measured in weeks.
| Timing Element | Future Norm | Practical Rule |
|---|---|---|
| Embargo lift time | UK morning, 08:00β10:00 GMT | State time zone explicitly in subject line |
| Embargo lead time | 5β10 working days | 3+ weeks for hardware reviews |
| Exclusivity | Accepted, per brand | Never promise the same exclusive to two Future titles |
| CES / MWC / IFA | Pre-briefed 2β4 weeks out | Book briefings before the show floor |
| Commerce peaks | Black Friday, Prime Day | Pitch 6β8 weeks ahead for buying guides |
| Friday afternoon | Dead zone | Send Tuesday to Thursday |
| Follow-up | One, after 3β4 days | Then close the loop and move on |
β οΈ Common Mistake: Announcing US pricing with "UK pricing TBC." For a UK-first portfolio, missing local pricing and availability kills the story outright.
Field-Tested 120-Word Pitch Template for Future Reporters#
Subject: EMBARGO [Date, 09:00 GMT]: [Company] raises $[X]M to [one-line mission]
Hi [Name],
[Company] has closed a $[X]M [round] led by [Investor] to [concrete outcome, e.g. cut inference costs 60%]. Our benchmark suite is reproducible from [GitHub link], and [independent tester] verified [metric] on [hardware].
Two angles for [TechRadar Pro / ITPro]:
- Architecture: [one sentence on how the system actually works].
- Buyer impact: what this changes for UK teams evaluating [category] this quarter.
Founder [Name] is ex-[Company] ([credential]). Review units, sandbox API keys and a 90-second demo are ready now; [Name] is free [dates] for a 20-minute technical walkthrough.
Embargo lifts [date/time GMT]. Spec sheet, images and raw data: [link].
[Signature]
Streamlining Founder PR Workflows with Pytch#
Pytch turns this guide into an operating system. Import and dedupe your Future journalists records, tag them by brand and beat, and track embargo windows per outlet.
Log every send, reply and decline. Set automatic suppression rules so a second "no" never becomes a third email.
Attach assets β review units, benchmark repos, demo links β to each record so a pitch takes minutes, not hours. Measure coverage by brand, not by volume.