69 resources from Lenny's Newsletter we point founders to, and the questions each answers.
📄 Article
✓ Link checkedFreemiumIntermediate
Why we picked it
Market size is meaningless until you know exactly who you're for, and Lenny turns that into a concrete, repeatable ICP exercise from real B2B operators. It grounds your SAM in an actual customer definition instead of a fuzzy segment.
Why we picked it
Synthesizes 25+ B2B founder interviews into concrete pre-build validation paths, so you don't build an MVP before you need one. The intro (the four validation paths) is free and directly on-topic.
Why we picked it
The canonical PM-community reference on choosing what to build next, from the most-read product newsletter. A pragmatic overview of scoring frameworks and how to actually use them.
Why we picked it
A data-backed teardown of how companies like Figma, Gusto, and Vanta actually sourced their earliest customers. Replaces guesswork with real patterns.
Why we picked it
A tactical follow-on covering the channels and motions top B2B startups scale after the first ten. Grounds distribution strategy in real company examples.
Why we picked it
Shows exactly how top startups turned early cold/warm outreach into paying customers, with real message-level detail. Grounds cold outreach advice in what actually worked.
Why we picked it
Lenny distills how the best product teams pick a single North Star that captures real customer value and drives the whole growth model, with concrete company examples.
Why we picked it
Based on studying 100+ consumer companies, Lenny shows that lasting growth comes from becoming world-class at one growth engine, viral, SEO, or paid, rather than dabbling in all three.
Why we picked it
From the founder of CMX and author of The Business of Belonging, a practical framework for deciding whether to build community and tying it to real business goals.
Why we picked it
Concrete retention benchmarks and cohort-analysis methods gathered from dozens of top companies, so you can tell a healthy retention curve from a dying one.
Why we picked it
Battle-tested referral advice from the person who turned Airbnb's host referral program into its biggest driver of supply growth, honest about when referrals do and don't work.
Why we picked it
A myth-busting piece showing most 'viral' growth is actually broadcast reach, so you can stop praying for virality and engineer word-of-mouth instead.
Why we picked it
A modern, tactical fundraising and pitch playbook aggregating advice from top operators and investors. Strong on how to build the narrative and materials that actually move investors today.
Why we picked it
A scoring matrix ranks ideas on paper, but the honest tiebreaker is which idea real people reach for. Todd Jackson (First Round) built this from interviews with founders of Vanta, LaunchDarkly and others, and it lays out cheap tests you can run on both ideas in parallel: customer interviews, mockups, fake landing pages, and doing the work manually before you build anything. Run the same test on both ideas and let the demand signal, not the debate, pick the winner.
Why we picked it
This is the most concrete answer to which of your two customers to define first, built from interviews with 17 major marketplaces (Airbnb, Uber, Etsy, DoorDash and more) rather than one founder's opinion. The finding is blunt: about 80 percent of successful marketplaces poured their early effort into the constrained side, usually supply, and built liquidity in one narrow niche before expanding. It is a practical playbook you can map onto your own marketplace this week.
Most successful marketplaces defined and won the constrained side first (usually supply), then let demand follow, so start by naming your ideal customer on that side.
Early liquidity comes from going deliberately narrow (one city, one category) and getting it genuinely working before you widen the definition of who you serve.
The number of levers the biggest marketplaces used to grow that first side was small (a median of two), so focus beats spreading effort across both sides at once.
Why we picked it
This is the canonical answer to your exact fear: you do not need both sides at scale, you need one tiny network that works. Chen (ex-Uber growth, now a16z) argues you win by nailing the smallest self-sustaining group first (one campus, one office, 5pm at one train station), then repeating it. As a solo founder, that reframes an impossible two-sided launch into one winnable, hand-run pocket of density.
Stop trying to fill a whole market. Pick the smallest group where the product is genuinely useful even with almost nobody else on it, and make that one network dense before expanding.
Early on, momentum beats scalability: launch stripped down, obsess over one atomic network, and only worry about repeatability once the first one clearly works.
Solving one side first is a feature, not a compromise: a working atomic network is what actually pulls the other side in, instead of you begging both sides at once.
Why we picked it
When people sign up and vanish, the first fork is: did they never hit the moment where the product clicked (activation), or did they hit it and still leave (a deeper product or fit gap)? This piece gives you a concrete way to find that moment for your own product, brainstorm candidate aha actions, then check with data whether they actually cause retention rather than just correlate with it. That test is what tells you which problem you are staring at, so it is a starting point for the diagnosis, not the whole answer.
Why we picked it
Todd Jackson studied how dozens of now-large companies validated their very first idea. The pattern that repeats: deliver the outcome by hand, talk to real users, and watch for genuine emotion. A polite 'that's cool' is a no. Strong reactions are the signal you want.
Why we picked it
If you are selling to companies rather than consumers, this is the specific playbook. Four concrete ways founders got signal before building, from doing the job by hand for one customer to interviewing dozens of potential users first.
Why we picked it
This piece helps you time the shift: it names the handful of B2B growth channels, argues most of your early growth comes from just one, and shows when to start layering the next one. That timing is the whole game, since dropping outbound too early or clinging to it too long both cost you. Use it as a starting point to figure out which channel is actually carrying you right now.
Most early B2B growth comes from a single dominant channel (inbound self-serve, inbound sales-assist, or outbound), so name yours before spreading thin.
Additional channels (content and SEO, paid, partnerships, expansion) are worth adding only once your primary channel is working, not as a rescue.
Nearly every B2B company eventually builds a sales motion, so the question is sequencing, not whether to move beyond cold outreach.
Why we picked it
Most first 100 users advice is vague. This piece is the opposite: it groups the real cold start tactics into seven concrete plays and names the exact company behind each one, from Tinder pitching sororities in person to Dropbox seeding online communities. Read it as a menu to pick from, not a checklist to run top to bottom, since almost every founder here won just one channel that fit them.
The tactics sort into seven repeatable plays: go to users offline, find them online, invite friends, manufacture exclusivity, use influencers, get press, and build a community before launch.
Most companies got their first users from a single channel that fit their product, so the job is finding your one, not doing all of them.
Nearly all of it was unglamorous and manual: door to door, one community at a time, personal invites rather than a growth machine.
Why we picked it
Once you know your curve should flatten, the next question is where it should flatten, and this piece answers it with concrete benchmark ranges by business type instead of hand-waving. Lenny pooled numbers from 20-plus growth leaders and investors, so you can put your own 6-month retention next to a real bar for your category. Treat the ranges as a starting point for judgment, not a pass-fail line, since a consumer social product and an enterprise SaaS live in completely different worlds.
The bar is category-specific: roughly 25% good / 45% great for consumer social, 40% / 70% for consumer subscription, and 70% / 90% for enterprise SaaS at 6 months.
Judge yourself against your own business type, not a global average. Comparing a marketplace to a SaaS number will just mislead you.
It also splits user retention from net revenue retention, a useful reminder that a subscription business can look flat on users while still growing revenue per account.
Why we picked it
A useful counterweight to the raw MVP idea, drawing on stories from Airbnb and WeWork about building the smallest thing people actually love. It helps you decide how much polish your test really needs so you learn something real and not just that a rough demo felt rough. Read it once you understand the basic MVP and want to avoid shipping something too thin to judge.
Why we picked it
This nails the discipline behind the highlight reel: with prospects you share momentum factually without handing over what they have not earned. The line to internalize is that you can say 'we are in a third meeting with a top multi-stage fund' without naming anyone, and you must never fake a term sheet or name investors who have not committed. For the growth fund that passed, that is the whole game: every touch carries one real positive development (revenue, a key hire, a feature, angels closed) so the story compounds, but your hard financials stay with the people already on the cap table.
Why we picked it
Once you are testing an idea, this piece gives you concrete signals that tell you whether it is actually working, from retention curves to organic word of mouth. It collects how experienced founders and investors describe the moment an idea starts to land. Read it so you know what evidence to look for instead of guessing whether the idea is good.
Why we picked it
Jackson breaks fit into levels and asks how acute the problem is, how reachable the audience is, and how differentiated your answer needs to be, which lines up neatly with judging an idea. It gives you a shared vocabulary for whether your idea is worth deeper investment. Read it for a structured way to grade an idea across problem, audience, and value.
Why we picked it
A deep conversation on why direct questions fail and how story-based interviews surface real behaviour. Torres names the common mistakes founders make (leading questions, asking about the future) and how to fix them. A good listen for your commute.
Why we picked it
Colonna, the coach founders go to when they are cracking, gives the question that actually moves boundaries: how am I complicit in creating the conditions I say I don't want? A founder who claims the startup demands 12-hour days often needs to notice how much of the always-on is self-imposed, attachment to outcome and identity fused to the company, not the business genuinely requiring it. That is the honest layer under a stop-time rule: the off-switch fails when your sense of worth is wired to the inbox. This is the self-inquiry that makes a boundary stick instead of collapsing the first stressful week.
Why we picked it
A raw first-hand account of exactly this fear. Kantaria names the psychology head-on: VC money is a drug, you sell your vision to people who praise you, and then the calls, the compressed timelines, and the constant signaling arrive. His sharpest confession is that once investors backed Savvy, he stopped trusting market signals because 'if investors backed us, we must be on the right path.' That is the trap the pressure sets, and watching a founder walk into it and out the other side (to an acquisition) defuses the terror better than any pep talk.
Why we picked it
When a strategy fight has calcified into a standoff, this walks through the mechanics of getting unstuck: name what each of you actually needs, separate that from what is best for the company, and bring in structured help when direct conversation stalls. It is the practical companion to Perel: less about the feelings underneath, more about the process to run when you cannot agree on what would even settle the question.
Why we picked it
This is the exact move your answer prescribes, from the former pro poker player who turned it into a discipline. Duke tells you to run a pre-mortem before you start, imagine the failure, name the early warning signs, and commit in advance to a tripwire (a specific metric plus a timeline) so you quit on data instead of on despair. Her line that founders should benchmark against concrete signals like usage thresholds and unit economics, and that if you are already wondering whether to quit it is probably overdue, is the antidote to the bootstrapper who drifts for years on savings and hope.
From
Lenny's Newsletterby Annie Duke (interviewed by Lenny Rachitsky)~25 min read
Set kill criteria before you launch: a specific metric and a date, decided while you are still clear-headed, so the decision to stop is already made when the number comes in.
Use a pre-mortem: picture the business having failed, list what early signals would have predicted it, and turn those signals into your tripwires.
If you are already asking whether to quit, the honest answer is usually that it is overdue, because sunk cost and attachment make founders hold on far too long.
Why we picked it
The qualitative half of the answer, told through founders describing the moment things flipped: inbound you cannot keep up with, servers falling over, customers telling their friends without being asked. It is useful precisely because the feeling arrives before the metrics confirm it. Read it to recognize the pull when it starts.
Why we picked it
Consumer PMF advice does not map cleanly onto B2B, where deals are few, considered, and slow, which describes many Indian startups selling to businesses. This guide covers the specific signals that matter when you have ten design partners instead of ten thousand users. Read it if the 40 percent survey feels awkward for your low-volume, high-value product.
Why we picked it
Lemkin makes the case, with hard numbers, for why founders must win the first 10 to 30 customers themselves before anything scales. That is the same depth-over-volume logic your short answer describes: real validation is a founder in the room getting a buyer to yes. It also warns why hiring salespeople before you have sold yourself quietly kills startups.
Why we picked it
Lenny interviewed dozens of people who built Airbnb, DoorDash, Thumbtack, Etsy, and Uber, then distilled how they actually got started. This opening piece frames the chicken and egg problem and why almost every winner picked one side to build first. It is the single best overview of the exact question you are asking.
Why we picked it
Once you decide supply is the harder side to get, this piece is the tactical playbook for signing up those first suppliers by hand. It catalogues the concrete levers real marketplaces used to seed supply from zero, with examples you can copy this week. Pair it with the overview to go from theory to a to-do list.
Why we picked it
The consumer counterpart to finding B2B customers, focused on manually recruiting your first users for a consumer product. It is full of tactics for going into communities, WhatsApp and Facebook groups, and forums where your users already spend time. Practical fuel for reaching a market that the metros are ignoring.
Why we picked it
Real benchmark data from founders on what a waitlist actually converts to paid, so you can calibrate expectations against your numbers. The clearest finding is that speed matters: convert people within a month and you can hit 20 percent or more, wait three months and it falls below 10 percent. Use it to stop hoarding signups and start reaching out now.
Why we picked it
The other side of the question, honestly told, including when a coordinated launch is actually the wrong move. It shows how much prep and existing momentum a real launch needs, which is exactly why you save it for pouring fuel on a fire. Read it so that when you do launch, you time it after your pitch already works.
Why we picked it
A companion breakdown of how early users became paying customers, including companies that had no paid plan at launch and worked with power users to figure one out. It is useful for the moment your former contacts have engaged and you need to turn genuine value into a fair ask for money. It keeps the focus on earned conversion rather than pressure.
Why we picked it
The other half of the problem: once you have supply, how do you get the first buyers so sellers do not churn out of an empty room. It covers hand matching early demand and the tactics marketplaces used before paid channels made sense. Read it alongside Part 3 so neither side of your market sits idle.
Why we picked it
A practical, structured playbook for the exact fear in this question: users quietly leaking away. Lenny breaks retention into activation, engagement, and resurrection, and shows that almost every durable win comes from fixing the first 7 to 30 days. It gives you concrete levers to pull rather than a vague plea to care more.
Why we picked it
Lenny addresses prioritization specifically for early startups, where the usual scoring frameworks break down and speed matters more than spreadsheets. It helps you decide what to work on when you have almost no data and everything feels urgent. Practical and grounded in how real early teams actually choose.
Why we picked it
Years on, Ries revisits what the lean method got right and where the MVP idea gets abused, which is precisely the trap in your question. He is candid that the hardest part is knowing what minimal, viable, and product really mean up front, so start smaller. A grounded read that treats the MVP as a tool that is easy to misuse rather than a magic word.
Why we picked it
Jason Levin grew a product to $100K ARR on Bubble with no engineers, then raised $3M and re-platformed to an API. It is a clean example of the arc our answer describes: find traction on no-code first, re-platform later once it is worth it. You get the specific decisions behind when and why he made the switch.
Why we picked it
A clear, tool by tool guide to turning an idea into a working prototype in minutes, aimed at people who do not code. It sorts the landscape into categories (chatbots, cloud builders, local assistants) so you understand what each type is good for rather than just chasing brand names. Useful whether you land on an AI builder or decide you need something more structured.
Why we picked it
Once no-code has carried you to traction, this is a grounded guide to building the early team you eventually need, including that first engineer. It helps you time the switch from doing it yourself to hiring, which is exactly where the short answer points. Save it for when the product clearly works.
Why we picked it
A crowdsourced look at what non-technical people are actually building for themselves with AI tools, which is useful evidence that the bar for building your own first version has dropped a lot. It names the specific tools people reach for and what they made with them. Scan it to see how far a domain expert can get alone before needing help.
Why we picked it
Another non-engineer, a designer this time, showing concretely how far you can push Cursor to build interactive things without a developer. It is a good proof point that the tool is usable by people who do not think of themselves as programmers. Skim it for workflow ideas you can adapt to your own custom feature.
Why we picked it
This is the operational how-to behind our short answer: how to run a paid, job-representative trial, drawing on how Linear, Automattic, 37signals, Gumroad, and PostHog actually do it. It answers the questions the shorter essays skip, like how long, paid or not, real task or synthetic, and how to score the output. If you only read one thing on running a trial, make it this.
Why we picked it
Linear is a small, largely distributed team that ships a famously polished product, and this breaks down how they organize around projects and keep scope tight. You will see how a lean team stays accountable through clear ownership and shipped work rather than process theater. Relevant because it is a modern example of the visible-output, small-team model working in practice.
Why we picked it
A practical roundup of the frameworks that startups actually use to break ties without drama, including role-centric decision making and disagree-and-commit. It helps you pick a lightweight system that fits a two person company rather than a corporate approval chain. Skim it to steal one method you can apply to the stack question this week.
Why we picked it
Testing with the wrong five people teaches you nothing, so this piece helps you decide who your five should actually be. Margolis lays out a one-day approach to find the specific customer most likely to adopt now. It sharpens the recruiting side of your usability test so the feedback is worth acting on.
Why we picked it
The inventor of Now-Next-Later goes deep with Lenny on how to run a roadmap that stays flexible without turning into chaos. She is practical about handling stakeholders who demand dates and about pruning the roadmap so it does not sprawl. Useful once you have picked a format and need to operate it without backsliding into a wishlist.
Why we picked it
A detailed look at a team obsessed with velocity: almost no estimating, minimal planning ceremony, and a bias toward shipping as early as possible. It is a real, named example of how a fast growing company keeps rituals light so they speed up decisions rather than becoming the work. Read it to see how far the lean toward doing over planning can go, and decide how much of it fits you.
Why we picked it
Duolingo's VP of Product walks through their planning cadence, org structure, and the team rituals that let many small teams ship independently at scale. It shows what an operating rhythm looks like once you are well past the founding team. Good for seeing how planning and execution cadences stay separate as headcount climbs.
Why we picked it
Your short answer tells founders to set a rough threshold before shipping, and this gives you real benchmarks so your threshold is not a guess. It collects activation numbers across many products so you know whether your result is good, bad, or average. Use it to decide honestly, a week later, whether the feature earned its place.
Why we picked it
Retention on the exact flow you shipped is one of the signals your short answer names, and this is the hands-on guide to measuring it. It explains cohorts, retention curves, and the difference between a curve that flattens (people keep using it) and one that decays to zero. This is how you tell a launch from a working feature.
Why we picked it
A practical checklist drawn from many product leaders on the exact question of when a feature has earned its removal. It gives you the concrete signals (low usage, high maintenance, off-strategy) and how to actually retire something without burning the few users who rely on it. This is the closest thing to a decision framework for your question.
Why we picked it
A collection of what founders and operators actually do to protect time, including treating the calendar as a strategy document and blocking the important work before the week fills up. You will find specific, copyable rhythms like mornings for building and afternoons for calls. Concrete enough to redesign your own week the same day you read it.
Why we picked it
Lenny interviewed founders of Gong, Notion, Figma, Amplitude, Retool and more to trace where their idea actually came from. The surprising finding is that most founders had no special background in the space and spoke to around thirty potential customers before committing. Read it to see that ideas come from paying attention, not from a rare gift.
Why we picked it
The consumer companion to the B2B piece, covering how Airbnb, Twitter, Pinterest, Tinder and others began. Many ideas felt trivial at the time and emerged organically rather than from a founder hunting for a business. It is reassuring proof that your small, unglamorous problem might be the one.
Why we picked it
This is a direct, practical breakdown of what a real why now looks like and how founders talk themselves into fake ones. It separates companies that genuinely rode a shift from ones that had almost no timing edge and won on execution, so you can be honest about which camp you are in. Useful for calibrating how much of your plan is actually resting on the tailwind.
Why we picked it
This is the honest, uncomfortable side of the answer: sometimes the doubters are right and the idea simply cannot reach venture scale. It lays out how to check whether there is a believable path to a very large business, and quotes investors who note that some big markets are bad and some small ones can be expanded. Read it to sit with the hard ceiling case before you talk yourself into a beachhead that leads nowhere.
Why we picked it
Lenny gathers how strong product people build intuition for what will work, which is really a method for reading signals and taste. It shows that product sense is trainable through inputs and reps, not something a hub grants you. Apply the habits to your own market and information diet.
Why we picked it
The founders started Saturn as University of Pennsylvania students and grew it to millions of young users across thousands of schools. This is the closest case study to your exact situation: students building for students, one campus at a time. You get concrete tactics for turning a school by school rollout into real momentum.
Why we picked it
Ivan Zhao talks in detail about the years Notion nearly died, including a full technical rewrite after the first version failed, and how he thought about telling that story once the company took off. It is a rare, specific account of a founder who does not sand down the failure, he describes exactly what did not work and what they changed to fix it. Listen for how a founder narrates a near death relaunch with confidence rather than shame.
Why we picked it
Dunford, who wrote the book on product positioning, breaks down how to build a pitch around the buyer's specific situation rather than a generic feature list, exactly the specifics about their world our short answer calls for. It's a practical structure you can apply to your very next call.
Why we picked it
If you are tempted to dump 20 transcripts into an AI tool and ask for the pattern, read this first. It explains why AI defaults to the loudest, most generic theme and can bury a sharper, less common signal that actually matters more. It gives a workflow for forcing an AI, or yourself, to keep exact quotes and flag contradictions rather than smoothing everything into one tidy summary. Useful if you want a second pass on your transcripts without fooling yourself.
