Many shots on goal

This is one of the channel’s signature ideas, voiced in more than fifty episodes and especially by indie app and micro-SaaS builders. The dominant view is that you cannot know in advance what will work, so you should compress build time, ship lots of small things and double down on whatever gets signal. Guests put numbers on the misses: Marc Lou says about 30 of his roughly 35 start-ups do nothing (a ~5% hit rate), Thomas Sanlis launched 30-plus failures before Uneed, CJ Zafir built 11 products in a public challenge and 10 collapsed, and Tibo expects a 90% failure rate. A second strand treats each project as a rep: skills, speed and audience compound, so later apps are better from day one. The same ‘volume negates luck’ logic is applied to distribution (posting, creator outreach, ad creatives). Pat repeatedly frames guests’ success as ‘shipping a lot until something works’, not a formula (host view). Caveats matter: several guests credit luck, Gus points out survivorship bias in portfolio stories, and the approach sits in tension with the focus camp (see Focus vs shiny-object syndrome); Pat’s own resolution is that the point is shipping, not running many projects at once. All failure and project counts are self-reported.

Key points

• Most attempts fail: expect a high failure rate, and count dozens of misses before the winner — 11 episodes. (Marc Lou · Marc Lou (Apr 2026) ▶ 02:53) (Tibo · Tibo (Dec 2025) ▶ 06:55) (Thomas Sanlis · Thomas Sanlis (Aug 2025) ▶ 01:16) +8 more
• Ship many small bets and double down on whatever gets signal, instead of one long project — 10 episodes. (Marc Lou · Marc Lou (Apr 2026) ▶ 02:56) (Louis Pereira · Louis Pereira (Dec 2025) ▶ 04:38) (CJ Zafir · CJ Zafir (May 2025) ▶ 04:30) +6 more
• Each project is a rep: skills, speed and judgement compound so the next one is better — 8 episodes. (Presh · Presh (Dec 2025) ▶ 09:39) (presenter · Denis Yurchak (Oct 2025) ▶ 05:48) (Thomas Frank · Thomas Frank (Apr 2024) ▶ 10:36) +4 more
• Volume negates luck in distribution too: more posts, creators or ad creatives mean more lottery tickets — 8 episodes. (Mark Vassilevskiy · Mark Vassilevskiy (Oct 2025) ▶ 08:49) (Steven Cravotta · Steven Cravotta (Sep 2025) ▶ 11:53) (Kelechi · Kelechi (Oct 2025) ▶ 09:33) +5 more
• Host framing: success comes from shipping a lot, not from a secret formula — 5 episodes. (presenter · CJ Zafir (May 2025) ▶ 18:09)
• Don’t get emotionally attached; compress build time and kill flat projects fast — 5 episodes. (Marc Lou · Marc Lou (Apr 2026) ▶ 09:32) (Jacob Seeger · Jacob Seeger & Alex (Jun 2025) ▶ 12:08) (Louis Pereira · Louis Pereira (Dec 2025) ▶ 07:52) +2 more
• Quantity and ceaseless action beat perfectionism early on — 3 episodes. (Sam Parr · Sam Parr (Jul 2026) ▶ 06:35) (Steven Cravotta · Steven Cravotta (Sep 2025) ▶ 11:53) (Jacky Chou · Jacky Chou (Mar 2026) ▶ 06:49)
• Build in public so a failed launch still leaves an audience for the next one — 3 episodes. (Marc Lou · Marc Lou (Aug 2024) ▶ 13:33) (Louis Pereira · Louis Pereira (Dec 2025) ▶ 04:05)

Where guests agree

• The eventual winner usually follows many failed or flat projects; ‘overnight success’ is years of attempts. (CJ Zafir · CJ Zafir (May 2025) ▶ 04:30) (Thomas Sanlis · Thomas Sanlis (Aug 2025) ▶ 01:16) (Louis Pereira · Louis Pereira (Dec 2025) ▶ 12:09) +3 more

Where guests disagree

Many small bets or one focused project? ⚠️

• Ship many small bets; years attached to one pet project is the mistake (Marc Lou · Marc Lou (Apr 2026) ▶ 09:40) (Max · Max (Dec 2025) ▶ 02:16)
• Pick one thing and get it to product-market fit before the next (Alex Lieberman · Alex Lieberman (Nov 2023) ▶ 14:48) (Adrian Horning · Adrian Horning (Oct 2025) ▶ 11:40)
• Host view: what matters is whether you are shipping, not how many projects you run; don’t start eight at once (presenter · Florin Pop (Feb 2026) ▶ 13:33)

