He Shipped 30 "AI Slop" Apps in 30 Days. Here's What It Got Him

Alex shipped 30 apps in 30 days.

One app every single day. Live in production by midnight. A video documenting each one.

The comments section had a field day. People called them AI slop apps. Garbage. A wasted month. One commenter went straight for the throat: "How many of these projects are actually making money?"

Then the challenge ended and the results came in.

One app crossed 1,000 users and 70,000 searches. The series pulled 40,000 views on YouTube and half a million impressions on X. And the app most likely to make real money is one nobody saw coming (it involves kitchens).

Alex came back on the Starter Story podcast to open the books. I went through the whole episode and pulled out the numbers, the three apps that mattered, and the lessons worth stealing.

Why He Did It: He Was "That Guy"

Alex's reason for the challenge is the most honest thing in the episode.

He was the guy telling everyone how easy it is to build apps with AI now. How fast he could ship. Except his track record didn't back it up. Almost nothing in production.

Sound familiar? I talk to founders like this every week. A backlog of ideas in their phone, a new one after every shower, and zero of them live.

He also knew something about himself: "When I do actually launch stuff, good things happen. Visitors come, money comes into the Stripe account."

So he forced the issue. One app per day, shipped by midnight, every day for 30 days, each one documented on YouTube.

Before this challenge, his pattern was the opposite. He'd spent the previous year on two main projects, three months each, building quietly and betting everything on a big launch.

His verdict on that approach: the big launch is "a bit of a myth." In his words: "You get to that point, you're burnt out, you're not hyped about the project, and people can tell that when you ship it."

Three months of quiet building, then a launch nobody noticed. I've made that exact mistake. Most of us have.

The Results After 30 Days

Straight numbers from the episode:

• 30 apps shipped in 30 days (he was 4 to 5 apps from the finish when this was filmed, and he finished)
• 40,000+ views on the YouTube series
• Half a million impressions on X
• 1,000+ users and 70,000+ domain searches on his biggest app
• Revenue: basically zero

Yes, zero revenue. He says it straight: "There's no big home run in the Stripe dashboard just yet."

Before you write the whole thing off, Pat (the Starter Story host) dropped a number of his own: his first online business took three months to make its first dollar.

I get it. I once paid $13,000 for a mastermind while making $15K a month, and it took six months before that bet showed up as $75K months. Nothing in this game pays off on day one.

Expecting revenue on day one is how people quit on day 30.

The challenge wasn't a revenue play anyway. Alex calls it "strengthening the shipping muscle." Before an app makes money, it needs to exist in production, in users' hands, collecting feedback. Most ideas die before that point.

App #1: The One That Found Product Market Fit

The winner of the 30 was NameStrong, a domain name finder. And it was one of the earliest apps he shipped.

You know the loop: you brainstorm names with ChatGPT, fall in love with one, go to Namecheap, and the .com is taken. Repeat until you hate your product idea.

NameStrong automates the loop. Describe your product, AI generates names, the app checks availability and only shows you names where the .com is free.

The numbers:

• 1,000+ users
• 70,000+ domain names searched

But the number isn't the story. The story is what Alex felt when he shipped it: "It's one of the first times I truly felt product market fit."

Every other app in the challenge got a shrug. This one got shared. People came back to tell him it worked, that they actually found a domain. On some apps he spent 10 hours and got 15 users. On this one, a few hours got him 1,000.

Same effort in. One hundred times the output.

That's what product market fit feels like from the inside. You stop tugging and the thing moves on its own.

You can't feel that difference if you only ship once a year. When you ship 30 times, the outlier is obvious.

App #2: The Boring One That Might Make Money First

Here's my favorite idea in the whole episode, and it's a kitchen app.

Kitchen respray companies charge $5,000 to $20,000 per job. Their sales process involves a customer sending a photo of their old kitchen and trying to imagine the result.

Alex's app: the renovator uploads the customer's kitchen photo, and Google's Nano Banana image model generates realistic versions of that exact kitchen in different finishes. The customer sees their own kitchen transformed before signing anything.

The plan is what makes it interesting. Once it's built, Alex is picking up the phone and cold calling kitchen companies to book demos.

