Loading video...

Video Failed to Load

Go Home

20-YEAR-OLD GUY SHOWS HOW CLAUDE API CAN TURN 500-VIEW CONTENT INTO A $40K/MONTH CLIENT WORKFLOW Not from a big agency. Not from hiring writers. Just taking the same service people sell every week and wiring Claude API into the boring middle. A topic goes in. It pulls the research,...

19,254 views • 1 month ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

THIS DEVELOPER BOUGHT A $799 MAC MINI AND NOW RUNS 5 FACELESS YOUTUBE CHANNELS FOR $55/MONTH WITH CLAUDE AGENTS the trick is not buying a stronger computer. the trick is giving claude its own 24/7 machine, so it can take over the screen, click through tools, move files, write scripts and keep working while his main laptop stays untouched each channel runs from its own skill. documentary, luxury, gaming, deep sea and infrastructure all have different tones, seo formats and script rules. claude can turn one topic into a 1,600-2,000 word script, 8-10 visual prompts and 3 title options without a new brief every night the whole system costs $799 once and around $55 a month to operate. claude, elevenlabs, midjourney and electricity replace the manual loop most faceless creators get stuck in after month two. the mac mini itself stays online for about $3/month setup takes around 45 minutes. fresh macos install, 32gb ram, claude desktop, computer use permissions, google drive routing, connectors and one dedicated output folder. after that the machine becomes the place where the work happens most people try to scale youtube by adding more channels and more manual work. this flips the model. one box handles research, scripts, prompts, descriptions and scheduling while the human does one review session per week month 6 is where this starts getting dangerous. the channels that survive the first 90 days are not just posting videos anymore. they are running a tiny content factory from a box under the desk

Gipp 🦅

19,638 views • 1 month ago

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 views • 18 days ago

This Chinese developer runs 9 agents on Claude Code under a GPT-5.5 orchestrator and they close 500 client tasks a month without a single assistant. His client work is closed without him, on a single laptop and only three subscriptions. The entire system lives on one MacBook Pro M4 with 128 GB of memory and subscriptions to Claude Code and GPT-5.5 cost him approximately $300 a month. There is no CRM, no team, no office only a terminal window with 9 parallel streams. The orchestrator works with a simple system prompt: «You are the orchestrator of a client inbox. Classify every incoming email into 4 categories: code, content, analysis, communication. Delegate to the corresponding worker agent. When the result is ready, check it for completeness, send it to the client on my behalf, and mark the task as closed. Do not ask clarifying questions.» And the orchestrator checks the inbox every 30 seconds, classifies fresh emails, and distributes them to 9 worker agents on Claude Code, each of whom is responsible for their own class of tasks. Here is an example of how one of them closes a request to refactor a client's auth module: Task: refactor user-auth module Broke the monolith into 3 files by responsibilities Added unit tests, coverage increased to 87% Renamed 4 functions to camelCase according to the style guide PR is ready for review, link below» And so about 50 cycles a day. By noon 25 tasks are closed, by dinner 50, and by the end of the month 500. On average, it takes about 7 minutes from the appearance of an email in the inbox to sending the result to the client. This is more than what a live team of 6 developers, copywriters and analysts working 8 hours a day closes. This is no longer an agency. This is a workstation where an orchestrator replaces a manager, and 9 worker agents replace the staff. The pipeline goes from inbox to closing 500 times a month without human participation at any step.

Blaze

29,917 views • 2 months ago