What Consultants Should Say on a Podcast

A consultant should give the diagnosis away completely and keep the delivery. Explain how you tell one kind of problem from another, what evidence changes your mind, and where the common diagnosis is wrong. Keep the sequencing, the client-specific judgement and the actual execution for paid work. Buyers do not hire consultants for frameworks, which they can find anywhere. They hire for the pattern recognition behind the framework, and that does not transfer inside forty minutes no matter how much you explain.

Choosing which piece of judgement to bring is a different task, handled in podcast interview topics for consultants. What follows concerns the answers.

Give away the diagnosis, keep the delivery

Consultants worry about the wrong asset. The framework on slide four is not what anyone is paying for, and a competitor who hears it will implement it badly because they lack the two hundred engagements that taught you when it does not apply.

What earns work on air is a distinction. "When a sales team misses target, nine times in ten the diagnosis is a pipeline problem and six times in ten it is actually a qualification problem, and you can tell the difference by looking at whether late-stage deals are slipping or dying." That is a real diagnostic and it is safe to say, because acting on it requires knowing what to do next, which is the part you sell.

The things genuinely worth withholding are narrower than most consultants assume: a client's internal data, the specific sequence you would use for a named situation, anything a current engagement's contract covers, and pricing for work you have not scoped. Everything else is fair material.

Four kinds of listener, and why that changes your answer

Every sentence reaches all four groups simultaneously, and forgetting one of them is how consultants create problems for themselves.

Row three is the one that bites. A consultant who tells a host that a particular sector is hopeless, or that clients never follow through, has said it in front of clients who are paying them right now. Assume every current client will hear the episode, because a proportion of them will.

Row two matters less than consultants fear and more than they realise in one specific way. Describing your framework is safe. An unsubstantiated claim about your results is not, because a competitor in a pitch against you is entirely willing to quote it back and ask you to prove it.

On that point, the FTC's guidance on its endorsement guides is worth reading before you cite a result at all. It notes that a non-expert endorser can be liable for unsubstantiated statements about performance or effectiveness, and that flagging an outcome as atypical is not sufficient on its own, because an advertisement featuring exceptional results "must make clear to the audience what the generally expected results of following that same regimen are." Whether a sentence in a podcast interview sits inside that framework is a question for your own counsel, and nothing here is legal advice. The practical rule is simpler than the legal one: if you cannot show the result is representative, do not present it as the reason to hire you.

What to say about an engagement you cannot name

Keep the shape of the problem and remove everything that locates it. "A manufacturer with four plants had a forecasting process that took nine people three weeks and was less accurate than last year's actuals. What fixed it had nothing to do with the model. Two of the plants were deliberately under-forecasting, because their bonus depended on beating the number."

Nothing there identifies the company and the lesson is intact. Then run the identification test: sector, size, timing and problem type combined will often narrow to one firm in a small market, so change the details that do not carry the lesson, or ask permission, or use your own practice as the example instead.

Your own practice decisions are underused and completely safe. How you decide to decline work, how you priced something wrong, what you changed after a bad engagement, how you handle a client who wants a conclusion you do not hold. All of that is yours to discuss and it demonstrates judgement as well as any client story does.

The fee question

Give a band and a shape. "Diagnostic phase is four to six weeks at a fixed fee in the mid five figures, and implementation support is monthly after that" is an answer, and it does the qualifying work the appearance is for.

The reason to answer is arithmetic rather than transparency for its own sake. An interview reaching a few thousand people will produce a handful of enquiries, and if your fee band is unstated, a large share of those enquiries will come from organisations that could never buy. Each one costs a call. Stating the band converts that wasted time into listeners who either fit or self-select out.

How to disagree with the host without performing

Hosts invite disagreement because conflict makes better audio, and consultants tend to either fold or perform contrarianism. An audience hears both of those for what they are.

Disagree on a specific claim, name what would change your mind, and concede the part of their point that holds. "I think that is right for companies over a certain size and wrong below it, and the reason is that the overhead of the process exceeds the benefit when you have fewer than about thirty people doing the work. If you showed me a twelve-person team where it paid off I would want to know what else was true about them." That reads as someone who thinks for a living.

Contrarianism for effect is the failure mode to watch. Taking a position because it is unusual, rather than because you hold it, is obvious to the practitioners in the audience and they are the people you are trying to reach.

What to say about a project that did not work

This is usually the best material available and consultants avoid it hardest.

Pick a closed engagement where the client is unidentifiable, and keep the misjudgement in. The version where you were right all along and the client failed to implement is the version everybody tells, and an audience of operators discounts it instantly. The version where you misread the problem for two months, and you can say exactly what you should have asked in week one, is credible and rare.

There is a reason understating works better here than elsewhere. The Podcast Study 2026 from Point-To-Point Marketing and Strategic Solutions Research, presented on 23 September 2026 from a census-balanced sample of 1,205 US podcast consumers, found that 82 percent of listeners said the host was either a big part of or the only reason for their listening. That research describes the host relationship and not how audiences receive guests, and no published study measures the second thing. The working implication is that you are borrowing someone else's credibility for forty minutes, and a claim the host quietly doubts costs more than it returns.

What to say at the close

Name the situation, not the service. "If your last two strategy processes produced documents nobody used, that is the problem I work on" identifies one listener and releases the others.

Write the diagnostic distinction you will lead with, your fee band, and the failed engagement you are willing to describe on one page before the pre-interview call. Test the de-identified version on a colleague who knows the account. The podcast booking page for consultants explains how the target list gets built around buyers of that specific diagnosis, and podcast ROI for consultants sets out what the channel returns. If you want to sharpen the positioning first, book a call and we will pressure-test it before anything is pitched.