Why a good pitch is more than a good idea

Pitching a podcast idea to a commissioner, an editorial platform or an audio network means turning a hunch into a project that can be assessed. The recipient is not only looking for an interesting subject. They need to understand what will be produced, for which audience, how often, with what resources, at what level of risk and where it would sit in an existing offering.

The word “pitch” usually refers to a short, structured presentation of the project. It can take the form of an introductory email, a note of a few pages, a conversation or a fuller proposal after an initial selection. Expectations vary between organisations and markets, but several questions remain constant:

  • What exactly is the podcast about?
  • Why does this subject deserve audio treatment now?
  • Who will listen to the programme, and in what circumstances?
  • What is its concrete form: running time, pace, narration, guests, a season or an open-ended series?
  • What expertise or perspective does the person behind the project bring?
  • What resources are needed to produce it properly?

A useful pitch reduces uncertainty. It does not promise an audience, does not present an idea as certain to succeed and does not replace editorial work. It gives the decision-maker enough to judge whether the project is relevant and to decide on the next step.

Before sending, find the right contact and the right format

The first mistake is to send the same document to every recipient. A broadcaster may be looking for documentary series, current affairs programmes, conversation formats, educational content or productions aimed at a specific audience. A network, for its part, may favour projects that have already been produced, formats that could be adapted or proposals from experienced producers.

So study the public information available before you write. Submission pages, calls for proposals, editorial guidelines and forms sometimes state the type of content accepted, the documents required, the deadlines and the rights under consideration. The rules are not uniform. Some organisations do not read unsolicited proposals, while others open limited submission windows.

This check also helps you choose the right level of detail. A first email does not need a full budget and twenty pages of appendices. Conversely, a meeting arranged after shortlisting calls for much more concrete information about the production.

Preparation in four questions

  1. Does the project match the stated editorial line? A subject can be relevant in general without meeting the recipient’s specific need.
  2. Is the contact route permitted? Follow the published submission procedures and any instructions on attachments.
  3. Does the document follow the requested format? A file that is too long, badly named or impossible to open creates an unnecessary obstacle.
  4. Is the project presented as a proposal rather than a done deal? This distinction avoids overstatement and makes clear how far the project has progressed.

The choice of recipient should not rest on reputation alone. The fit between the project, the intended audience and the editorial catalogue matters more than a list of prestigious names.

The essential structure of a pitch document

A pitch document can be short and still substantial. Its job is to allow a quick read, then a more thorough check. A clear structure helps the reader find information without having to infer it.

1. The working title and the one-line summary

The title should be clear, memorable and distinctive enough. The one-line summary, sometimes called a logline, sums up the project in one or two sentences. It should state the subject, the angle and the form. A phrase such as “a podcast about mental health” is too broad. A more informative proposal names the audience, the question addressed and the storytelling approach, without claiming to cover every issue.

2. The editorial concept

This section explains what the show actually offers. Describe the point of view, the tone, the role of the presenter, and the place of first-hand accounts, archive material, data, experts and ambient sound. The reader should be able to picture an episode, not just grasp a theme.

3. The listening promise

The promise answers a simple question: why would someone spend time on this programme rather than on another source of information or entertainment? It might rest on an investigation, a step-by-step explanation, an immersive experience, a clash of arguments or historical context. It must remain verifiable. It is better to describe a specific editorial experience than to promise a “unique” or “unmissable” show.

4. The audience

An audience is not defined by age group alone. Specify interests, information needs, familiarity with the subject and likely listening moments. For a programme about a public policy, for example, listeners might be people directly affected, professionals, students or citizens who want to understand a decision. These groups do not necessarily expect the same vocabulary or the same level of detail.

5. The format

Give an indicative running time, a frequency, the planned number of episodes and the recurring structure. The difference between a limited series and an ongoing programme matters for the budget, the schedule and the editorial strategy. If the number of episodes is not fixed, explain why and suggest a working assumption.

Describe an episode to make the project tangible

A decision-maker can understand a general concept without knowing how it will sound on air. That is why the document should include at least one detailed sample episode. The aim is not to lock in the whole series, but to show that the format works in practice.

An episode outline might include:

  • a provisional title;
  • the central question;
  • the running order in a few segments;
  • the intended sources and their role;
  • the contributors being approached, without presenting their participation as confirmed;
  • the sounds or archive material needed;
  • the ending and the link to the next episode, if the series is serialised.

