Lenny Rachitsky just published a detailed breakdown of his podcast tech stack, workflows, and hard-won lessons after building one of the most-listened-to product podcasts in the world. It is a generous post. It is also, unintentionally, a useful mirror for B2B marketing leaders who are trying to work out why their own podcast programme costs so much and produces so little.
The Stack Is Not the Hard Part
Lenny’s gear list is straightforward. A decent USB microphone, a remote recording platform, an editor, a scheduler. The tools are not exotic. Most of them cost less per month than a single LinkedIn ad campaign.
What the post actually documents, under the surface, is time. Booking guests, preparing briefs, reviewing edits, distributing clips, replying to listener questions. Lenny can absorb that time because the podcast is his primary product. For a B2B marketing team where the podcast is one item on a long list of quarterly deliverables, it is exactly the kind of work that gets deprioritised the moment a campaign goes into crisis.
This is the central failure mode of in-house B2B podcast programmes. The tools get bought. The first few episodes get recorded. Then the editor leaves, the host gets pulled into a product launch, and the feed goes quiet for six weeks. Listeners notice. Prospects who found you through episode three and were warming up quietly unsubscribe. The pipeline contribution never materialises, and the programme gets cut before it had any real chance to build an audience.
The stack is not the hard part. Consistent execution is.
What Lenny’s Lessons Actually Cost You
One of the most honest sections of Lenny’s post covers what he wishes he had known at the start. Better guest preparation. Tighter episode structure. A clear point of view rather than a series of loosely connected conversations.
Those lessons took him years and hundreds of episodes to accumulate. For a B2B company launching a podcast to support a sales cycle, you do not have that runway. If your first twenty episodes are meandering interviews with customers who say broadly positive things about your category, you will not build an audience. You will build a content archive that your sales team ignores.
The structural risk for B2B podcasts is not bad audio quality. It is undifferentiated content. A weekly show that covers the same themes every competitor covers, with no specific editorial position, no recurring format, and no reason for a senior buyer to listen rather than read a summary. Lenny built a clear identity early: rigorous, specific, practitioner-to-practitioner conversations about product. B2B podcasts that work do the same thing. They are not brand awareness plays dressed up as interviews. They are programmes with a defined audience, a clear point of view, and episodes that make a listener feel smarter about a specific, expensive decision they are trying to make.
If you cannot describe your podcast’s editorial position in one sentence, your listeners cannot either.
The Outsourcing Question Lenny Does Not Quite Answer
Lenny handles most of his production personally or with a small trusted team. That works when the podcast is the business. For a B2B company, the host is almost always a senior leader or subject matter expert whose time costs significantly more per hour than any production fee. Every hour a VP of Product spends chasing a transcript edit is an hour not spent in customer conversations.
The teams that run B2B podcast programmes sustainably are the ones who have separated the creative from the operational. The internal host or executive brings the point of view and the relationships. An external team handles everything that turns a recorded conversation into a published, distributed, and repurposed asset. Not because the internal team cannot do it, but because they consistently will not, once the quarter gets busy.
Lenny’s post is worth reading in full. But read it as a map of the operational load you are taking on, not just as a gear guide. The question to answer before you buy any equipment is who owns this when it is not convenient.
