What Should a Business Podcast Measure? Relationships, Useful Content, and Business Results

Saul Marquez has a memorable challenge for podcast measurement: "Downloads are vanity, contacts and contracts are sanity." A business owner can tell you how many episodes they've published and still struggle to explain what changed because of them.

I wouldn't throw away the download numbers. I'd put them beside the questions they can't answer: Did the guest receive the finished episode? Did a customer use the explanation? Did a relevant conversation continue? What time and money did the work require?

Those answers give you something to improve. A rising audience total doesn't tell you that four guests are still waiting for their links, and a modest audience doesn't prove a useful customer resource failed.

First decide which business the podcast supports

In our healthcare marketing conversation, Saul distinguished a media business, a show supporting another business, and a hobby. They aren't interchangeable measurement problems.

If the company earns its money from consulting, accounting, or another service, the podcast may support customer education and professional relationships rather than sell advertising. Decide which job you're asking it to do before treating another show's audience as the benchmark.

I would write one sentence: "We use our podcast to help this audience understand this problem and to develop these relationships or business outcomes." Make the audience and outcome specific enough to guide the next invitation.

Suppose one show receives 500 downloads from a relevant audience and another receives 5,000 from people uninterested in the service. Those are hypothetical numbers, not proof that smaller is better. They show why reach and audience fit need different fields.

Lyndsay Phillips described an encouraging early download milestone. It mattered in the context of her experience and broader goals. The number alone couldn't establish revenue. Keep that distinction when evaluating your own show.

Measure what happened, then choose one change
  1. 1. Name the business purposeDefine the audience, problem, and relationship or outcome the show supports.
  2. 2. Review five episodesRecord guest fit, insight, follow-up, content use, response, and effort.
  3. 3. Find the blocked stepSeparate missing work from unknown interest or unproven outcomes.
  4. 4. Test one changeAssign the action and check evidence at the next review.

Review the last five published episodes

Choose five recent conversations that have been available long enough for the follow-up you intended. Don't select only the impressive guests or the episodes with the best numbers. You're looking for the ordinary process your business is running.

Use this one-page scorecard. These are my suggested fields, not a combined system endorsed by the guests cited here.

Field What to record
Guest relevance Who participated, why they fit, and whether they were a client, prospect, partner, or expert
Customer insight A question, problem, objection, or useful observation from the conversation
Follow-up What was sent, whether the person responded, and any agreed next action
Relationship and business progress Continued discussions, introductions, inquiries, opportunities, clients, or documented revenue
Content use Where the episode or an excerpt was actually published, sent, or used
Audience response Consistent download/view trends, relevant replies, questions, subscriptions, or opt-outs
Production effort Host time, support time, direct expenses, and unfinished work

You don't need a numerical grade in every cell. If an introduction happened, record whom it connected and why. If you don't know whether anything followed, write "unknown." An imaginary dollar value won't make the record more useful.

Separate an introduction from a commercial result

Jessica Rhodes and I have exchanged jokes about The Office. That detail has helped us stay connected beyond the original business topic. It doesn't require a sales label to be a real part of the relationship.

Our conversation about guest relationships also makes a practical measurement point: completing an interview isn't the same as maintaining contact. Publication, guest delivery, a reply, and another discussion are observable steps. Record them rather than score how much someone must trust you.

John Corcoran discussed deliberate relationship development. An interview can give you time to understand someone before deciding whether there's a reason to continue. It doesn't establish that a customer or referral is waiting behind every recording.

Keep commercial stages separate too. An inquiry expresses interest. A qualified opportunity should meet your company's actual criteria. A client has agreed to buy. Recorded revenue reflects transactions, and profit needs to account for relevant costs.

Casey Cheshire described discovering a prospect's Pardot migration need through a conversation. That's a concrete example of learning a business problem. It isn't a reason to call every guest a lead.

When a customer does emerge, record how the relationship began, what happened afterward, and what they say influenced their decision. If the evidence doesn't establish which interaction mattered, leave the uncertainty visible.

Record whether the content leaves the folder

A team can finish three clips, an article, and social graphics without using any of them. "Created" and "published" belong in different statuses. So do "sent to a prospect" and "viewed by that prospect."

Suppose a guest explains a mistake people make before hiring a consultant. A short excerpt could introduce the idea publicly, while the full answer could help during a specific customer conversation. Record the destination, date, purpose, and observable response.

Lyndsay discussed organizing older episodes around themes. That can make an existing archive easier to use when a customer raises a recurring problem. You still need to choose the material, check its freshness, and explain how the pieces fit. A folder of unrelated links isn't the same as a useful resource.

Steve Gordon described how repeated listening can build familiarity. You can look for that effect through what people tell you and the conversations that follow. You don't need to assign a made-up number of listening hours to trust.

Keep downloads, video views, subscribers, and individual people distinct in your report. Consistency helps you see trends. It doesn't make one metric interchangeable with another.

Count the work the show consumes

Include more than the editing invoice. Track the host's preparation, recording, guest coordination, review, and follow-up time. Note promotion and any work waiting on someone else.

Two interviews a week means eight conversations in a four-week stretch if you maintain that schedule. The recording time is only part of the commitment. If production takes the hours you meant to spend developing relationships, that's an operating problem worth recording.

The financial calculation needs the same discipline. A prospective contract isn't money collected. A contract's full value isn't podcast profit. Keep production costs, selling effort, and the cost of delivering the service in view.

Steve discussed production support as a way to protect the host's attention. Outsourcing can help, but you still need to know which work is being completed and what you're paying for. A larger deliverable list doesn't automatically mean a better business result.

Use the scorecard to change one thing

Suppose all five episodes are published, but only one guest has been sent the finished link. That's a follow-up problem, not yet evidence that you chose the wrong guests. Put one person in charge of sending the remaining links. Then check who replies at your next review before changing the guest list.

Different problems call for different decisions. Changing guest-selection criteria won't clear an editing backlog. Recording more episodes won't get existing clips distributed. The scorecard should narrow the next action rather than provide another description of how busy everyone is.

"Unknown" is more useful than an invented business result.

I'd check the operating details monthly and plan a broader quarterly review adjusted for your sales cycle. Those are suggested checkpoints. You may need longer to evaluate a substantial relationship, but not to discover that nobody has delivered last month's episodes.

Use plain descriptions such as "working as intended," "promising but early," "needs a process change," or "needs a strategy review." Then write down one change you're going to test and the evidence you'll examine next time.

Related conversations and resources

Bring the blocked work into the next conversation

Jessica discussed giving a marketing strategy enough time while recognizing that budgets and priorities change. That seems more sensible than abandoning an effort after a handful of recordings or repeating it indefinitely because you've already paid for it.

Your five-episode review may show a useful relationship process with limited audience growth. It may show strong recordings nobody distributes, or expenses you can't yet connect to a clear purpose. Each is something specific to investigate.

If production is the blocked stage, bring that scorecard and one recording to our podcast production page. At DFY Podcast, we'll start with the work that's piling up and how a publishing process could give the host more time for the conversations the show is meant to support.