It is better to choose an episode that represents the editorial core than an exceptional case that cannot be repeated. A show built around a particularly well-known guest should not depend entirely on their availability. The format must still make sense if the people originally approached do not take part.

When the podcast deals with current affairs, also specify what will be checked, dated and reassessed. Institutional and social issues move on: a reform can be announced, amended and then implemented at different dates. The document should distinguish established facts, reporting hypotheses and questions that remain open.

Present the team, resources and schedule without overpromising

An editorial project is more than an idea. Explain who can handle the research, preparation, interviewing, writing, recording, editing, mixing, fact-checking and production coordination. If some skills need to be recruited or outsourced to freelancers, it is better to say so than to imply that everything is already in place.

The team section should stay factual. It can mention relevant experience, technical skills, knowledge of the subject or previous work, without turning the document into an autobiography. For a sensitive project, editorial independence, the handling of conflicts of interest and the protection of interviewees deserve a specific explanation.

The production schedule

A credible schedule separates the stages. For example:

  1. research and background reading;
  2. preparing interviews and checking contacts;
  3. recording;
  4. editing a first cut;
  5. editorial review and fact-checking;
  6. corrections, mixing and delivery;
  7. preparing the release and the supporting material.

Avoid giving a release date that depends on permissions, archive material or contributors who have not confirmed. An estimate in weeks or phases can be more honest than an artificially precise timetable.

The budget as a tool for understanding

The budget is not only a way of asking for funding. It shows that the production needs have been identified. It can separate the costs of preparation, production, editing, music or archive material, travel, translation, transcription, data protection and editorial promotion. Amounts should be presented as estimates, together with the assumptions behind them.

It helps to plan several scenarios: a minimum version, a reference version and the factors that would change the cost. On the other hand, do not quote unverified figures or automatically reuse a rate found elsewhere. Conditions depend on the country, the status of the people involved, the duration, the rights and the level of finish expected.

Distinguish audience, editorial value and performance promises

Audience is a central question, but vague promises do not answer it. A solid document distinguishes three things: the intended audience, the usefulness of the programme and the indicators that could be tracked after release.

The intended audience is the people the content is meant for. Usefulness explains what they will be able to understand, question or explore further. Indicators then belong to monitoring: downloads, complete listens, qualitative feedback, newsletter sign-ups, participation in a discussion or use of related resources. No single indicator guarantees editorial quality.

For a podcast about education, institutions or public life, the value may lie in the clarity of an explanation, a range of viewpoints, the checking of a claim or access to documents that are hard to understand. So it makes sense to describe the planned methods: cross-checking sources, separating facts from opinions, a right of reply where necessary, flagging uncertainties and publicly correcting any substantial error.

The document can also set out a discovery strategy without confusing it with a guaranteed audience. Examples: a descriptive title, an accessible summary, a transcript, chapter markers, clips adapted to permitted channels and cooperation with relevant organisations where this does not compromise editorial independence.

The mistakes that most often weaken a pitch

The weaknesses of a pitch rarely come from a lack of enthusiasm. They tend to come from a gap between the stated ambition and the evidence provided.

A subject that is too broad

“The future of work”, “young people” or “the climate crisis” are territories, not yet series concepts. Choose a question, an angle, a period, a place or a storytelling device. A vast subject can become a series if its progression is made explicit.

An idea mistaken for a format

Saying that the show will cover politics, culture or health specifies neither how it will be built in sound nor the host’s role. The format shows how the listener moves through the episode.

Guests announced as confirmed

A person can be relevant without having agreed to take part. Distinguish the contacts you have in mind, the conversations under way and written confirmations. This precision protects the credibility of the document.

An imaginary audience

Phrases such as “everyone will be interested” or “the subject is going viral” are no substitute for an analysis of the audience. A concrete justification is more useful: a need for explanation, documented news, an underserved audience or a recurring question.

No limits

A serious project states what it will not do. It might specify that it will not give individual medical advice, will not broadcast unverified documents or will not try to cover every dimension of a subject in a single episode. Limits show that the scope has been thought through.

A document that is hard to read

Long paragraphs, decorative headings and essential information hidden on the last page slow down the assessment. The first pages should be enough to understand the project, even if the appendices then add detail.

A vague request