Frameworks

• Lean MVP loop: ship small, get feedback, iterate or move on — His start-over process for building and validating quickly. (Louis Pereira · Louis Pereira (Dec 2025) ▶ 07:46)
  • Build many small things for fun that can be shut down without harming users
  • Design before you build
  • Build in public; spin up a quick email list (even a Google form) if it resonates
  • Launch the simplest version; raise the price as you refine
• Halfday Build — An online hackathon he started: builders join on a Sunday and try to go from idea to MVP and at least a dollar of revenue between noon and midnight. (Louis Pereira · Louis Pereira (Dec 2025) ▶ 03:38)
  • Start at noon
  • Build independently, together in Slack/Discord
  • Goal: idea to MVP and revenue within 12 hours
  • At least a dollar by midnight
• Lean MVP loop: ship small, get feedback, iterate or move on — Florin’s loop for finding a first winning project: build, ship, get feedback, monetise, decide, repeat. (Florin Pop · Florin Pop (Feb 2026) ▶ 09:35)
  • Build something small but useful, in days or weeks
  • Ship it publicly where potential users hang out
  • Get feedback: usage, questions, return visits, complaints
  • Add monetisation early (a paid tier) as validation
  • Decide after weeks or months: double down on traction, move on if flat
  • Then reduce dependence on you: automate, simplify, step out of operations
• Build to sell (flip micro-SaaS and apps) — Build an app a month; when one succeeds, sell it (e.g. at two times annual revenue) to extend runway, then try to release another successful app before the runway runs out. (Adam Lyttle · Adam Lyttle (Feb 2025) ▶ 11:52)
  • Build one app every month
  • Sell a successful app for about two years of revenue
  • Treat the proceeds as runway
  • Release the next hit before the runway runs out
• Build to sell (flip micro-SaaS and apps) — Launch, validate and sell a micro business every 30 days. (Domenico Gagliardi · Domenico Gagliardi (Oct 2025) ▶ 02:18)
  • Launch
  • Validate
  • Sell within 30 days
  • Repeat month after month
• Building a business is like surfing — Rob’s analogy: time in the water teaches you to read waves; the job is to spot big waves early and ride them, and repeat winners keep winning because they’re already in the water. (Rob Hallam · Rob Hallam (Aug 2026) ▶ 05:59)
  • Get in the water (the hardest step)
  • Spend lots of time watching waves
  • Learn what a wave that will break properly looks like
  • Pick big waves and ride them
  • Keep catching waves; switching waves is your choice
• Reps and feedback cycle — Learn, try, publish on a schedule and improve one small thing each time; skills compound over years. (Thomas Frank · Thomas Frank (Apr 2024) ▶ 10:36)
  • Learn
  • Try stuff out
  • Publish on schedule
  • Get feedback
  • Improve something small each time

Tactics

• One app a month challenge — Set yourself the challenge of shipping one app every month to launch fast and validate ideas. (Adam Lyttle · Adam Lyttle (Feb 2025) ▶ 08:28)
• Ship many tiny tools publicly and watch for signal — He built four or five tiny tools in a week on his personal site, shared each on Twitter, and followed the one that got unexpected love. (Louis Pereira · Louis Pereira (Dec 2025) ▶ 04:05)
• Build in public so a failed app still leaves an audience — Share what you build publicly so that, if the app fails, you have a small following to launch the next project to. (Marc Lou · Marc Lou (Aug 2024) ▶ 13:33)
• Ship a small warm-up project first — He built a simple card game from high school in about six weeks to learn AI-assisted development, app store approvals and launching end to end. (Ken · Ken (Sep 2026) ▶ 04:14)
• Take shortcuts to ship an MVP in days or weeks — Use no-code (he built MVPs on Bubble.io) or boilerplates and skip things experts wouldn’t compromise on, so you can ship a new project every week given a ~90% failure rate. (Tibo · Tibo (Dec 2025) ▶ 06:41)
• Constantly test ads across products — With a little money, keep testing ads to find the one winning ad that funds the next month. (Jeremy · Jeremy (Mar 2024) ▶ 09:39)

Stories & examples

