The source
A founder's 50-minute guest appearance on a SaaS podcast
An illustrative example: the founder of a small analytics company is interviewed about bootstrapping. The host asks about pricing, hiring, and saying no to customers.
Key passages we'll work from
- “Our first price was $19 a month because that's what felt polite. We raised it to $79 and lost two customers out of forty. Nobody else said a word.”
- “I hired our first engineer from our support inbox. He'd sent us three bug reports with the fix already written.”
- “The feature request I'm proudest of saying no to was a custom dashboard for our biggest customer. Building it would have made us a consultancy.”
The method
- Listen for the answers you'd repeat
The best material is usually a story you have told more than once. If you'd tell it at dinner, it will work as a post.
- Rewrite, don't transcribe
Spoken sentences run long and circle back. Keep the phrases that sound like you, cut the fillers, and reorder so the point lands in the first two lines.
- Add the detail the host didn't ask for
On a podcast you answer the question you're given. In a post you can add the number, the date, or the second half of the story that didn't fit the conversation.
- Mention the show, but don't lead with it
“I talked about this on X podcast” works well as a closing line with a link in the comments. As an opening line, it tells readers nothing about why they should keep going.
Three angles, not one summary
Each angle below could carry a post without the others. That's the test for whether you have distinct posts or one post cut into pieces.
The finished posts
Each post uses a different format so the series doesn't read like one idea split three ways.
Our first price was $19 a month. Not because of any research. Because it felt polite. A year later we raised it to $79. I braced for a wave of cancellations. We lost two customers out of forty. Nobody else said a word. The lesson I took: a price that feels polite to you can read as “not serious” to a buyer. If customers are getting real value, they usually expect to pay for it. (I told the longer version of this on a podcast this week. Link in the comments.)
I hired our first engineer from our support inbox. He'd sent three bug reports. Each one included the fix. No résumé screen would have found him. He wasn't looking for a job; he was just annoyed by our bugs. If you're hiring early, read your support inbox like a list of candidates.
Our biggest customer asked for a custom dashboard. It would have been about 15% of our revenue that year. I said no. Here's the reasoning: a feature only one customer can use doesn't make the product better. It makes you their contractor. Do that three times and you're a consultancy with a login page. They stayed. We built a flexible export instead, and four other customers used it within a month.
Mistakes to avoid
- Pasting a quote from the transcript as the whole post. Spoken language needs editing to read well.
- Assuming readers heard the episode. Every post must make sense on its own.
- Changing the facts to make a better story. If the number was 2 out of 40, say 2 out of 40.
The source material in this guide is an illustrative example written for teaching, not a real company's content.