How a marketer trying to automate ad creation accidentally built an entire AI-powered agency in 10 days — using nothing but a terminal and Claude Code.
On March 24, I opened a terminal and typed claude for the first time. I wasn't trying to start a company. I wasn't building a platform. I was a marketer at my day job trying to solve one small problem: I needed to make more ads, faster.
I figured if I could get AI to generate image ads from product photos, I could test more creatives and scale what was working. That was the whole idea. A little script to save me time.
But one script turned into two. The ad generator needed a brand config. The brand config needed compliance rules. The compliance rules needed a copy engine. The copy engine needed real marketing methodology. And before I knew it, I wasn't automating a task anymore — I was building the operating system for a marketing agency.
This journal is a record of how that happened. Day by day, prompt by prompt. Not to show off — but because I think there's something powerful about what happens when you just start building. You don't need a business plan. You don't need funding. You don't even need to know where it's going. You just need to start solving the problem in front of you and let it pull you forward.
Every build below was created using Claude Code — Anthropic's CLI tool that lets you talk to Claude directly in your terminal. No IDE plugins, no copy-paste. You describe what you want, and Claude writes the code, creates the files, runs the commands, and deploys it.
Each card shows what was built, why it matters, a sample prompt, and where possible a real example of the output. Click any card to expand. Click any image to enlarge it.
The tool is claude in your terminal. That's it. Everything on this page was built that way.
This was the seed. It wasn't sophisticated — but it worked. And once you realize you can generate ads in seconds instead of hours, you immediately start thinking: "What else can I automate?"
This was the first sign the project was growing beyond "a script." I didn't plan to build photo intelligence — but the generator needed it, so I built it. That pattern would repeat every day for the next week.
product shot → brand config
sku catalog
This was the accidental architecture moment. I didn't set out to build a "brand engine" — I just didn't want to update the same product name in 5 different files. But once the config existed, every new tool could plug into it. One change propagates everywhere.
I realized the generators were only as good as the thinking behind them. If I wanted the copy engine to write like a top media buyer, it needed to learn from top media buyers.
This was the moment the project changed trajectory. Once I had real practitioner methodology in searchable markdown, I realized: this isn't just for my ads. This is the foundation for an entire agency's knowledge base. The scope started expanding.
That evening at Friday dinner, a family friend who's a developer asked what I'd been working on. I showed him Claude Code on the desktop app and he said: "Why aren't you using the terminal? You can run multiple sessions at once."
My mind broke a little. Up until that moment, I'd been seriously thinking about borrowing my mom's laptop just to get a second Claude Code window running. I didn't know you could open multiple terminal tabs and run Claude in each one.
Then he mentioned how he keeps hitting rate limits on the $100 Pro subscription. I was confused — we're on the same plan and I wasn't getting anywhere close to those numbers. That's when I realized how much faster he was working by running parallel sessions. He was getting 3x the output I was because he'd have Claude building one thing while he prompted another.
I went home that night, opened three terminal windows, and everything changed. My output roughly tripled overnight. The next four days — the marathon stretch where the real agency got built — wouldn't have been possible without that one conversation over dinner.
Total transcription cost for all 248 videos: ~$7.20 via Whisper API. Less than a coffee for an entire agency's knowledge base.
v4 · ugc raw · 9:16
v4 · editorial · 4:5
v4 · close-up macro
v10 · composited
8 visual styles × 16 scenes × 6 colors × 5 lighting moods = 3,840 unique combinations per SKU per avatar. Creative testing at a scale no human team can match.
Went from zero to launch-ready for a completely different niche in a single session. That's the power of the brand engine — plug in new configs, get a fully operational brand.
Image-to-video always beats text-to-video for ads. The orchestrator knows this and automatically chains the optimal sequence. Clients just describe what they want — the system figures out how.
/eval/ (free scan, shareable) → /discover/ (7-step brand questionnaire) → onboarding → book a call. Top of funnel is completely self-serve and viral.
demo gallery · v9 no-text
demo gallery · scene photo
advertorial · hero image
248 transcripts from 15+ practitioners, synthesized into searchable methodology
56 production docs: playbooks, SOPs, templates, legal — the operating system
10+ generators, deployment CLI, transcriber, brand engine, video engine
FastAPI + Next.js + Supabase. 30 endpoints, 11 tables, full auth + onboarding
Multiple brands onboarded — each with full config, generators, and launch assets
Marketing site, demos, pitch deck, eval tool, internal hub — all live