By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
The Calum Johnson ShowI Made $20K In 7 Days: The Fastest Way To Use AI Agents To Make Money & Be More Productive (No Code)
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
Great conversations run long. Their best ideas don't have to.
uListen is free on iPhone, iPad, Android, Chrome, and Claude.
See howCHAPTERS
Jump to publisher timestampsChapter summaries
Why Claude Code feels like “magic”: building and earning quickly without a dev team
Oliur opens by describing how easy Claude Code felt to use and how it enabled him to build a membership platform over a weekend. He frames the experience as replacing expensive development with fast solo-building, which surprised him with immediate revenue.
- •Claude Code is presented as simple to use even without months of experience
- •Oliur says he built digitalcreatorclub.com in a weekend
- •He contrasts this with the high cost of hiring developers to build similar products
- •He describes the first week’s sales as roughly $20,000 and calls the experience “magic”
From skepticism to excitement: what changed about AI for building online
Calum asks about Oliur’s shift from being anti-AI to being excited. Oliur explains the change as a collapse in the cost and friction of building apps and websites, making solo creation far more viable.
- •Calum highlights Oliur’s earlier skepticism about AI being hype
- •Oliur identifies Claude Code as the key tool that changed his view
- •He says building online used to be extremely expensive and developer-dependent
- •He argues the gap has narrowed enough that a solo builder can create near-professional results
Career leverage for nine-to-five workers: compressing time and looking better at work
The conversation shifts to what Claude Code (and related tools) can do for people with standard jobs. Oliur describes how live demonstrations help people understand time savings and how AI can compress work when used correctly.
- •Calum asks how Claude Code could impact someone in a nine-to-five
- •Oliur says people only “get it” after seeing a live demonstration
- •He emphasizes saving time and improving perceived performance at work
- •He frames AI as a way to compact both time and workload
The two moments that proved it: one-prompt website and building a full membership platform
Oliur shares two turning points that made Claude Code feel real rather than hype. First, a one-prompt portfolio/gallery site from a folder of photos; second, building a paid membership platform with logic, payments, and integrations despite limited backend experience.
- •Oliur describes prompting Claude Code to build a gallery website from local photos
- •He says it took minutes instead of days even with his basic coding background
- •He later built a membership site with payments, database needs, pricing logic, email invites, and Discord access
- •He says these experiences made him feel the main constraint became imagination
Digital Creators Club business model: pricing, member quality, and early revenue
Calum asks Oliur to unpack the first-week sales and how the club evolved. Oliur explains it began as an experiment driven by audience requests, and that charging (instead of free access) improved member quality and exceeded his expectations.
- •Oliur says the club started as an experiment based on audience demand for a community space
- •He shares advice he received: don’t make it free, because pricing affects member quality
- •He describes the club as attracting creators, businesspeople, investors, and generally higher-quality members
- •He estimates total revenue so far at roughly $40,000–$50,000 with minimal advertising
Scaling beyond selling time: how AI tools mirror “big company” leverage
After a sponsor break, Oliur connects AI tools to scalability—doing work not tied to hours. He describes AI agents as an always-on workforce and ties this to lessons about wealth creation and scalable impact.
- •Oliur links AI tools to scalable work not tied to personal time
- •He describes AI agents as an “army” working 24/7
- •He compares agent-enabled output to companies operating at massive scale
- •He argues people can cover tasks once requiring large teams by implementing agents
The hard-work myth and Oliur’s pivot: from client work to digital products
Calum asks for a vivid moment when Oliur learned that hard work doesn’t automatically lead to wealth. Oliur points to client work being capped by daily rates and time, then describes a breakthrough month earning $30,000 from Tumblr templates, which pushed him toward scalable products.
- •Oliur describes client work limits: income capped by day rates and time commitment
- •He says selling time reduced freedom due to calls and fixed obligations
- •He recounts earning $30,000 in a month from Tumblr templates during the Tumblr era
- •He explains this made him prioritize scalable outputs like digital products, YouTube, and building online
Seeing the product: walkthrough of the Digital Creators Club site built by Claude
Oliur shares his screen and gives a tour of Digital Creators Club’s public and logged-in views. He emphasizes that Claude generated the code and even some of the text, while he guided changes using natural language as an “orchestrator.”
- •Oliur shows the public homepage with pricing and testimonial elements
- •He describes the logged-in content area with manuals and resources
- •He shows the account page including Discord connection, membership card, and billing management
- •He stresses he didn’t hand-code it; he iterated via simple edit requests in natural language
Beginner-friendly mindset: how fast someone can start building and learning terminology
Calum asks how experienced Oliur was before building the platform. Oliur insists people can start from zero, learn by asking questions when stuck, and gradually pick up concepts like databases and APIs through usage.
- •Oliur says someone could start and build within a week
- •He calls himself a beginner and believes beginners can teach other beginners
- •He emphasizes asking the tool to explain concepts when you get stuck
- •He says repeated use builds familiarity with technical terms and systems over time
Workplace automation example: generating post-campaign reports from video performance data
Oliur gives a concrete job-relevant workflow: assembling a performance report for sponsored YouTube campaigns. He describes having Claude Code gather metrics and generate a PDF report, replacing work that used to be time-consuming and sometimes handled by agencies.
- •Oliur describes asking Claude Code to collect views, engagement, comments, likes, and thumbnail details
- •He uses the output to produce a PDF report for a client
- •He says this replaces a labor-heavy process of gathering data and designing a report
- •Calum highlights that data-heavy workflows are strong candidates for automation
Live Claude Code demo: setting up a local project in the Claude app (not the terminal)
They begin a live build, focusing on reducing intimidation and using the Claude desktop app’s Code tab. Oliur explains choosing a local folder, the app’s permission model, and why he discourages beginners from using the terminal.
- •Oliur starts a new session and selects a local folder for the project
- •He recommends the Claude app’s Code tab instead of terminal usage for most people
- •He notes the app asks for permissions and limits actions to the chosen folder
- •He explains Claude is designed to reduce risk around unintended file changes
Building a minimalist to-do app with a concise prompt and quick iteration
Calum suggests a Monday-morning prioritization dashboard; Oliur simplifies it to a to-do list app for speed. Oliur explains how he thinks about prompting: include specific behaviors you care about, and expect to refine rather than “one-shot.”
- •They decide to build a simple to-do list with check-off behavior that moves completed items to the bottom
- •Oliur discusses prompting strategy: specify key behaviors, refine later, don’t expect one perfect prompt
- •Claude Code requests permissions to write into the project folder
- •They preview and open the generated HTML locally in a browser
Adding visual polish: prompting an “Apple-style” aesthetic and using references/brand guidelines
After confirming the to-do app works, Calum asks for a more design-forward demonstration. Oliur prompts Claude Code to restyle the app, then explains how providing brand colors, fonts, data, and even website links can help the model match a desired look.
- •Oliur asks Claude Code to apply an “Apple style” aesthetic with colors, backgrounds, and card UI
- •He explains you can provide brand guidelines like fonts, colors, and sizes as hard data
- •He notes it can pull styling from links to existing websites to apply similar CSS
- •The updated UI resembles a Reminders-style interface and even changes labels accordingly
Common pitfalls and troubleshooting: using screenshots, errors, and persistence
Calum asks what can derail someone’s first experience. Oliur says things won’t work every time, and the key is learning basic troubleshooting—capturing errors, providing screenshots/logs, and asking Claude Code to fix issues rather than getting demoralized.
- •Oliur notes Claude Code sometimes produces results that break or don’t work as expected
- •He describes capturing visible errors or relevant information and feeding it back in
- •He recommends using screenshots, logs, and error messages to guide fixes
- •He emphasizes persistence as the antidote to the “demoralizing” moment when something fails
Connecting apps and data: using connectors, and when to use Cowork vs Code vs chat
Oliur shows where connectors live and describes linking external services to Claude for deeper workflows. He clarifies that scheduled, recurring tasks are better suited to Claude Cowork, and explains how he personally divides tasks across Claude chat, Cowork, and Claude Code.
- •Oliur shows the Connectors section and lists examples of connected services (e.g., ClickUp, GitHub, Google Calendar, PayPal)
- •He explains connectors let Claude pull and act on information across tools within a session’s context
- •He says recurring scheduled tasks are better handled by Claude Cowork rather than Claude Code
- •He outlines his usage: chat for questions, Cowork for tasks like file sorting, and Code for building apps/websites
What to build first: personal website momentum and the value of an online hub
To close, Calum asks what someone should do immediately after watching. Oliur recommends building a simple personal website first to build momentum, then using Claude Code to prototype business ideas; they discuss personal websites as public resumes and long-term credibility hubs.
- •Oliur recommends building a personal website as the easiest first project to gain confidence
- •He suggests iterating with fonts, colors, and adding a profile image to personalize it
- •Calum reflects on the value of a website as a hub for products and career footprint
- •Oliur describes personal sites as public resumes, archives, and credibility signals that help others understand who you are
Publisher timestamps
- 0:00Intro
- 9:41How Claude Code made me $20k in 7 days
- 21:24How I made $30k in a month selling Wallpapers
- 25:34How Claude Code can save you time at your jobRead this chapter
- 30:08[LIVE CLAUDE CODE DEMO STARTS]
- 46:48How to connect your favorite apps to Claude Code
- 48:23How to automate your weekly tasksRead this chapter
- 52:29The first thing you should build with Claude CodeRead this chapter