His pitch, from the episode: "This isn't another cold call about software you don't need. If you don't apply this, then I'm going to go next door to the other kitchen refurb. They're going to take it and they're going to convert more people."

Notice the pattern → new AI capability + boring local niche + sales process that already exists = an app a $15K/job business will happily pay for.

Everyone on X uses Nano Banana to make demo videos for likes. Almost nobody drives 20 minutes to sell it to a business that closes five-figure jobs with it.

The demos get applause. The boring niche gets revenue.

The "AI Slop" Question

So were the haters right? Is this all slop?

Alex concedes half the point. AI slop is real: the auto-generated Twitter replies, the AI voiceover videos, content with zero human intent behind it. No argument.

But he draws a line I think more founders should steal: the models he's building on took billions of dollars of R&D. Plugging OpenAI or Nano Banana into an app might take 15 minutes, but the capability you just wired in is world class.

Calling it slop because it was built quickly? He doesn't buy it, and neither do I.

Speed of build says nothing about value delivered. A golf stats tracker he built in one day is something he now uses every round. His typing app rawtyping.com (it slowly deletes your text if you stop writing, which is both cruel and effective) got feedback from one user calling it "a wonderful mixture of stupid and genius."

Some of these apps are ugly. Most are tiny. But slop is a word for things nobody uses.

And a thousand people used the domain app. That's not slop. That's a concert hall full of people using a thing one guy built in his living room.

What I'd Steal From This Challenge

You don't need to ship 30 apps. I'm not going to either. But four things from this episode transfer directly to anyone bootstrapping a SaaS:

→ Deadlines beat motivation. "Shipped by midnight" produced more live products in a month than "when it's ready" produced in a year. Set a ship date measured in days, not months.

→ Ship in public or ship into the void. The 40,000 views and 500K impressions weren't vanity. They were his feedback loop: waitlists, comments, users showing up the next morning. Silence after a launch is also data. I've written a full playbook on how to build in public if you want the tactical version.

→ Volume reveals the winner. Nobody, including Alex, predicted the domain app would be the one. Your most exciting idea and your best idea are usually different ideas. The only way to find out is to ship several and watch what moves.

→ Solve your own problem first. The golf app, the typing app, the domain finder. All three started as "I want this to exist." If you have the problem, thousands of others do too.

The challenge also broke a mental barrier that has nothing to do with code. Every idea in his backlog is now a "ship it tomorrow" candidate instead of a someday project.

That shift alone is worth a month.

This was actually Alex's second appearance on the channel. If you want the origin story, when everyone was still calling the idea stupid, I covered the start of the 30 apps in 30 days challenge too. Reading both back to back is a nice before-and-after.

FAQ

What are AI slop apps?

"AI slop apps" is a dismissive label for apps built quickly with AI tools, implying they're low quality mass-produced junk. The criticism fits some of the output flooding app stores. But build speed and quality are separate things: Alex's one-day domain app served 1,000+ real users and 70,000+ searches, which is more traction than most apps built over six months ever get.

Did the 30 apps in 30 days challenge make money?

Not directly, as of the results episode. Alex is upfront that there was no revenue home run in his Stripe dashboard. The returns came as distribution (40,000+ YouTube views, 500K X impressions), 1,000+ users on his best app, and a boot camp (four apps in four weeks) launched off the back of the challenge with Starter Story. Monetization is his stated next phase.

How can one person build an app in a single day?

By keeping scope brutal and letting AI models do the heavy lifting. Alex builds around existing models (OpenAI's APIs, Google's Nano Banana for images), which take minutes to integrate, then spends his time on positioning the tool for a specific user. A golf tracker, a typing timer, a domain checker: each is one core feature shipped to production, not a platform.

Is shipping fast better than polishing one product?

Early on, yes. Shipping fast generates the feedback that tells you what deserves polish. Alex spent three months quietly polishing two previous projects and launched both to silence. Thirty fast ships surfaced one app with genuine product market fit. Polish is for after the market has voted, not before.

Want more real numbers from founders actually in the arena? That's the entire format of the Profitable Founder Podcast: bootstrapped SaaS founders opening their books, from $100K/yr to $10M/yr. Listen to the latest episode here.