10 Tiny Apps Making $30K to $1M a Month (Built With AI)
This video profiles ten tiny, mostly solo-built AI apps earning $30K to $1.4M a month — from Pieter Levels' 3-hour Cursor-built flight sim to Cal AI's photo calorie counter and Base44's $80M Wix exit — tagging each revenue number as press-verified or self-reported and distilling four repeatable app patterns plus the real moat: distribution.
Creative automation uses agents to accelerate production while keeping human taste in story, pacing, selection, and critique.
New playlist item from Hyperautomation Labs; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to pattern-match profitable micro-app opportunities — wrapper, niche tool, selfie loop, or fun object — and to start from an audience and distribution channel instead of from the code.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Brief
02Source
03Generation
04Selection
05Edit
06Taste Review
Deep lesson
Turn this video into working knowledge.
2,073 cleaned transcript words reviewed across 838 timed caption segments.
Thesis
10 Tiny Apps Making $30K to $1M a Month (Built With AI) teaches a practical creative automation move: This video profiles ten tiny, mostly solo-built AI apps earning $30K to $1.4M a month — from Pieter Levels' 3-hour Cursor-built flight sim to Cal AI's photo calorie counter and Base44's $80M Wix exit — tagging each revenue number as press-verified or self-reported and distilling four repeatable app patterns plus the real moat: distribution.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
1:09
Ship the fun object
“like CNBC or TechCrunch or self-reported by the founder. I'm not going to pretend a tweet is a code document. And here's the uncomfortable truth I'll prove by the end. The code in these apps is genuinely something...”
Pieter Levels built fly.pieter.com '100% with Cursor in about 3 hours' — a simple browser flight sim monetized by selling billboard ad space inside the game, pegged by 404 Media at around $50K/month with a claimed $1M annual run rate at peak; the mechanic is one genuinely fun, shareable thing with ads inside it. Open an AI coding tool and describe one tiny browser game in a single prompt, then ship whatever you get in an afternoon — the point is proving the code was never the hard part.
3:32
Creator-growth niche tools
“The founder, Cameron Drew, built a tool that helps people grow on LinkedIn, writing posts, tracking what works. He's open that AI code editors, and Claude Code specifically, were, in his words, his single biggest advantage, without a...”
Cameron Drew's Cleo (LinkedIn post-writing and tracking) went from zero to a self-reported $62K MRR in about 3 months, with Claude Code as 'his single biggest advantage'; the mechanic — pick one platform creators are desperate to grow on and solve its most painful growth task — also powers Blake Anderson's UMax, which scores selfies and sells the upgrade, claimed at ~$500K/month via TikTok virality. Pick one platform (LinkedIn, X, YouTube, or TikTok), write down the single most painful growth task its creators face, and sketch the one-feature tool you would charge monthly for.
10:19
Distribution is the moat
“ceiling. One-person AI tools, 6 months. The mechanic. Build the picks and shovels, tools that help other people build. Your blueprint. Once you've built a few apps, the most valuable thing you can build next is the tool...”
The closing lesson: since AI makes the code a weekend job, code is no longer the moat — Levels had hundreds of thousands of followers before typing a word, Anderson won by posting relentlessly on TikTok, and in every case the money came from an audience or channel, not app cleverness; the build stack is always describe-to-Cursor/Claude/Lovable plus Stripe. Before building anything, write one sentence naming exactly who your app is for and the specific channel where you will reach them first — then treat the app itself as the easy part.
01
Brief
Start with this video's job: This video profiles ten tiny, mostly solo-built AI apps earning $30K to $1.4M a month — from Pieter Levels' 3-hour Cursor-built flight sim to Cal AI's photo calorie counter and Base44's $80M Wix exit — tagging each revenue number as press-verified or self-reported and distilling four repeatable app patterns plus the real moat: distribution. Treat "Brief" as the outcome you are trying to make visible, not a topic label. Anchor it to 1:09, where the video says: “like CNBC or TechCrunch or self-reported by the founder. I'm not going to pretend a tweet is a code document. And here's the uncomfortable truth I'll prove by the end. The code in these apps is genuinely something...”
02
Source
Use "Source" to locate the part of the creative automation workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 3:32, where the video says: “The founder, Cameron Drew, built a tool that helps people grow on LinkedIn, writing posts, tracking what works. He's open that AI code editors, and Claude Code specifically, were, in his words, his single biggest advantage, without a...”
03
Generation
Turn "Generation" into the reusable artifact for this lesson: A creative workflow board with critique criteria and review checkpoints. This is where watching becomes something you can inspect and reuse.
04
Selection
Use "Selection" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Edit
Use "Edit" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Taste Review
Use "Taste Review" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a creative workflow board with critique criteria and review checkpoints..
Example
Claim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
Example
Teach-back module
Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
Letting the prompt drift into generic advice that could apply to any video in the playlist.
Copying the tool setup without identifying the operating principle that transfers to your own stack.
Skipping the artifact, which means the learning never becomes operational or inspectable.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: This video profiles ten tiny, mostly solo-built AI apps earning $30K to $1.4M a month — from Pieter Levels' 3-hour Cursor-built flight sim to Cal AI's photo calorie counter and Base44's $80M Wix exit — tagging each revenue number as press-verified or self-reported and distilling four repeatable app patterns plus the real moat: distribution.
02
Explain the practical stakes without hype: New playlist item from Hyperautomation Labs; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Brief -> Source -> Generation -> Selection -> Edit -> Taste Review sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A creative workflow board with critique criteria and review checkpoints.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: 10 Tiny Apps Making $30K to $1M a Month (Built With AI)
- URL: https://www.youtube.com/watch?v=zbAmmnMh5ew
- Topic: Creative Automation
- My current learning frame: Choose one of the four money patterns (wrapper, niche tool, selfie loop, fun object), pick an audience you already understand and the channel to reach them, then describe the app to an AI builder and ship a Stripe-connected v1 in a single weekend.
- Why this matters: New playlist item from Hyperautomation Labs; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 1:09 / Evidence 1: "like CNBC or TechCrunch or self-reported by the founder. I'm not going to pretend a tweet is a code document. And here's the uncomfortable truth I'll prove by the end. The code in these apps is genuinely something..."
- 3:32 / Evidence 2: "The founder, Cameron Drew, built a tool that helps people grow on LinkedIn, writing posts, tracking what works. He's open that AI code editors, and Claude Code specifically, were, in his words, his single biggest advantage, without a..."
- 6:09 / Evidence 3: "Safety, money, health. Describe the app to an AI builder and let it write the code. Number six. Formula Bot. The founder, David Bressler, built a tool that turns plain English into the right Excel or Google Sheets..."
- 7:45 / Evidence 4: "autopilot. Your blueprint. Look at expensive agency services, pick one repeatable piece, and build the AI tool that does it cheaper while the owner sleeps. Number eight, Cal AI. Now, I want to be honest. This one's founders..."
- 10:19 / Evidence 5: "ceiling. One-person AI tools, 6 months. The mechanic. Build the picks and shovels, tools that help other people build. Your blueprint. Once you've built a few apps, the most valuable thing you can build next is the tool..."
- 13:05 / Evidence 6: "I built you the full thing for free. Comment the word tiny, and I'll send you the tiny app blueprint. All 10 apps, the exact build stack, the four money patterns, and the copy-paste prompts to start your..."
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A creative workflow board with critique criteria and review checkpoints.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Brief -> Source -> Generation -> Selection -> Edit -> Taste Review
- 3 concrete examples that apply the video idea to real agentic work
- 2 failure modes the video helps prevent
- a checklist I can use the next time I run Codex or Claude
- one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "10 Tiny Apps Making $30K to $1M a Month (Built With AI)", not a generic Creative Automation essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
Creative AI removes the need for taste.
It increases the need for taste because output volume explodes.
The best prompt is enough.
References, critique, iteration, and post-production matter just as much.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a creative workflow board with critique criteria and review checkpoints..
A reusable artifact with a done signal and one verification step.03
Teach-back card
Explain the lesson to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
How did Pieter Levels build fly.pieter.com and how does it make money?
What mechanic did Cleo use to reach $62K MRR in about 3 months, and what tool did its founder credit?
What is the one lesson all ten founders got right that the video says almost nobody copies?
Source shelf
Use the video as a doorway, then verify with primary sources.
