Adam Bird watched the PodGlue book builder for ninety seconds and said it should be its own product.
He's probably right. That doesn't mean I'm doing it this month.
What he actually saw
We were on a call. I was walking him through PodGlue — the part where you point it at a podcast feed, it ingests the episodes, and a few minutes later you have a structured outline you could turn into a book. He went quiet for a beat, then said: "Junaid, that's not a feature. That's the product. Spin it off."
I've heard versions of this five or six times now from people I respect. Every time it lands the same way — a flush of validation, then a small panic. Because the person saying it is right and they're handing me a fork in the road they don't have to walk down.
Why the suggestion is right
The book builder solves a problem people will pay for today. Coaches, consultants, and host-led shows have years of audio sitting in their feed. They want a book out of it. Most won't transcribe 200 hours and hand it to a ghostwriter. They want something that does the structural work — chapter outlines, themes, callouts, a draft they can edit — without losing their voice.
That's a clean wedge. Narrower than PodGlue, easier to explain, easier to sell. A spin-off would probably grow faster than the parent in the next 12 months.
Why I'm not doing it
Because the parent is still mid-build, and I have one of me.
PodGlue's whole bet is that podcasters need an operating layer — guest CRM, prep, post-production, content distribution, and yes, long-form content like books — that talks to each other. The book builder is sharp precisely because it inherits the ingestion pipeline, the speaker diarization, the topic modeling. Pull it out and it becomes a brittle thin wrapper around a transcription API. The moat shrinks the second it's standalone.
There's also the founder math. Spinning out a product means a second positioning, a second landing page, a second pricing page, a second onboarding flow, a second support inbox, a second analytics dashboard. Each of those is a tiny tax. Two products at half-attention beats one at full attention only when the products genuinely don't compete for the same builder hour. Mine do.
What I'm doing instead
Three things, in order:
- Treat the book builder like a first-class feature inside PodGlue, not a quiet side door. Get it on the marketing page. Run a paid pilot with five hosts whose archives are deep enough to test it.
- Watch the engagement. If 80% of new signups touch the book builder in the first week and ignore the rest, that's the market voting. I'll listen.
- Write down the spin-off thesis now, with the criteria I'd need to see before pulling the trigger — ARR, customer concentration, infrastructure overlap, my own bandwidth. Future-me will be tempted to wing it. Past-me is going to hand him a checklist.
The harder lesson
Beta users telling you to spin something off is one of the best signals you can get. It means the thing you built is good enough to make a stranger imagine the alternate roadmap.
But your job as the founder is to stay on the road you picked, especially when the off-ramp looks paved. The strongest companies I know weren't built by taking every smart person's advice. They were built by knowing which advice to defer.
Adam, if you're reading this: thank you. The note is in the file. I'm just not opening it yet.