Security podcasts do not look like a good media buy on paper. The download numbers are small next to almost any other channel, attribution is poor, and the audience skips ads for a living. They are still one of the few places where a practitioner will voluntarily give a vendor forty uninterrupted minutes of attention. Most brands buy them badly, usually because nobody was clear about which of three products was on the table.
Three different things get sold as a podcast sponsorship
- The scripted read. A spot at the top or middle of the episode, usually 30 to 60 seconds, delivered in the host’s voice but written by you.
- The host integration. The host describes your product in their own words, ideally after using it, often with a specific anecdote attached.
- The episode. A full conversation featuring someone from your company, either sold outright or quietly arranged as part of the deal.
These are usually priced as one spectrum, cheapest to most expensive. They are not. They fail for different reasons, they need different things from you, and only one of them is worth paying a premium for.
The scripted read is the weakest item on the menu
A spot you wrote, read out by someone who has never opened your product, is the closest thing this channel has to a banner ad. A technical audience recognises the shift in cadence within a sentence and either skips or stops listening. Nothing about the host’s credibility transfers, because the host has not actually said anything.
That does not make it worthless. It does one job well: putting a name in front of a narrow, defined audience repeatedly until the name stops being unfamiliar. In a field where buyers shortlist from memory, that is a real effect. But it only works on repetition. One episode is money set on fire. A run across a quarter gives the name somewhere to land, and should be priced as the cheap awareness buy it is.
The host integration is what you are actually paying for
When a host says they ran your scanner against their own lab and it caught something they did not expect, the audience hears a peer, not an advertiser. That is the whole asset, and it has a hard constraint attached: the host can only lend credibility as far as their own experience goes.
So the question to settle before you agree a price is not what the slot costs. It is whether the host is willing to genuinely use the thing. If they are, give them real access and real time, and expect them to mention what annoyed them. If they are not, you are buying a scripted read with better delivery, and you should pay scripted read money for it.
The guest episode is not a sponsorship
Plenty of brands try to buy a seat on the show, and some hosts sell one. It is the fastest available way to damage a security podcast. The audience assumes a guest was invited because they had something worth hearing. When that assumption turns out to be false, they stop trusting every other episode too, including the ones that were earned.
There is an honest version of this. The host invites your researcher because the topic is genuinely interesting, discloses the commercial relationship in the first minute, and keeps full editorial control of the questions. The sponsorship pays for ad slots. It never buys the seat. Any deal that blurs those two should be rewritten before it is signed.
What a host needs from you before recording
- A working account with realistic data in it, provisioned at least two weeks before the recording date, not a sales demo environment.
- The limits, in writing: what the product does not do, and which kind of team it is wrong for.
- One or two technical details worth saying out loud, the sort of thing an engineer would find interesting even if they never buy.
- Every claim you want made, each with the source behind it, so nobody repeats a number that cannot be defended.
- A named engineer they can email directly when something breaks mid-test.
Hosts almost never get this package. The ones who do tend to produce the spots that listeners quote back months later.
Measuring it without lying to yourself
Podcast attribution is genuinely bad and no vanity URL will fix it. People listen while driving, then search your name three days later on a laptop. Treat a discount code or a dedicated link as a floor, never as the number.
More useful signals: branded search volume in the days after an episode drops, direct traffic in the same window, the show being named unprompted on sales calls, and a plain open text question on your signup form asking where people heard about you. Judge the whole thing on a quarter of episodes, not on one.
What a fair scope looks like
Write down which of the three products you are buying, how many episodes it covers, and whether the words are yours or the host’s. Then settle the part most deals forget: how long the spot stays in the back catalogue. Podcast archives get downloaded for years, and an evergreen ad running forever is a substantial transfer of value that is almost never priced. Agree a term, agree that disclosure sits at the top of the episode and in the show notes, and agree that the editorial content of the episode belongs to the host.
Influous is pre-launch. We are building a marketplace where security brands and manually vetted technical creators, podcast hosts included, agree scope, usage, and disclosure before any money moves. If you host a security show, or you are planning a first sponsorship and want the scope right, apply as a creator or email us at info@influous.io.