Handling podcast, press, and speaking invites without becoming a full-time guest

If you've built any visibility in your consulting practice — published a piece that went somewhere, gave a talk that got shared, ran an engagement that became a case study — the inbound starts. Podcast invites, press requests, conference speaking, workshop facilitation, "would you be a quote source on this article?" The cumulative volume is small in any given week and substantial across a year.

The trap is that each individual invite looks small ("just 45 minutes for the podcast"), so the reflex is to say yes. Twenty yeses across a year is a meaningful chunk of calendar and prep time, much of which produces nothing for the business.

This article is about how to filter them, what to accept, and how to decline gracefully.

The three-question filter

For every inbound invite, three questions:

1. Does the audience match the buyers I want?

The honest test is: would a meaningful fraction of the podcast's listeners, the conference's attendees, or the article's readers plausibly hire me for the work I do?

If yes — accept seriously.

If no — usually decline, regardless of how flattering the invite is.

The high-volume podcast for a tangential audience is worse than the niche podcast for the exact audience. Subscriber counts and prestige matter less than fit. A podcast with 800 listeners who are CMOs at $20M+ companies is worth more than one with 80,000 listeners who are mostly other consultants.

2. Can I actually be valuable in this format?

Some formats are wrong for the consultant's strengths. A 5-minute Bloomberg TV hit on a topic you know cold is a fine use of time. A 45-minute open-ended podcast on a topic you have lukewarm thoughts about is a bad use.

The honest answer is sometimes "no." Decline if so.

3. What's the realistic effort cost?

Most invites have a hidden tail. The 45-minute podcast also requires 30 minutes of prep, 15 minutes of "tech check," and inevitably a reschedule. The article quote requires 20 minutes of email back-and-forth. The conference talk requires deck prep (4-8 hours) plus travel.

Estimate the real effort cost, not the on-stage cost.

If the answer to question 1 and 2 is yes and the effort cost is bounded, accept. If 1 or 2 is no, decline regardless of how light the time commitment looks.

The "yes" response template

When you're accepting, the response should set the engagement up cleanly:

Hi [name],

Thanks for the invite — happy to come on the [podcast / panel / article].

Before we lock in a time, a few quick logistics:

1. Format and length. I assume [podcast / written interview / live talk]? Confirming the length so I can plan around it.
2. Topic specifics. What angle are you most interested in? I'd rather come in prepared on the actual conversation than wing it.
3. Audience. Quick context on who typically [listens / attends / reads] would help me calibrate.

For scheduling, I'm generally available [Tuesday / Wednesday / Thursday] afternoons Pacific. Pick a slot that works on your end and I'll confirm.

Looking forward to it, [Your name]

Two things this does:

• Sets up the prep. You'll know the audience and angle before you walk in. Better preparation = better content = more leverage from the appearance.
• Bounds the calendar. You named your availability windows; they pick within them. Avoids the "they suggest Friday at 8pm" pattern.

The "no" response template

The decline is where most consultants overthink. Don't. A short, warm, no-explanation-needed response works almost universally:

Hi [name],

Thanks for the invite — appreciate you thinking of me. Unfortunately I'm going to pass on this one. My calendar is committed through [vague timeframe] and I'm trying to keep the scope of what I take on focused.

If you're looking for someone specifically on [topic], a couple of colleagues who do excellent work in this area: [Name 1] at [firm] and [Name 2] at [firm]. Either would be a good fit.

Wishing you a great [podcast season / conference / article], [Your name]

Three things to notice:

• No detailed explanation. "My calendar is committed" is sufficient. Detailed reasons invite negotiation.
• The referral. This is the part most consultants skip. A specific 1-2 person referral makes the decline relationship-building rather than relationship-neutral. The asker gets value; you build goodwill with both the asker and the referred.
• Warm close. "Wishing you a great X" lands kindly without being effusive.

The asker almost always accepts the decline gracefully. The relationship is intact; the calendar is protected.

The "let's see if it's a fit" middle response

For invites where you're uncertain, a brief filtering exchange works:

Hi [name],

Thanks for reaching out. Quick clarifying questions before I commit:

1. What's the format and typical length?
2. Who's the audience — what's the typical attendee / listener profile?
3. What angle are you most interested in covering?

Once I have those, I can give you a clean yes or no.

[Your name]

This works because it doesn't commit either way. If the answers come back strong on all three filter questions, accept. If they come back weak, decline with the template above.

The annual budget

A useful discipline: set an annual budget for how many invites you'll accept. Most working consultants find the right number is 6-12 per year of substantive guest appearances (podcasts, panels, talks) plus 3-6 quote-source contributions.

That's roughly 1-2 substantive appearances a month at the high end. Less than that, you're under-investing in visibility; more than that, you're starting to optimize for being a guest instead of being a consultant.

Once you've hit the annual budget, the filter shifts harder toward decline. The opportunity cost of yes #14 in a year is now higher than the opportunity cost of yes #6.

What kills the system

Three patterns:

Saying yes because it's flattering. The invite came; you're known enough to be asked; the ego wants to say yes. Notice the pattern and override it. Flattery is a bias to filter out, not a reason to accept.

Saying yes because it's "easy." Many invites look easy in the abstract — 45 minutes, just chat, no prep needed. The real cost is always higher. Estimate honestly.

Saying yes because someone specific asked. Sometimes the asker matters — a long-time colleague, a key referral partner, a high-profile peer. Worth doing on relationship grounds even if the filter questions are weak. The fix isn't to never accept these; it's to be aware that "this is a relationship investment, not a business-development one" and budget for it explicitly.

What the visibility actually does

Worth being honest about what guest appearances do for an independent consulting practice:

• They don't directly generate engagements. A consultant who does 12 podcast appearances a year rarely traces specific engagements to specific podcasts.
• They compound network effects over years. The cumulative effect of "I keep seeing this consultant in places I respect" is real, but it operates on a 2-3 year horizon, not a quarterly one.
• They strengthen positioning. When a prospect is evaluating you against a competitor, having visible third-party endorsements (you on respected podcasts, you quoted in industry pieces) tips the calibration.
• They lower friction on new business. Buyers who already know your work from outside venues are easier to engage. Less explanation required.

The right framing: visibility is a long-term investment in positioning, not a short-term lead generator. Budget accordingly.

Operationalizing it

Three patterns:

The filter habit. When an invite arrives, run the three questions before deciding. Don't reply immediately; reply within 24 hours after filtering deliberately.

The templated responses. The yes-with-logistics, the no-with-referral, the let's-see-if-fit. Save them. Adapt per invite. Real-world time per invite: 5 minutes (decision + reply).

The annual budget review. Once a year, look at what you accepted and what came of it. Adjust the budget and the filter accordingly. Many consultants discover they're over-accepting at the niche end (low-fit podcasts) and under-accepting at the high-value end (industry-specific events where buyers actually attend).

The system is small. The cumulative effect of running it for several years is large. Build visibility intentionally; protect the calendar; let the right yeses compound while the wrong ones never enter the schedule.