WEBVTT 00:00:00.000 --> 00:00:02.819 The terrifying truth about billion -dollar startup 00:00:02.819 --> 00:00:06.860 success is that the winning ideas, they rarely 00:00:06.860 --> 00:00:09.699 start as these strokes of genius. Not at all. 00:00:09.820 --> 00:00:12.000 They're often messy, they can be really boring, 00:00:12.140 --> 00:00:15.220 and they're frequently ignored by everyone who's 00:00:15.220 --> 00:00:17.460 chasing the next shiny object. That's exactly 00:00:17.460 --> 00:00:19.879 right. The core insight we get from looking at 00:00:19.879 --> 00:00:23.199 companies like Airbnb or Stripe isn't about finding 00:00:23.199 --> 00:00:26.980 some perfect, pristine idea. It's about systematically 00:00:26.980 --> 00:00:30.460 avoiding the big pitfalls, specifically that 00:00:30.460 --> 00:00:33.060 trap of building a solution for a problem that 00:00:33.060 --> 00:00:35.899 doesn't really exist. Welcome to the Deep Dive. 00:00:36.000 --> 00:00:38.259 Today, we are doing a comprehensive deep dive 00:00:38.259 --> 00:00:40.719 into sources based on Y Combinator's analysis 00:00:40.719 --> 00:00:44.450 of startup viability. This guide, it's been refined 00:00:44.450 --> 00:00:46.570 over years of funding thousands of companies. 00:00:46.670 --> 00:00:48.829 It's essentially a shortcut for you to understand 00:00:48.829 --> 00:00:51.390 why founders fail and, maybe more importantly, 00:00:51.570 --> 00:00:54.070 how the successful ones actually win. Our mission 00:00:54.070 --> 00:00:57.369 today is to unpack the hard, kind of counterintuitive 00:00:57.369 --> 00:01:00.170 truths behind idea validation. We're going deep 00:01:00.170 --> 00:01:02.450 on the 10 -question framework that YC partners 00:01:02.450 --> 00:01:05.510 themselves use to evaluate if an idea is viable. 00:01:05.730 --> 00:01:07.870 And the goal is simple. Yeah, the goal is to 00:01:07.870 --> 00:01:10.010 dramatically increase your chances of choosing 00:01:10.010 --> 00:01:12.689 the right path from day one. So we've got a clear 00:01:12.689 --> 00:01:15.489 roadmap. We'll first dissect the four common... 00:01:16.829 --> 00:01:20.010 cognitive traps that kill promising ideas before 00:01:20.010 --> 00:01:22.510 they even get started. Then we'll move into those 00:01:22.510 --> 00:01:25.469 10 critical questions, the litmus test for whether 00:01:25.469 --> 00:01:27.510 you should dedicate the next decade of your life 00:01:27.510 --> 00:01:29.989 to something. And then the really fun part, we'll 00:01:29.989 --> 00:01:33.370 look at three surprising bad signs that are actually 00:01:33.370 --> 00:01:35.650 golden opportunities. Okay, let's unpack this 00:01:35.650 --> 00:01:37.989 before we can even really define what a good 00:01:37.989 --> 00:01:40.209 idea looks like. We have to stop making these 00:01:40.209 --> 00:01:42.650 four specific mistakes that just poison the well. 00:01:43.000 --> 00:01:44.939 The first, and I think it's possibly the most 00:01:44.939 --> 00:01:49.579 dangerous, is what YC calls SISP. SISP. Solution 00:01:49.579 --> 00:01:52.219 in Search of a Problem. I mean, it's completely 00:01:52.219 --> 00:01:54.900 backward thinking. A founder gets excited about 00:01:54.900 --> 00:01:59.420 a new technology. AI? Maybe AI, maybe a complex 00:01:59.420 --> 00:02:02.099 new blockchain protocol or some no -code tool. 00:02:02.340 --> 00:02:03.900 And then they try to find something, you know, 00:02:03.920 --> 00:02:06.099 anything to apply it to. And the result almost 00:02:06.099 --> 00:02:08.400 every time is a product that is technically elegant, 00:02:08.639 --> 00:02:11.520 but it completely fails that one fundamental 00:02:11.520 --> 00:02:14.740 test. Will customers actually pay for this? Exactly. 00:02:14.900 --> 00:02:18.979 It looks cool, but there's just no urgent customer 00:02:18.979 --> 00:02:22.159 pull. Playing Grid is the perfect corrective 00:02:22.159 --> 00:02:25.580 story here. The founder, Tracy Young. She didn't 00:02:25.580 --> 00:02:27.719 start by asking, hey, what can we do with this 00:02:27.719 --> 00:02:30.580 new iPad? Right. She started with the acute daily 00:02:30.580 --> 00:02:32.860 pain point she knew from the construction world. 00:02:33.120 --> 00:02:35.860 You know, crews were literally drowning in these 00:02:35.860 --> 00:02:39.199 massive, outdated paper blueprints. She saw the 00:02:39.199 --> 00:02:41.740 pain first. I mean, those documents were so huge 00:02:41.740 --> 00:02:44.800 and so hard to manage that they led to multimillion 00:02:44.800 --> 00:02:47.400 dollar errors. The iPad just happened to be the 00:02:47.400 --> 00:02:49.300 most efficient tool for that urgent problem. 00:02:49.479 --> 00:02:51.849 And the principle is so clear. fall in love with 00:02:51.849 --> 00:02:54.490 the problem not the solution so why does leading 00:02:54.490 --> 00:02:56.650 with a solution almost always lead to failure 00:02:56.650 --> 00:02:58.849 because customers you know they only pay to solve 00:02:58.849 --> 00:03:01.810 real painful problems not for cool tech gimmicks 00:03:01.810 --> 00:03:05.729 that brings us to trap number two the tar pit 00:03:05.729 --> 00:03:09.370 these are idea categories that look so deceptively 00:03:09.370 --> 00:03:11.669 promising everyone thinks they need them but 00:03:11.669 --> 00:03:13.449 they have these hidden structural obstacles that 00:03:13.449 --> 00:03:16.370 just lead to repeated failure oh yeah think about 00:03:16.370 --> 00:03:18.349 things like the next great social coordination 00:03:18.349 --> 00:03:21.620 app or trying to build a better email client. 00:03:21.919 --> 00:03:24.219 They seem easy enough to build, but they're built 00:03:24.219 --> 00:03:27.139 on these huge obstacles like the massive network 00:03:27.139 --> 00:03:29.960 effects you need for a social app or just user 00:03:29.960 --> 00:03:32.620 behavior that refuses to change. And the obstacles 00:03:32.620 --> 00:03:35.139 are almost never technical. It's about human 00:03:35.139 --> 00:03:38.159 inertia. Yeah. High switching costs. People might 00:03:38.159 --> 00:03:40.479 complain about group chats for planning, but 00:03:40.479 --> 00:03:43.960 the convenience is just. It's good enough. The 00:03:43.960 --> 00:03:46.479 sources suggest a really great antidote for this. 00:03:46.539 --> 00:03:49.939 Just Google your idea plus failed startup. Right. 00:03:50.020 --> 00:03:52.599 You have to really understand why all the previous 00:03:52.599 --> 00:03:55.379 attempts died. Was the problem engineering or 00:03:55.379 --> 00:03:57.659 was it just the unyielding nature of how people 00:03:57.659 --> 00:03:59.979 behave? You know, I still wrestle with prompt 00:03:59.979 --> 00:04:03.169 drift myself. The tendency for users to lose 00:04:03.169 --> 00:04:05.610 focus when they're using a new tool. And it just 00:04:05.610 --> 00:04:07.949 shows how easy it is to fixate on the tool instead 00:04:07.949 --> 00:04:10.009 of the essential unchanging problem the customer 00:04:10.009 --> 00:04:12.270 actually has. That intimate understanding is 00:04:12.270 --> 00:04:15.270 just, it's vital. So what's the single most important 00:04:15.270 --> 00:04:17.350 thing founders need to find when they're researching 00:04:17.350 --> 00:04:19.529 those failures? They have to find out if the 00:04:19.529 --> 00:04:22.449 obstacle was solvable engineering or if it was 00:04:22.449 --> 00:04:25.329 just deeply ingrained, unchanging user behavior. 00:04:26.529 --> 00:04:29.769 Okay, moving to trap three, we get the Goldilocks 00:04:29.769 --> 00:04:32.620 paradox. The two extremes. The two extremes that 00:04:32.620 --> 00:04:35.180 paralyze founders. On one side, you have the 00:04:35.180 --> 00:04:37.920 builder who just jumps in, codes for six months, 00:04:38.040 --> 00:04:40.259 and never talks to a customer. And on the other, 00:04:40.319 --> 00:04:42.500 you have the analyzer who's waiting for this 00:04:42.500 --> 00:04:45.319 theoretically perfect idea, just paralyzed by 00:04:45.319 --> 00:04:47.800 every tiny flaw they see. The optimal strategy 00:04:47.800 --> 00:04:51.120 is that middle path. You shouldn't treat an idea 00:04:51.120 --> 00:04:53.920 like an irreversible life commitment. You should 00:04:53.920 --> 00:04:56.660 treat it as a high -quality starting point that 00:04:56.660 --> 00:05:00.209 needs market feedback. Fivetran. which is now 00:05:00.209 --> 00:05:02.769 a multi -billion dollar data company, is a perfect 00:05:02.769 --> 00:05:05.529 example. They pivoted multiple times in their 00:05:05.529 --> 00:05:07.649 early years. But they stayed within that larger 00:05:07.649 --> 00:05:10.170 data tool space. They were always learning and 00:05:10.170 --> 00:05:12.230 adjusting. They were constantly executing and 00:05:12.230 --> 00:05:14.329 iterating, not just waiting for the perfect moment. 00:05:14.730 --> 00:05:17.470 So how can a founder know if they're being too 00:05:17.470 --> 00:05:19.629 analytical, if they're getting paralyzed? Well, 00:05:19.689 --> 00:05:22.029 if you're waiting for an idea that has zero flaws 00:05:22.029 --> 00:05:23.930 on paper, you are just never going to start. 00:05:24.089 --> 00:05:26.430 The market is the only thing that provides real 00:05:26.430 --> 00:05:29.639 validation. And the fourth trap. Yeah. This one 00:05:29.639 --> 00:05:32.860 is all about self -awareness, the good idea for 00:05:32.860 --> 00:05:37.000 someone else problem. Or, you know, a lack of 00:05:37.000 --> 00:05:40.040 founder market fit. Right. An idea can be objectively 00:05:40.040 --> 00:05:43.439 perfect, huge market, acute pain point. But if 00:05:43.439 --> 00:05:45.480 it's wrong for you, if you don't have that unique 00:05:45.480 --> 00:05:48.360 insight, you will fail to execute. Founder market 00:05:48.360 --> 00:05:50.860 fit means having a distinct personal insight 00:05:50.860 --> 00:05:54.160 or direct experience that other people just don't 00:05:54.160 --> 00:05:56.720 have. The playing grid example is perfect again. 00:05:56.920 --> 00:05:59.439 Tracy Young understood construction pain. Her 00:05:59.439 --> 00:06:01.560 co -founder was an iPad expert is a perfect match. 00:06:01.720 --> 00:06:03.920 Yeah. And contrast that with a team of, say, 00:06:04.000 --> 00:06:06.800 top tier Stanford CS grads. They might have better 00:06:06.800 --> 00:06:09.160 coding skills, sure. But if they've never set 00:06:09.160 --> 00:06:11.720 foot on a construction site, they lack that visceral 00:06:11.720 --> 00:06:14.060 understanding of the customer's daily reality. 00:06:14.220 --> 00:06:16.259 They won't know the nuances of the sales cycle 00:06:16.259 --> 00:06:19.000 or all those hidden frustrations. That intimate 00:06:19.000 --> 00:06:22.220 personal insight is the key differentiator, especially 00:06:22.220 --> 00:06:25.879 early on. So why is a founder's unique experience 00:06:25.879 --> 00:06:28.139 so often more important than just having superior 00:06:28.139 --> 00:06:31.100 code? Because personal insight is essential to 00:06:31.100 --> 00:06:33.459 truly understand the customer's daily reality, 00:06:33.699 --> 00:06:36.779 how they think, and most importantly, how to 00:06:36.779 --> 00:06:38.939 sell to them. Okay, so we've learned what to 00:06:38.939 --> 00:06:41.060 avoid. This is where it gets really interesting. 00:06:41.360 --> 00:06:44.019 Let's switch gears and actively evaluate opportunities 00:06:44.019 --> 00:06:47.740 using that YC10 question framework. This is the 00:06:47.740 --> 00:06:50.519 model that separates strong starting points from, 00:06:50.600 --> 00:06:53.759 well... Time sinks. And question one just reinforces 00:06:53.759 --> 00:06:55.959 what we were talking about. Founder market fit. 00:06:56.399 --> 00:06:58.540 Beyond just general industry knowledge, what 00:06:58.540 --> 00:07:00.980 unique, non -obvious insight do you actually 00:07:00.980 --> 00:07:03.800 possess? The founders of Brex, the corporate 00:07:03.800 --> 00:07:06.240 card company for startups, are a great case study. 00:07:06.420 --> 00:07:08.300 They had built a premiums company in Brazil before. 00:07:08.540 --> 00:07:11.120 They understood the incredibly complex back end 00:07:11.120 --> 00:07:13.199 of payments and the specific needs of startup 00:07:13.199 --> 00:07:15.279 customers. They knew the cane inside and out. 00:07:15.480 --> 00:07:19.160 Question two. How big is the market? Now, the 00:07:19.160 --> 00:07:22.160 ultimate goal is billion dollar potential. But 00:07:22.160 --> 00:07:25.079 the sources stress this important nuance. You 00:07:25.079 --> 00:07:27.680 should probably beware of markets that are too 00:07:27.680 --> 00:07:30.160 big. Right. The ones already dominated by titans 00:07:30.160 --> 00:07:32.980 like Google or Facebook. Exactly. What's fascinating 00:07:32.980 --> 00:07:35.399 here is that the best opportunities are often 00:07:35.399 --> 00:07:38.279 these mid -sized, currently underserved markets, 00:07:38.519 --> 00:07:42.160 maybe in the $100 to $500 million range. They 00:07:42.160 --> 00:07:44.839 have room to grow exponentially without attracting 00:07:44.839 --> 00:07:47.100 the big guys right away. And you have to factor 00:07:47.100 --> 00:07:49.319 in that potential growth. I mean, the Coinbase 00:07:49.319 --> 00:07:52.160 example from 2012 shows that while the crypto 00:07:52.160 --> 00:07:54.660 market was minuscule back then, the argument 00:07:54.660 --> 00:07:57.360 for exponential growth just completely overrode 00:07:57.360 --> 00:07:59.569 the... initial skepticism about its current size. 00:07:59.769 --> 00:08:03.170 Whoa. Imagine having to argue for scaling to 00:08:03.170 --> 00:08:05.470 a billion queries in a market that barely even 00:08:05.470 --> 00:08:07.310 registers. That's why you have to look for that 00:08:07.310 --> 00:08:09.750 potential curve. Question three focuses on urgency. 00:08:10.089 --> 00:08:12.750 How acute is the problem? This is really the 00:08:12.750 --> 00:08:15.329 difference between a nice to have and hair on 00:08:15.329 --> 00:08:17.589 fire. And the test is simple. Would customers 00:08:17.589 --> 00:08:20.490 pay for a partial buggy imperfect solution today? 00:08:20.860 --> 00:08:23.420 If they're willing to deal with the pain of an 00:08:23.420 --> 00:08:26.540 incomplete solution, you know the problem is 00:08:26.540 --> 00:08:29.040 absolutely essential. Before Brex, for example, 00:08:29.279 --> 00:08:32.340 venture -backed startups often literally couldn't 00:08:32.340 --> 00:08:34.259 get corporate credit cards. Right, because they 00:08:34.259 --> 00:08:36.340 had no credit history. That was a missing piece 00:08:36.340 --> 00:08:38.720 of infrastructure, not just a marginally better 00:08:38.720 --> 00:08:42.539 app. Question four is delightfully counterintuitive. 00:08:43.039 --> 00:08:46.019 Do you have competition? Yeah, this one is great. 00:08:46.259 --> 00:08:49.299 Most people think competition is a killer, but... 00:08:49.500 --> 00:08:52.159 YC says it's often a strong positive signal. 00:08:52.259 --> 00:08:55.080 It validates that there's market demand. Because 00:08:55.080 --> 00:08:56.940 if nobody else is trying to solve the problem, 00:08:57.080 --> 00:09:00.080 maybe, maybe the problem isn't real, or maybe 00:09:00.080 --> 00:09:02.799 the solution is just impossible. Dropbox is the 00:09:02.799 --> 00:09:05.340 classic example here. They entered a market with 00:09:05.340 --> 00:09:07.639 about 20 existing cloud storage competitors. 00:09:08.440 --> 00:09:10.899 But they won because they were demonstrably 10 00:09:10.899 --> 00:09:13.700 times better in file syncing and user experience. 00:09:14.360 --> 00:09:17.080 Competition forces you to be aggressive. Okay, 00:09:17.139 --> 00:09:19.019 so let's link questions five and eight together 00:09:19.019 --> 00:09:21.539 to focus on the founders' resilience, personal 00:09:21.539 --> 00:09:25.279 desire, and longevity. Question five asks, simply, 00:09:25.460 --> 00:09:28.440 do you want this? Do people you know want this? 00:09:29.059 --> 00:09:30.899 DoorDash started because the founders genuinely 00:09:30.899 --> 00:09:33.240 wanted delivery from local restaurants that didn't 00:09:33.240 --> 00:09:35.250 offer it. They were just solving their own problem. 00:09:35.409 --> 00:09:37.590 And question eight is all about the grit you 00:09:37.590 --> 00:09:40.470 need for the long haul. Is the idea tolerable 00:09:40.470 --> 00:09:42.330 enough that you won't quit when it gets really 00:09:42.330 --> 00:09:44.950 hard? Right. I mean, most people aren't passionate 00:09:44.950 --> 00:09:47.970 about tax forms or compliance, but Josh Reeves 00:09:47.970 --> 00:09:50.070 of Gusto was passionate about building a successful 00:09:50.070 --> 00:09:52.490 company that helps small businesses manage those 00:09:52.490 --> 00:09:55.769 boring tasks. Passion often follows success, 00:09:55.889 --> 00:09:58.710 not the other way around. Questions six and seven 00:09:58.710 --> 00:10:01.899 cover timing and validation. Great ideas ride 00:10:01.899 --> 00:10:04.519 these waves of recent change, and the waves come 00:10:04.519 --> 00:10:08.539 in three flavors. Technology, like GPT -3, enabling 00:10:08.539 --> 00:10:11.519 all these new AI tools. New regulation, like 00:10:11.519 --> 00:10:14.159 legal cannabis markets, or behavior shifts, like 00:10:14.159 --> 00:10:17.340 remote work making Zoom a necessity. Checkter, 00:10:17.440 --> 00:10:19.759 the background checking platform, succeeded because 00:10:19.759 --> 00:10:22.480 the rise of the gig economy created this massive 00:10:22.480 --> 00:10:24.820 new demand for instant background checks that 00:10:24.820 --> 00:10:27.399 the legacy providers just couldn't deliver. The 00:10:27.399 --> 00:10:29.789 timing was everything. And Question Slithin is 00:10:29.789 --> 00:10:31.809 a reminder that if you are inventing a new business 00:10:31.809 --> 00:10:34.490 model, you should validate it. Are there successful 00:10:34.490 --> 00:10:36.570 examples of the model working somewhere else? 00:10:37.049 --> 00:10:39.710 Rappi applied the DoorDash model to Latin America. 00:10:40.309 --> 00:10:42.690 It's smart to prove the model works and then 00:10:42.690 --> 00:10:44.809 find a new market that desperately needs it. 00:10:45.389 --> 00:10:48.250 Finally, questions 9 and 10 cover scalability 00:10:48.250 --> 00:10:51.950 and idea space. Scalability asks, does the business 00:10:51.950 --> 00:10:54.610 model allow for infinite software -style growth, 00:10:54.830 --> 00:10:57.309 or does it grow slowly by adding consultants 00:10:57.309 --> 00:11:00.690 or physical stuff? VC funding really only flows 00:11:00.690 --> 00:11:03.610 to those infinitely scalable models. The idea 00:11:03.610 --> 00:11:06.129 space itself matters. High hit rate spaces like 00:11:06.129 --> 00:11:08.710 B2B SaaS, fintech infrastructure, and developer 00:11:08.710 --> 00:11:11.590 tools just have better statistical odds. Fivetran, 00:11:11.710 --> 00:11:13.909 again, they pivoted multiple times, but they 00:11:13.909 --> 00:11:16.470 stayed securely in that data tool space, which 00:11:16.470 --> 00:11:19.070 is a known area of high value. So if competition 00:11:19.070 --> 00:11:21.269 is good, should you just always enter a crowded 00:11:21.269 --> 00:11:24.809 field? Yes, but only if you can clearly identify 00:11:24.809 --> 00:11:27.289 how your solution is going to be demonstrably 00:11:27.289 --> 00:11:30.009 10 times better than the existing options, not 00:11:30.009 --> 00:11:34.580 just 10 % better. So if we connect this whole 00:11:34.580 --> 00:11:37.419 framework to the bigger picture, we get to Jared 00:11:37.419 --> 00:11:39.940 Friedman's amazing counterintuitive insight. 00:11:40.159 --> 00:11:43.179 The very things that look like major flaws to 00:11:43.179 --> 00:11:46.240 the average person are often exactly what repel 00:11:46.240 --> 00:11:48.679 competition and create these massive, durable 00:11:48.679 --> 00:11:50.500 opportunities. And the first of these positive 00:11:50.500 --> 00:11:53.559 signals is that. It's hard to get started, which 00:11:53.559 --> 00:11:56.039 Paul Graham famously calls Schlett blindness. 00:11:56.240 --> 00:11:59.200 Yes. This is that natural human tendency to avoid 00:11:59.200 --> 00:12:03.049 messy, boring or uncomfortable work. even if 00:12:03.049 --> 00:12:06.029 the eventual payoff is huge. Stripe is the textbook 00:12:06.029 --> 00:12:09.029 case of schlep blindness. Everyone knew online 00:12:09.029 --> 00:12:12.330 payments were awful clunky APIs, terrible documentation, 00:12:12.750 --> 00:12:14.629 high fraud rates. Always a nightmare. A total 00:12:14.629 --> 00:12:16.889 nightmare. But almost no one tried to fix it 00:12:16.889 --> 00:12:19.370 because the work was so tedious. Wrestling with 00:12:19.370 --> 00:12:21.750 ancient financial infrastructure, dealing with 00:12:21.750 --> 00:12:24.789 complex compliance, navigating all these banking 00:12:24.789 --> 00:12:27.669 regulations. That work was deeply unsexy. It 00:12:27.669 --> 00:12:30.450 was repetitive, often really stressful. But because 00:12:30.450 --> 00:12:32.250 Patrick and John Collison were just... just willing 00:12:32.250 --> 00:12:34.090 to do the hard schlep work that everyone else 00:12:34.090 --> 00:12:36.850 avoided, they built a massive business with surprisingly 00:12:36.850 --> 00:12:39.710 little early competition. The sheer pain and 00:12:39.710 --> 00:12:41.789 difficulty of the problem itself became their 00:12:41.789 --> 00:12:45.429 defense. It was the moat. Exactly. Signal number 00:12:45.429 --> 00:12:47.789 two is when the market looks boring. We call 00:12:47.789 --> 00:12:50.669 this the gusto principle. Founders, you know, 00:12:50.669 --> 00:12:53.230 being human, they flock to glamorous ideas, consumer 00:12:53.230 --> 00:12:56.470 social, anything related to metaverse, exciting 00:12:56.470 --> 00:13:00.490 AI interfaces. Meanwhile, these huge... Essential 00:13:00.490 --> 00:13:03.269 painful markets like payroll, insurance, construction 00:13:03.269 --> 00:13:06.570 tools, or specialized veterinary supply like 00:13:06.570 --> 00:13:09.889 Vetcov, they're just ignored. Right. Gusto, which 00:13:09.889 --> 00:13:12.070 does payroll and HR software, won because the 00:13:12.070 --> 00:13:14.649 market was massive, the incumbents like ADP were 00:13:14.649 --> 00:13:17.350 terrible, and customers were just desperate for 00:13:17.350 --> 00:13:19.750 a modern experience. But payroll isn't glamorous, 00:13:19.990 --> 00:13:22.580 so founders avoided it. And this pattern repeats 00:13:22.580 --> 00:13:25.019 across all kinds of vertical software. These 00:13:25.019 --> 00:13:27.340 ideas rarely make headlines on Twitter, and that 00:13:27.340 --> 00:13:29.259 lack of glamour is precisely their strength. 00:13:29.379 --> 00:13:31.440 And signal number three is the Dropbox paradox. 00:13:32.019 --> 00:13:34.820 Competitors already exist. We just discussed 00:13:34.820 --> 00:13:36.539 this in the framework, but it really bears repeating. 00:13:37.039 --> 00:13:39.340 Conventional wisdom says to avoid crowded markets, 00:13:39.539 --> 00:13:42.039 but reality shows that competition proves demand 00:13:42.039 --> 00:13:46.690 exists. When Dropbox launched, 20. 20 cloud storage 00:13:46.690 --> 00:13:48.970 tools already existed. That didn't kill them. 00:13:49.110 --> 00:13:51.389 It validated that people needed file syncing. 00:13:51.490 --> 00:13:54.470 So Dropbox's job wasn't to be first. It was just 00:13:54.470 --> 00:13:56.450 to build something meaningfully, demonstrably 00:13:56.450 --> 00:13:59.029 better. Faster syncing, a cleaner user experience, 00:13:59.289 --> 00:14:01.690 a better pricing model. Right. Markets with zero 00:14:01.690 --> 00:14:04.389 competitors often mean the problem isn't real 00:14:04.389 --> 00:14:06.570 or the solution you're thinking of is just impossible. 00:14:07.230 --> 00:14:10.289 So your job, if you see competition, is to understand 00:14:10.289 --> 00:14:13.409 exactly why existing solutions aren't good enough 00:14:13.409 --> 00:14:16.250 and then solve that gap 10 times better. So if 00:14:16.250 --> 00:14:18.409 we look at those three signals, what's the biggest 00:14:18.409 --> 00:14:20.970 underlying benefit of tackling a truly boring 00:14:20.970 --> 00:14:24.840 market? structurally ignored by most ambitious 00:14:24.840 --> 00:14:27.299 founders. It's an opportunity hiding in plain 00:14:27.299 --> 00:14:29.659 sight. So what does all of this mean for you 00:14:29.659 --> 00:14:32.120 as a founder or a potential founder? The core 00:14:32.120 --> 00:14:34.419 lesson from the YC framework isn't having the 00:14:34.419 --> 00:14:37.080 perfect idea on day one. No. It's about being 00:14:37.080 --> 00:14:39.919 positioned in a fertile space, recognizing real 00:14:39.919 --> 00:14:42.860 problems, even the messy, boring ones, and then 00:14:42.860 --> 00:14:46.240 just executing quickly. Stripe, Airbnb, DoorDash, 00:14:46.279 --> 00:14:49.100 they all succeeded because they executed aggressively 00:14:49.100 --> 00:14:52.659 in spaces where a real acute problem existed, 00:14:52.899 --> 00:14:55.620 and they were willing to do that hard, tedious 00:14:55.620 --> 00:14:59.379 schlep work that repelled everyone else. So if 00:14:59.379 --> 00:15:01.519 your idea passes the sniff test with the four 00:15:01.519 --> 00:15:03.759 traps and the ten questions, you need to stop 00:15:03.759 --> 00:15:07.399 analyzing. Please stop analyzing. Start building 00:15:07.399 --> 00:15:09.879 a minimal version. The market is going to teach 00:15:09.879 --> 00:15:13.120 you more in one month of real execution than 00:15:13.120 --> 00:15:15.740 any framework can in six months of just thinking 00:15:15.740 --> 00:15:17.820 about it. And finally, the guide suggests that 00:15:17.820 --> 00:15:19.320 if you don't have an idea yet, you shouldn't 00:15:19.320 --> 00:15:20.980 just wait for a lightning bolt of inspiration. 00:15:21.440 --> 00:15:24.200 There are systematic ways to actually force inspiration. 00:15:24.679 --> 00:15:26.759 That brings us to our provocative closing thought. 00:15:27.210 --> 00:15:29.029 If you aren't waiting for that sudden flash of 00:15:29.029 --> 00:15:31.409 genius, what kind of structured recipes could 00:15:31.409 --> 00:15:33.330 you use right now to systematically generate 00:15:33.330 --> 00:15:35.049 a billion -dollar problem?