Crafting a Winning Freelance Pitch

WHY IT EXISTS A freelance writer needs a standardized way to propose a story or their services to an editor or company. A pitch, or query, solves this by creating a compact, persuasive business case for a specific idea or for the writer themselves, allowing editors to quickly assess fit.

THE MENTAL MODEL Think of a pitch as the answer to the question: "Someone is doing something for a compelling reason." This framework forces you to build a story with inherent stakes, action, and a clear reason for the audience to care. If you can't answer an editor's potential "So what? Who cares?" question, your idea isn't ready.

HOW IT WORKS A pitch is a short proposal sent to an editor. For journalism, it includes a headline, a brief outline of the story, and potential sources. For business or content marketing, a "letter of inquiry" is more common; it pitches the writer's skills for an ongoing relationship rather than a single story. The process is to research the outlet, find their submission guidelines, and craft a message that fits their needs. If you're unknown to the editor, you must include links to relevant published work.

WHEN TO USE IT Use a pitch when you have a specific, well-defined story idea for a publication. It's the standard method for responding to "calls for pitches" that editors post on social media. For corporate work, use a letter of inquiry to introduce yourself to a marketing manager, aiming for a long-term working relationship rather than a one-off assignment.

WHEN NOT TO USE IT Don't send a pitch for a vague, unformed idea. Don't pitch a publication without first reading their work to understand their audience and style. A generic, mass-emailed pitch is almost always ignored. The most common failure is not following the publication's explicit submission guidelines—they are telling you exactly how to pitch them.

ONE CANONICAL EXAMPLE An editor posts a call on Twitter for stories about open-source software. You email them with the subject line "PITCH: The Burnout Toll of a One-Person Open Source Project". The email body explains the story of a specific developer (the SOMEONE) struggling to maintain a popular library (the SOMETHING) because they can't secure funding (the COMPELLING REASON). You list your interview plan and link to two relevant articles you've written.