What SaaS Founders Should Say on a Podcast

A SaaS founder should spend an interview describing the problem their customers had before the company existed, one number they have decided in advance they can publish, and one opinion about their market they would defend in front of a competitor. The product should come up as little as possible. A founder who spends forty minutes explaining what the software does has given away the slot and will get nothing from it.

That advice is about delivery rather than subject selection. Choosing which subject to pitch is a separate job, covered in podcast interview topics for SaaS founders. What follows is the substance of the answers once you are recording.

How to answer "so what do you do?" in two sentences

This question opens almost every interview and most founders waste it. The common failure is to start with the category, which tells the listener nothing they can hold on to.

Name the person with the problem, say what the problem costs them, then say what changes. "Finance teams at mid-market manufacturers close their books in eleven days because three systems disagree about the same invoice. We make the three agree, so the close takes four." A listener can repeat that. They cannot repeat a sentence containing the words platform and workflow.

There is some evidence on timing. 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 55 percent of listeners decide what they think about a new podcast within the first five minutes and 14 percent decide within the first minute. That research measures how people judge a show rather than how they judge a guest, and nobody has published research on the second question. A founder who takes four minutes to get to the problem is still spending the audience's patience on setup.

The one number you are allowed to say out loud

Decide this before the recording, with whoever else has a claim on the answer. A private company has no obligation to disclose anything, and a founder who improvises a figure on air has published it permanently.

Pick one number and hold to it. Customer count in a band works. A growth rate over a defined period works. Retention expressed as a range works. Annual recurring revenue to the dollar is the figure a host will push for and the one most founders should decline, because it invites a valuation conversation, it dates immediately, and it is the number your competitors want most.

Declining well matters as much as choosing. "We do not publish revenue, but I can tell you we have gone from forty to a hundred and ten customers in eighteen months and churn is under two percent a month" answers the underlying question, which was about traction. A flat refusal reads as evasion; a substitution reads as discipline.

What to say when the host brings up a competitor

The pattern in the right-hand column is that every answer names a group of people you are not for. A founder who claims to suit everyone has told the listener nothing, and a listener who hears a clear exclusion learns whether they are in or out, which is the only thing the interview can usefully do for them.

Never criticise a competitor by name. Some share of the audience is a customer of theirs, and you have just told those people their judgement was poor.

What to say about pricing

Say the actual number if you publish it. A founder who publishes pricing on the website and then goes vague on air sounds like they are hiding something.

If you do not publish pricing, say why in one sentence and give a shape. "It scales with the number of production sites, and a typical customer is in the low five figures a year" is an answer. "It depends on your needs" is not, and a host will move on rather than pressing, which means you have lost the chance to qualify half the audience out of contacting you.

The churn question, and the failure question

A good host will ask what is not working. Answer it, because the alternative is worse than the admission.

Pick a failure that is genuinely resolved and that reveals a judgement rather than an accident. Three shapes work: a segment you sold to for a year before concluding they were unservable, a feature you shipped that nobody used along with what you had misread about the workflow, or a pricing change that cost you customers and what you would do differently now. All three are safe because they are finished and because the lesson transfers to a listener running a different company.

Two things to keep out. Anything about a named customer's internals, which is theirs and not yours to discuss. And anything currently in dispute, under negotiation or unresolved with an investor, because a recorded answer about a live situation cannot be taken back.

What to say about automation in your product

Hosts ask about this constantly and most founders answer with a category label, which is now worth nothing because every company uses it.

Say what the software decides and what a person still decides. "It drafts the reconciliation and a controller approves every one over a thousand dollars" is specific and checkable. Then say what it gets wrong, because a founder who admits a failure mode is more credible than one who does not, and every practitioner in the audience already knows the failure modes exist.

If the honest answer is that automation is a small part of the product, say that. Overclaiming here is the fastest way to lose the technical part of your audience.

What to say when the host hands you the floor at the end

The reflex here is to recite a URL. A listener cannot type a URL while driving, and the show notes will carry the link anyway.

Use the slot to describe the person you want to hear from. "If you run finance at a manufacturer with more than three plants and your close takes longer than a week, I would like to talk to you" does work that a URL cannot: it tells one specific listener the conversation is for them, and it tells everyone else not to bother, which protects your inbox.

One note on format before you plan the close. Acast's Podcast Pulse 2026, run by Differentology across 13 markets with 4,300 respondents aged 16 to 64 and published on 17 September 2026, found that 88 percent of podcast fans consume both audio and video and 63 percent start an episode in one format and finish in another. That study measures consumption habits and not guest outcomes. It does mean you should assume some of the audience is watching rather than listening, so avoid answers that depend on something you said twenty minutes earlier.

Write your two-sentence description, your one publishable number and your closing ask on a single page before the pre-interview call, then test them on someone who does not work with you. If you want a version of that page built to the format hosts and producers actually read, use the one-sheet builder, and the podcast booking page for SaaS founders explains how we match founders to shows where that description will land.