• 12 startups in 12 months: He publicly announced 12 start-ups while coding with AI 10-12 hours a day; he built 11, 10 collapsed and one, CodeGuide, grew fast. Lesson: Volume of attempts eventually produces the one that works; the ‘overnight success’ took seven years. (CJ Zafir · CJ Zafir (May 2025) ▶ 04:30)
• SunSeek was better on day one: After Go Polar, SunSeek was crafted better from launch because of the reps he had taken. Lesson: Each product is a repetition that improves the next. (Presh · Presh (Dec 2025) ▶ 09:39)
• ChatGPT made him a ‘9x developer’: Joking that ChatGPT makes you a 10x developer, he tried to release ten apps in a month and managed nine, which gave him enough portfolio revenue to stop selling apps. (Adam Lyttle · Adam Lyttle (Feb 2025) ▶ 13:50)
• The pottery class study: One class was told to make as many pots as possible, another to make one perfect pot; the quantity group got better and were happier, the perfection group made worse pots and were unhappier. Lesson: Ceaseless action beats perfectionism, especially when chasing your first million. (Sam Parr · Sam Parr (Jul 2026) ▶ 06:35)
• First flip: pitch deck generator: He worked only 45 days on a pitch deck generator, made $300 and sold it for $2,500, which convinced him to repeat fast execution month after month. Lesson: Fast execution can be repeated as a monthly process. (Domenico Gagliardi · Domenico Gagliardi (Oct 2025) ▶ 02:34)
• Ten failed apps before GlowUp: His earlier apps were built first and marketed afterwards and got no views or users; GlowUp flipped the order. Lesson: Show users what you have before building. (Louis · Louis (Dec 2025) ▶ 00:00)
• Six failed ideas before Faceless: Jacob went through six ideas before Faceless; being attached to the first would have kept him on something that might never have worked. Lesson: Move on quickly from ideas that aren’t working. (Jacob Seeger · Jacob Seeger & Alex (Jun 2025) ▶ 12:00)
• Years on one pet app: For years he spent time on a single mobile pet project, trying different techniques, and nothing worked until he switched to shipping many small apps. Lesson: Focusing all effort on one unproven app can waste years. (Max · Max (Dec 2025) ▶ 02:16)

Numbers

• Startups shipped: 35 startups (self-reported, approx.) (Marc Lou · Marc Lou (Apr 2026) ▶ 02:43)
• Hit rate: 5 percent (self-reported, approx.) (Marc Lou · Marc Lou (Apr 2026) ▶ 02:53)
• Products built / collapsed in the 12-startup challenge: 11 built, 10 collapsed products (self-reported) (CJ Zafir · CJ Zafir (May 2025) ▶ 04:33)
• Apps built in a year: 17 apps (self-reported) (Nico · Nico (Mar 2025) ▶ 01:10)
• Apps built in about a year: 45 apps (self-reported, approx.) (Benji · Benji (May 2026) ▶ 02:55)
• Failed projects before Uneed: 30 projects (self-reported, approx.) (Thomas Sanlis · Thomas Sanlis (Aug 2025) ▶ 01:16)
• Apps built in the 60-day build challenge (target about 100): 72 apps (self-reported, approx.) (Gaurabh · Gaurabh (Aug 2026) ▶ 01:08)
• Apps released in the ‘10x developer’ month: 9 apps (self-reported) (Adam Lyttle · Adam Lyttle (Feb 2025) ▶ 13:53)
• Tools built before success: 15-20 tools (self-reported, approx.) (Louis Pereira · Louis Pereira (Dec 2025) ▶ 03:12)
• Failed businesses before two successes: 15-20+ businesses (self-reported, approx.) (Will Cannon · Will Cannon (Oct 2025) ▶ 05:10)

Caveats & warnings

• He credits a large portion of luck. (Louis Pereira · Louis Pereira (Dec 2025) ▶ 04:35)
• Gus notes there are probably many unsuccessful projects Jacky didn’t mention, and finding winners takes a lot of work. (presenter · Jacky Chou (Mar 2026) ▶ 10:46)
• Many people see this and start eight projects at once, which is not the method (Pat). (presenter · Florin Pop (Feb 2026) ▶ 07:12)
• Even with the formula, a hit Roblox game will probably take a few attempts. (Cole · Cole & Ian (Apr 2025) ▶ 13:22)
• People underestimate the amount of work needed. (Mark Vassilevskiy · Mark Vassilevskiy (Oct 2025) ▶ 08:45)
• Most of his 10-12 earlier AI-built projects never reached production. (Hassam · Hassam (Jan 2026) ▶ 02:49)
• Success may only come on a later product (‘it might be product five’), cumulatively. (Jeremy Redman · Jeremy Redman (Apr 2026) ▶ 14:53)

How much to trust this

• Evidence: 54 episodes, 51 independent speakers (repeat guests counted once; Pat and Gus counted as one voice).

Blueprints that use this

• Portfolio, app flipping & selling