Who Should You Invite Onto Your Business Podcast? A Relationship-First Guest Strategy
John Corcoran interviewed other lawyers while he was practicing law, including lawyers more experienced than he was. Some might have looked like competitors. Some later referred him work that fit his practice better than theirs.
That doesn't make interviewing competitors a referral formula. It shows why a guest list deserves more thought than finding the most impressive available name. Two people can work in the same field and have different clients, specialties, and reasons to know each other.
For a business podcast, I want to answer two questions before sending the invitation: What can listeners learn from this person, and why is this a relationship worth developing? If I can only answer one, I still have preparation to do.
Give the Show a Purpose You Can Use When Choosing People
Start with two plain sentences. "This show helps these people understand this problem." Then, "These conversations help our business learn about or develop these relationships." Fill in the actual people and problem rather than leaving yourself a statement broad enough to justify anyone.
Suppose an IT consultant wants to help operations leaders understand major systems changes. That points toward clients who've managed a migration, executives responsible for implementation, and technology partners who understand the handoffs. It doesn't require every available entrepreneur with a new book.
In our conversation about healthcare strategy, Saul Marquez distinguished the person in the interview from the audience listening afterward. You may develop the guest relationship before publication, but the listeners still need a worthwhile episode. A hoped-for customer isn't automatically the right guest.
I wouldn't require an immediate commercial result either. Someone can challenge an assumption or explain a customer problem without ever hiring you. The test is whether you can explain the value before recording, rather than invent a reason after a pleasant conversation.
- 1. Define the Listener's ProblemWrite what this audience should understand after an episode.
- 2. Choose Relevant ExperienceFind a client, peer, prospect, or expert who can explain it firsthand.
- 3. Offer a Specific ConversationSay why you chose them and what participating will involve.
- 4. Deliver and ReconnectPublish what you promised and follow up for an actual reason.
Look at the People Already Connected to the Work
Steve Gordon described a useful content mix: clients, influencers, prospective customers, and solo episodes. I like that it doesn't assume every good episode requires meeting a stranger.
A current client can explain a difficult decision, what changed during a project, and what they'd approach differently. That is more useful than arranging an interview whose only job is getting them to praise your company. Their experience should teach something even if the listener never hires you.
In the IT example, a client might discuss which parts of a migration required more preparation than expected. Let the client supply the facts. Don't arrive with a tidy success story you've already decided they should tell.
Existing champions deserve attention too. John discusses that in his Dream 200 relationship approach. The person who has already made thoughtful introductions may understand your market better than the stranger you're spending weeks trying to reach.
That relationship can make the invitation easier to personalize. It doesn't remove the need for a useful topic. Invite someone because of what the audience can learn, not as a transaction for having sent you a referral.
Use the Guest Category to Improve the Questions
Different relationships call for different conversations. A prospective customer shouldn't receive a disguised sales presentation. A complementary provider shouldn't be pushed into a referral agreement. A client shouldn't feel obliged to deliver a testimonial.
| Guest category | Useful subject | Question to resolve before inviting |
|---|---|---|
| Current client | A decision, obstacle, or lesson from their experience | Can they discuss it publicly without turning the episode into praise for us? |
| Prospective buyer | The problems and choices they understand firsthand | Would we still publish a useful episode if they never buy? |
| Complementary provider | Another part of the same customer's problem | Do we serve a connected audience without assuming a referral deal? |
| Industry expert | A specific issue listeners need explained | What relevant experience makes this person worth hearing? |
| Experienced peer | A different approach or specialization | Can we exchange useful ideas without disclosing sensitive information? |
In our discussion of customer connections, Casey Cheshire emphasized the time and attention you offer the guest. He also described a conversation involving a prospect's Pardot migration needs that became a business opportunity. That's a reported example, not a result you can attach to every booking.
I'd keep the interview separate from any commercial discussion. The guest should have room to explain a real problem without realizing halfway through that the recording is a sales appointment. If both people later want to explore working together, make that a separate, explicit decision.
A bookkeeper and an operations adviser provide another possible pairing. They may serve similar business owners while seeing different problems. An interview can explore how financial reporting connects with the way work moves through a company. The topic earns the conversation even if neither sends the other a client.
Research What Someone Did, Not Just Who They Know
Read enough of the person's work to propose a specific subject. What problem have they handled? What decision can they explain? Which question would let listeners benefit from that experience?
Saul described a historical research project that narrowed several hundred prospective contacts to 70 potential early adopters using market mapping and voice-of-customer work. The useful habit for guest selection is investigating relevance. A new title, published opinion, or podcast appearance is a clue to research, not proof that someone wants to buy.
You may discover a less recognizable person has just dealt with the exact issue your audience faces. That's a stronger reason to invite them than being able to put a famous name on the episode list.
John also discussed researching the communities around difficult-to-reach people. You can learn from their peers and understand the conversation already happening in that field. That is different from pretending friendship or collecting introductions until someone gives in.
Keep a larger list for people who need more research or a legitimate introduction. Your next recording doesn't have to wait for your most ambitious target.
Make a Small List You Can Explain
I'd start with 12 realistic names, then choose six to investigate more closely. That's my suggested exercise, not a numerical system prescribed by the guests. The numbers matter less than the reasoning beside each name.
For each person, record the audience question, their relevant experience, your existing connection, what participation offers them, and the next invitation step. If you can't write a question you're genuinely curious about, don't send the message yet.
You could start with two clients or advocates, two prospective buyers, a complementary provider, and an industry expert. Change that mix if your show's purpose suggests something else. It's a starting roster, not a quota that justifies a weak booking.
Check capacity before committing. Someone must prepare, record, edit, approve, publish, and deliver the episode to the guest. Booking eight interviews while six are waiting for publication isn't relationship development. It's a new queue of promises.
Write the Invitation so the Person Can Make a Decision
Explain why you chose this person, what you'd discuss, who would benefit, and what participating involves. Include the actual recording length and process rather than promises you hope the production team can later deliver.
For the operations example, a hypothetical invitation could say: "Your experience helping teams adapt to a new workflow would be useful to the business owners our show serves. Would you be interested in discussing the decisions that made that transition easier?"
That gives the recipient a topic. It doesn't require exaggerated audience numbers or a paragraph of manufactured admiration. If they want more information, you have a clear conversation to continue.
Be willing to decline a poor fit too. Enthusiasm, follower count, and friendliness don't solve a missing audience question. A guest who wants an uninterrupted product pitch may be better suited to another format.
The reasoning beside the name matters more than the size of the guest list.
Related Conversations and Resources
Keep the Promise After They Say Yes
Thank the guest, publish the agreed material, and send the finished episode and any promised assets. Explain the process for flagging factual concerns if your arrangement includes it. Don't imply unlimited editorial control that nobody agreed to provide.
Ask a well-matched guest for another introduction when you can describe the experience you're looking for. "An operations leader who's managed a significant change" is easier to respond to than "anybody who wants to be on a podcast."
Then stay in touch when you have an actual reason. Remember an answer they gave, share something relevant, or offer an appropriate introduction. You don't need an artificial sequence of check-ins to prove the relationship exists.
If producing the episodes is taking the time you meant to spend on those conversations, bring your guest list and an existing recording to our podcast production page. At DFY Podcast, we help turn those interviews into published work so the person you chose doesn't become another guest waiting to hear what happened to the recording.