Lenny Rachitsky built one of Substack’s top five business newsletters (531,000+ subscribers) and a profitable podcast by treating his writing as a product that solves specific jobs for product managers, founders, and builders — prioritizing high-signal, actionable content over style, and growing almost entirely through word of mouth and Substack’s recommendation engine.
Origin: leaving Airbnb and starting the newsletter
After seven years at Airbnb, Lenny left to start a company but realized he would have to relearn everything unless he captured what he knew.
He wrote “What seven years at Airbnb taught me about building a business” as a personal reference; a friend urged him to publish it.
The post went viral on Medium, got featured on the homepage, and seeded his initial audience and Twitter following.
He didn’t plan a newsletter business — he just kept writing useful posts because they resonated, and growth compounded from there.
Core philosophy: jobs to be done and high signal-to-noise
People read newsletters because they have a “job” they want done: get better at building product, grow their product, accelerate their career.
Lenny frames every post around a specific question his readers have (e.g., “How do I get my first 1,000 users?” “What is good retention?”).
He aims to answer each question better than anything else available, treating the newsletter as a puzzle board of founder/product problems to solve.
He avoids “thirsty” audience-building tactics; instead he focuses on delivering value, trusting that word of mouth drives sustainable growth.
Writing style is secondary: he strips intros, cuts fluff, leads with the answer, and optimizes for “high signal-to-noise, actionable, succinct” information.
He reads each post 10–30 times, cutting, simplifying, and rearranging until he can’t find anything else to improve.
Research process: interviewing the best and synthesizing patterns
For deep-dive series (marketplaces, B2B startups, product-market fit), he builds a wish list of top companies (Uber, Airbnb, Etsy, Stripe, Figma, etc.).
He secures interviews via warm intros, LinkedIn connections, and his growing network — often talking to founders or early employees, not just CEOs.
He asks every interviewee the same structured questions (e.g., “How did you decide supply vs. demand constraint?”).
He pastes all answers into a doc, stares at them, and looks for recurring patterns, frameworks, and vivid stories.
Example: the “start with one company that loves you” pattern for B2B product-market fit emerged from Figma’s obsession with making Coda successful.
He moves from raw notes in Coda (his content hub with calendar, idea park, and writing prompts) to Substack for final formatting.
Growth and distribution: word of mouth, guest posts, and Substack recommendations
99% of growth comes from word of mouth: readers share useful posts with colleagues; Substack’s “recommendations” feature created a massive inflection point (9,000+ newsletters now recommend his).
Early boosters: Medium feature, Andrew Chen retweet, guest posts on First Round Review and Andrew Chen’s blog — all serendipitous, not strategic.
He doesn’t optimize email conversion rates; he tracks post views and learns from underperformers (e.g., a hiring post failed because it lacked surprise and unique insights).
LinkedIn drives more traffic than X/Twitter, but X is more fun and conversational; he cross-posts with slightly more depth on LinkedIn.
Schedule, productivity, and protecting creative time
No meetings before 3 p.m. — mornings are reserved for deep work, research, and writing.
He never pulls all-nighters; if a post isn’t ready by Tuesday, he takes “PTO” (a self-invented policy) rather than ship low-quality work.
He avoids conferences, panels, networking events, and most interviews — citing Naval’s warning that success brings distractions that pull you from the work that made you successful.
Saying no is systematized: policies (“I don’t do talks”), excuses (“just had a kid”), templates, and sometimes simply not replying.
He works on 3–4 posts simultaneously, uses guest posts (heavily edited) to manage load, and takes real vacations (though growth plateaus without promotion).
Editing: friction, copy editors, and killing darlings
He edits by re-reading from the top repeatedly, hunting for “friction” — confusion, boredom, tangents — like a smoothie that won’t go through a straw.
A copy editor (~$100/post) catches ~100 issues per post (grammar, capitalization, pronouns) that he’s blind to; he considers this a game-changer.
He cuts beloved sections if they derail the core answer (“kill your darlings”), often saving them for future posts.
Introductions are the hardest part; he keeps a prompt list in Coda: “What’s surprising? What’s a story? What’s unexpected?” but still struggles.
Tools and environment
Coda: content calendar, idea park, initial drafts, writing prompts, research synthesis.
Google Docs: only for guest post collaboration (superior commenting/editing).
He deliberately avoided a narrow “product management only” label; his personal monopoly spans product, growth, career, and company-building — whatever he’s genuinely curious about.
This breadth sustains motivation; he warns against picking a niche you’ll hate writing about for years (“prison of your own creation”).
“Niche fame”: recognized by product folks in SF, asked for selfies, but not mainstream famous — ideal for access without lifestyle disruption.
He has no master plan, no empire ambition, no book (yet); the podcast (suggested by Harry Stebbings) now earns more than the newsletter and grew faster.
At 1,000 paid subscribers he made $100k/year — Kevin Kelly’s “1,000 true fans” in action; growth still hasn’t hit an S-curve plateau.
Advice for writers: write from experience, serve the reader, ignore the meta
Use writing to capture lessons while you’re in the job — memory fades fast after you leave.
Write about what you’re excited by, not what you think will grow; the vent diagram of “what you love” and “what people value” is where durability lives.
Don’t overthink platform, branding, design, or strategy — every hour spent there is an hour not writing awesome stuff.
Quality + consistency = success; “good” is probably good enough, but strive to be among the best on your specific topic.
Criticism stings (he shudders at the word), but he mines it for corrections and signal; a Hindi subtitles misfire taught him not to assume audience needs.
He admires high signal-to-noise writers: Tyler Cowen, Noah Smith, Ben Thompson, Kevin Kelly, Rick Rubin (taste via consumption).
If a “Write of Passage” archetype existed, it would be him: domain expertise, loves the craft, avoids distraction, serves the reader.