The recipient needs to know what is being asked: editorial feedback, a meeting, a co-production, funding, a licence, support or a referral to the right department. A precise request makes a precise answer easier.

Protect the project and clarify the rights

Pitching an idea does not automatically mean transferring the rights in the project. The terms depend on the country, the contract, the status of the contributors and the nature of the material used. A pitch note should therefore not contain material you are not authorised to use, such as sound clips, photographs, archive material or protected texts.

Before an in-depth discussion, it can be useful to keep a dated version of the document and of the research material. This precaution does not replace legal advice and does not, on its own, create any particular protection. It simply lets you track how the project has evolved.

Questions to clarify during a contract discussion may include:

  • who holds the rights in the concept, the finished episodes and any derived material;
  • the duration and scope of the licence to use it;
  • who approves editorial changes;
  • how authors, producers, journalists and technical staff are credited;
  • who handles permissions, archive material and any music rights;
  • how corrections, takedowns and updates are dealt with;
  • what obligations apply to confidentiality and personal data.

These points should not be buried in the first email. They become relevant as the project moves forward, when confidential material is exchanged or when a contractual relationship is being considered.

Write an effective first-contact email

The approach email should make it possible to decide quickly whether a closer read is worthwhile. It can fit into a few paragraphs, with an attached document if the guidelines allow it.

  1. Specific subject line: say that it is a podcast proposal and give the working title.
  2. Brief context: introduce your role and explain why you are contacting this organisation.
  3. Summary: set out the concept in a few lines, with the audience and the format.
  4. Progress so far: say what is already researched, recorded or confirmed, without exaggeration.
  5. Request: suggest a realistic next step, such as a conversation or a review of the document under the stated procedure.
  6. Attachments: name the documents clearly and follow the requested format.

A follow-up message can be short and courteous. It should mention the date of the first email and should not pile on further requests. If there is no reply, follow the published contact rules and do not treat silence as acceptance.

The final read-through should cover facts, names, dates, links between episodes, the rights claimed and any audience promises. It also helps to have the pitch read by someone who does not know the subject. Their questions will reveal passages that are implicit or too technical.

A checklist before sending

The following checklist helps you test whether the document hangs together without making it artificially long.

ElementChecking questionCommon mistake
ConceptCan the subject, angle and form be understood in a few lines?Presenting only a general theme.
AudienceAre listeners described by their needs and listening habits?Using a vague category or claiming to target everyone.
FormatAre the running time, pace and structure compatible with the project?Promising a format whose production has not been assessed.
Sample episodeDoes an episode let the reader picture the final result?Staying at the level of intention.
SourcesAre facts, archive material and contributors identified with their actual status?Presenting contacts you have in mind as confirmed.
ProductionAre the skills, stages and needs visible?Forgetting editing, fact-checking or permissions.
RequestDoes the recipient know what response is expected?Sending a document with no proposed next step.

This checklist is not meant to produce a standardised document. It helps you check that the idea, the editorial approach and the feasibility support one another. A project can still be in development and remain convincing, provided its uncertainties are identified.

FAQ: pitching a podcast idea to a broadcaster

Do you need to have recorded a pilot episode already?

Not always. A pilot can help demonstrate the tone, the voice and the sound quality, but it takes time and can give too fixed an impression of a format that is still under discussion. A trailer, a short clip or an episode outline can sometimes be enough at the first stage. Follow the recipient’s guidelines and do not produce sound clips containing material whose rights have not been cleared.

How many pages should a pitch document be?

There is no universal length. The document should be short enough to be read and complete enough to answer the essential questions. The format set by the recipient always takes precedence. Without any guidance, a summary followed by separate appendices is often easier to read than a single very long document.

How do you handle a news topic that is still uncertain?

Date the information, distinguish announcements from decisions that have been adopted and flag the points to check before release. The pitch can set out a working approach while stating the conditions that would change the series. This transparency is better than artificial certainty.

Can you send the same idea to several networks?

Check the submission rules and any exclusivity clauses. Tailor the message to each contact and do not suggest that an organisation holds rights it has not obtained. If discussions are well advanced, examine the commitments carefully before accepting anything.

What should you do after a rejection?

A rejection may concern the timing, the format, the audience or editorial priorities, and not necessarily the overall value of the subject. When feedback is given, it can be used to rewrite the scope, the sample episode or the request. Avoid changing the project in every direction, though: a useful revision keeps its central intention and explains clearly what has changed.