Launched to Crickets: Why Pat Walls Didn't Kill His Flopped App

Pat Walls launched an AI thumbnail maker and made exactly one sale.

One. After weeks of late nights and a full launch video. One sale.

He said it on camera: he felt embarrassed, like a failure. Then he went on vacation, got sick, forgot the thing existed... and came back to paying customers showing up almost every day.

If you have ever launched to crickets, this episode of his $100K challenge is the one to watch. Not for the money (there isn't much yet). For what he did next, which is the opposite of what most of us do after a quiet launch.

Watch it, then I'll break down the whole arc with the numbers and the playbook.

One Sale on Launch Day

Quick context if you're new to this series. Pat Walls runs Starter Story, the site and YouTube channel where founders share their revenue numbers. On the side, he's running the $100K Build Challenge: make $100,000 using only AI tools.

Three rules:

• AI tools only, no hand-coding his way out
• Document everything publicly on the Starter Story Build channel
• No quitting until he hits $100K

His first real product in the challenge was an AI thumbnail maker for YouTubers. He shipped it, hit publish on the launch video, and waited for the spike.

His words: "We launched it. It didn't go viral. It made basically one sale and I kind of felt embarrassed by that and like a failure."

That's the moment most side projects die. The launch goes quiet, the ego takes the hit, and the project gets shut down before anyone writes a postmortem (nobody wants to admit the thing existed).

Pat almost did the same thing. His exact self-diagnosis later in the video: "I was an impatient loser."

Then He Stopped Watching. That's When It Worked.

Here's the part that makes this episode worth 20 minutes of your time.

Pat went on vacation, then got sick. For about three weeks he didn't touch the product, didn't check the dashboard, didn't post about it. Total neglect.

When he finally opened things back up:

• Hundreds of people were visiting the site every single day
• Paying customers were coming in almost daily
• A complete stranger had made a TikTok about the tool, and it pulled in thousands of views (he still has no idea how they found it)

And the line that sums it up: "2 weeks later, I forgot about it. And then a week later, I opened up Stripe and there was a bunch of sales."

Nothing about the product changed in those three weeks. No new features. No ad spend. The only variable was time.

→ A launch is a starting gun, not a verdict.

Search traffic needs weeks to index. Word of mouth needs people to actually use the thing. A random TikTok needs someone to stumble onto your product first. None of that fits inside the 24 hours after you hit publish, which is exactly the window most founders use to judge their launch.

Pat's takeaway from watching it happen: software keeps working while you don't. People were browsing his site and pulling out credit cards while he was, in his words, playing tennis or sleeping in.

The Pivot: One New Project Every Week

The flop-that-wasn't changed his whole strategy for the challenge.

His conclusion: $100K is not going to come from one hit. So instead of riding the thumbnail maker, he committed to building and launching a new startup or project every single week, each one documented on the channel.

To keep himself honest, he vibe-coded a public dashboard at labs.starterstory.com in about 5 minutes: a progress bar toward the $100K goal pulling from live revenue data, a list of failed ideas, and a backlog of ideas he openly invited viewers to steal.

The compounding part is speed. His third project (borderline fourth) came together in a few hours, in one session. Each build made the next one faster, because the boilerplate, the deploy setup, and the AI prompts carry over.

I wrote a full breakdown of this approach in my piece on running a SaaS portfolio strategy, and Pat's version is the same logic with the timeline compressed: take a lot of small swings on shared infrastructure and let the winners reveal themselves.

One Thing or Many Things?

Pat is honest about the debate here, and it's one I hear constantly from founders.

School one: go all-in on a single product. Focus wins. Why split your attention five ways when one deep bet compounds?

School two: ship a portfolio of small projects and let the market pick.

His answer is both, depending on the season. Starter Story is his one thing. It's the established business that pays the bills, and he's not diluting it. The challenge runs on scraps of time around that business, and scraps of time can't support a huge SaaS build. They can support a weekly string of small, shippable products that live in one ecosystem and feed each other.

If you have a day job, a family, and 90 minutes a night, you're in the same constraint box. A 12-month mega-project will stall the first time life gets busy. A one-week project ships before you lose momentum.

He also drops a name from the Starter Story interview archive: Alex Finn, who makes around $300,000 a year building products with Cursor and started with no coding background at all. Pat says he's learning from that playbook himself.

What he's actually training is the ability to take an idea to a live, paying product in days. Pat calls learning to build with AI the most valuable skill of the next 5 to 10 years. Whether or not you buy the timeline, every rep makes the next launch cheaper.

What To Do When You Launch to Crickets

Here's the playbook I take from this episode, plus a few things I'd add after interviewing a lot of founders who lived the same week-one silence.

• Give it 30 days before any verdict. Pat's tool went from 1 sale to near-daily customers in roughly three weeks with zero extra effort. Killing it on day 2 would have erased all of that.
• Ship the next thing while the last one simmers. Building something new is the only reliable cure for refreshing your Stripe dashboard every 40 minutes.
• Count signals, not just revenue. Daily visitors, actual usage, one stranger posting about you. Those show up before the money does.
• Leave the product online. Keeping a dead-looking site running costs a few dollars a month. Shutting it down costs you every future customer who would have found it.

One more thing worth saying out loud: crickets after a launch is the normal case. Every founder I've interviewed on the podcast has a version of this story. The ones who made it just happened to still have the product online when the market showed up.

And in Pat's challenge, it got rougher before it got better. The very next launch in the series got called AI slop in the comments before it earned its first $1. He kept shipping anyway. That's the whole trick.

Where the Challenge Stands Now

This episode is from mid-2025, so a quick status check as of October 2026.

The weekly-shipping cadence stuck: the Build channel has kept documenting new products, launches, and the occasional public faceplant ever since. The labs.starterstory.com dashboard, though, has since been taken private, so the public progress bar toward $100K is no longer visible.

Which, honestly, fits the lesson of this episode. The reps matter more than the scoreboard.

FAQ

What is the Starter Story $100K Build Challenge?

It's a public challenge by Pat Walls, founder of Starter Story, to make $100,000 using only AI tools. The three rules: he can only build with AI tools, he has to document everything on the Starter Story Build YouTube channel, and he can't quit until he reaches $100K. Day 7 (this episode) is where he pivoted from one product to launching a new project every week.

What should you do if your product launch gets no sales?

Wait before you judge it. Pat's AI thumbnail maker made one sale at launch, then grew to hundreds of daily visitors and near-daily paying customers within about three weeks, with no changes to the product. Give a launch at least 30 days, keep the site live, and start building your next thing while this one simmers.

How long should you wait before killing a product?

Longer than a week, shorter than forever. A usable bar: 30 to 60 days with the product live and at least one distribution channel running (SEO, posts, a directory listing). If after that there are no visitors, no usage, and no signals from strangers, kill it and roll the lessons into the next build. If anything is moving, let it keep breathing.

Is it better to build one product or a portfolio of small ones?

Depends on your constraints. If you can give a product full-time focus, one deep bet compounds harder. If you're building on nights and weekends, small weekly projects in one ecosystem (like Pat's approach, or the portfolio strategy I've written about) keep momentum alive and let real customer demand pick your winner for you.