What an industry benchmark survey is, and what it is not
An industry benchmark survey collects original data from people across your field, not from your own audience. Guests and listeners answer the same instrument every year, and the answers are the finding, whether ten people respond or a thousand. It produces a number nobody in your niche has published yet.
That is the difference from the annual listener survey, which exists to steer your own show: what to book more of, what almost made someone unsubscribe. A benchmark survey exists to produce research the field itself does not have yet, using the reach a podcast already carries: guests willing to answer a short instrument, and listeners willing to forward the link to a colleague in the same role.
Design the instrument once, and change it as little as possible
Write ten to fifteen questions the first year and hold most of them steady after that. A trend only exists if the same question gets asked the same way twice. Add one or two new questions each edition if the field shifts, and treat the core set as fixed.
| Question type | What it produces | How many to include |
|---|---|---|
| Multiple choice, fixed options | A number you can chart edition over edition | Six to eight, the backbone of the report |
| Ranked choice | An ordered list of priorities across the field, not just your listeners | One or two |
| Numeric input | A rate, a headcount, or a budget figure the respondent supplies themselves | One or two |
| One open box | A quote worth reading on the results episode | One, placed near the end |
Write down the exact wording you land on and keep a copy outside the survey tool. Tools change vendors, forms get rebuilt from memory, and a question that reads slightly differently next year breaks the comparison you built the whole report around.
Field it through guests and listeners, not a cold list
A benchmark survey lives or dies on who answers it, and a general link posted with no context gets ignored. Ask every guest booked during the fielding window to answer and to send the link to two people in their own role. Ask your listener base once, in the feed and in an email.
Set a fixed fielding window, eight weeks is workable for most shows, and hold it to the same weeks every year. Guests answer inside the interview booking flow rather than a separate ask, since a person already on your calendar for a recording is far more likely to fill out a short form than a stranger clicking a link in an email footer.
This is not the panel episode where three guests discuss where the industry stands from their own read of it. A recurring state-of-the-industry panel is a conversation with a rotating cast, built on opinion. A benchmark survey is a structured instrument fielded across dozens or hundreds of respondents, built on data the panel can then argue about instead of guess at.
Analyze for the number that becomes the headline
Most of what the survey produces is context. One or two numbers are the actual headline, the figure a trade writer or a competitor's sponsor deck will quote with your show's name attached. Find those before writing anything else, and build the results episode and the written report around them.
- A number that moved from last year's edition, stated plainly against last year's figure rather than in isolation.
- A split between two roles or two segments of the field that respondents themselves would not have guessed.
- A gap between what people say they do and what the numeric-input questions actually show them doing.
A headline candidate that only makes sense with three paragraphs of setup is not a headline. If you cannot state it in one sentence a stranger to your show would understand, keep digging or drop it to a supporting chart.
The results episode reports the finding, it does not read the spreadsheet
Publish the results as an episode built around the headline number, with two or three guests who can react to it on air. The episode is the distribution mechanism for the data, not a recitation of every question asked. Save the full breakdown for the written report.
Release the written report alongside the episode, gated behind an email address if you want the list, open if you want the citations. The report is the artifact a journalist links to and a competitor's sponsor deck quotes from months later. The episode is what most of your audience actually consumes.
The sponsor package built on the data
A benchmark survey sells differently than an ad slot. A sponsor buys presence inside the report itself: a named presenting-sponsor line on the episode and the written report, early access to the findings before publication, or a custom cut of the data specific to their category. None of that exists in a rate card built around downloads.
Pod Green Room keeps every respondent who is also a past or booked guest on the guest pipeline, so the list of people who answered this year's edition is not a spreadsheet rebuilt from memory next year. Pod Green Room also holds the sponsor conversation on the same sponsor tracking record, so the brand that asked for early access to this year's findings is the first call when next year's fielding window opens.
This sits next to, not inside, the media kit: the kit packages the audience and download numbers you already have, and the benchmark report is new research the kit did not have to invent from nothing to look substantial. Point a sponsor at the report and the kit and let each one do a different job in the conversation.
Run the same survey again next year
The first edition establishes the instrument. The second is the first real data point in a trend, and a trend is what a reporter, a sponsor, and a guest all reference over a one-time figure. Field it in the same window, ask the same core questions, and hold the format until the report has a history.
- Keep the fielding window fixed on the calendar, so the report earns a reputation for showing up when the field expects it.
- Re-invite last year's respondents first, then add this year's new guests and listeners on top of that list.
- State the headline number against last year's number in the same sentence, every edition, so the comparison is never a search the reader has to do themselves.
- Revisit the wording of the core questions only if the field actually changed, and note the change in the report when you make it.