A Business Card Says What You Do. A Book Says Who You Are.

By Junaid Ahmed

I came across a story about Michael DeLon, a publishing consultant who walks into every client meeting with a copy of his book sitting on the table before anyone says a word.

He doesn't open with credentials. He doesn't explain his process. The book does it. The meeting starts already tilted in his direction.

That's not a sales trick. That's positioning made physical.

Here's what I've been thinking about since I read that.

A business card says what you do. A podcast says what you talked about last Tuesday. A book says who you are, how you think, what you believe, and why you're the right person to solve this specific problem.

Those are three completely different things.

Podcasters have figured out how to do the first two. Most of them haven't made the third thing yet. And the strange part is, they already have everything they need to.

I have 750+ episodes of Hacks and Hobbies. For years I was doing the same thing as everyone else: describing the show, listing guest names, talking about what we covered.

None of that told anyone who I was or what I actually believed.

The through-line was there the whole time. Every guest, every conversation, every episode, it kept coming back to the same idea. That success is not a solo endeavor. That community is the engine. I just hadn't named it yet.

I didn't need more episodes to say that. I needed to look at what I'd already built.

Henrik De Gyor is a podcast consultant who has interviewed hundreds of podcast producers, and he asked each one the same set of questions.

He didn't plan to write a book. He was just doing interviews.

But because he asked the same questions across hundreds of conversations, patterns emerged. Answers rhymed across guests who had never met each other. The book was already organized. He just hadn't looked at it that way.

That's what happens when you interview people on the same topic long enough. The IP accumulates. What's missing isn't the material, it's the structure.

Most podcasters I talk to think writing a book means starting from scratch.

Sit down, open a blank document, write a hundred thousand words. That's not wrong, but it's also not the only path. And for podcasters, it's probably the harder one.

The easier path starts with a question: what is the one argument my show has been making for years without ever stating it directly?

Answer that, and you're not starting a book. You're surfacing one.

Your transcripts already contain the through-lines. The quotes that would anchor a chapter. The guests who said the same true thing from completely different angles. None of that needs to be written. It needs to be found.

PodGlue's IP Lab does exactly that.

You feed it episodes. It reads the transcripts, identifies recurring themes, clusters conversations that belong together, and builds a first-draft manuscript organized by idea instead of by date.

The first time I ran my own interviews through it, I had a working draft in less than an hour. Not a polished book, a working document that proved the book existed and showed me its shape before I'd written a single original word.

That's the moment the project becomes real. Not when you decide to write a book. When you see that it's already there.

If you've been podcasting on the same topic for two or three years, you've been building proof the whole time.

Not just proof that you show up. Proof that you think deeply about something. That you've stress-tested your ideas across dozens of conversations. That you've sat across from the people doing the actual work and asked them hard questions.

That's what a book can carry. A podcast delivers it one episode at a time, then it moves on. A book holds it in place.

If you want to see what's hiding in your archive, that's what IP Lab is built for.

Join the waitlist →

Content library