A few years back, McKinsey dropped a report that still stings: 60% of your workday isn't actually work. Meetings, emails, status updates. That's not the deep, satisfying problem-solving we signed up for. I looked at that number and refused to accept it. Last month, I shipped forty-seven videos across four channels. One person. And I'm going to show you exactly how I did it.
Just two years back, that kind of output would've demanded a team of eight and a budget neither you nor I have. Today, it costs me about three hundred bucks a month in infrastructure. But the real story isn't the tools. It's the one specific mistake I made that cost me three months of my life. We'll circle back to that. This isn't just another tools list. Every YouTuber has a tools list. This is the actual, end-to-end workflow you can steal. What I use, how I chain them, and precisely where your biggest productivity multiplier hides.
Research: Stop Using AI Like a Search Engine
Everything starts with research. And if you're like most people, you're getting this spectacularly wrong from the jump. You open ChatGPT, type a question, and call it a day. That's using AI like a glorified search engine. You're leaving ninety percent of its actual value on the table.
My research stack has two critical layers. Layer one: Gemini with Google Search grounding. And let me be clear, I'm not talking about Gemini chat. I'm talking about the Gemini API with grounding explicitly turned on. This isn't some black box. It actively searches the live web and, crucially, returns citations you can actually verify. Transparency matters.
Layer two: Claude for synthesis. You take those grounded, verifiable facts from Gemini and feed them to Claude with a very specific prompt. Don't just say "summarize this." Say, "Analyze this data and find the three insights that contradict conventional wisdom." That's where your interesting content lives. That's where you find the gold.
The combination isn't just convenient; it's essential. Gemini grounds you in reality. Claude elevates you to insight. There's a synergy here that most teams completely miss. One without the other gives you either a Wikipedia summary or a hallucinated essay. Together, they give you research you can trust and ideas worth sharing.
I once sat across from a colleague, Raj, a product manager who was absolutely drowning in competitive research. He was clocking twenty hours a week on it. I showed him this two-layer approach. He cut it to three hours. He looked at me, bewildered, and said, "I've been doing this job for six years and I never once questioned the process." Don't be Raj. Question the process.
Writing: AI Doesn't Write, It Thinks
Writing is where most AI workflows fall apart. People paste a topic into an LLM and publish whatever garbage comes back. You can spot AI-written content from orbit. It hedges. It uses the same tired transitions. It sounds like a press release wrote a term paper. It's an instant credibility killer, especially on a platform like dev.to.
Here's the thing: I do not use AI to write. I use AI to think. There's a massive difference. If you take one single insight from this post, let it be this.
My video scripts aren't generated. They're not prompted once and done. They're written interactively in Claude Code. I argue with the AI. I push back. I rewrite its rewrites. You should be doing the same. It's a dialogue, a collaborative sparring match, not a one-way command.
The result? Scripts that consistently score ninety-plus on our internal humanize metrics across five domains: AI fingerprint detection, viewer engagement, rhythm variation, story architecture, and hook quality. Every script gets scored before it enters the pipeline. If it fails, it doesn't ship. Period.
The key insight most people miss: AI is not a replacement for taste. It is an amplifier. If you have nothing to say, AI will help you say nothing faster, and with more conviction. If you have a unique perspective, a strong opinion, or a nuanced insight, AI will help you articulate it at ten times the speed. That changes everything. It turns your brain into a supercomputer.
Code & Automation: My Digital Production Line
For code, I live in Claude Code. Again, not the chat interface. I'm talking about the command-line tool that can read your entire codebase, run commands, write new files, and commit code. It is, hands down, the single biggest productivity shift I've experienced since moving from jQuery to React. That's not hyperbole.
I built my entire video production pipeline using it. Ten distinct steps. Six different AI services. Script generation, image creation, text-to-speech, video assembly, subtitle burning, YouTube upload. All automated. All triggered from one command. It's a digital production line for content.
Claude Code doesn't just write code for you. It debugs it. I had eleven production bugs in my pipeline after a single session of rapid development. Claude found every root cause, wrote the fix, and committed it. Eleven bugs. One afternoon. If you've ever spent a sprint on bug triage, you know exactly what kind of superpower that is.
For frontend work, I still reach for Cursor. If you write React, you'll love it. The tab completion alone saves you hours per week, it's that good. But for backend Python, for infrastructure as code, and for pipeline orchestration, Claude Code has no equal right now. It's a game-changer for anyone managing complex systems.
The Multiplier: One Script, Twelve Deliverables
Here's where it really gets interesting. Most people stop when the "writing" is done. But the real multiplication starts after the script is final. My pipeline then generates five vertical shorts. It pulls YouTube metadata. It creates SEO tags. It adds timestamps. And yes, it generates this dev.to blog post.
One script. Twelve distinct deliverables. And you can absolutely replicate this.
The images for the videos and posts? They come from Imagen 3 on Vertex AI. The voice? Google Cloud Text-to-Speech, using a custom-cloned voice that sounds exactly like me. Video assembly? FFmpeg, dynamically generating Ken Burns-style animations. Subtitles? Word-by-word synced, straight from Whisper.
And this blog post? It's not some lazy transcript dump. It's rewritten from the ground up, in a developer's voice, by Claude Opus. First person. Opinionated. Technically precise. The kind of post that gets engagement because it reads like a human wrote it. Because a human directed it. You could do this for your newsletter, for internal documentation, for anything where voice and consistency matter.
The Hard Numbers & The Three-Month Mistake
Let me show you the actual numbers, because that's where the rubber meets the road.
Before AI, producing one video took me about twelve hours. That's research, writing, recording, editing, thumbnails, metadata, the whole shebang. Now? The total human time per video is about ninety minutes. The pipeline handles the other ten and a half hours. That's a staggering efficiency gain.
What does this cost?
- Claude API: Roughly forty dollars a month.
- Gemini and Imagen on Vertex: Around sixty.
- Google Cloud Text-to-Speech: About thirty.
- Total AI infrastructure across all four channels: Roughly three hundred dollars a month.
A single video editor costs more than that per day.
But here's the real question, the one that matters more than hours saved or dollars saved: What about your output? I went from publishing one video every two weeks to publishing twelve per week across four channels. That's a twenty-four X increase in output. Not ten X. Twenty-four.
Remember the three-month mistake I mentioned at the top? Here it is. I wasted three months trying to automate taste. I thought if I built a good enough prompt, the AI would just write scripts that sounded human, that had my voice, that captured nuance.
It didn't work. Not once. Gemini Flash scripts consistently scored forty out of a hundred on our metrics. Every single time. They were bland. Generic. Uninspired.
The fix was counterintuitive. Stop trying to automate the creative part. Stop trying to delegate judgment. Automate everything else. I write scripts manually, interactively, in Claude Code Opus. With judgment. With taste. Then the pipeline handles the other ninety percent – the research synthesis, the image generation, the video assembly, the publishing logistics – all the stuff that doesn't require taste.
The other mistake was tool hopping. I tried seventeen different AI tools in the first two months. Most of them did the same damn thing with different branding, different UIs, and different ways to frustrate me. The real productivity gains didn't come from dabbling. They came from going deep with three core tools, not shallow with seventeen.
Key Takeaways
- Don't use AI like a search engine. Grounded research (Gemini API) combined with insightful synthesis (Claude) is key. You need reality and elevation.
- AI amplifies your taste, it doesn't replace it. If you have nothing interesting to say, AI makes you boring faster. If you have a perspective, AI makes you articulate it at 10x speed.
- Interact with AI for creative tasks. Don't prompt and publish. Argue, refine, push back. Treat it like a co-pilot, not an intern.
- Claude Code is a game-changer for automation. For backend, infrastructure, and pipeline work, its ability to read, write, and commit code is unparalleled.
- Automate around taste, not taste itself. Focus your human judgment on the core creative output, and let AI handle the repetitive, non-judgmental tasks.
- Go deep, not wide, with tools. Master a few powerful tools that truly integrate into your workflow, rather than dabbling in dozens of similar ones.
- Shift your mental model. Stop asking "How do I do this?" Start asking "How do I build a system that does this for me, repeatedly?" That mental shift is worth more than any tool subscription.
Four channels. Forty-seven videos. Three hundred dollars. One person. The tools exist. The workflows exist. The question isn't whether AI can multiply your output. It already can, dramatically. The question is what you would build if your capacity was no longer the bottleneck.
Watch the full video breakdown on YouTube: How I Use AI to Do 10x the Work (My Complete Workflow)
The Machine Pulse covers the technology that's rewriting the rules — how AI actually works under the hood, what's hype vs. what's real, and what it means for your career and your future.
Follow @themachinepulse for weekly deep dives into AI, emerging tech, and the future of work.
Top comments (0)