Alex has a folder full of apps built to 90%.
Weeks of work in some of them. Months in others. None of them launched. He'd get close, decide it wasn't good enough, and quietly let it die.
Sound familiar? I've done it. You've probably done it.
His fix was extreme: ship 30 apps in 30 days, on camera, with a YouTube video documenting every build. Pat Walls brought him on the Starter Story podcast at day 5 to ask the question everyone was already yelling in the replies: is this a genius move, or are you just building 30 projects that go nowhere?
I think the answer comes down to one idea from the episode: the shipping muscle. The skill of actually getting things over the line. Alex had every other skill. This was the one that was missing.
This isn't a beginner doing a stunt
Worth knowing who Alex is before you judge the challenge.
He's UK-based, came up through Webflow and no-code, then joined a startup as roughly employee number 15. He watched it grow to nearly 200 people and about $40M ARR over his four years there. He left last year to ride the vibe coding wave full time.
Last summer he ran a warm-up: six products in six weeks. But he admits those were closer to demos than real products. Nothing fully out there. Nothing taking payments.
And that's the pattern he wanted to break. His words: "I've built many apps to 80, 90%. I've spent weeks, months doing it, and then I talk myself out of actually getting them over the line."
He has hundreds of ideas in a list. He loves building. That combination is exactly the trap.
The night before announcing the challenge, he asked a friend to talk him out of it. The friend said "you've got to do it." So he posted the launch video, it went down better than expected, and suddenly he had an audience watching to see if he'd actually deliver.
I covered how the challenge started when the first episode dropped. This conversation is the mid-flight check-in, and it's the most honest part of the whole series.
Haters corner: "you're playing a lottery"
Pat pulled up the meanest replies from Alex's launch post and read them to his face. (More podcasts should do this.)
The sharpest one: "Don't do it. Focus on one or two good ideas and talk to users. Right now you are playing a lottery, and even if you win, you will never know that you had the winning ticket."
Alex didn't dodge it. He called it valid advice. He'd spent months this year deep in the weeds on a couple of projects, doing exactly what the commenter suggested. It didn't fix his real problem. He'd lose motivation, start doubting, and fizzle out before launch.
Then he dropped the stat that reframes the whole debate: someone analyzed years of Product Hunt launches and found only 3% are still alive and making money.
→ If 97% of "focused" launches die anyway, 30 fast attempts just compress the same odds into one month, with skills and an audience as the floor.
The second hater said the challenge isn't even hard, since you can one-shot prototypes in Lovable. Alex's reply was two words: "Simple, not easy."
Anyone can build an app in a day now. The hard part is doing it every day, in public, with a video attached, while fixing the auth bugs and payment flows that kill most projects at the 90% mark. Pat's summary of it stuck with me: "It's more mental than it is technical."
What a day actually looks like
Forget the 5am Casey Neistat routine. Alex is running on reactive chaos.
Build until the midnight deadline. Sleep. Wake up and edit the video, which always takes longer than planned. Thumbnail, tweet, package it all up. By 1pm he's shipped the video and usually hasn't eaten. Then straight back to building the next app.
Repeat 30 times.
Pat's take was the right one: anybody can do anything for one month. That's the entire trick of the format. You're not committing to a lifestyle. You're committing to a sprint with a hard end date, and the deadline does the motivating for you.
By day 5, Alex had already learned the thing every founder learns eventually: scope expands to fill whatever container you give it. Pick a "small" app in the morning, and by 10pm you're scrambling. Give yourself a month, and every small piece inside it grows too. That's how a simple product quietly becomes a 6-month build.
A one-day deadline is brutal, but it caps the damage.
The stack: boring on purpose
Alex planned to use the challenge to test lots of different tools. That lasted about a week.
He tried something new mid-build, it broke completely near the deadline, and he had to rip it all out. Lesson learned: stick to what you know when the clock is running.
His working setup:
- Claude Code for the actual building. He's a self-described "big Claude Code guy".
- Lovable, v0, or Bolt only as a starting gun. They generate the boilerplate and infrastructure, then he downloads the project and works locally.
- Next.js starter templates so he can deploy immediately instead of fighting dependencies.
His biggest unsolved problem at day 5: he still couldn't get auth and payments done in half an hour. Every day, the setup tax ate hours before the fun part started.
That's the general rule hiding inside the challenge. Any step you repeat every day deserves a system, not willpower. It's the same reason I keep pushing founders to systemize their ops instead of re-doing them by hand (TwiLead has a good breakdown of business automations if you want to go deep on that side).
Alex even started dogfooding the problem: one of his 30 apps was a business name and domain finder, built because naming a product every single day was eating his time.
The taste gap will lie to you
Pat asked the question that hits every builder: when you ship something in a day, does it ever feel good enough?
Alex's answer: "Even if I work on something every day for 3 months, I still will tell myself that it's not good enough."
He pointed to Shaan Puri's idea of the taste gap. Your first draft never matches the version in your head. Most people read that gap as a signal to keep polishing. It isn't. It's a permanent condition. The gap exists at day 1 and it still exists at month 3.
So waiting until it feels ready means waiting forever. Shipping daily forces you to launch while the gap is still wide open, and the world gives you feedback anyway.
Same thing happened with his videos. He burned 45 minutes on a fancy intro one morning, then cut it. The raw, low-production builds were outperforming polished content anyway. People wanted to sit next to him while he built, not watch a trailer.
Building in public finally worked
Alex had been building in public for a long time before this. Five to ten people engaging per post. That's the reality for most founders posting into the void.
The challenge changed it overnight. The launch post blew up, individual build videos were pulling 3,000 to 4,000 views, and strangers started showing up with feedback and ideas.
His explanation is the best build-in-public advice I've heard in a while: people struggle to know what to post because they aren't doing anything worth posting about. Do something interesting first and the content writes itself. The challenge IS the content strategy.
→ Don't start with "I should build in public." Start with "I should do something cool," then document it.
So: smart or stupid?
Alex leaned on a Tim Ferriss question: how can you set this up so that even if it fails, it's a success?
Worst case, he ships 30 things and walks away with more live apps than he'd launched in his entire life, plus 30 reps of design and content practice. Pat put a sharper frame on it: the challenge condenses 3 or 4 years of founder lessons into one 30-day cave.
And since this episode aired, we know how it ended. He finished all 30. The best app, a naming tool called NameStrong, pulled over 1,000 users and 70,000 searches. The content did 40,000+ YouTube views and 500,000 X impressions. Revenue across all 30 apps: $0. I broke down the full results here, including what he'd change.
So the lottery hater was half right. No winning ticket. But Alex came out the other side with an audience and a shipping muscle that actually fires, which is exactly what he said he was training for.
My take: stupid as a business plan, smart as a cure. If you have a graveyard of 90% finished projects, one month of forced reps will do more for you than another quarter of "focusing" on a product you'll never launch.
FAQ
What is a shipping muscle?
The shipping muscle is your ability to take a project from 90% done to actually launched: live URL, working payments, announced in public. Like a real muscle, it weakens when unused and grows with reps. Alex's 30 apps in 30 days challenge is deliberate high-volume training for it, since each daily deadline forces a full launch rep.
Did Alex actually finish 30 apps in 30 days?
Yes. He shipped all 30, each with a build video. The standout was NameStrong, a naming tool that got 1,000+ users and 70,000 searches. Total revenue across every app was $0, but the challenge earned him tens of thousands of views, a much bigger audience, and a faster build system.
Should you build 30 apps in 30 days?
Only if your problem is shipping, not ideas. If you consistently abandon projects at 80-90%, a volume challenge breaks the perfectionism loop and builds real speed. If you already ship and have paying users, you're better off pouring that energy into the product that's working. Momentum matters more than the specific number of apps.
Want the versions of this story that end in revenue? Every week on the Profitable Founder Podcast I sit down with bootstrapped SaaS founders making $100K to $10M a year and pull out the exact playbooks they used.
