Evaluating Startup Ideas

Evaluating Startup Ideas

Systematically validate problem-solution fit, market timing, and business viability before you build.

Help the user with evaluating startup ideas using insights from 21 guests and posts across Lenny's Podcast and Newsletter.

How to Help

1. Assess Problem Urgency - Determine if you are solving a hair-on-fire problem or an incremental convenience.
2. Analyze Market Timing - Evaluate if there is a clear why now inflection point in technology, regulation, or behavior.
3. Review Business Viability - Scrutinize the underlying math to ensure a path to $100M in annual revenue.
4. Validate via Experiments - Guide the transition from brainstorming to manual testing before committing to code.

Core Principles

Seek unglamorous niches

Andrew Wilkinson: "I think that's probably the most important thing in business is actually to find those niches where you can actually make real money because competition equals lower margin. The more competitors there are, the lower your prices have to be and the more competitive the business is ultimately."

Identify uncrowded industries like pest control or government software where lack of competition allows for higher margins and easier growth.

Prioritize autonomous outcomes

Bret Taylor: "First is, I think as you have these new technologies, rather than literally digitizing what came before, if you can create an entirely new experience, it answers the question for a new customer, why should I give this the time of day? And so, really disassembling the Lego set and reassembling into something new rather than just digitizing what was there before."

In the age of AI, the best opportunities lie in delivering autonomous results rather than just building productivity tools that require manual effort.

Wait for external turning points

Mike Maples Jr: "The three are inflections, insights and then the founder future fit. Business is never a fair fight. What inflections let the founder do is wage asymmetric warfare on the present."

Successful breakthroughs depend on identifying specific shifts in technology or behavior that allow a founder to challenge the status quo.

Validate demand before writing code

From "How to validate your B2B startup idea": "And then we got an email from an old Dropbox colleague who was like, ‘I hear you guys have become SOC 2 consultants. That’s super-weird. I thought you were going to do other things with your life. But also, can you come do this for my company?’ And that’s when it was like, no, but I’ll start writing code. That was the validation process for us."

Commit to building only after you have confirmed that users are willing to pay for or hire a manual version of your solution.

Look for polarizing signals

Sam Schillace: "And that bifurcation of love it, hate it, is really how you have an idea of whether you have impact in what you're building. If you get more of the bell curve of modern indifference and maybe mild like and mild dislike, that's an's an incremental product. That's not really disrupting anything."

True disruption is characterized by polarization where early users either love the product or hate it, rather than offering lukewarm acceptance.