How to pitch an internal podcast to your boss

Why this pitch is worth making

Internal podcasts are still new enough that most decision makers have not seen them work firsthand. That makes the pitch harder than it should be. But it also means that companies who adopt now have a real advantage over those who wait until it is obvious.

The good news is that this is not a hard sell. You are not proposing a new technology or a risky experiment. You are proposing a new channel for communication that already happens. The question is whether that communication reaches people clearly and consistently, or whether it leaks, fragments, and gets distorted along the way.

Most organisations already know their internal comms are not working well. Your job is to connect that problem to a solution that is cheap, fast to start, and easy to reverse if it does not land.

The problem you are solving, in business terms

Before you pitch the solution, name the problem in language that resonates with your decision maker. Depending on their role, the frame changes.

For a CEO or founder

"As we grow, the same priorities and decisions mean different things to different teams. We are losing alignment, and it is slowing us down. An internal podcast gives leadership a consistent, scalable voice without adding more time to the calendar."

For an HR or People director

"Our onboarding varies too much depending on the manager. Our policy changes are understood inconsistently across teams. Employees say they feel out of the loop in engagement surveys. We need a channel that reaches people where they are, not where we assume they are."

For a COO or Operations lead

"Field and frontline employees miss most of our communications because they are not at a desk. Important process changes take weeks to reach the right people, and by then they are applied differently across sites. Audio fixes this with near-zero operational overhead."

For a CFO or budget owner

"We are spending time and money on all-hands meetings that could be compressed. We are repeating the same training and onboarding content at significant cost. A private podcast replaces part of that cost with a low-overhead channel that employees actually use."

Handling the objections you will hear

Most objections to internal podcasts are reasonable. They come from people who have seen "new channel" initiatives fail before. Here is how to address them directly.

"Nobody will listen to it"

This is a content and relevance problem, not a format problem. Employees listen to consumer podcasts every day. They will listen to an internal podcast if it is useful, short, and consistent. The ask is to start with a pilot group where you can validate adoption before a wider rollout. If nobody listens after six weeks, you stop.

"We already have too many communication channels"

This is a reason to add a channel that works, not to keep using channels that do not. An internal podcast does not replace chat or email. It replaces the portion of meetings, PDFs, and intranet updates that nobody reads. You are not adding noise. You are giving the important information a home that people actually visit.

"It will create extra work"

Recording a ten minute episode takes about thirty minutes including preparation. Publishing takes five. The question is not whether it creates work, but whether that work replaces something more expensive. An episode that prevents ten manager conversations about the same policy change is clearly net positive.

"Our employees are not podcast listeners"

Podcast listening has grown across every demographic and industry, including frontline, manufacturing, and healthcare workers. The format is familiar. The friction is low because it works on the smartphone everyone already carries. You are not asking people to adopt a new habit. You are meeting a habit they already have.

"What happens with sensitive content"

Private podcasts are not public. Access is controlled at the listener level. You decide who can hear each episode. Content can be restricted to specific teams, roles, or locations. Access is revoked immediately when someone leaves. It is as secure as any other internal system you already use.

A simple pitch structure that works

You do not need a long presentation. A fifteen minute conversation with the right framing is enough.

Open with the problem, not the solution

"I want to talk about how we communicate X. Right now, the way we do it is not landing. Here is the evidence." Use one or two specific examples: a policy that was misapplied, an onboarding inconsistency, an all-hands that felt too long for the information it conveyed.

Name what you have tried and why it is not enough

"We have tried email, and open rates are low. We have tried the intranet, and nobody goes back to check it. We have tried longer meetings, and people leave with the same questions." This validates that the problem is real and that easier fixes have already been attempted.

Introduce the channel, not the tool

"I would like to propose a private internal podcast. Short audio episodes, five to ten minutes, available on any smartphone. People listen when it suits them, not when we schedule it." Keep this brief. You are describing the channel, not pitching the software yet.

Propose a pilot, not a programme

"I am not asking for a full rollout. I want six weeks, one team, and two episodes per month. At the end of six weeks, we review listening data and decide whether to continue." A pilot is easy to approve because it is easy to stop.

Give one specific success metric

"If 60 percent of the pilot group listens to at least one full episode in the first four weeks, I will call that a meaningful start." One metric, agreed in advance, makes the review conversation simple.

What to prepare before the meeting

You will have a stronger pitch if you walk in with three things ready.

One internal communication failure you can name

A specific example: a policy that was misunderstood, a decision that was interpreted differently across teams, an onboarding that varies too much by manager. One real, recent example lands better than any statistic.

A cost estimate for the current approach

If you run a monthly all-hands for sixty people that lasts ninety minutes, that is ninety hours of collective time per month. Put a rough salary cost on that. Even if you only reduce the broadcast portion by thirty percent, the saving is significant. This context makes the conversation about trade-offs, not just costs.

A proposed pilot plan on one page

Team or group you would pilot with. Number of episodes per month. Episode format and length. Who records. How you will share the subscribe link. What you will measure. How you will review it. One page, not a deck.