THE EDITORIAL TEST

Relevance is the real targeting metric: the same research may interest a specialist trade editor and bore a general technology writer.

01 /

Audit the publication's actual coverage

Read the recent work of the reporter and identify the audience they serve. Determine whether they cover software procurement, enterprise infrastructure, founders, financing or a specific industry. Don't infer an interest from a broad 'technology' job title.

02 /

Write the pitch as a contribution

Lead with the independently useful finding, a precise source and what the reporter can verify. Make access to data and experts straightforward. Avoid asking for a link in a way that undermines the editor's independence.

03 /

Run a respectful follow-up and record outcomes

Track the original pitch, any reply, requested facts, internal ownership, publication permissions and resulting coverage. Do not have several automated senders contact the same reporter without awareness of the conversation.

ILLUSTRATIVE STORY BRIEF — NOT A CLIENT CASE

What this might look like

A journalist covering developer platform reliability may welcome documented integration failure patterns; a consumer gadget reviewer probably won't. The pitch should reflect that difference.

Is a huge journalist database the main advantage?

No. Accurate beat classification, reliable evidence, timely spokespeople and an auditable history of real editorial decisions matter more.

Watch out: Template emails sent to unrelated editors or repeated by multiple accounts.

USEFUL PRIMARY REFERENCE

PRSA Code of Ethics. This is contextual reading, not an endorsement of the service or an approved client claim.