COO Podcasts That Accept Guests

Three public routes were verified among the COO podcasts reviewed. Second in Command has a formal application. Modern Business Operations invites direct guest inquiries. The Operations Room asks for suggestions about another person. The remaining shows below publish interviews, but their first-party pages and feeds do not grant equivalent public permission to pitch.

Guest permission needs its own source

An interview tells you that a producer uses outside voices. It does not tell you how the guest entered the process. The host may have invited that person, accepted a private referral, worked through a publisher relationship, or selected a proposal sent through a public route.

Those paths cannot share one label. An application lets a prospective guest submit information through a defined workflow. A direct inquiry invites the person to contact the publisher about appearing, while a suggestion route allows someone to recommend a guest. A generic company form keeps its stated business purpose unless the publisher assigns it to the podcast.

The Convokast podcast directory can help with discovery. Treat each listing as a lead to research, not proof that a producer welcomes outreach.

Second in Command publishes a formal application

The Second in Command publisher page asks whether the visitor wants to be a featured guest and links to an application. The embedded workflow requests professional and company information. Its fields include a LinkedIn profile and job title, plus employee count and annual revenue. That evidence supports the narrow label "formal application."

The show's official feed describes conversations with top-level COOs and other second-in-command leaders about the work behind the chief executive. A fitting proposal should therefore connect the applicant's role to a decision about executive partnership or authority, scaling pressure, hiring, or operating responsibility. A broad leadership biography gives the producer less to assess than a case with a clear decision and consequence.

The application is permission to submit. It says nothing about response time or acceptance, and it promises neither recording nor publication. Applicants should answer the form as written and avoid treating eligibility questions as evidence that they have already passed an editorial screen.

The Operations Room accepts third-party suggestions

The Operations Room publisher page uses the heading "Pitch a Guest for The Operations Room." Its supporting text asks whether the reader has someone in mind and requests the proposed person's identity plus the reason the story matters. That third-person wording verifies a suggestion route.

Do not silently expand that permission into an open self-application. Someone proposing a colleague or client, a portfolio executive, or another operator can use the published instruction. A prospective guest proposing themselves should first ask whether self-nominations are considered, and should identify the proposal as a self-nomination rather than writing as though another person made it.

The official Operations Room feed focuses on operating leaders and the problems that emerge while companies scale. Useful suggestions should show why the proposed guest can speak from direct responsibility. Role design and executive hiring fit the published territory, as do process ownership and operating systems. A title alone does not show that the person owns a case the audience can use.

The publisher also has a sponsorship route. That commercial page does not change the editorial suggestion wording and should stay out of a guest-permission record unless the publisher explicitly connects the two.

Modern Business Operations invites direct guest inquiries

Tonkean's Modern Business Operations page says "Be our Guest" and asks people who want to share their story to email the show or reach out through its social profiles. The email link names guesting on the podcast in its subject. This is a direct inquiry from a prospective guest, not a structured application.

The official feed covers operations across finance, revenue, legal, procurement, IT, and HR. That remit favors a cross-functional case over a generic claim to operational expertise. A proposal might explain how an operator redesigned an intake process, changed ownership across departments, or handled governance around automation. The claim should stay within the guest's direct responsibility.

An inquiry still leaves selection with the producer. The public wording does not promise a reply or define an acceptance schedule. Keep the first message short enough for the team to assess the person, story, and functional relevance without opening attachments.

The other reviewed shows verify interviews, not public access

The McKinsey Talks Operations feed includes C-suite leaders and McKinsey experts discussing enterprise operations. The reviewed feed contained no application, nomination, or guest-pitch instruction. Its invitation to connect on LinkedIn is general community contact.

The Operations Science Podcast publishes detailed conversations with operations and project leaders in industrial settings. Its publisher page and official feed show an interview format, but neither source gives prospective guests an application or guest-specific contact instruction.

Operations with Sean Lane also uses outside operators. The official feed covers commercial operating systems, including customer, partner, and post-sale work. Social contact for the host and an invitation to discuss consulting services do not grant podcast access. Its publishing cadence also warrants a current scheduling check before anyone spends time researching an approach.

Label all three "interviews verified; public access unconfirmed." That wording records what the sources establish without claiming that a show rejects guests or accepts unsolicited submissions.

Keep a route record before outreach

Save the official URL, the publisher's exact permission wording, the route class, and the date checked. Add a separate field for current production evidence because an old application can remain online after a schedule changes. Check the endpoint as well: a visible button, form, or email address may fail even while the page remains live.

Then match one directly handled operating decision to the show's current territory. State the proposed guest's authority, the company context that may be named, and any client, vendor, or investment interest. The guest-access verification guide provides a reusable classification method, while the audience-overlap guide helps test whether listeners own the problem in the proposed story.

If you want these COO routes checked again and matched to a defensible premise before outreach, talk with Convokast about podcast booking.